Bug 1956714 - Machines stuck in Provisioning state due to missing 'providerID' - IPI Baremetal Installation
Summary: Machines stuck in Provisioning state due to missing 'providerID' - IPI Bareme...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: assisted-installer
Version: 4.6.z
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.8.0
Assignee: Ronnie Lazar
QA Contact: Yuri Obshansky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-04 09:50 UTC by Kaushal Sathe
Modified: 2024-10-01 18:05 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-12 21:14:29 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 2 Zane Bitter 2021-05-04 17:40:12 UTC 
I'm not sure what has happened here; this looks like a cluster that has been cobbled together manually, although the reproduction instructions appear to indicate that is not the case?

- metal3 is not running (the Deployment does not exist)
- master BareMetalHosts still have paused annotations, as if the installation never finished
- no attempt has been made to provision the worker BareMetalHosts, although they have inspection data (presumably added by the installer?)

I think the Machines are failing to pick up any BareMetalHosts because they have an empty provisioning status (due to metal3 not running to reconcile them). So the warnings are correct. 2 worker Nodes are up and ready, but I'm not sure what provisioned them. It doesn't appear to be the Machines.
Note You need to log in before you can comment on or make changes to this bug.