[Bug 1958676] Re: error: too early for operation, device not yet seeded or device model not acknowledged Install failed

[Alfonso Sanchez-Beato]

This is what I see in a jammy lxd container:

Jan 21 17:47:55 jammy systemd[1]: Starting Load AppArmor profiles managed internally by snapd...
Jan 21 17:47:55 jammy systemd[1]: Condition check resulted in Auto import assertions from block devices being skipped.
Jan 21 17:47:55 jammy systemd[1]: Condition check resulted in Automatically repair incorrect owner/permissions on core devices being skipped.
Jan 21 17:47:55 jammy systemd[1]: Condition check resulted in Wait for the Ubuntu Core chooser trigger being skipped.
Jan 21 17:47:55 jammy snapd-apparmor[1217]: /usr/lib/snapd/snapd-apparmor: 47: ns_stacked: not found
Jan 21 17:47:55 jammy snapd-apparmor[1217]: /usr/lib/snapd/snapd-apparmor: 48: ns_name: not found
Jan 21 17:47:55 jammy systemd[1]: Starting Socket activation for snappy daemon...
Jan 21 17:47:55 jammy snapd-apparmor[1220]: find: ‘/var/lib/snapd/apparmor/profiles/’: No such file or directory
Jan 21 17:47:55 jammy systemd[1]: Listening on Socket activation for snappy daemon.
Jan 21 17:47:55 jammy systemd[1]: Starting Wait until snapd is fully seeded...
Jan 21 17:47:55 jammy systemd[1]: Finished Load AppArmor profiles managed internally by snapd.
Jan 21 17:47:55 jammy systemd[1]: Starting Snap Daemon...
Jan 21 17:47:55 jammy systemd[1]: Condition check resulted in Timer to automatically fetch and run repair assertions being skipped.
Jan 21 17:47:55 jammy systemd[1]: snapd.socket: Deactivated successfully.
Jan 21 17:47:55 jammy systemd[1]: Closed Socket activation for snappy daemon.
Jan 21 17:47:55 jammy systemd[1]: Stopping Socket activation for snappy daemon...
Jan 21 17:47:55 jammy systemd[1]: snapd.socket: Socket service snapd.service already active, refusing.
Jan 21 17:47:55 jammy systemd[1]: Failed to listen on Socket activation for snappy daemon.
Jan 21 17:47:55 jammy systemd[1]: Dependency failed for Snap Daemon.
Jan 21 17:47:55 jammy systemd[1]: snapd.service: Job snapd.service/start failed with result 'dependency'.
Jan 21 17:47:55 jammy systemd[1]: snapd.service: Triggering OnFailure= dependencies.
Jan 21 17:47:55 jammy systemd[1]: Dependency failed for Wait until snapd is fully seeded.
Jan 21 17:47:55 jammy systemd[1]: snapd.seeded.service: Job snapd.seeded.service/start failed with result 'dependency'.
Jan 21 17:47:55 jammy systemd[1]: Starting Failure handling of the snapd snap...

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1958676

Title:
  error: too early for operation, device not yet seeded or device model
  not acknowledged Install failed

Status in launchpad-buildd:
  New
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/launchpad-buildd/+bug/1958676/+subscriptions