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

Bug 1874435

Summary:	[IPI Baremetal] OCP 4.6 Installer survey failed to generate install-config - Insisting on 10.0.0.0/16 for the machine network
Product:	OpenShift Container Platform	Reporter:	Ori Michaeli <omichael>
Component:	Installer	Assignee:	Kiran Thyagaraja <kiran>
Installer sub component:	OpenShift on Bare Metal IPI	QA Contact:	Amit Ugol <augol>
Status:	CLOSED NOTABUG	Docs Contact:
Severity:	high
Priority:	high	CC:	beth.white, omichael, prabinov, shardy, smiron
Version:	4.6	Keywords:	TestBlocker, 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-12-17 16:08:52 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:
Bug Blocks:	1865707

Description Ori Michaeli 2020-09-01 10:58:41 UTC

Description of problem:
Survey completed and failed due to mismatch of the machine network:

FATAL failed to fetch Install Config: failed to generate asset "Install Config": invalid install config: [platform.baremetal.apiVIP: Invalid value: "192.168.123.5": IP expected to be in one of the machine networks: 10.0.0.0/16, platform.baremetal.ingressVIP: Invalid value: "192.168.123.10": IP expected to be in one of the machine networks: 10.0.0.0/16]

Version-Release number of the following components:
4.6.0-0.nightly-2020-08-27-005538

How reproducible:
Always

Steps to Reproduce:
1. Provision a dicsonnected env 
2. Retrieve the openshift-baremetal-install 
3. Run ./openshift-baremetal-install create install-config
4. Fill out all of the questions

Actual results:
Survey failed to create install-config.

Expected results:
Install-config created based on survey input.

Additional info:

Comment 1 Steven Hardy 2020-10-06 10:34:41 UTC

The VIPs are expected to be on the same subnet as the machineNetwork, so I think the validation failure indicates an invalid configuration - can you please provide details of the input to each of the questions in the survey, and also the generated install-config.yaml?

Comment 2 Kiran Thyagaraja 2020-10-06 12:38:14 UTC

This is not a bug. Sorry I thought I had updated this issue. The survey expects the VIP to be in the 10.0.0.0/16. Unfortunately we cannot change it in the survey. The survey purportedly is to be used to only generate a default install-config and then supposed to be manually customized.

Comment 3 Ori Michaeli 2020-10-06 12:51:55 UTC

(In reply to Steven Hardy from comment #1)
> The VIPs are expected to be on the same subnet as the machineNetwork, so I
> think the validation failure indicates an invalid configuration - can you
> please provide details of the input to each of the questions in the survey,
> and also the generated install-config.yaml?

The survey is not letting me customize the machine network.
When failing the survey does not generate an install-config.yaml.

Comment 5 Kiran Thyagaraja 2020-12-17 16:08:52 UTC

(In reply to Ori Michaeli from comment #3)
> (In reply to Steven Hardy from comment #1)
> > The VIPs are expected to be on the same subnet as the machineNetwork, so I
> > think the validation failure indicates an invalid configuration - can you
> > please provide details of the input to each of the questions in the survey,
> > and also the generated install-config.yaml?
> 
> The survey is not letting me customize the machine network.
> When failing the survey does not generate an install-config.yaml.

The machinenetwork is not customizable in the installer survey. The installer survey is not designed to make a final render of the install-config.yaml. It was intended to be a starting point after which the end user should modify the defaults (in this case machineconfig: 10.0.0.0/16). Like I mentioned this is not a IPI baremetal specific bug. Its an installer-wide default that we have to honor.