public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Gabriel Goller <g.goller@proxmox.com>
To: Christoph Heiss <c.heiss@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [PATCH ifupdown2] fix #8117: backport upstream fix for unavailable bond slaves
Date: Thu, 15 Oct 2026 16:49:16 +0200	[thread overview]
Message-ID: <atDnmYUQXNM9U6Uo@luna.proxmox.com> (raw)
In-Reply-To: <26eeb088-76f6-4a17-9d9c-2ae3fb13310f@proxmox.com>

On 15.10.2026 16:43, Christoph Heiss wrote:
> Thanks for tackling this!
> 
> On 10/8/26 12:23, Gabriel Goller wrote:
> > A missing slave at boot can abort bond setup before available slaves are
> > enslaved, leaving the bond broken. Backport upstream PR #355 to continue
> > setup after single slave failures.
> > 
> > Upstream-Link: https://github.com/CumulusNetworks/ifupdown2/pull/355
> > Fixes: https://bugzilla.proxmox.com/show_bug.cgi?id=8117
> > 
> > Signed-off-by: Gabriel Goller <g.goller@proxmox.com>
> 
> Tested this with a similar setup to [0], just with `bond-slaves` set to:
> 
>   bond-slaves doesnotexist enp6s20.1 enp6s21.1
> 
> Please consider this:
> 
> Tested-by: Christoph Heiss <c.heiss@proxmox.com>
> 
> [0]
> https://lore.proxmox.com/pve-devel/DM5AYOQZLL1E.2J6DHNGY4O0N4@proxmox.com/
> 
> [..]
> 
> > +diff --git a/tests/unit/test_bond.py b/tests/unit/test_bond.py
> > +new file mode 100644
> > +index 00000000..01fab468
> > +--- /dev/null
> > ++++ b/tests/unit/test_bond.py
> > +@@ -0,0 +1,103 @@
> > ++"""Bond regression tests; run with python3 -m unittest discover -s tests/unit."""
> 
> These tests don't run when doing a `make deb` with our (downstream)
> packaging:
> 
>   dh_auto_test -O--buildsystem=pybuild
>   I: pybuild base:311: cd
> [..]ifupdown2/ifupdown2-3.3.0-1+pmx12/.pybuild/cpython3_3.13_ifupdown2/build;
> python3.13 -m unittest discover -v
> 
>   ----------------------------------------------------------------------
>   Ran 0 tests in 0.000s
> 
>   NO TESTS RAN
> 
> IMO would make sense to have them run on a `make deb` too.

Hmm good catch, didn't run the tests :/

This should be fixed with something like:

 diff --git a/debian/rules b/debian/rules
 index cc9547dce6..0443852924 100755
 --- a/debian/rules
 +++ b/debian/rules
 @@ -3,6 +3,7 @@
  #export DH_VERBOSE=1
  export PYBUILD_NAME=ifupdown2
  export PYBUILD_INSTALL_ARGS=--install-lib=/usr/share/ --install-scripts=/usr/share/
 +export PYBUILD_TEST_ARGS=--start-directory {dir}/tests/unit
 
  %:
  	dh $@ --with=python3 --buildsystem=pybuild

I'll send a patch.

Thanks for the review!




      reply	other threads:[~2026-10-15 14:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08 10:23 [PATCH ifupdown2] fix #8117: backport upstream fix for unavailable bond slaves Gabriel Goller
2026-10-15 14:43 ` Christoph Heiss
2026-10-15 14:49   ` Gabriel Goller [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=atDnmYUQXNM9U6Uo@luna.proxmox.com \
    --to=g.goller@proxmox.com \
    --cc=c.heiss@proxmox.com \
    --cc=pve-devel@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal