all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Daniel Berteaud <daniel@firewall-services.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: [PVE-User] SDN issues in 6.4
Date: Wed, 28 Apr 2021 14:10:19 +0200 (CEST)	[thread overview]
Message-ID: <299675699.4847.1619611819855.JavaMail.zimbra@fws.fr> (raw)

Hi. 

Just upgraded a small 3 nodes cluster to 6.4 today. This cluster used the SDN feature with a single VLAN zone, and a few vnets (each one of the vnets using a VLAN tag, and not VLAN-aware themself). 
I see several issues regarding SDN since the upgrade : 



    * The biggest issue is that in Datacenter -> SDN I only see a single node (with the status "available"). The other two do not appear anymore. Without paying attention, I clicked on the "Apply" button. This wiped the /etc/network/interfaces.d/sdn file on the 2 nodes which do not appear anymore, and reloaded their network stack. Needless to say it was a complete failure as all the VM attached to one of those vnets lost network connectivity. I've manually copied this /etc/network/interfaces.d/sdn file from the only working node to the other two for now, but I can't make any change from the GUI now or it'll do the same again 
    * In Datacenter -> SDN -> Zones, my single zone didn't appear anymore. No Zone were displayed at all. But the Vnets correctly showed they were attached to my zone. /etc/pve/sdn/zones.cfg correctly had my zone defined here. I tried adding it again from the GUI, which seemed to work. The only change it made to /etc/pve/sdn/zones.cfg is the new "ipam: pve" option added to the existing zone 


Anyone know what could be wrong ? Why would 2 (out of 3) nodes not showing up in the SDN status anymore ? 

The 3 nodes are fully up to date using the no-subscription repo, here's the complete pveversion : 

pve-manager/6.4-4/337d6701 (running kernel: 5.4.106-1-pve) 
root@pvo5:~# pveversion -v 
proxmox-ve: 6.4-1 (running kernel: 5.4.106-1-pve) 
pve-manager: 6.4-4 (running version: 6.4-4/337d6701) 
pve-kernel-5.4: 6.4-1 
pve-kernel-helper: 6.4-1 
pve-kernel-5.4.106-1-pve: 5.4.106-1 
pve-kernel-5.4.103-1-pve: 5.4.103-1 
pve-kernel-5.4.73-1-pve: 5.4.73-1 
ceph-fuse: 12.2.11+dfsg1-2.1+b1 
corosync: 3.1.2-pve1 
criu: 3.11-3 
glusterfs-client: 5.5-3 
ifupdown: residual config 
ifupdown2: 3.0.0-1+pve3 
ksm-control-daemon: 1.3-1 
libjs-extjs: 6.0.1-10 
libknet1: 1.20-pve1 
libproxmox-acme-perl: 1.0.8 
libproxmox-backup-qemu0: 1.0.3-1 
libpve-access-control: 6.4-1 
libpve-apiclient-perl: 3.1-3 
libpve-common-perl: 6.4-2 
libpve-guest-common-perl: 3.1-5 
libpve-http-server-perl: 3.2-1 
libpve-network-perl: 0.5-1 
libpve-storage-perl: 6.4-1 
libqb0: 1.0.5-1 
libspice-server1: 0.14.2-4~pve6+1 
lvm2: 2.03.02-pve4 
lxc-pve: 4.0.6-2 
lxcfs: 4.0.6-pve1 
novnc-pve: 1.1.0-1 
openvswitch-switch: 2.12.3-1 
proxmox-backup-client: 1.1.5-1 
proxmox-mini-journalreader: 1.1-1 
proxmox-widget-toolkit: 2.5-3 
pve-cluster: 6.4-1 
pve-container: 3.3-5 
pve-docs: 6.4-1 
pve-edk2-firmware: 2.20200531-1 
pve-firewall: 4.1-3 
pve-firmware: 3.2-2 
pve-ha-manager: 3.1-1 
pve-i18n: 2.3-1 
pve-qemu-kvm: 5.2.0-6 
pve-xtermjs: 4.7.0-3 
qemu-server: 6.4-1 
smartmontools: 7.2-pve2 
spiceterm: 3.1-1 
vncterm: 1.6-2 
zfsutils-linux: 2.0.4-pve1 
root@pvo5:~# 


-- 


[ https://www.firewall-services.com/ ] 	
Daniel Berteaud 
FIREWALL-SERVICES SAS, La sécurité des réseaux 
Société de Services en Logiciels Libres 
Tél : +33.5 56 64 15 32 
Matrix: @dani:fws.fr 
[ https://www.firewall-services.com/ | https://www.firewall-services.com ] 


             reply	other threads:[~2021-04-28 12:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-28 12:10 Daniel Berteaud [this message]
2021-04-28 12:14 ` Daniel Berteaud
2021-04-28 12:39 ` Daniel Berteaud
2021-04-28 12:50   ` Gilberto Ferreira
2021-04-28 12:57     ` Daniel Berteaud
2021-04-28 13:04       ` Gilberto Ferreira

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=299675699.4847.1619611819855.JavaMail.zimbra@fws.fr \
    --to=daniel@firewall-services.com \
    --cc=pve-user@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal