[Bug 1958676] Re: error: too early for operation, device not yet seeded or device model not acknowledged Install failed
Tired Sysadmin
1958676 at bugs.launchpad.net
Thu Jul 28 18:22:54 UTC 2022
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) ...
** Also affects: sssd (Ubuntu)
Importance: Undecided
Status: New
--
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 sssd 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
More information about the foundations-bugs
mailing list