-
Bug
-
Resolution: Unresolved
-
Normal
-
4.12
-
None
-
Moderate
-
None
-
CLOUD Sprint 239, CLOUD Sprint 240, CLOUD Sprint 241, CLOUD Sprint 242, CLOUD Sprint 243, CLOUD Sprint 244, CLOUD Sprint 245, CLOUD Sprint 246, CLOUD Sprint 247, CLOUD Sprint 248, CLOUD Sprint 249
-
11
-
Rejected
-
False
-
-
If Release Note Needed, Set a Value
-
Set a Value
Description of problem:
capi machine cannot be deleted by installer during cluster destroy, checked on GCP console, found this machine lacks label(kubernetes-io-cluster-clusterid: owned), if adding this label manually on GCP console for the machine, then the machine can be deleted by installer during cluster destroy.
Version-Release number of selected component (if applicable):
4.12.0-0.nightly-2022-10-05-053337
How reproducible:
Always
Steps to Reproduce:
1.Follow the steps here https://bugzilla.redhat.com/show_bug.cgi?id=2107999#c9 to create a capi machine liuhuali@Lius-MacBook-Pro huali-test % oc get machine.cluster.x-k8s.io -n openshift-cluster-api NAME CLUSTER NODENAME PROVIDERID PHASE AGE VERSION capi-ms-mtchm huliu-gcpx-c55vm gce://openshift-qe/us-central1-a/capi-gcp-machine-template-gcw9t Provisioned 51m 2.Destroy the cluster The cluster destroyed successfully, but checked on GCP console, found the capi machine is still there.
labels of capi machine
labels of mapi machine
Actual results:
capi machine cannot be deleted by installer during cluster destroy
Expected results:
capi machine should be deleted by installer during cluster destroy
Additional info:
Also checked on aws, the case worked well, and found there is tag(kubernetes.io/cluster/clusterid:owned) for capi machines.
