Your message dated Fri, 11 Jan 2019 17:44:48 +0100
with message-id <[email protected]>
and subject line Re: udev 240 breaks network interface naming
has caused the Debian Bug report #917128,
regarding udev 240 breaks network interface naming
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.)
--
917128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917128
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: udev
Version: 240-1
Severity: important
After upgrading from 239-15 to 240-1 or higher my network setup breaks.
The breakage is similar to the last one I reported (bug #904198) though
different in detail.
This times all my vlan-devices on a physical device netint are first renamed to
renameX and than udev tries to rename them again but this time it tries to give
them all the name netint - which of course fails.
A setup like the following one should be able to reproduce this problem:
10-netint.link:
[Match]
MACAddress=00:01:2e:77:a5:45
[Link]
Name=netint
WakeOnLan=off
netint.network:
[Match]
Name=netint
[Network]
VLAN=kbs
LinkLocalAddressing=no
DHCP=no
kbs.link
[NetDev]
Name=kbs
Kind=vlan
[VLAN]
Id=10
In the journal you should see something like
kernel: rename31: renamed from kbs
....
systemd-networkd[852]: kbs: Interface name change detected, kbs has been
renamed to rename31
....
[347]: kbs: Failed to rename network interface 31 from 'kbs' to 'netint':
Device or resource busy
....
Downgrading udev to 239-15 fixes it in principle that is this rename does not
happen.
systemd-networkd from 240-1 though crashes with
Assertion 'IN_SET(link->state, LINK_STATE_CONFIGURING,
LINK_STATE_CONFIGURING, LINK_STATE_FAILED, LINK_STATE_LINGER)' failed at
../src/network/network/networkd-link.c:934, function address_handler().
Aborting.
Therefor I also had to downgrade systemd back to 239-15.
Regards,
--
Wolfgang Walter
Studentenwerk München
Anstalt des öffentlichen Rechts
--- End Message ---
--- Begin Message ---
Version: 240-3
On Wed, 9 Jan 2019 22:41:24 +0100 Michael Biebl <[email protected]> wrote:
> On Fri, 28 Dec 2018 15:24:03 +0100 Wolfgang Walter
> <[email protected]> wrote:
> > On Friday, 28 December 2018 15:05:06 CET Michael Biebl wrote:
> > > On Sun, 23 Dec 2018 01:51:00 +0100 Wolfgang Walter
> > >
> > > <[email protected]> wrote:
> > > > systemd-networkd from 240-1 though crashes with
> > > >
> > > > Assertion 'IN_SET(link->state, LINK_STATE_CONFIGURING,
> > > > LINK_STATE_CONFIGURING, LINK_STATE_FAILED, LINK_STATE_LINGER)'
> > > > failed at
> > > > ../src/network/network/networkd-link.c:934, function
> > > > address_handler().
> > > > Aborting.
> > > That error message looks a lot like
> > >
> > > https://github.com/systemd/systemd/issues/11272
> > >
> > > Would you mind testing the pull request at
> > > https://github.com/systemd/systemd/pull/11274
> > >
> > > If this fixes your problem, we can consider cherry-picking that fix.
> >
> > Will do, but can't do it immediately as I'm not back till 2.1.2019
>
> I've pulled this patch and applied it to 240-3.
As I'm pretty sure this is fixed in 240-3, I'm going to close the bug
report.
Please reopen if you still have problems.
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
