[Expired for launchpad-buildd because there has been no activity for 60
days.]
** Changed in: launchpad-buildd
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
[Expired for snapd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: snapd (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
[Expired for sssd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: sssd (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
[Expired for init-system-helpers (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: init-system-helpers (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: systemd (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Yes I can confirm this is still an issue for me
--
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/1958676
Title:
error: too early for operation, device not yet seeded or
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 changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: sssd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: init-system-helpers (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I see the same "could not execute" error on a fresh 22.04 Jammy system,
when installing the 'sssd' metapackage. The install ends with:
Created symlink /etc/systemd/system/sssd.service.wants/sssd-autofs.socket →
/lib/systemd/system/sssd-autofs.socket.
Created symlink
With systemd debug trace enabled.
Look for
Got message type=method_call sender=n/a destination=org.freedesktop.systemd1
path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager
member=RestartUnit cookie=22 reply_cookie=0 signature=ss error-name=n/a
error-message=n/a
**
Full journal attached
** Attachment added: "journal-fail.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1958676/+attachment/5556929/+files/journal-fail.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
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]:
The error indicates that snapd is still in the process of early init &
setting up device. Ideally it's enough to wait for seed.loaded event,
(snap wait system seed.loaded). This is what snapd.seeded.service does,
but from the piece of log you provided, the service did not start,
because its
I guess i can modify init-system-helpers again, to dump journal from the
build such that we can see what is going on.
** Also affects: launchpad-buildd
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Summary changed:
- Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142.
+ error: too early for operation, device not yet seeded or device model not
acknowledged Install failed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
18 matches
Mail list logo