public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Daniel Berteaud <daniel@firewall-services.com>
To: pve-devel <pve-devel@pve.proxmox.com>
Subject: [pve-devel] Regression in ifupdown2 with templates ?
Date: Thu, 16 Jul 2020 08:04:42 +0200 (CEST)	[thread overview]
Message-ID: <820036375.40230.1594879482824.JavaMail.zimbra@fws.fr> (raw)

Hi there. 

I'm running a 5 nodes PVE6 cluster, and I'm using ifupdown2 templating features to create vxlan overlays between my nodes (setup this before the SDN feature went live). Here's a snippet of my /etc/network/interfaces : 

%for i in range(1, 6): 
%for v in range(0, 21): 
auto vxlan${i*100+v} 
iface vxlan${i*100+v} 
vxlan-id ${i*100+v} 
vxlan-mcastgrp 225.20.118.1 
vxlan-physdev enp132s0f0.2018 
bridge-access ${i*100+v} 
%endfor 
%endfor 

auto vmbr0 
iface vmbr0 inet manual 
%for i in range(1, 6): 
bridge-ports glob vxlan${i*100}-${i*100+20} 
%endfor 
bridge-stp off 
bridge-fd 0 
bridge-vlan-aware yes 
bridge-vids 2-4094 


Everything is working fine with ifupdown2-2.0.1-1+pve10 but if I update ifupdown to v 3.0.0-1+pve2, my vxlan aren't created anymore. An ifreload -a outputs these errors : 

root@pve4:~# ifreload -a 
warning: unable to set template lookup path /etc/network/ifupdown2/templates ('NoneType' object is not callable): are you sure 'python-mako'is installed? 
warning: /etc/network/interfaces: line33: vxlan${i*100+v}: unexpected characters in interface name 
error: /etc/network/interfaces: line37: iface vxlan${i*100+v}: invalid syntax '%endfor' 
error: /etc/network/interfaces: line38: iface vxlan${i*100+v}: invalid syntax '%endfor' 
error: /etc/network/interfaces: line44: iface vmbr0: invalid syntax '%endfor' 
warning: vmbr0: error parsing glob expression 'vxlan${i*100}-${i*100+20}' (supported glob syntax: swp1-10.300 or swp[1-10].300 or swp[1-10]sub[0-4].300 
warning: vmbr0: error parsing glob expression 'vxlan${i*100}-${i*100+20}' (supported glob syntax: swp1-10.300 or swp[1-10].300 or swp[1-10]sub[0-4].300 
error: vxlan${i*100+v}: invalid vxlan-id '${i*100+v}' 
warning: vxlan${i*100+v}: invalid use of bridge attribute (bridge-access) on non-bridge stanza 
error: netlink: vxlan${i*100}-${i*100+20}: cannot enslave link vxlan${i*100}-${i*100+20} to vmbr0: interface name exceeds max length of 15 
warning: vmbr0: error parsing glob expression 'vxlan${i*100}-${i*100+20}' (supported glob syntax: swp1-10.300 or swp[1-10].300 or swp[1-10]sub[0-4].300 
error: vmbr0: bridge port vxlan${i*100}-${i*100+20} does not exist 


(yes, python-mako is installed) 

I had to downgrade ifupdown2 on all my nodes to get my network stack back online. 

Is there a regression with templating support in ifupdown2 v3 or has something changed and must be adapted ? 

Cheers, 
Daniel 
-- 


[ 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:[~2020-07-16  6:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-16  6:04 Daniel Berteaud [this message]
2020-07-16  7:29 ` Alexandre DERUMIER
2020-07-16  8:14   ` Daniel Berteaud
2020-07-16  8:38     ` Alexandre DERUMIER
2020-07-16  9:17       ` Daniel Berteaud
2020-07-16  9:48         ` Alexandre DERUMIER

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=820036375.40230.1594879482824.JavaMail.zimbra@fws.fr \
    --to=daniel@firewall-services.com \
    --cc=pve-devel@pve.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal