Job:
periodic-ci-openshift-release-master-nightly-4.13-e2e-metal-ipi-upgrade-ovn-ipv6 (all) - 23 runs, 43% failed, 30% of failures match = 13% impact
#1783090262524825600junit6 days ago
# operator conditions machine-config
Operator degraded (RequiredPoolsFailed): Unable to apply 4.13.0-0.nightly-2024-04-24-110322: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, error pool master is not ready, retrying. Status: (pool degraded: true total: 3, ready 0, updated: 0, unavailable: 1)]
#1783090262524825600junit6 days ago
Apr 24 13:07:17.956 E ns/openshift-multus pod/multus-admission-controller-6b6d596d84-6wbv5 node/master-1.ostest.test.metalkube.org uid/7b0820ef-e853-488c-bfc2-587461f31e83 container/multus-admission-controller reason/ContainerExit code/137 cause/Error
Apr 24 13:16:53.655 - 7238s E clusteroperator/machine-config condition/Degraded status/True reason/Unable to apply 4.13.0-0.nightly-2024-04-24-110322: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, error pool master is not ready, retrying. Status: (pool degraded: true total: 3, ready 0, updated: 0, unavailable: 1)]
Apr 24 13:16:53.655 E clusteroperator/machine-config condition/Degraded status/True reason/RequiredPoolsFailed changed: Unable to apply 4.13.0-0.nightly-2024-04-24-110322: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, error pool master is not ready, retrying. Status: (pool degraded: true total: 3, ready 0, updated: 0, unavailable: 1)]
Apr 24 13:36:42.826 - 6049s E clusteroperator/openshift-apiserver condition/Degraded status/True reason/APIServerDeploymentDegraded: 1 of 3 requested instances are unavailable for apiserver.openshift-apiserver ()
#1783090262524825600junit6 days ago
Apr 24 13:16:53.655 - 7238s E clusteroperator/machine-config condition/Degraded status/True reason/Unable to apply 4.13.0-0.nightly-2024-04-24-110322: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, error pool master is not ready, retrying. Status: (pool degraded: true total: 3, ready 0, updated: 0, unavailable: 1)]
1 tests failed during this blip (2024-04-24 13:16:53.655011448 +0000 UTC to 2024-04-24 13:16:53.655011448 +0000 UTC): [sig-arch][Feature:ClusterUpgrade] Cluster should remain functional during upgrade [Disruptive]
#1780962740488114176junit12 days ago
# operator conditions machine-config
Operator degraded (RequiredPoolsFailed): Unable to apply 4.13.0-0.nightly-2024-04-18-140931: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, error pool master is not ready, retrying. Status: (pool degraded: true total: 3, ready 0, updated: 0, unavailable: 1)]
#1780712390145347584junit12 days ago
# operator conditions machine-config
Operator degraded (RequiredPoolsFailed): Unable to apply 4.13.0-0.nightly-2024-04-17-213443: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, error pool master is not ready, retrying. Status: (pool degraded: true total: 3, ready 0, updated: 0, unavailable: 1)]
#1780712390145347584junit12 days ago
Apr 17 23:53:34.595 E ns/openshift-multus pod/multus-admission-controller-7c79bf4cb-rcxfx node/master-1.ostest.test.metalkube.org uid/8b3fcf79-d1e5-4c13-ae31-0a6dfd2dd4b9 container/multus-admission-controller reason/ContainerExit code/137 cause/Error
Apr 18 00:02:30.255 - 6399s E clusteroperator/machine-config condition/Degraded status/True reason/Unable to apply 4.13.0-0.nightly-2024-04-17-213443: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, error pool master is not ready, retrying. Status: (pool degraded: true total: 3, ready 0, updated: 0, unavailable: 1)]
Apr 18 00:02:30.255 E clusteroperator/machine-config condition/Degraded status/True reason/RequiredPoolsFailed changed: Unable to apply 4.13.0-0.nightly-2024-04-17-213443: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, error pool master is not ready, retrying. Status: (pool degraded: true total: 3, ready 0, updated: 0, unavailable: 1)]
Apr 18 00:14:52.490 E clusterversion/version changed Failing to True: ClusterOperatorDegraded: Cluster operator machine-config is degraded
#1780712390145347584junit12 days ago
Apr 18 00:02:30.255 - 6399s E clusteroperator/machine-config condition/Degraded status/True reason/Unable to apply 4.13.0-0.nightly-2024-04-17-213443: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, error pool master is not ready, retrying. Status: (pool degraded: true total: 3, ready 0, updated: 0, unavailable: 1)]
1 tests failed during this blip (2024-04-18 00:02:30.255683617 +0000 UTC to 2024-04-18 00:02:30.255683617 +0000 UTC): [sig-arch][Feature:ClusterUpgrade] Cluster should remain functional during upgrade [Disruptive]

Found in 13.04% of runs (30.00% of failures) across 23 total runs and 1 jobs (43.48% failed) in 396ms - clear search | chart view - source code located on github