-
Bug
-
Resolution: Done-Errata
-
Undefined
-
None
-
4.16, 4.17
This is a clone of issue OCPBUGS-38733. The following is the description of the original issue:
—
Description of problem:
In OpenShift 4.13-4.15, when a "rendered" MachineConfig in use is deleted, it's automatically recreated. In OpenShift 4.16, it's not recreated, and nodes and MCP becomes degraded due to the "rendered" not found error.
Version-Release number of selected component (if applicable):
4.16
How reproducible:
Always
Steps to Reproduce:
1. Create a MC to deploy any file in the worker MCP 2. Get the name of the new rendered MC, like for example "rendered-worker-bf829671270609af06e077311a39363e" 3. When the first node starts updating, delete the new rendered MC oc delete mc rendered-worker-bf829671270609af06e077311a39363e
Actual results:
Node degraded with "rendered" not found error
Expected results:
In OCP 4.13 to 4.15, the "rendered" MC is automatically re-created, and the node continues updating to the MC content without issues. It should be the same in 4.16.
Additional info:
The same behavior in 4.12 and older than now in 4.16. In 4.13-4.15, the "rendered" is re-created and no issues with the nodes/MCPs are shown.
- blocks
-
OCPBUGS-43680 rendered MachineConfig in use not recreated in OpenShift 4.16
- POST
- clones
-
OCPBUGS-38733 rendered MachineConfig in use not recreated in OpenShift 4.16
- Verified
- is blocked by
-
OCPBUGS-38733 rendered MachineConfig in use not recreated in OpenShift 4.16
- Verified
- links to
-
RHBA-2024:8434 OpenShift Container Platform 4.17.z bug fix update