Description of problem: metal3 deployment is installed by machine-api-operator, as mentioned in [1] currently the CRDs within the machine-api-operator are installed for all platforms. There is no way to selectively install CRDs after determining if it is a baremetal platform. This means that UI can't use CRD presence as a flag for enabling metal3-plugin for baremetal management. UI need to explicitly detect the baremetal platform by checking infrastructure/cluster resource. Version-Release number of selected component (if applicable): How reproducible: Install AWS based cluster, Compute > Bare Metal Hosts navigation item is present
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1746114
1. Create 4.2 cluster with nightly build registry.svc.ci.openshift.org/ocp/release:4.2.0-0.nightly-2019-09-15-052022 2. Cluster admin visit Compute menu, no Bare Metal Hosts sub menu 3. Home -> Dashboards, no bare metal hosts info shown in Cluster Inventory
Cluster is created on AWS
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, 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/RHBA-2019:2922