May 16 20:59:00.823 E ns/openshift-cloud-credential-operator pod/pod-identity-webhook-66d56469f6-hc8rf node/ip-10-0-203-49.us-west-1.compute.internal uid/e9046b06-66be-47eb-9438-00be64ee58fe container/pod-identity-webhook reason/ContainerExit code/137 cause/Error
May 16 21:01:45.680 E clusteroperator/machine-config condition/Degraded status/True reason/RequiredPoolsFailed changed: Unable to apply 4.13.0-0.nightly-2024-05-16-191307: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, pool master has not progressed to latest configuration: controller version mismatch for rendered-master-d818c99c443c48c56a024b1e9be195b9 expected 2d7a09cc9acd5ffd96ef777a1bd2c348cd49a0c9 has 33a010772d604aff2cb625d04a9469a47f53c96e: 2 (ready 2) out of 3 nodes are updating to latest configuration rendered-master-8a2e736606e73ba9c4eba3a81e033958, retrying]
May 16 21:01:45.680 - 222s  E clusteroperator/machine-config condition/Degraded status/True reason/Unable to apply 4.13.0-0.nightly-2024-05-16-191307: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, pool master has not progressed to latest configuration: controller version mismatch for rendered-master-d818c99c443c48c56a024b1e9be195b9 expected 2d7a09cc9acd5ffd96ef777a1bd2c348cd49a0c9 has 33a010772d604aff2cb625d04a9469a47f53c96e: 2 (ready 2) out of 3 nodes are updating to latest configuration rendered-master-8a2e736606e73ba9c4eba3a81e033958, retrying]

... 1 lines not shown

May 16 15:00:00.436 E ns/openshift-monitoring pod/alertmanager-main-1 node/ip-10-0-253-234.us-west-2.compute.internal uid/096af163-ea58-4b89-b071-5097606397ed container/alertmanager reason/TerminationStateCleared lastState.terminated was cleared on a pod (bug https://bugzilla.redhat.com/show_bug.cgi?id=1933760 or similar)
May 16 15:00:06.332 E clusteroperator/machine-config condition/Degraded status/True reason/RequiredPoolsFailed changed: Unable to apply 4.13.0-0.nightly-2024-05-16-131307: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, pool master has not progressed to latest configuration: controller version mismatch for rendered-master-738e3aa33ae10b545ee3d25e62e1add9 expected 2d7a09cc9acd5ffd96ef777a1bd2c348cd49a0c9 has 33a010772d604aff2cb625d04a9469a47f53c96e: 1 (ready 1) out of 3 nodes are updating to latest configuration rendered-master-9b56af24c4368bf1a37158ae5eabd500, retrying]
May 16 15:00:06.332 - 725s  E clusteroperator/machine-config condition/Degraded status/True reason/Unable to apply 4.13.0-0.nightly-2024-05-16-131307: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, pool master has not progressed to latest configuration: controller version mismatch for rendered-master-738e3aa33ae10b545ee3d25e62e1add9 expected 2d7a09cc9acd5ffd96ef777a1bd2c348cd49a0c9 has 33a010772d604aff2cb625d04a9469a47f53c96e: 1 (ready 1) out of 3 nodes are updating to latest configuration rendered-master-9b56af24c4368bf1a37158ae5eabd500, retrying]

... 1 lines not shown

May 15 12:31:41.986 E ns/openshift-monitoring pod/alertmanager-main-1 node/ip-10-0-182-230.us-west-1.compute.internal uid/c34f531c-590d-4ad7-aa1e-d735a1f3c7c8 container/alertmanager reason/TerminationStateCleared lastState.terminated was cleared on a pod (bug https://bugzilla.redhat.com/show_bug.cgi?id=1933760 or similar)
May 15 12:32:09.382 E clusteroperator/machine-config condition/Degraded status/True reason/RequiredPoolsFailed changed: Unable to apply 4.13.0-0.nightly-2024-05-15-105412: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, pool master has not progressed to latest configuration: controller version mismatch for rendered-master-1b2026bddbd7a23a0dbc2e4560e74c02 expected 2d7a09cc9acd5ffd96ef777a1bd2c348cd49a0c9 has 33a010772d604aff2cb625d04a9469a47f53c96e: 1 (ready 1) out of 3 nodes are updating to latest configuration rendered-master-a66fbcadcfd5201ab3539b8c45aa6fd0, retrying]
May 15 12:32:09.382 - 699s  E clusteroperator/machine-config condition/Degraded status/True reason/Unable to apply 4.13.0-0.nightly-2024-05-15-105412: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, pool master has not progressed to latest configuration: controller version mismatch for rendered-master-1b2026bddbd7a23a0dbc2e4560e74c02 expected 2d7a09cc9acd5ffd96ef777a1bd2c348cd49a0c9 has 33a010772d604aff2cb625d04a9469a47f53c96e: 1 (ready 1) out of 3 nodes are updating to latest configuration rendered-master-a66fbcadcfd5201ab3539b8c45aa6fd0, retrying]

