mirror of
https://github.com/cozystack/cozystack.git
synced 2026-11-04 11:07:03 +09:00
Ivan Okhotnikov
11c025b0fc
Sections (a) and (c) of the existing node-join failure diagnostic pin down WHERE the worker stalled (VMI/DV provisioning versus tenant kubelet CSR). They cannot answer WHY the second Machine was created minutes after the first became Ready, which is the pattern observed in recent tenant-latest / tenant-previous flakes: a 5- to 10-minute gap between Machine №1 Ready and MachineSet.ScalingUp to 2. That gap is only legible in the CAPI controller-manager reconcile timeline. Add section (d) that dumps the last 15m of controller-manager output across cozy-cluster-api (capi-manager, capk-manager, capi-kamaji-controller-manager, capi-kubeadm-bootstrap-manager, cabpt-manager), cozy-kamaji, cozy-kubevirt-cdi, and cozy-linstor, with timestamps and all sidecar containers included. Guarded with \`|| true\` end-to-end so a dead pod never masks the real \`exit 1\`. Diagnostics-only change: the happy path is untouched and never runs these commands. Signed-off-by: Ivan Okhotnikov <ivan.okhotnikov@aenix.io>