Bug 2038303

Summary:	User is unable to create a default_connection in network config
Product:	OpenShift Container Platform	Reporter:	Zane Bitter <zbitter>
Component:	Bare Metal Hardware Provisioning	Assignee:	Zane Bitter <zbitter>
Bare Metal Hardware Provisioning sub component:	OS Image Provider	QA Contact:	Amit Ugol <augol>
Status:	CLOSED NOTABUG	Docs Contact:
Severity:	medium
Priority:	high	CC:	aos-bugs, eweiss, zbitter
Version:	4.10	Keywords:	OtherQA, Triaged
Target Milestone:	---
Target Release:	4.11.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:	2022-04-26 10:25:32 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 Zane Bitter 2022-01-07 18:22:03 UTC

At startup, network manager creates a default_connection.nmconnection file. Currently, this means that the user would be unable to use an nmstate config that generated a file of the same name because:

1. we don't set the overwrite option on network configuration files
2. as a workaround for bug 2032717, we delete that file before calling coreos-installer


What we should do instead is to tell IPA whether the user has supplied any custom network config or not, and only pass the --copy-network flag to coreos-installer if there is config to copy. Then we won't need to delete default_connection.nmconnection and we can allow the user to overwrite it.

Comment 4 Zane Bitter 2022-04-25 13:41:39 UTC

I don't know to be honest. It was more of a theoretical limitation - a better design approach was suggested and we didn't want to forget about it so we created this bug. I'm most interested in testing for regressions (i.e. can we still specify a network config at all?).