[Bug 1958676] Re: error: too early for operation, device not yet seeded or device model not acknowledged Install failed
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 ** Attachment added: "journal-debug.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1958676/+attachment/5556977/+files/journal-debug.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958676 Title: error: too early for operation, device not yet seeded or device model not acknowledged Install failed To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1958676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958676] Re: error: too early for operation, device not yet seeded or device model not acknowledged Install failed
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958676 Title: error: too early for operation, device not yet seeded or device model not acknowledged Install failed To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1958676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958676] Re: error: too early for operation, device not yet seeded or device model not acknowledged Install failed
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958676 Title: error: too early for operation, device not yet seeded or device model not acknowledged Install failed To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1958676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958676] Re: error: too early for operation, device not yet seeded or device model not acknowledged Install failed
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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958676 Title: error: too early for operation, device not yet seeded or device model not acknowledged Install failed To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1958676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958676] Re: error: too early for operation, device not yet seeded or device model not acknowledged Install failed
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958676 Title: error: too early for operation, device not yet seeded or device model not acknowledged Install failed To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1958676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958676] Re: error: too early for operation, device not yet seeded or device model not acknowledged Install failed
** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958676 Title: error: too early for operation, device not yet seeded or device model not acknowledged Install failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1958676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
