Looks like this is some actual regression somewhere. systemd-resolved's
ExecStartPost fails to start:
Process: 4728 ExecStartPost=/bin/sh -c [ ! -e /run/resolvconf/enable-
updates ] || echo "nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-
resolved (code=exited, status=127)
Aug 15 07:16:39 autopkgtest sh[4659]: sed: error while loading shared
libraries: cannot restore segment prot after reloc: Operation not permitted
Aug 15 07:16:39 autopkgtest sh[4659]: sed: error while loading shared
libraries: cannot restore segment prot after reloc: Operation not permitted
In 231, several units got some privilege reduction:
MemoryDenyWriteExecute=yes
SystemCallFilter=~@clock @cpu-emulation @debug @keyring @module @mount
@obsolete @raw-io
Apparently the former upsets sed (which is called by resolvconf) on
ppc64el. So we need to disable the privilege reduction for
/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf
** Changed in: systemd (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609740
Title:
please investigate ppc64el networkd-test.py failure
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1609740/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
