Bug 1748219

Summary:	Baremetal management UI should be disabled on non-baremetal cluster
Product:	OpenShift Container Platform	Reporter:	Jiri Tomasek <jtomasek>
Component:	Console Metal3 Plugin	Assignee:	Jiri Tomasek <jtomasek>
Status:	CLOSED ERRATA	QA Contact:	Yadan Pei <yapei>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.2.0	CC:	aos-bugs, xtian, yapei
Target Milestone:	---
Target Release:	4.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-16 06:39:51 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jiri Tomasek 2019-09-03 07:57:09 UTC

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

Comment 1 Jiri Tomasek 2019-09-03 07:57:59 UTC

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1746114

Comment 4 Yadan Pei 2019-09-17 07:03:36 UTC

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

Comment 5 Yadan Pei 2019-09-17 07:04:08 UTC

Cluster is created on AWS

Comment 6 errata-xmlrpc 2019-10-16 06:39:51 UTC

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