Bug 1872787

Summary:	Installer uses non-routable provisioning network address to mount virtual media that is not accessible by the BMC address
Product:	OpenShift Container Platform	Reporter:	rlopez
Component:	Bare Metal Hardware Provisioning	Assignee:	Tomas Sedovic <tsedovic>
Bare Metal Hardware Provisioning sub component:	ironic	QA Contact:	Amit Ugol <augol>
Status:	CLOSED NOTABUG	Docs Contact:
Severity:	medium
Priority:	medium	CC:	beth.white, lshilin, rbartal
Version:	4.6	Keywords:	Triaged
Target Milestone:	---
Target Release:	4.7.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-21 14:19:53 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:
Bug Depends On:	1880104
Bug Blocks:

Description rlopez 2020-08-26 15:47:19 UTC

Description of problem:

When attempting to use RedFish Virtual Media, the installer attempts to mount the ISO on the 172.22.0.2 address which is the provisioning network. However, the provisioning network is a non-routeable network so the BMC can never access it. 

Customers are likely to have their BMC addressing on an external network or a separate management network. They won't have their BMC addressing based off the provisioning network.




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




Steps to Reproduce:
1. Attempt to install using Dell systems with idrac-redfish://

Comment 3 Tomas Sedovic 2020-09-17 17:08:47 UTC

This is working as currently intended. In order to deploy OpenShift using virtual media, the provisioning network should either be turned off or be accessible from the BMC. We do need to make sure this is documented, however.

I've created https://bugzilla.redhat.com/show_bug.cgi?id=1880104 to track the documentation change.

Once that is resolved, we can close this as NOTABUG.

Comment 4 Tomas Sedovic 2020-09-21 14:19:53 UTC

The linked bug was closed (the documentation will appear in known issues in the release notes). Closing this as NOTABUG.