Your message dated Mon, 20 Feb 2023 01:47:37 +0100
with message-id <2547466.Lt9SDvczpP@bagend>
and subject line Re: Bug#1031137: bridge-utils: No longer recognizes
alternative NIC name (enp5s0)
has caused the Debian Bug report #1031137,
regarding bridge-utils: No longer recognizes alternative NIC name (enp5s0)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1031137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031137
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bridge-utils
Version: 1.7.1-1
Severity: important
I have bridge-utils configured on my Xen server (with SysV-init) and
after today's upgrade round and subsequent reboot, networking did not
come up again.
With that upgrade round bridge-utils went from 1.7-1 to 1.7.1-1.
That server has an iKVM module so I could still access it and found that
`brctl show` did not show any interfaces.
While I do have `net.ifnames=0` in my cmdline I (somehow?) was still
using `enp5s0` in my /etc/network/interfaces file and that worked before.
When I did `brctl addif xenbr0 enp5s0` I did get an interface in
`brctl show`, but it was named `eth0`.
After changing /e/n/i to use `eth0` instead of `enp5s0` and doing
`/etc/init.d/networking restart` everything was working again.
I know there were some changes wrt IPv6 handling, but I'm using IPv4.
The previous kernel was 6.1.4 (6.1.0-1-amd64) so I doubt that that
upgrade triggered this issue, so my guess is that it's 1.7-1 to 1.7.1-1.
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable-security'), (500, 'unstable'),
(1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-4-amd64 (SMP w/32 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled
Versions of packages bridge-utils depends on:
ii libc6 2.36-8
bridge-utils recommends no packages.
Versions of packages bridge-utils suggests:
ii ifupdown 0.8.41
-- no debconf information
--- End Message ---
--- Begin Message ---
On Monday, 13 February 2023 22:12:04 CET Santiago Garcia Mantinan wrote:
> > With that upgrade round bridge-utils went from 1.7-1 to 1.7.1-1.
> > That server has an iKVM module so I could still access it and found that
> > `brctl show` did not show any interfaces.
>
> I'd say it is impossible that it was the bridge-utils change, could you have
> a look at what had changed from the last reboot to this one?
> Maybe something related to systemd or udev or similar stuff, that is, along
> with the kernel, what is typically playing with interface naming.
I just tried booting into 6.1.4 kernel and bridge was not set up, so it's not
caused by a kernel upgrade.
Then I wanted to do other tests, primarily downgrading bridge-utils to 1.7-1,
but it seems something went wrong on the HW side of my server, possibly
(also?) with the iKVM module which is critical for those test ...
> Let's see if you can have more info on the changes so that we can assign
> this bug to the right package.
Before I started those tests I had already concluded that the real anomaly is
that it didn't break a LONG time ago.
I added "net.ifnames=0" to /etc/default/grub on 2020-12-15 ... so my enp5s0
NIC name should have stopped working then.
So it's very well possible that one of the 452 package updates actually fixed a
bug which I somehow 'benefited' from ...
https://xkcd.com/1172/ comes to mind ;-)
As I now have to force-fully shutdown my server and remove the power before I
can start up my server again, and even then it doesn't always work/boot
properly, I'm worried I may be causing (further) HW damage.
While I wanted to test the bridge-utils downgrade to verify it indeed wasn't
the cause of the reported issue, I no longer consider it worth the risk.
Especially since my configuration was wrong and the fix simple.
Sorry for the noise,
Diederik
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
