Details
-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
4.13.0
-
None
-
No
-
False
-
Description
Description of problem:
We noticed in our build01, master pool was degraded on Apr 12. We also have https://prow.ci.openshift.org/?job=periodic-build01-upgrade , which periodically execute cluster upgrade (oc adm upgrade --to-latest). We find build01 started upgrading to 4.13.0-rc3 on Apr 13.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
[fedora@Bear-Work-RedHat ~]$ oc --context build01 describe mcp master ...omitted... The master pool reports: Status: Conditions: Last Transition Time: 2021-03-11T20:49:24Z Message: Reason: Status: False Type: RenderDegraded Last Transition Time: 2023-04-12T13:28:44Z Message: Reason: Status: False Type: Updated Last Transition Time: 2023-04-12T13:29:17Z Message: Node ip-10-0-140-81.ec2.internal is reporting: "exit status 1" Reason: 1 nodes are reporting degraded status on sync Status: True Type: NodeDegraded Last Transition Time: 2023-04-12T13:29:17Z Message: Reason: Status: True Type: Degraded Last Transition Time: 2023-04-12T13:28:44Z Message: All nodes are updating to rendered-master-26f9e3d3ea47eadf53d3b00e9c447fa5 Reason: Status: True Type: Updating ...omitted...