Ubuntu
sssd package

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

Bug #1958676 reported by Dimitri John Ledkov
22
This bug affects 1 person
Affects Status Importance Assigned to Milestone
launchpad-buildd
Expired
Undecided
Unassigned
init-system-helpers (Ubuntu)
Expired
Undecided
Unassigned
snapd (Ubuntu)
Expired
Undecided
Unassigned
sssd (Ubuntu)
Expired
Undecided
Unassigned
systemd (Ubuntu)
Expired
Undecided
Unassigned

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.

Dimitri John Ledkov (xnox)
Changed in init-system-helpers (Ubuntu):
importance: Undecided → Critical
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

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

Changed in init-system-helpers (Ubuntu):
importance: Critical → Undecided
Dimitri John Ledkov (xnox)
summary: - 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
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

I guess i can modify init-system-helpers again, to dump journal from the build such that we can see what is going on.

Revision history for this message
Maciej Borzecki (maciek-borzecki) wrote :

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 dependencies failed. So by the time `snap install core22` ran snapd was still not ready. Getting the contents of the journal to see what exactly failed would be great.

Revision history for this message
Alfonso Sanchez-Beato (alfonsosanchezbeato) wrote :

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...

Revision history for this message
Alfonso Sanchez-Beato (alfonsosanchezbeato) wrote :

Full journal attached

Revision history for this message
Alfonso Sanchez-Beato (alfonsosanchezbeato) wrote :

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

Revision history for this message
Tired Sysadmin (wearyofallthiscrap) wrote :

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 /etc/systemd/system/sssd.service.wants/sssd-nss.socket → /lib/systemd/system/sssd-nss.socket.
Created symlink /etc/systemd/system/sssd.service.wants/sssd-pam-priv.socket → /lib/systemd/system/sssd-pam-priv.socket.
Created symlink /etc/systemd/system/sssd.service.wants/sssd-pam.socket → /lib/systemd/system/sssd-pam.socket.
Created symlink /etc/systemd/system/sssd.service.wants/sssd-ssh.socket → /lib/systemd/system/sssd-ssh.socket.
Created symlink /etc/systemd/system/sssd.service.wants/sssd-sudo.socket → /lib/systemd/system/sssd-sudo.socket.
Created symlink /etc/systemd/system/multi-user.target.wants/sssd.service → /lib/systemd/system/sssd.service.
sssd-autofs.service is a disabled or a static unit, not starting it.
sssd-nss.service is a disabled or a static unit, not starting it.
sssd-pam.service is a disabled or a static unit, not starting it.
sssd-ssh.service is a disabled or a static unit, not starting it.
sssd-sudo.service is a disabled or a static unit, not starting it.
Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142.
Setting up sssd-proxy (2.6.3-1ubuntu3.1) ...
Setting up sssd-ad-common (2.6.3-1ubuntu3.1) ...
Created symlink /etc/systemd/system/sssd.service.wants/sssd-pac.socket → /lib/systemd/system/sssd-pac.socket.
sssd-pac.service is a disabled or a static unit, not starting it.
Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142.
Setting up sssd-krb5-common (2.6.3-1ubuntu3.1) ...
Setting up libsmbclient:amd64 (2:4.15.5~dfsg-0ubuntu5.1) ...
Setting up sssd-krb5 (2.6.3-1ubuntu3.1) ...
Setting up sssd-ldap (2.6.3-1ubuntu3.1) ...
Setting up sssd-ad (2.6.3-1ubuntu3.1) ...
Setting up sssd-ipa (2.6.3-1ubuntu3.1) ...
Setting up sssd (2.6.3-1ubuntu3.1) ...

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in init-system-helpers (Ubuntu):
status: New → Confirmed
Changed in snapd (Ubuntu):
status: New → Confirmed
Changed in sssd (Ubuntu):
status: New → Confirmed
Changed in systemd (Ubuntu):
status: New → Confirmed
Revision history for this message
Paride Legovini (paride) wrote :

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
Revision history for this message
Clare Rodger (clarosoft) wrote :

Yes I can confirm this is still an issue for me

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for systemd (Ubuntu) because there has been no activity for 60 days.]

Changed in systemd (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for sssd (Ubuntu) because there has been no activity for 60 days.]

Changed in sssd (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for init-system-helpers (Ubuntu) because there has been no activity for 60 days.]

Changed in init-system-helpers (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]

Changed in snapd (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for launchpad-buildd because there has been no activity for 60 days.]

Changed in launchpad-buildd:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.