cloud-init does not provide configurable network activator priority overrides
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Fix Released
|
Undecided
|
Chad Smith | ||
subiquity |
New
|
Undecided
|
Unassigned |
Bug Description
cloud-init has two interactions with network backplanes
1. to write (or render) network configuration to the approapriate config files for the network system: systemd, netplan, network-manager, ENI, freebsd, netbsd, openbsd. This is done via cloudinit.
2. optionally to bring up the network configuration via "network activation" for datasources discovered only in init boot stage after network is already up[2]
/etc/cloud/
Cloud-init should either:
- Expose system_info: network: activators discovery priorty/order configuration in /etc/cloud/
-- OR --
- make activators aware of customized/
Without this feature, overridden network: renderer priority order to set network-manager as default renderer will result in cloud-init writing /etc/NetworkMan
References:
[1] network renderers discovery: https:/
[2] network activators discovery: https:/
[3] renderer overrides honored: https:/
[4] No activator overrides: https:/
Changed in cloud-init: | |
status: | Fix Committed → Fix Released |
Adding subiquity FYI for ubuntu- desktop- installer. This fix will be required from cloud-init if subiquity installer/ephemeral environment wants to override network: activators: [network-manager] in /etc/cloud/ cloud.cfg. d/*cfg