cloud-init does not support ignoring a network interface with NetworkManager
Bug #1914784 reported by
Thomas Stringer
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Expired
|
Undecided
|
Unassigned |
Bug Description
NetworkManager will attempt to manage all network interfaces with no configuration. To ignore an interface, you need to specify an ifcfg file in /etc/sysconfig/
Currently, cloud-init does not have support for the NM_CONTROLLED option or any way for a data source to explicitly generate config to tell NetworkManager to ignore a particular interface.
This functionality is currently possible with Netplan, and this report is a request for feature parity in NetworkManager config rendering.
Changed in cloud-init: | |
status: | New → Incomplete |
Changed in cloud-init: | |
status: | New → Triaged |
To post a comment you must log in.
Hi Thomas, thanks for the bug report!
Can you give some example network configuration which does what you expect on a netplan-using system, but doesn't on your NM-using system? Some more details about the NM-using system (e.g. distro) would be good too, to enable us to reproduce the issue.
As an aside: netplan does have support for rendering NetworkManager configuration (as well as networkd config, the default), so I think it's more accurate to describe this as an issue with cloud-init's sysconfig renderer.
I'm moving this to Incomplete, please move it back to New once you've provided the above.
Thanks!
Dan