From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <daniel@firewall-services.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 147A5778E2 for <pve-user@lists.proxmox.com>; Wed, 28 Apr 2021 14:14:14 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id E845EDDF8 for <pve-user@lists.proxmox.com>; Wed, 28 Apr 2021 14:14:13 +0200 (CEST) Received: from pmg.fws.fr (pmg.fws.fr [51.91.175.36]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 6C48EDDDE for <pve-user@lists.proxmox.com>; Wed, 28 Apr 2021 14:14:12 +0200 (CEST) Received: from pmg.fws.fr (localhost [127.0.0.1]) by pmg.fws.fr (Proxmox) with ESMTP id 17F31C484B for <pve-user@lists.proxmox.com>; Wed, 28 Apr 2021 14:14:12 +0200 (CEST) Received: from zmproxy.fws.fr (zmproxy.fws.fr [10.29.1.17]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pmg.fws.fr (Proxmox) with ESMTPS id C997BC035E for <pve-user@lists.proxmox.com>; Wed, 28 Apr 2021 14:14:10 +0200 (CEST) Received: from zmproxy.fws.fr (localhost [127.0.0.1]) by zmproxy.fws.fr (Postfix) with ESMTPS id B598D8B4FCA; Wed, 28 Apr 2021 14:14:10 +0200 (CEST) Received: from zmproxy.fws.fr (localhost [127.0.0.1]) by zmproxy.fws.fr (Postfix) with ESMTPS id 9BF198B4FCB; Wed, 28 Apr 2021 14:14:10 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.10.3 zmproxy.fws.fr 9BF198B4FCB DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=firewall-services.com; s=7DAD15A2-D84A-11E9-8F77-BEC4FAA34EBC; t=1619612050; bh=jAs9ZDdjT+dJCfGCb6ywy8RwFpHDP3ebtZMV0W6v5Tg=; h=Date:From:To:Message-ID:MIME-Version; b=J4RxMeduFQ7sJgHdQ4js6GEzCPAwcFhFS1XHq6/j4iG6AObMVzWlZ2slhUtMT5ua9 tG9DJOSAkV6Q0NyRX/e2aVBdPzdeMD00CIet1jWQmsQxbmQQ64IPbGSXiSs9xA4QVS p+GL7LWnIj7pgW9pDGlMmwts4sHSryULnYnhMNqE7yoRzCpho4GEZwk4N9//M1ncvO QJVnOYcUDm+7KeYVys3JXSla4LjPuOmoWnxk5/8vIRwTIsb/G5NVQqGK4vQyN5ceTY CYwvMEIQnnouvQM0t2Dk+AP8580wjKtw6d6bdGLanTWXKm4mL0va01NkqXPwrXW29Q Sgp1dnRqWFBKg== Received: from zmstore.fws.fr (zmstore.fws.fr [10.29.3.15]) by zmproxy.fws.fr (Postfix) with ESMTP id 951B28B4FCA for <pve-user@lists.proxmox.com>; Wed, 28 Apr 2021 14:14:10 +0200 (CEST) Date: Wed, 28 Apr 2021 14:14:10 +0200 (CEST) From: Daniel Berteaud <daniel@firewall-services.com> To: Proxmox VE user list <pve-user@lists.proxmox.com> Message-ID: <371322183.4890.1619612050577.JavaMail.zimbra@fws.fr> In-Reply-To: <299675699.4847.1619611819855.JavaMail.zimbra@fws.fr> References: <299675699.4847.1619611819855.JavaMail.zimbra@fws.fr> MIME-Version: 1.0 X-Originating-IP: [192.168.7.101] X-Mailer: Zimbra 8.8.15_GA_4018 (ZimbraWebClient - GC89 (Linux)/8.8.15_GA_4026) Thread-Topic: SDN issues in 6.4 Thread-Index: iXeBWa76wCf0dmkyWJYKWdvjhuFpQXGWxlOM X-SPAM-LEVEL: Spam detection results: 0 AWL -0.247 Adjusted score from AWL reputation of From: address DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain HTML_MESSAGE 0.001 HTML included in message KAM_NUMSUBJECT 0.5 Subject ends in numbers excluding current years RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_REMOTE_IMAGE 0.01 Message contains an external image URI_TRUNCATED 0.001 Message contained a URI which was truncated Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: Re: [PVE-User] SDN issues in 6.4 X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list <pve-user.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-user>, <mailto:pve-user-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-user/> List-Post: <mailto:pve-user@lists.proxmox.com> List-Help: <mailto:pve-user-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user>, <mailto:pve-user-request@lists.proxmox.com?subject=subscribe> X-List-Received-Date: Wed, 28 Apr 2021 12:14:14 -0000 ----- Le 28 Avr 21, =C3=A0 14:10, Daniel Berteaud <daniel@firewall-services= .com> a =C3=A9crit :=20 > 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 u= sing 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 n= ode (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 fa= ilure 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 GU= I 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 attach= ed to my > zone. /etc/pve/sdn/zones.cfg correctly had my zone defined here. I tri= ed adding > it again from the GUI, which seemed to work. The only change it made t= o > /etc/pve/sdn/zones.cfg is the new "ipam: pve" option added to the exi= sting zone Also, I have a lot of errors like this now :=20 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.=20 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.=20 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.=20 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.=20 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.=20 On all the 3 nodes (even the one which still appears in the SDN Status page= on the GUI)=20 --=20 [ https://www.firewall-services.com/ ] =09 Daniel Berteaud=20 FIREWALL-SERVICES SAS, La s=C3=A9curit=C3=A9 des r=C3=A9seaux=20 Soci=C3=A9t=C3=A9 de Services en Logiciels Libres=20 T=C3=A9l : +33.5 56 64 15 32=20 Matrix: @dani:fws.fr=20 [ https://www.firewall-services.com/ | https://www.firewall-services.com ]= =20