Bug 1872489

Summary:	MAO should not manage metal3 deployments if cluster-baremetal-operator is available
Product:	OpenShift Container Platform	Reporter:	sdasu
Component:	Cloud Compute	Assignee:	sdasu
Cloud Compute sub component:	Other Providers	QA Contact:	sunzhaohua <zhsun>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	medium
Priority:	unspecified	CC:	agarcial
Version:	4.6	Keywords:	Triaged
Target Milestone:	---
Target Release:	4.6.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:	2020-09-01 08:32:24 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:

Comment 1 Alberto 2020-09-01 08:32:24 UTC

@sdasu is this a dup of https://bugzilla.redhat.com/show_bug.cgi?id=1873234?
Can you please make the comment above public?

>As a pre-requisite for the cluster-baremetal-operator to take over management of metal3 deployments in a future release (4.7), MAO should posses the capability (in 4.6) to recognize that the CBO is available and will manage the metal3 deployment.

Why is this needed at all? if the CBO is running on 4.7, all baremetal related code just need to be removed from MAO in 4.7

*** This bug has been marked as a duplicate of bug 1873234 ***