Proxmox SDN Incorrect Node Deployment

u432897

Member
Dec 15, 2020
7
0
6
34
Hi all,

I'm unsure if I'm running into a bug- I am deploying a few "Simple" zones to a specific proxmox node. However, they show up under the primary node in the "server view" in the web UI even when I select a different node to deploy to under the "node" selector drop down.

Thanks!
 
Hello,

Below is the requested information, thank you for being willing to look into it. After pulling this the zones in the GUI show up as on pve01, yet show up in pve03 config files. Please note these hosts are in a cluster with a third node.

pve03 (host I attempted to deploy to):
pveversion -v
Code:
root@pve03:~# pveversion -v
proxmox-ve: 7.0-2 (running kernel: 5.11.22-7-pve)
pve-manager: 7.0-14+1 (running version: 7.0-14+1/08975a4c)
pve-kernel-helper: 7.1-4
pve-kernel-5.11: 7.0-10
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-5-pve: 5.11.22-10
pve-kernel-5.11.22-4-pve: 5.11.22-9
ceph-fuse: 15.2.14-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-6
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-12
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-3
libpve-storage-perl: 7.0-13
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.13-1
proxmox-backup-file-restore: 2.0.13-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.3-6
pve-cluster: 7.0-3
pve-container: 4.1-1
pve-docs: 7.0-5
pve-edk2-firmware: 3.20210831-1
pve-firewall: 4.2-5
pve-firmware: 3.3-3
pve-ha-manager: 3.3-1
pve-i18n: 2.5-1
pve-qemu-kvm: 6.1.0-1
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-18
smartmontools: 7.2-1
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.1.1-pve3
root@pve03:~#

/etc/pve/sdn/*.cfg
Code:
root@pve03:~# cat /etc/pve/sdn/zones.cfg
simple: zone2
        ipam pve
        nodes pve03

simple: zone5
        ipam pve
        nodes pve03

root@pve03:~#


pve01 (host that shows the zones in the GUI, see screenshot):
pveversion -v
Code:
root@pve01:~# pveversion -v
proxmox-ve: 7.0-2 (running kernel: 5.11.22-5-pve)
pve-manager: 7.0-13 (running version: 7.0-13/7aa7e488)
pve-kernel-helper: 7.1-2
pve-kernel-5.11: 7.0-8
pve-kernel-5.4: 6.4-5
pve-kernel-5.11.22-5-pve: 5.11.22-10
pve-kernel-5.11.22-3-pve: 5.11.22-7
pve-kernel-5.4.128-1-pve: 5.4.128-1
pve-kernel-5.4.114-1-pve: 5.4.114-1
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph-fuse: 15.2.14-pve1
corosync: 3.1.5-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve1
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-10
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-3
libpve-network-perl: 0.6.1
libpve-storage-perl: 7.0-12
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.11-1
proxmox-backup-file-restore: 2.0.11-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.3-6
pve-cluster: 7.0-3
pve-container: 4.1-1
pve-docs: 7.0-5
pve-edk2-firmware: 3.20210831-1
pve-firewall: 4.2-4
pve-firmware: 3.3-2
pve-ha-manager: 3.3-1
pve-i18n: 2.5-1
pve-qemu-kvm: 6.0.0-4
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-16
smartmontools: 7.2-pve2
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.5-pve1
root@pve01:~#

/etc/pve/sdn/*.cfg
Code:
root@pve01:~# cat /etc/pve/sdn/vnets.cfg
root@pve01:~# cat /etc/pve/sdn/zones.cfg
simple: zone2
        ipam pve
        nodes pve03

simple: zone5
        ipam pve
        nodes pve03

root@pve01:~#
 

Attachments

  • 2021-11-17_22-30.png
    2021-11-17_22-30.png
    17.3 KB · Views: 3
Seem to be a display bug on the tree only, the sdn config is correcty not generated.

you can fix it by editing:

/usr/share/perl5/PVE/Network/SDN/Zones.pm
Code:
    for my $id (sort keys %{$zone_cfg->{ids}}) {
        $zone_status->{$id}->{status} = $err_config ? 'pending' : 'available';
    }

replace with
Code:
    for my $id (sort keys %{$zone_cfg->{ids}}) {
        next if defined($zone_cfg->{ids}->{$id}->{nodes}) && !$zone_cfg->{ids}->{$id}->{nodes}->{$nodename};
        $zone_status->{$id}->{status} = $err_config ? 'pending' : 'available';
    }


then restart pvestatd service:

systemctl restart pvestatd


I'll send an official patch next week.
 
Thank you very much for the quick patch and continuing to support SDN! I look forward to the official patch as this is only a UI issue.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!