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

[Paride Legovini]

Stumbled on this in triage.

The bug description writes about "added functionality for systemd v250
which ubuntu does not have yet", which is not the case anymore.

The bug report didn't have any significant activity in >1 year. Is this
still an issue?

** Changed in: launchpad-buildd
       Status: New => Incomplete

** Changed in: init-system-helpers (Ubuntu)
       Status: Confirmed => Incomplete

** Changed in: snapd (Ubuntu)
       Status: Confirmed => Incomplete

** Changed in: sssd (Ubuntu)
       Status: Confirmed => Incomplete

** Changed in: systemd (Ubuntu)
       Status: Confirmed => Incomplete

-- 
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:
  Incomplete
Status in init-system-helpers package in Ubuntu:
  Incomplete
Status in snapd package in Ubuntu:
  Incomplete
Status in sssd package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

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