Bug 2081141

Summary:	[16.2]Deploy Overcloud failing with separate nic
Product:	Red Hat OpenStack	Reporter:	Jason Paroly <jparoly>
Component:	openstack-ironic	Assignee:	OSP Team <rhos-maint>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16.2 (Train)	CC:	hjensas, sbaker
Target Milestone:	---
Target Release:	---
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:	2022-05-04 20:14:04 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:

Description Jason Paroly 2022-05-02 20:38:44 UTC

Description of problem:
Deploy of OC failing on separate nic configuration

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


How reproducible:
every time

Steps to Reproduce:
1. Setup configuration to use separate nic
2. Attempt Install OC
3.

Actual results:
OC deploy fails

Expected results:
OC deploy succeeds

Additional info:
Error: Cannot find device br-ex
Fatal failure on "Check all networks Gateway availability"

Comment 4 Harald Jensås 2022-05-04 20:14:04 UTC

Closing this as NOTABUG since the issue was due to a configuration error.
Configuring gateway addresses on flat networks where there is no gateway is not good practice, the new validation that ensure configured gateways are accessible during deployment will cause a failure when using such a configuration.