... 1 lines not shown

May 15 18:39:16.865 E ns/e2e-k8s-sig-apps-job-upgrade-319 pod/foo-5dchr node/ip-10-0-227-26.us-east-2.compute.internal uid/41c230af-5be1-4dbd-87b9-6ff112ae8f38 container/c reason/ContainerExit code/137 cause/Error
May 15 18:41:11.775 E clusteroperator/machine-config condition/Degraded status/True reason/RequiredPoolsFailed changed: Unable to apply 4.13.0-0.nightly-2024-05-15-165412: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, pool master has not progressed to latest configuration: controller version mismatch for rendered-master-0a9529f17e851563be8ffdee7e9584d2 expected 2d7a09cc9acd5ffd96ef777a1bd2c348cd49a0c9 has 33a010772d604aff2cb625d04a9469a47f53c96e: 1 (ready 1) out of 3 nodes are updating to latest configuration rendered-master-1d8f09aff52ec049d7c7e52865a74daa, retrying]
May 15 18:41:11.775 - 522s  E clusteroperator/machine-config condition/Degraded status/True reason/Unable to apply 4.13.0-0.nightly-2024-05-15-165412: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, pool master has not progressed to latest configuration: controller version mismatch for rendered-master-0a9529f17e851563be8ffdee7e9584d2 expected 2d7a09cc9acd5ffd96ef777a1bd2c348cd49a0c9 has 33a010772d604aff2cb625d04a9469a47f53c96e: 1 (ready 1) out of 3 nodes are updating to latest configuration rendered-master-1d8f09aff52ec049d7c7e52865a74daa, retrying]

... 1 lines not shown

May 14 15:47:49.503 E ns/openshift-multus pod/multus-additional-cni-plugins-zssxn node/ip-10-0-175-237.us-west-2.compute.internal uid/9be29d0c-b348-447d-a6ce-11d34bb1a3d0 container/kube-multus-additional-cni-plugins reason/TerminationStateCleared lastState.terminated was cleared on a pod (bug https://bugzilla.redhat.com/show_bug.cgi?id=1933760 or similar)
May 14 15:48:17.580 E clusteroperator/machine-config condition/Degraded status/True reason/RequiredPoolsFailed changed: Unable to apply 4.13.0-0.nightly-2024-05-14-140838: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, pool master has not progressed to latest configuration: controller version mismatch for rendered-master-c8d6d2282c5c30b4d26f74d8a8c00e4a expected bb00d4f6f57ab3a3fc11644a958a6e1781389a23 has 33a010772d604aff2cb625d04a9469a47f53c96e: 1 (ready 1) out of 3 nodes are updating to latest configuration rendered-master-37853bea93c12cfcdf9a6b70ed39addd, retrying]
May 14 15:48:17.580 - 673s  E clusteroperator/machine-config condition/Degraded status/True reason/Unable to apply 4.13.0-0.nightly-2024-05-14-140838: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, pool master has not progressed to latest configuration: controller version mismatch for rendered-master-c8d6d2282c5c30b4d26f74d8a8c00e4a expected bb00d4f6f57ab3a3fc11644a958a6e1781389a23 has 33a010772d604aff2cb625d04a9469a47f53c96e: 1 (ready 1) out of 3 nodes are updating to latest configuration rendered-master-37853bea93c12cfcdf9a6b70ed39addd, retrying]

... 1 lines not shown

May 16 07:05:12.831 E ns/openshift-multus pod/multus-admission-controller-76d6fb4b78-gz7l5 node/ip-10-0-176-1.us-east-2.compute.internal uid/756d783f-326a-4acd-9968-f4a46325b728 container/multus-admission-controller reason/ContainerExit code/137 cause/Error
May 16 07:08:14.558 E clusteroperator/machine-config condition/Degraded status/True reason/RequiredPoolsFailed changed: Unable to apply 4.13.0-0.nightly-2024-05-16-052445: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, pool master has not progressed to latest configuration: controller version mismatch for rendered-master-20c1202ff2e4b731b6b4aa54d129a38f expected 2d7a09cc9acd5ffd96ef777a1bd2c348cd49a0c9 has 33a010772d604aff2cb625d04a9469a47f53c96e: 2 (ready 2) out of 3 nodes are updating to latest configuration rendered-master-2d8a4f7cef4a58edca0ac7c08b9e24a9, retrying]
May 16 07:08:14.558 - 152s  E clusteroperator/machine-config condition/Degraded status/True reason/Unable to apply 4.13.0-0.nightly-2024-05-16-052445: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, pool master has not progressed to latest configuration: controller version mismatch for rendered-master-20c1202ff2e4b731b6b4aa54d129a38f expected 2d7a09cc9acd5ffd96ef777a1bd2c348cd49a0c9 has 33a010772d604aff2cb625d04a9469a47f53c96e: 2 (ready 2) out of 3 nodes are updating to latest configuration rendered-master-2d8a4f7cef4a58edca0ac7c08b9e24a9, retrying]

... 1 lines not shown

May 10 15:22:20.409 E ns/e2e-k8s-sig-apps-job-upgrade-8211 pod/foo-llphv node/ip-10-0-254-24.us-west-2.compute.internal uid/b93f0406-287a-4270-8519-a30002107598 container/c reason/ContainerExit code/137 cause/Error
May 10 15:22:39.654 E clusteroperator/machine-config condition/Degraded status/True reason/RequiredPoolsFailed changed: Unable to apply 4.13.0-0.nightly-2024-05-10-134150: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, pool master has not progressed to latest configuration: controller version mismatch for rendered-master-9a17fdbfd73f2c971c87ca2bd44e7715 expected bb00d4f6f57ab3a3fc11644a958a6e1781389a23 has 33a010772d604aff2cb625d04a9469a47f53c96e: 1 (ready 1) out of 3 nodes are updating to latest configuration rendered-master-0dcfb438df4d62e501df7dbf7f52fcf1, retrying]
May 10 15:22:39.654 - 686s  E clusteroperator/machine-config condition/Degraded status/True reason/Unable to apply 4.13.0-0.nightly-2024-05-10-134150: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, pool master has not progressed to latest configuration: controller version mismatch for rendered-master-9a17fdbfd73f2c971c87ca2bd44e7715 expected bb00d4f6f57ab3a3fc11644a958a6e1781389a23 has 33a010772d604aff2cb625d04a9469a47f53c96e: 1 (ready 1) out of 3 nodes are updating to latest configuration rendered-master-0dcfb438df4d62e501df7dbf7f52fcf1, retrying]

... 1 lines not shown

May 14 09:44:04.843 E ns/openshift-monitoring pod/alertmanager-main-1 node/ip-10-0-141-53.us-west-2.compute.internal uid/ba38b603-ffb8-4559-ad15-5b1bb6be4a61 container/alertmanager reason/ContainerExit code/1 cause/Error ts=2024-05-14T09:44:02.382Z caller=main.go:240 level=info msg="Starting Alertmanager" version="(version=0.25.0, branch=rhaos-4.13-rhel-8, revision=38194c1bde7b693bb84526d1084400a1e76da31b)"\nts=2024-05-14T09:44:02.382Z caller=main.go:241 level=info build_context="(go=go1.19.13 X:strictfipsruntime, user=root@cbb9d02780b4, date=20240510-00:07:28)"\nts=2024-05-14T09:44:02.409Z caller=cluster.go:681 level=info component=cluster msg="Waiting for gossip to settle..." interval=2s\nts=2024-05-14T09:44:02.462Z caller=coordinator.go:113 level=info component=configuration msg="Loading configuration file" file=/etc/alertmanager/config_out/alertmanager.env.yaml\nts=2024-05-14T09:44:02.463Z caller=coordinator.go:118 level=error component=configuration msg="Loading configuration file failed" file=/etc/alertmanager/config_out/alertmanager.env.yaml err="open /etc/alertmanager/config_out/alertmanager.env.yaml: no such file or directory"\nts=2024-05-14T09:44:02.463Z caller=cluster.go:690 level=info component=cluster msg="gossip not settled but continuing anyway" polls=0 elapsed=53.790712ms\n
May 14 09:44:23.743 E clusteroperator/machine-config condition/Degraded status/True reason/RequiredPoolsFailed changed: Unable to apply 4.13.0-0.nightly-2024-05-14-080341: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, pool master has not progressed to latest configuration: controller version mismatch for rendered-master-29dea8d3bd958cdead798ab2ead5a11e expected bb00d4f6f57ab3a3fc11644a958a6e1781389a23 has 33a010772d604aff2cb625d04a9469a47f53c96e: 1 (ready 1) out of 3 nodes are updating to latest configuration rendered-master-8703f6030f071f06bdd0f663d2ca1be1, retrying]
May 14 09:44:23.743 - 683s  E clusteroperator/machine-config condition/Degraded status/True reason/Unable to apply 4.13.0-0.nightly-2024-05-14-080341: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, pool master has not progressed to latest configuration: controller version mismatch for rendered-master-29dea8d3bd958cdead798ab2ead5a11e expected bb00d4f6f57ab3a3fc11644a958a6e1781389a23 has 33a010772d604aff2cb625d04a9469a47f53c96e: 1 (ready 1) out of 3 nodes are updating to latest configuration rendered-master-8703f6030f071f06bdd0f663d2ca1be1, retrying]

... 1 lines not shown

May 08 17:21:39.109 - 633ms E clusteroperator/storage condition/Degraded status/True reason/AWSEBSCSIDriverOperatorStaticControllerDegraded: "csidriveroperators/aws-ebs/standalone/08_rolebinding_aws_config.yaml" (string): client rate limiter Wait returned an error: context canceled\nAWSEBSCSIDriverOperatorStaticControllerDegraded:
May 08 17:21:49.695 E clusteroperator/machine-config condition/Degraded status/True reason/RequiredPoolsFailed changed: Unable to apply 4.13.0-0.nightly-2024-05-08-153833: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, pool master has not progressed to latest configuration: controller version mismatch for rendered-master-94335b046540c323759c0c1c9fe48444 expected bb00d4f6f57ab3a3fc11644a958a6e1781389a23 has 33a010772d604aff2cb625d04a9469a47f53c96e: 1 (ready 1) out of 3 nodes are updating to latest configuration rendered-master-10fec68a449bcf71a34110725d833710, retrying]
May 08 17:21:49.695 - 622s  E clusteroperator/machine-config condition/Degraded status/True reason/Unable to apply 4.13.0-0.nightly-2024-05-08-153833: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, pool master has not progressed to latest configuration: controller version mismatch for rendered-master-94335b046540c323759c0c1c9fe48444 expected bb00d4f6f57ab3a3fc11644a958a6e1781389a23 has 33a010772d604aff2cb625d04a9469a47f53c96e: 1 (ready 1) out of 3 nodes are updating to latest configuration rendered-master-10fec68a449bcf71a34110725d833710, retrying]

... 1 lines not shown

May 09 14:41:20.732 E ns/e2e-k8s-sig-apps-job-upgrade-857 pod/foo-6fqg8 node/ip-10-0-223-197.us-west-2.compute.internal uid/09be04aa-a834-4626-8a7d-2baa1b13aea6 container/c reason/ContainerExit code/137 cause/Error
May 09 14:41:40.464 E clusteroperator/machine-config condition/Degraded status/True reason/RequiredPoolsFailed changed: Unable to apply 4.13.0-0.nightly-2024-05-09-130302: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, pool master has not progressed to latest configuration: controller version mismatch for rendered-master-11890400ac5ea6e63e73f05a321d690f expected bb00d4f6f57ab3a3fc11644a958a6e1781389a23 has 33a010772d604aff2cb625d04a9469a47f53c96e: 1 (ready 1) out of 3 nodes are updating to latest configuration rendered-master-e219f6a09febdf3a6c616c0859fd6edc, retrying]
May 09 14:41:40.464 - 686s  E clusteroperator/machine-config condition/Degraded status/True reason/Unable to apply 4.13.0-0.nightly-2024-05-09-130302: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, pool master has not progressed to latest configuration: controller version mismatch for rendered-master-11890400ac5ea6e63e73f05a321d690f expected bb00d4f6f57ab3a3fc11644a958a6e1781389a23 has 33a010772d604aff2cb625d04a9469a47f53c96e: 1 (ready 1) out of 3 nodes are updating to latest configuration rendered-master-e219f6a09febdf3a6c616c0859fd6edc, retrying]

... 1 lines not shown

May 08 10:52:42.688 E ns/openshift-multus pod/multus-admission-controller-5cd68b7cf5-mztn5 node/ip-10-0-218-127.us-west-1.compute.internal uid/1096d779-da64-40ae-897a-283fe3c5146b container/multus-admission-controller reason/ContainerExit code/137 cause/Error
May 08 10:55:21.724 E clusteroperator/machine-config condition/Degraded status/True reason/RequiredPoolsFailed changed: Unable to apply 4.13.0-0.nightly-2024-05-08-090908: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, pool master has not progressed to latest configuration: controller version mismatch for rendered-master-c534993b8fb0589050aaa7bbd7550233 expected bb00d4f6f57ab3a3fc11644a958a6e1781389a23 has 33a010772d604aff2cb625d04a9469a47f53c96e: 2 (ready 2) out of 3 nodes are updating to latest configuration rendered-master-ea8ff37f441346ad925ee10b6b08aa49, retrying]
May 08 10:55:21.724 - 214s  E clusteroperator/machine-config condition/Degraded status/True reason/Unable to apply 4.13.0-0.nightly-2024-05-08-090908: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, pool master has not progressed to latest configuration: controller version mismatch for rendered-master-c534993b8fb0589050aaa7bbd7550233 expected bb00d4f6f57ab3a3fc11644a958a6e1781389a23 has 33a010772d604aff2cb625d04a9469a47f53c96e: 2 (ready 2) out of 3 nodes are updating to latest configuration rendered-master-ea8ff37f441346ad925ee10b6b08aa49, retrying]

... 1 lines not shown

May 08 04:26:35.619 E ns/openshift-cloud-credential-operator pod/pod-identity-webhook-5495f46bc-b5bpn node/ip-10-0-148-71.us-east-2.compute.internal uid/8bdf8e0b-d532-4572-a8b2-33e76f002eed container/pod-identity-webhook reason/ContainerExit code/137 cause/Error
May 08 04:29:44.225 E clusteroperator/machine-config condition/Degraded status/True reason/RequiredPoolsFailed changed: Unable to apply 4.13.0-0.nightly-2024-05-08-025210: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, pool master has not progressed to latest configuration: controller version mismatch for rendered-master-aaf46a4fa789eb340e21d7653680524e expected bb00d4f6f57ab3a3fc11644a958a6e1781389a23 has 33a010772d604aff2cb625d04a9469a47f53c96e: 2 (ready 2) out of 3 nodes are updating to latest configuration rendered-master-71baa98b815d47e0f4b313109a0db921, retrying]
May 08 04:29:44.225 - 148s  E clusteroperator/machine-config condition/Degraded status/True reason/Unable to apply 4.13.0-0.nightly-2024-05-08-025210: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, pool master has not progressed to latest configuration: controller version mismatch for rendered-master-aaf46a4fa789eb340e21d7653680524e expected bb00d4f6f57ab3a3fc11644a958a6e1781389a23 has 33a010772d604aff2cb625d04a9469a47f53c96e: 2 (ready 2) out of 3 nodes are updating to latest configuration rendered-master-71baa98b815d47e0f4b313109a0db921, retrying]

... 1 lines not shown