From: Daniel Berteaud <daniel@firewall-services.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] SDN issues in 6.4
Date: Wed, 28 Apr 2021 14:14:10 +0200 (CEST) [thread overview]
Message-ID: <371322183.4890.1619612050577.JavaMail.zimbra@fws.fr> (raw)
In-Reply-To: <299675699.4847.1619611819855.JavaMail.zimbra@fws.fr>
----- Le 28 Avr 21, à 14:10, Daniel Berteaud <daniel@firewall-services.com> a écrit :
> 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
Also, I have a lot of errors like this now :
Apr 28 13:14:16 pvo6 pvestatd[2624]: sdn status update error: cannot lookup undefined type! at /usr/share/perl5/PVE/Network/SDN/Zones.pm line 260.
Apr 28 13:14:25 pvo6 pvestatd[2624]: sdn status update error: cannot lookup undefined type! at /usr/share/perl5/PVE/Network/SDN/Zones.pm line 260.
Apr 28 13:14:35 pvo6 pvestatd[2624]: sdn status update error: cannot lookup undefined type! at /usr/share/perl5/PVE/Network/SDN/Zones.pm line 260.
Apr 28 13:14:46 pvo6 pvestatd[2624]: sdn status update error: cannot lookup undefined type! at /usr/share/perl5/PVE/Network/SDN/Zones.pm line 260.
Apr 28 13:14:55 pvo6 pvestatd[2624]: sdn status update error: cannot lookup undefined type! at /usr/share/perl5/PVE/Network/SDN/Zones.pm line 260.
On all the 3 nodes (even the one which still appears in the SDN Status page on the GUI)
--
[ 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 ]
next prev parent reply other threads:[~2021-04-28 12:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 12:10 Daniel Berteaud
2021-04-28 12:14 ` Daniel Berteaud [this message]
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=371322183.4890.1619612050577.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox