This bug was initially created as a copy of Bug #1968372 I am copying this bug because: Description of problem: BMH resources are marked as detached once the deployment completes. Currently, BMAC takes care of re-attaching the BMH when an ISO is regenerated. This will cause a node re-deployment for every BMH associated to the InfraEnv that an image has been regenerated for, including installed nodes. As far as assisted service is concerned, an installed spoke cluster is not part of the hub cluster anymore. Therefore, BMAC should respect this principle and skip reconcile for BMH nodes that have been detached.
this bug doesn't block OCP4.8.0 -release - the fix will be delivered the the ACM channel on the AI-operator add verified then
Verified with ACM: 2.3.0-DOWNSTREAM-2021-07-06-21-29-18 Node is installed and and bmh is marked as detached before regenerating the ISO: oc get bmh sno-0-bmh -o json | jq '.status.operationalStatus' "detached" oc get agent ee2b463e-9c54-429b-bcf5-8ef57551d471 -o json | jq '.status.conditions[-1]' { "lastTransitionTime": "2021-07-08T12:10:42Z", "message": "The installation has completed: Done", "reason": "InstallationCompleted", "status": "True", "type": "Installed" } ISO is regenerated by removing nmstateconfig_label. bmh remains in detached state: oc get bmh sno-0-bmh -o json | jq '.status.operationalStatus' "detached"
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.8.2 bug fix and security 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-2021:2438