Bug 1840782 - Baremetal assisted installs should not deploy Baremetal specific metal3 pod
Summary: Baremetal assisted installs should not deploy Baremetal specific metal3 pod
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Compute
Version: 4.5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.6.0
Assignee: sdasu
QA Contact: Omri Hochman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-27 15:46 UTC by sdasu
Modified: 2020-10-27 16:01 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 16:01:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift machine-api-operator pull 560 0 None closed Bug 1840782: Update conditions under which metal3 pod would be deployed 2021-01-29 07:02:30 UTC
Red Hat Product Errata RHBA-2020:4196 0 None None None 2020-10-27 16:01:21 UTC

Description sdasu 2020-05-27 15:46:52 UTC
Description of problem:
The Baremetal assisted installs do not need the metal3 pod to be deployed by the MAO. For these installs, the platform types continues to be "BareMetal" but does not need the metal3 pod to deploy workers.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 5 Alexander Chuzhoy 2020-09-30 14:17:17 UTC
Verified:
OCP version: 4.6.0-0.nightly-2020-08-31-220837 deployed with assisted-instaler


oc get pod -n openshift-machine-api
NAME                                          READY   STATUS    RESTARTS   AGE
cluster-autoscaler-operator-f55f8ffbd-fxshw   2/2     Running   0          20h
machine-api-controllers-7c8fff8689-sxgfn      7/7     Running   0          20h
machine-api-operator-6d495c9c97-clqs4         2/2     Running   0          20h

oc get provisioning 
No resources found



No metal3 listed and no provisioning cr.


Below is an output from a deployment done OUTSIDE of assisted and it has the above:



oc get pod -n openshift-machine-api 
NAME                                           READY   STATUS    RESTARTS   AGE
cluster-autoscaler-operator-5db4d558d5-ckcr8   2/2     Running   0          19h
machine-api-controllers-74889ccdf-8j9wf        7/7     Running   0          19h
machine-api-operator-7b7d59c5cb-9fqdf          2/2     Running   0          19h
metal3-6bb8f96766-qbn9x                        8/8     Running   0          19h

oc get provisioning 
NAME                         AGE
provisioning-configuration   19h
[kni@provisionhost-0-0 ~]$

Comment 7 errata-xmlrpc 2020-10-27 16:01:07 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 (OpenShift Container Platform 4.6 GA Images), 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-2020:4196


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