** No longer affects: lxd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1914062
Title:
NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start
in
This bug was fixed in the package systemd - 247.3-1ubuntu4
---
systemd (247.3-1ubuntu4) hirsute; urgency=medium
[ Dimitri John Ledkov ]
*
d/p/debian/UBUNTU-resolved-Mitigate-DVE-2018-0001-by-retrying-NXDOMAIN-with.patch:
Patch updated to reduce log level to debug
@stgraber Thank you. I'm including the originally proposed patch in the
next systemd upload and will switch to v248 when it is out to include
the full fix. Most likely final v248 will be out in a few weeks.
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Balint Reczey (rbalint)
** Changed in: systemd (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1914062
Title:
NetworkManager-wait-online.service in
This bug was fixed in the package network-manager - 1.30.0-1ubuntu1
---
network-manager (1.30.0-1ubuntu1) hirsute; urgency=medium
* Resynchronize on Debian, remaining changes:
- Use systemd-resolved instead of dnsmasq
- debian/control:
+ Depend on isc-dhcp-client
Christian submitted https://github.com/systemd/systemd/pull/18559 which
got turned into https://github.com/systemd/systemd/pull/18684 and has
now been merged in upstream systemd.
We've both tested the resulting systemd and can confirm that /run/udev is now
properly populated.
Please cherry-pick
This bug was fixed in the package systemd - 247.3-1ubuntu2
---
systemd (247.3-1ubuntu2) hirsute; urgency=medium
[ Stéphane Graber ]
* Revert the change to udevd service and sockets. They must start in LXC.
LXD containers do have proper uevent handling and actively send
@seb128 please also include the fix for n-m tests failing due to MAC
changes to let systemd 247.1-4ubuntu1 migrate.
** Changed in: network-manager (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Just FTR, note that the change in NM upstream was needed so the network-
manager snap was able to correctly detect if udevd is running. We
currently build the snap from the source package + some patches
including this one. But, the long term target is to be able to create
the snap by simply
> @seb128 could you please patch network-manager 1.28 to behave in LXC
like it did in 1.26 to let it migrate and not fail in LXC with systemd
247 until the udevd behaviour is fixed in LXC?
alright, I can temporarily revert the commit that made it use udev under
lxc
--
You received this bug
@stgraber Thank you for assisting with aligning udevs's behaviour with
LXD. I've added the tests-in-lxd autopkgtests to ensure catching issues
in LXD earlier. I'd be happy to add more tests in systemd's autopkgtest
to not let udevd regress in LXD.
@xnox I don't like to idea of letting services be
** Changed in: systemd (Ubuntu)
Assignee: Ubuntu containers team (ubuntu-lxc) => Christian Brauner
(cbrauner)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1914062
We should probably ignore failure to start NetworkManager-wait-
online.service in the autopkgtests for now.
** Changed in: systemd (Ubuntu)
Importance: High => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: network-manager (Ubuntu)
Status: New => Invalid
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Ubuntu containers team (ubuntu-lxc)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
This is a systemd/udev bug. We're aware of the CONTAINER_INTERFACE and
it being wrong doesn't mean we need to change LXD to make it similarly
wrong.
LXD containers need to have udevd running to function properly, so you'll need
to undo that change.
If there is a bug in how udevd now behaves,
@stgraber or work with systemd upstream to extend the container API.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1914062
Title:
NetworkManager-wait-online.service in
@stgraber nothing should break honoring
https://systemd.io/CONTAINER_INTERFACE/ and we are in constant uphill
battle with systemd and other upstreams checking /sys's ro status.
Detecting the init system is easy, please do it in LXD. It may make
sense to allow the user to override that and force
Making /sys read-only will break very very many things that we have no
intention of breaking.
LXD is also completely init system agnostic and we have no idea what the init
system in a particular container may be.
** Changed in: lxd (Ubuntu)
Status: New => Invalid
--
You received this
@seb128 I tried remounting /sys in systemd but it created other issues.
I've fixed udevd to not start in lxc in systemd, but this is all systemd can
do. Please detect running udev in network-manager without assuming that rw /sys
implies running udev.
@ LXD devs, please check if the init to
** Tags removed: rls-hh-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1914062
Title:
NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start
in
** Tags added: fr-1102
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1914062
Title:
NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start
in LXC
Status
downgrading systemd to the focal version in the lxc container fixes the
issue
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1914062
Title:
l16 is was creates the issue
** Attachment added: "Example program showing the bug"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1914062/+attachment/5459445/+files/bug.c
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Reassigning to systemd but it could be a lxc issue
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1914062
Title:
NetworkManager-wait-online.service in 1.28.0-2ubuntu1
The example works outside of the container or in a focal instance,
commenting l30 makes it work on hirsute
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1914062
Title:
Investigating the issue, udev fails to enumerate devices in the lxc
environment when udev_enumerate_add_match_is_initialized is called. The
same test program works in a focal instance.
Discussing the issue on the LXD channel it was raised that the systemd
udev changes in 247 could be creating
There is here a change in behavior in lxc/lxd. Running
https://paste.ubuntu.com/p/vz7SXcX3K9/:
On hirsute lxd container:
root@hirsute:~# ./test
access errno 13
path is read only: 0
root@hirsute:~# mount | grep 'sysfs on /sys '
sysfs on /sys type sysfs (rw,relatime)
On focal lxd container:
Reported upstream
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/650
** Bug watch added:
gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #650
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/650
--
You received this bug notification
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
** Changed in: network-manager (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
>From the log you linked:
Get:263 http://ftpmaster.internal/ubuntu hirsute-proposed/main amd64
network-manager amd64 1.28.0-2ubuntu1 [2002 kB]
** Package changed: systemd (Ubuntu) => network-manager (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
the log also has that warning that seems new
[0;1;39mInvalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you
should use systemd-escape?).[0m
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Retrying with the release pocket version of network-manager it fails the same
way
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210129_131945_c0965@/log.gz
reassigning to systemd
** Package changed:
The regression isn't due to the network-manager update, could foundation
help investigating the systemd side of things?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
33 matches
Mail list logo
