debian/test: ignore systemd-remount-fs.service failure in containers (LP: #1991285)
The failure is caused by an entry in /etc/fstab for a disk label
(cloudimg-rootfts) that does not exist on the system. The /etc/fstab is
specific to the lxd images used in autopkgtest, so just ignore this
failure when running in containers.
test-seccomp: accept ENOSYS from sysctl(2) too (LP: #1933090)
upstream and root-unitttest suites are failing on focal-5.15 backports
on test_protect_syscall:
Assertion 'errno == EFAULT' failed at src/test/test-seccomp.c:311
This is due to sysctl being removed completely from 5.5 onwards
(88db0aa2421666d2f73486d15b239a4521983d55)
The assertion now check if either EFAULT or ENOSYS is returned instead.
udev: avoid NIC renaming race with kernel (LP: #2002445)
This consists of the following upstream commits:
* udev: attempt device rename even if interface is up
* sd-netlink: restore altname on error in rtnl_set_link_name
* sd-netlink: do not swap old name and alternative name
* netlink: do not fail when new interface name is already used as an
* netlink: introduce rtnl_get/delete_link_alternative_names()
* udev/net: allow new link name as an altname before renaming happens
A security update was released before this upload was accepted, so these
changes will be released in 245.4-4ubuntu3.21 instead. These changes
need to be reverted so that the security update can be imported
correctly.
debian/test: ignore systemd-remount-fs.service failure on armhf (LP: #1991285)
This appears to have started happening after kernel updates. Since there
have not been any reports of this causing issues in real deployments,
just ignore the failure in autopkgtest.
