Description of problem: When Provisioning CR is deleted, all resources created by the cluster-baremetal-operator needs to be deleted. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
*** Bug 1906934 has been marked as a duplicate of this bug. ***
Test plan: 1. Observe the provisioning: oc get provisioning provisioning-congiguration -o yaml Save the yaml as new-provisioning.yaml 2.Delete the provisioning CR: oc delete provisioning provisioning-configuration 3. Check that CR is deleted: oc get provisioning There are no resources to display 4. Check the pods list in openshift-machine-api namespace: oc get pods -n openshift-machine-api The metal3 pods (metal3 and metal3-image-cache) switch to Terminating and then disappear 5. Check the clusteroperator: oc get clusteroperator The baremetal clusteroperator switches to Available: False 6. Check the deployment, the metal3 deployment is supposed to be down: oc get deploy -n openshift-machine-api There is no metal3 deploy in the list 7. Check the serviceaccount: oc get sa -n openshift-machine-api cluster-baremetal-operator sa is deleted 8. Observe the metal3-state service The metal3-state service is down 9. Observe the secrets: oc get secrets Metal3 secrets are deleted 10. Restore the provisioning: oc apply -f new-provisioning.yaml The provisioning and all the resources are restored The actual results: 1. metal3-service wasn't found so it's deletion wasn't tested 2. There is cluster-baremetal-operator ServiceAccount, it remains after deletion of provisioning. @sadasu, is this an OK behavior?
SA is supposed to remain up, service was tested to go down. Verified
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:5633