-
Story
-
Resolution: Unresolved
-
Critical
-
None
-
0.42
-
False
-
-
False
-
None
-
No
-
---
-
---
-
There are a lot of failures at the 4.14 periodic lane where the hosted cluster health check test is failing, checking that looks like one of the VM is not starting up propertly and guest agent is not reporting an ip
NAME AGE PHASE IP NODENAME READY 6eab8052c7af3bde60cd-efd39dd6-5d5rv 52m Running 10.129.0.174 master-1 True 6eab8052c7af3bde60cd-efd39dd6-mj28s 52m Running master-0 True
One of the possible causes could be the VM not being able to access ignition server somehow.
Jobs:
- https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-hypershift-release-4.14-periodics-e2e-kubevirt-metal-mce/1781533432497573888
- https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-hypershift-release-4.14-periodics-e2e-kubevirt-metal-mce/1781171079717326848
- https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-hypershift-release-4.14-periodics-e2e-kubevirt-metal-mce/1780084009905164288