Bug 2038303 - User is unable to create a default_connection in network config
Summary: User is unable to create a default_connection in network config
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Bare Metal Hardware Provisioning
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.11.0
Assignee: Zane Bitter
QA Contact: Amit Ugol
Depends On:
TreeView+ depends on / blocked
Reported: 2022-01-07 18:22 UTC by Zane Bitter
Modified: 2022-04-26 10:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-04-26 10:25:32 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift image-customization-controller pull 32 0 None open Bug 2038303: Handle default_connection 2022-01-13 16:35:08 UTC
Github openshift ironic-agent-image pull 32 0 None open Bug 2038303: Allow customisation of default_connection file 2022-01-13 16:58:28 UTC

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?).

Note You need to log in before you can comment on or make changes to this bug.