GitLab

NetworkManager-1.22.14-1.fc32.x86_64

I'm configuring a vlan interface on top of a normal interface. I pass in kernel arguments like:

rd.neednet=1 vlan=ens2.251:ens2 ip=192.168.122.111::192.168.122.1:255.255.255.0:initrdhost:ens2.251:none:192.168.122.1

nm-initrd-generator spits out something like:

# cat ens2.251.nmconnection 
[connection]
id=ens2.251
uuid=f43743e4-71e9-4a81-bc0c-fa568c136e51
type=vlan
interface-name=ens2.251
multi-connect=1
permissions=

[ethernet]
mac-address-blacklist=

[vlan]
egress-priority-map=
flags=1
id=251
ingress-priority-map=
parent=ens2

[ipv4]
address1=192.168.122.111/24,192.168.122.1
dhcp-hostname=initrdhost
dns=192.168.122.1;
dns-search=
may-fail=false
method=manual

[ipv6]
addr-gen-mode=eui64
dhcp-hostname=initrdhost
dns-search=
method=disabled

[proxy]

It does not output a file for ens2, which means NM will assume it's "unconfigured" and will attempt DHCP on ens2 (this is configurable, but it is the default).

I believe the behavior of legacy initscripts was to not bring up and attempt DHCP on ens2 in this specific scenario.

What should the user expect?