Bug 1872489 - MAO should not manage metal3 deployments if cluster-baremetal-operator is available
Summary: MAO should not manage metal3 deployments if cluster-baremetal-operator is ava...
Keywords:
Status: CLOSED DUPLICATE of bug 1873234
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Compute
Version: 4.6
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.6.0
Assignee: sdasu
QA Contact: sunzhaohua
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-25 21:42 UTC by sdasu
Modified: 2020-09-01 08:32 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-01 08:32:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.