even with reverted init-system-helps snapd units fail to start during launchpad-buildd
https://launchpad.net/~ubuntu-core-service/+snap/core22/+build/1650698 Setting up snapd (2.54.2+22.04ubuntu1) ... Created symlink /etc/systemd/system/multi-user.target.wants/snapd.apparmor.service → /lib/systemd/system/snapd.apparmor.service. Created symlink /etc/systemd/system/multi-user.target.wants/snapd.autoimport.service → /lib/systemd/system/snapd.autoimport.service. Created symlink /etc/systemd/system/multi-user.target.wants/snapd.core-fixup.service → /lib/systemd/system/snapd.core-fixup.service. Created symlink /etc/systemd/system/multi-user.target.wants/snapd.recovery-chooser-trigger.service → /lib/systemd/system/snapd.recovery-chooser-trigger.service. Created symlink /etc/systemd/system/multi-user.target.wants/snapd.seeded.service → /lib/systemd/system/snapd.seeded.service. Created symlink /etc/systemd/system/cloud-final.service.wants/snapd.seeded.service → /lib/systemd/system/snapd.seeded.service. Unit /lib/systemd/system/snapd.seeded.service is added as a dependency to a non-existent unit cloud-final.service. Created symlink /etc/systemd/system/multi-user.target.wants/snapd.service → /lib/systemd/system/snapd.service. Created symlink /etc/systemd/system/timers.target.wants/snapd.snap-repair.timer → /lib/systemd/system/snapd.snap-repair.timer. Created symlink /etc/systemd/system/sockets.target.wants/snapd.socket → /lib/systemd/system/snapd.socket. Created symlink /etc/systemd/system/final.target.wants/snapd.system-shutdown.service → /lib/systemd/system/snapd.system-shutdown.service. snapd.failure.service is a disabled or a static unit not running, not starting it. snapd.snap-repair.service is a disabled or a static unit not running, not starting it. Job failed. See "journalctl -xe" for details. A dependency job for snapd.service failed. See 'journalctl -xe' for details. A dependency job for snapd.seeded.service failed. See 'journalctl -xe' for details. Processing triggers for libc-bin (2.34-0ubuntu3) ... error: too early for operation, device not yet seeded or device model not acknowledged Install failed ** Also affects: snapd (Ubuntu) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: init-system-helpers (Ubuntu) Importance: Critical => Undecided -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1958676 Title: Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142. Status in init-system-helpers package in Ubuntu: New Status in snapd package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: https://launchpad.net/~ubuntu-core-service/+snap/core22/+build/1650565 New deb-systemd-invoke added functionality for systemd v250 which ubuntu does not have yet. But it also appears to break postinst calls to deb-systemd-invoke, at least as seen during snap builds in lxd containers operated by launchpad-buildd. I wonder if there is a regression in new code, or new systemd, which may warrant a revert. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1958676/+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
