public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	alexandre derumier <aderumier@odiso.com>,
	pve-devel <pve-devel@pve.proxmox.com>
Subject: Re: [pve-devel] debian11 ifslave bonding bug (with ifupdown1)
Date: Wed, 25 Aug 2021 10:46:10 +0200	[thread overview]
Message-ID: <1f540c95-6922-8dee-7143-92ce692caa19@proxmox.com> (raw)
In-Reply-To: <5f2911bdc581cd9ff71eb935d5b83fb4847036c8.camel@odiso.com>

Hi,

On 25/08/2021 07:55, alexandre derumier wrote:
> multiple users have reported problems if ifenslave (ifupdown1),
> (maintly upgrade from proxmox6 without switch to ifupdown2)

FWIW, I thought about adding a note to the pve6to7 upgrade checker script
to recommend switching to ifupdown2, IMO most probably would fare better with
that, more features (e.g., live reload) and more and more of our setups run it
too, so it gets good testing too.
 
> 
> when physical interfaces have "auto .."
> 
> auto eth0
> iface eth0
>  ...
> auto eth1
> iface eth1 
>   ....
> 
> auto bond0
>   iface bond0
>   bond-slaves eth0 eth1
> 
> 
> it seem to come from a bug in ifenslave pre-up script
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968368
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990428
> 
> patch here:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?att=2;bug=968368;filename=ifenslave-args.diff;msg=5
> 

did you by chance verify that patch already?

> Maybe it could be great to add a note in the upgrade procedure about
> this until it's fixed. (or maybe provide a fixed proxmox ifenslave
> package)

IMO it's always better to ship a fixed package if possible, upgrade notes tend
to get missed by a not negligible percentage of users.

cheers,
Thomas




      reply	other threads:[~2021-08-25  8:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-25  5:55 alexandre derumier
2021-08-25  8:46 ` Thomas Lamprecht [this message]

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=1f540c95-6922-8dee-7143-92ce692caa19@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=aderumier@odiso.com \
    --cc=pve-devel@lists.proxmox.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