VM IP assigned from wrong VNET, through cloud-init and not DHCP

[kmorwath]

I have a 8.3.0 cluster (six nodes). I'm trying to use the SDN feature, but I encountered issues with IP assignements. I created:

• A vmbr1 OVS bridge (on each node) on a dedicated bridge interface (eno3). I did not assign an IP/gateway yet, it's not clear to me on which network they should reside. eno3 physical port is connected to a trunk port on a switch.
• Created two VLAN Zones (V120 and V130) using the vmbr1 bridge and pve IPAM
• Created two VNets, one for each Zone, Mgmt (VLAN 120) and Payload (VLAN 130)
• In the Mgmt VNet, I created the 192.168.120.0/24 subnet, gateway 192.168.120.1, SNAT disabled, and assigned a DHCP range 192.168.120.10-192.168.120.200
• In the Payload VNet, I created the 10.100.0.0/16 subnet, gateway 10.100.0.1, SNAT disabled DHCP range 10.100.0.10 - 10.100.250.254
• I created a test Ubuntu 22 LTS VM - installed it directly from the official latest ISO. It has only one network device, assigned to the Mgmt "bridge", and using VirtIO.

I expected it to get an IP via DHCP from the Mgmt VNET192.168.120.x range. Instead it gets and IP from the Payload VNET 10.100.x.x range, and does it through cloud-init, the netplan configuration files has a static IP configuration created by cloud-init (50-cloud-init.yaml file). There is no cloud-init disk assigned to the VM. And the IP doesn't appear in the pve IPAM list.

The VM is on the correct VLAN, through. The gateways are VLAN interfaces on an external pfSense appliance that allows internet access - I have to manually change the IP address to set in the correct subnet to reach the internet.

Do I need additional configuration for the OVS bridge (IP and gateway)? Which one should I use, the cluster management network? Or DHCP is available only for "simple" Zones?

Still I don't understand where the cloud-init assigned IP comes from, and why they are from the wrong VNet.

 

[kmorwath]

OK, I found in the doc "Currently only Simple Zones have support for automatic DHCP" - it would be useful to repeat it in the Zones documentation.

Still, why cloud-init uses an IP from a VNet not assigned to the VM?