-
Bug
-
Resolution: Done-Errata
-
Critical
-
None
-
4.16
Description of problem: OCP doesn't resume from "hibernation" (shutdown/restart of cloud instances).
NB: This is not related to certs.
Version-Release number of selected component (if applicable): 4.16 nightlies, at least 4.16.0-0.nightly-2024-05-14-095225 through 4.16.0-0.nightly-2024-05-21-043355
How reproducible: 100%
Steps to Reproduce:
1. Install 4.16 nightly on AWS. (Other platforms may be affected, don't know.)
2. Shut down all instances. (I've done this via hive hibernation; vrutkovs@redhat.com has done it via cloud console.)
3. Start instances. (Ditto.)
Actual results: OCP doesn't start. Per Vadim:
"kubelet says host IP unknown; known addresses: [] so etcd can't start."
Expected results: OCP starts normally.
Additional info: We originally thought this was related to OCPBUGS-30860, but reproduced with nightlies containing the updated AMIs.
- is cloned by
-
OCPBUGS-35291 OpenShift won't start when instances shut down and restarted
- Closed
- is depended on by
-
OCPBUGS-35291 OpenShift won't start when instances shut down and restarted
- Closed
- is duplicated by
-
HIVE-2504 [OSD] 4.16.z clusters cannot be resumed from hibernating status
- Closed
- relates to
-
ACM-11706 Resuming cluster stuck for OCP 4.16 hibernated clusters
- Closed
-
HIVE-2504 [OSD] 4.16.z clusters cannot be resumed from hibernating status
- Closed
-
HIVE-2507 [ROSA] cluster cannot scale up with version 4.16 nightly/rc build
- Closed
-
OCPBUGS-30860 API is unavailable after bootstrap server is destroyed
- Closed
- links to
-
RHEA-2024:3718 OpenShift Container Platform 4.17.z bug fix update