This bug was fixed in the package systemd - 244.1-0ubuntu2
---------------
systemd (244.1-0ubuntu2) focal; urgency=medium
[ Dimitri John Ledkov ]
* shutdown: do not detach autoclear loopback devices
Author: Dimitri John Ledkov
File: debian/patches/shutdown-do-not-detach-autoclear-loopback-devices.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3978d34b59e98cdd01836c41a10442967636b8fc
[ Balint Reczey ]
* Revert upstream commit breaking IPv4 DHCP in LXC containers in 244.1
(LP: #1857123)
File:
debian/patches/Revert-network-if-sys-is-rw-then-udev-should-be-around.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=39c12f8e736afd1b7bdeb13ff6bccaea85020873
systemd (244.1-0ubuntu1) focal; urgency=medium
* New upstream version 244.1
- network: set ipv6 mtu after link-up or device mtu change (LP: #1671951)
- & other changes
* Refresh patches.
- Dropped changes:
* d/p/lp-1853852-*: fix issues with muliplexed shmat calls (LP: #1853852)
Files:
- debian/patches/lp-1853852-seccomp-fix-multiplexed-system-calls.patch
-
debian/patches/lp-1853852-seccomp-mmap-test-results-depend-on-kernel-libseccom.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=382271662c60c339b0a404c7a1772fe5670516ef
*
d/p/lp1671951-network-set-ipv6-mtu-after-link-up-or-device-mtu-cha.patch:
set ipv6 mtu at correct time
* pstore: Don't start systemd-pstore.service in containers.
Usually it is not useful and can also fail making
boot-and-services autopkgtest fail. (LP: #1856729)
File:
debian/patches/pstore-Don-t-start-systemd-pstore.service-in-containers.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=28b5a03769cbed9d3170ebac38508b867530a2d6
* Revert: network: do not drop foreign config if interface is in initialized
state.
This fixes FTBFS with the other network-related reverts.
File:
debian/patches/Revert-network-do-not-drop-foreign-config-if-interface-is.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=22a9fa3bb03ba2a629926af39ea7df81fe33c9b8
systemd (244-3ubuntu5) focal; urgency=medium
[ Dariusz Gadomski ]
*
d/p/lp1762391/0001-user-util-Add-helper-functions-for-gid-lists-operati.patch,
d/p/lp1762391/0002-execute-Restore-call-to-pam_setcred.patch,
d/p/lp1762391/0003-execute-Detect-groups-added-by-PAM-and-merge-them-wi.patch,
d/p/lp1762391/0004-test-Add-tests-for-gid-list-ops.patch,
d/p/lp1762391/0005-execute-add-const-to-array-parameters-where-possible.patch,
d/p/lp1762391/0006-execute-allow-pam_setcred-to-fail-ignore-errors.patch:
- Restore call to pam_setcred (LP: #1762391)
[ Dan Streetman ]
* d/t/storage: without scsi_debug, skip test (LP: #1847816)
systemd (244-3ubuntu4) focal; urgency=medium
* d/p/lp1671951-network-set-ipv6-mtu-after-link-up-or-device-mtu-cha.patch:
set ipv6 mtu at correct time (LP: #1671951)
* d/p/0001-network-rename-linux_configure_after_setting_mtu-to-linux.patch,
d/p/0002-network-add-link-setting_genmode-flag.patch,
d/p/0003-network-if-ipv6ll-is-disabled-enumerate-tentative-ipv6-ad.patch,
d/p/0004-network-drop-foreign-config-after-addr_gen_mode-has-been-.patch:
- drop foreign config and raise interface after setting genmode
(LP: #1845909)
systemd (244-3ubuntu3) focal; urgency=medium
* shutdown: cherry-pick PR#14409 to fix detach of loopback devices
for Ubuntu Core 20
File: debian/patches/shutdown-modernizations-pr-14409.patch
https://github.com/systemd/systemd/pull/14409.diff
systemd (244-3ubuntu2) focal; urgency=medium
* d/p/debian/UBUNTU-Support-system-image-read-only-etc.patch:
- re-add missing bits for timedated.c (LP: #1778936)
-- Balint Reczey <rbal...@ubuntu.com> Wed, 22 Jan 2020 16:27:49 +0100
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
--
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/1856729
Title:
autopkgtest: boot-and-services test fails in armhf containers
Status in systemd package in Ubuntu:
Fix Released
Bug description:
systemd-pstore.service fails but should not be running in a container
anyway:
test_udev (__main__.ServicesTest) ... skipped 'udev does not work in
containers'
======================================================================
FAIL: test_no_failed (__main__.ServicesTest)
No failed units
----------------------------------------------------------------------
Traceback (most recent call last):
File
"/tmp/autopkgtest.z4wDHc/build.x55/src/debian/tests/boot-and-services", line
68, in test_no_failed
self.assertEqual(failed, [])
AssertionError: Lists differ: ['systemd-pstore.service loaded failed fai[37
chars]val'] != []
First list contains 1 additional elements.
First extra element 0:
'systemd-pstore.service loaded failed failed Platform Persistent Storage
Archival'
+ []
- ['systemd-pstore.service loaded failed failed Platform Persistent Storage '
- 'Archival']
----------------------------------------------------------------------
Ran 23 tests in 7.758s
FAILED (failures=1, skipped=6)
autopkgtest [18:52:16]: test boot-and-services: -----------------------]
autopkgtest [18:52:19]: test boot-and-services: - - - - - - - - - - results
- - - - - - - - - -
boot-and-services FAIL non-zero exit status 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1856729/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
