In the baremetal-operator the "baremetalhost.metal3.io/detached" annotation is a string value with the following behaviour - existence of the label defines host as detached - missing label defines the host as not detached This has the following consequence - the value of the annotation is always ignored (this was a design decision). In assisted-service we are setting value to "true" what may create an implicit assumption that the value is a boolean and setting it to "false" would reverse the behaviour. This is not the case and `baremetalhost.metal3.io/detached: "false"` still causes the host to be treated as detached. The issue has been already fixed on master via https://github.com/openshift/assisted-service/pull/1974 so that we are setting `baremetalhost.metal3.io/detached: "assisted-service-controller"`
I have verified the bug after merging to master, QE confirmation/approval would be appreciated ``` # oc -n assisted-installer-manual-bundle describe bmh ostest-extraworker-0 Name: ostest-extraworker-0 Namespace: assisted-installer-manual-bundle Labels: infraenvs.agent-install.openshift.io=myinfraenv Annotations: baremetalhost.metal3.io/detached: assisted-service-controller inspect.metal3.io: disabled API Version: metal3.io/v1alpha1 Kind: BareMetalHost [...] ```
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.9.0 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:3759