Bug 2006770

Summary: When trying to boot nodes with ctlplane on anything else than nic1, it's impossible to provision instances.
Product: Red Hat OpenStack Reporter: Harald Jensås <hjensas>
Component: python-metalsmithAssignee: Harald Jensås <hjensas>
Status: ON_QA --- QA Contact: Jason Paroly <jparoly>
Severity: high Docs Contact:
Priority: high    
Version: 17.0 (Wallaby)CC: jparoly, jschluet, sbaker
Target Milestone: AlphaKeywords: TestOnly, Triaged
Target Release: 17.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-metalsmith-1.4.3-0.20211210121855.324b758.el8ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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 Harald Jensås 2021-09-22 11:29:23 UTC 
Description of problem:
When trying to boot nodes with ctlplane on anything else than nic1, it's impossible to provision instances.

This doesn't happen when ctlplane (provisioning NIC) is nic1.





How reproducible:
100% reproducible.

Steps to Reproduce:

I was able to reproduce this in a virtual environment using the manual-management hardware type.
My VM has two NIC's enp1s0 (nic1) and enp7s0 (nic2), it is configured to boot using enp7s0 (nic2).

cloud-init only write a config for enp1s0 (nic1), since there is no DHCP where enp1s0 (nic1) is wired the nodes boots with no network.

cloud-init is doing "Fallback network configuration", which seem to behave as designed. Unfortunately not good for this use case.
https://cloudinit.readthedocs.io/en/latest/topics/network-config.html#fallback-network-configuration
Actual results:


Expected results:

It should be possible to provision nodes even if the NIC used for provisioning is not the first one discovered.

metalsmith should write network metadata to the config drive so that cloud-init can configure instance networking.
Comment 3 Harald Jensås 2023-03-07 09:58:18 UTC 
Moving to ON_QA - the fix has been released.

https://access.redhat.com/downloads/content/python3-metalsmith/1.4.3-0.20220712230441.324b758.el9ost/noarch/fd431d51/package-changelog

2021-12-10 OSP Prod Chain <dev-null> 1.4.3-0.20211210130412.324b758
[...]
- Write network_data.json metadata to config-dirve 
[...]