-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.18.0
Description of problem:
Cluster's global address "<infra id>-apiserver" not deleted during "destroy cluster"
Version-Release number of selected component (if applicable):
4.18.0-0.nightly-multi-2024-08-15-212448
How reproducible:
Always
Steps to Reproduce:
1. "create install-config", then optionally insert interested settings (see [1]) 2. "create cluster", and make sure the cluster turns healthy finally (see [2]) 3. check the cluster's addresses on GCP (see [3]) 4. "destroy cluster", and make sure everything of the cluster getting deleted (see [4])
Actual results:
The global address "<infra id>-apiserver" is not deleted during "destroy cluster".
Expected results:
Everything of the cluster shoudl get deleted during "destroy cluster".
Additional info:
FYI we had a 4.16 bug once, see https://issues.redhat.com/browse/OCPBUGS-32306
- blocks
-
OCPBUGS-38600 [gcp] Global apiserver address not removed on destroy
-
- Closed
-
- is cloned by
-
OCPBUGS-38600 [gcp] Global apiserver address not removed on destroy
-
- Closed
-
- relates to
-
CORS-3525 Provision GCP with CAPI (GA)
-
- Closed
-
-
OCPBUGS-32306 CAPG: Global apiserver addresses not removed on destroy
-
- Closed
-
- links to
-
RHEA-2024:6122 OpenShift Container Platform 4.18.z bug fix update
(1 links to)