Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1771431

Summary:	installer exit upon an installation from ignition files with customer subnets specified
Product:	OpenShift Container Platform	Reporter:	Johnny Liu <jialiu>
Component:	Installer	Assignee:	W. Trevor King <wking>
Installer sub component:	openshift-installer	QA Contact:	Johnny Liu <jialiu>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	high
Version:	4.3.0
Target Milestone:	---
Target Release:	4.3.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-01-23 11:12:22 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 Johnny Liu 2019-11-12 11:15:59 UTC

Description of problem:

Version-Release number of the following components:
# openshift-install version
openshift-install v4.3.0
built from commit 93c16db3508065d3de74e362cbf5281ef46ce3f7
release image registry.svc.ci.openshift.org/ocp/release@sha256:70f5199ac2b055bc04e84d13571f7cc1b5e2955302f7a35731960b0cfccb49ca


How reproducible:
Always

Steps to Reproduce:
1. create a install-config.yaml
2. copy it to demo4 and demo5 folder separately.
3. Run the following steps against demo4 folder
# openshift-install create ignition-configs --dir demo4
INFO Consuming Install Config from target directory 
# openshift-install create cluster --dir demo4
FATAL failed to fetch Terraform Variables: failed to generate asset "Terraform Variables": no subnets configured 

4. Run the following steps against demo5 folder
# openshift-install create cluster --dir demo5
INFO Consuming Install Config from target directory 
INFO Creating infrastructure resources...         


Actual results:
Step 4 is failed when installation is triggered from ignition files.
Step 5 is succeeded when installation is triggered from install-config.yaml file.

Expected results:
Step 4 is working well.

Additional info:
Please attach logs from ansible-playbook with the -vvv flag

Comment 2 Johnny Liu 2019-11-14 05:45:55 UTC

Verified this bug with 4.3.0-0.nightly-2019-11-13-233341, and PASS.

Comment 4 errata-xmlrpc 2020-01-23 11:12:22 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, 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:0062