[enhancement] verify the runner baseline after provisioning

Aperta
#955 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 4 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go, linux

Direzione di ricerca

Start with the provisioning flow in the Go code, where a host is reported ready, and see where a final verification step could hook in. The checks touch /etc/fstab, /etc/containers/containers.conf, the runner dns key and the executor containers.conf, so read how the provisioner writes each of them first. Done means a mapt verify command that exits non-zero and names the failing item on a broken host, and prints one line per check on a healthy one.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement provider/IBMCLOUD
Problem

Failures of this kind are silent. mapt reported the instance ready while every CI job failed, and the cause was in the host configuration, not in the job: the DNS order a job container reads, the proxy variables, the data volume and its SELinux type, and the storage path that /etc/fstab produces after a reboot.

Each of these takes seconds to check on the finished host. Nothing checks them now, so the next rebuild repeats the same defect, and the operator finds it from a failed pipeline.

Proposal

Run a verification step at the end of provisioning, and expose it as a command the user can run later (mapt verify ..., or a script left on the host). It asserts at least:

  • the runner service is active and enabled;
  • every DNS source a job container reads lists the internal resolvers before any public one (the runner dns key, /etc/containers/containers.conf, and the executor containers.conf);
  • container storage sits on the data volume, not on the root disk, and carries the expected SELinux type;
  • the /etc/fstab entry for the data volume produces the same container storage path after a reboot as it does now. A wrong mount point passes findmnt --verify and orphans the image store at the next boot;
  • the data volume mount helper contains no mkfs;
  • the container MTU matches the underlay;
  • the proxy variables are present when they were requested, in both cases and with no CIDR in no_proxy;
  • one job-style container starts, resolves a name, and writes to the cache volume.

Exit non-zero with a short report. provision should fail, not warn, when a check fails.

Acceptance
  • A provisioning run on a host with one broken item (for example a wrong fstab target) exits non-zero and names the item.
  • A healthy host exits zero and prints one line per check.
Lingua principale
Go
Stelle
25
Fork
41
Merge medio
5g 3h
PR unite (30g)
16

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di redhat-developer/mapt

Tutte le issue di redhat-developer/mapt

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.