REQ: Add post mortem logs in case cluster-up failed #1329
Labels
kind/enhancement
sig/ci
Denotes an issue or PR as being related to sig-ci, marks changes to the CI system.
Is your feature request related to a problem? Please describe:
Upon Kubevirtci cluster-up failures we don't have logs, such as kubectl pods, logs, describe etc
example https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/13282/pull-kubevirt-e2e-k8s-1.30-ipv6-sig-network/1859255594477686784
Describe the solution you'd like:
Would be good to have collected artifacts on CI in case the cluster-up itself failed.
We need for example the following commands:
kubectl get pods -A
for each pod, we need please the
kubectl describe
, and thelogs
(for each of its containers)Or whatever crucial info that we find beside that on the fly.
Describe alternatives you've considered:
Additional context:
Note that we do have some logs collecting as far as i remember, need to adapt / see if something miss.
(they are mostly about the docker BM containers, not the pods)
The text was updated successfully, but these errors were encountered: