-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.16, 4.17, 4.18, 4.19, 4.20
-
Quality / Stability / Reliability
-
True
-
-
None
-
Moderate
-
None
-
None
-
None
-
None
-
T&PS 2025 #9, T&PS 2025 #10
-
2
-
contract-priority
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
While running SNO IBU a rollback can't be performed after 24 hours because certificates expire. Following this instructions: https://docs.redhat.com/en/documentation/openshift_container_platform/4.16/html/edge_computing/image-based-upgrade-for-single-node-openshift-clusters#cnf-understanding-image-based-upgrade Wondering if a note like the one in the Deployment guide should be added. That note reads: "ImportantThe SSL certificates for the RHCOS ISO installation image are only valid for 24 hours. If you use the ISO image to install a node more than 24 hours after creating the image, the installation can fail. To re-create the image after 24 hours, delete the ocp directory and re-create the OpenShift Container Platform assets." Which can be found here: https://docs.redhat.com/en/documentation/openshift_container_platform/4.16/html/installing_on_a_single_node/install-sno-installing-sno
Version-Release number of selected component (if applicable):
4.16
How reproducible:
SNO IBU and try to rollback after 24 hours
Steps to Reproduce:
1) SNO cluster is freshly deployed. 2) IBU prepare and IBU Upgrade is performed but Upgrade is not finalized with in 24 hours from the time cluster is deployed. 3) if you check rollbackAvailabilityExpiration time in the ibu CR. it shows 24 hours from cluster is deployed. That means rollback not possible from ater 24 hrs. That is because for freshly deployed clusters certificates are valid only for 24hrs.
Actual results:
Note in docs not found
Expected results:
There should be a note stating this in docs
Additional info: