FS#55993 - [systemd] 235.0-1 breaks systemd-networkd in LXD/LXC container

Attached to Project: Arch Linux
Opened by Peter (hippopete) - Saturday, 14 October 2017, 20:24 GMT
Last edited by Eli Schwartz (eschwartz) - Sunday, 15 October 2017, 07:43 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

As of systemd 2.35.0-1 systemd-networkd.service fails when launched in lxd managed lxc container.
lxd is hosted on ubuntu16.04.4

No such issues in systemd-234.11-8



Additional info:
* systemd 2.35.0-1
* lxd 2.0.10

systemctl status systemd-networkd
Oct 14 21:54:44 arch-x2btc systemd[1]: systemd-networkd.service: Failed to reset devices.list: Operation not permitted
Oct 14 21:54:44 arch-x2btc systemd[1]: systemd-networkd.service: Failed to set invocation ID on control group /system.slice/systemd-networkd.service, ignoring: Operation not permitted
Oct 14 21:54:44 arch-x2btc systemd[1]: Starting Network Service...
Oct 14 21:54:44 arch-x2btc systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=237/KEYRING
Oct 14 21:54:44 arch-x2btc systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Oct 14 21:54:44 arch-x2btc systemd[1]: Failed to start Network Service.
Oct 14 21:54:44 arch-x2btc systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart.
Oct 14 21:54:44 arch-x2btc systemd[1]: systemd-networkd.service: Start request repeated too quickly.
Oct 14 21:54:44 arch-x2btc systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Oct 14 21:54:44 arch-x2btc systemd[1]: Failed to start Network Service.




Steps to reproduce:

pacman -Syu

restart/reboot container


This task depends upon

Closed by  Eli Schwartz (eschwartz)
Sunday, 15 October 2017, 07:43 GMT
Reason for closing:  Upstream
Additional comments about closing:  Following the links in the linked upstream issue, this seems to be an upstream regression that will not be changed.
Comment by loqs (loqs) - Saturday, 14 October 2017, 21:53 GMT

Loading...