-
Bug
-
Resolution: Done-Errata
-
Critical
-
4.13, 4.12, 4.14, 4.15, 4.16
-
None
-
Important
-
No
-
Rejected
-
False
-
-
Before this bug fix the wait-for-ceo command used during bootstrap to verify etcd rollout would not report errors for some failure modes. With this fix those error messages should now be visible on the bootkube script if the cmd exits in an error case.
-
Bug Fix
-
In Progress
This is a clone of issue OCPBUGS-34495. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-33564. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-33495. The following is the description of the original issue:
—
The wait-for-ceo cmd is used during bootstrap to wait until the bootstrap completion conditions are met i.e etcd has scaled up to 3 members + bootstrap.
https://github.com/openshift/installer/blob/d08c982cdbb7f66b810f71aa9608bf51cce8c38c/data/data/bootstrap/files/usr/local/bin/bootkube.sh.template#L569-L576
Currently this cmd won't return errors in the following two places:
- Only logging not returning: https://github.com/openshift/cluster-etcd-operator/blob/cbfb856ec8892687a303989b84e01c8f34c1967e/pkg/cmd/waitforceo/waitforceo.go#L51-L58
- Defining a new err in the if block's scope means it doesn't get passed out: https://github.com/openshift/cluster-etcd-operator/blob/master/pkg/operator/bootstrapteardown/waitforceo.go#L26-L28
- blocks
-
-
- Closed
-
- clones
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
- is cloned by
-
-
- Closed
-
- links to
-
RHBA-2024:4484
OpenShift Container Platform 4.13.z bug fix update
