[Bug 2028862] Re: Mantic hangs during install with continuous 'Job snapd.seeded.service/start running' messages

[Launchpad Bug Tracker]

This bug was fixed in the package livecd-rootfs - 23.10.12

---------------
livecd-rootfs (23.10.12) mantic; urgency=medium

  * live-build/auto/build: Avoid purging packages for ubuntu-cpc.
    With the switch to the ubuntu-cloud-minimal seed, we
    don't really need to purge anything now. On the contrary,
    the purging of packages if not installed, fails with the
    exit code of 100.

 -- Utkarsh Gupta <utkarsh at ubuntu.com>  Tue, 08 Aug 2023 15:44:42 +0530

** Changed in: livecd-rootfs (Ubuntu)
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/2028862

Title:
  Mantic hangs during install with continuous 'Job
  snapd.seeded.service/start running' messages

Status in snapd:
  New
Status in subiquity:
  In Progress
Status in Ubuntu on IBM z Systems:
  In Progress
Status in livecd-rootfs package in Ubuntu:
  Fix Released

Bug description:
  While trying to install the latest mantic ISO image (tried current and
  pending) on s390x (but it's probably not limited to a certain
  architecture) the installation hangs with never-ending messages like
  this:

  M[K[[0;1;31m*[0m[0;31m*    [0m] Job snapd.seeded.service/start running (16min 23s / no limit)
  M[K[[0m[0;31m*     [0m] Job snapd.seeded.service/start running (16min 23s / no limit)
  M[K[[0;1;31m*[0m[0;31m*    [0m] Job snapd.seeded.service/start running (16min 24s / no limit)
  M[K[[0;31m*[0;1;31m*[0m[0;31m*   [0m] Job snapd.seeded.service/start running (16min 24s / no limit)
  M[K[ [0;31m*[0;1;31m*[0m[0;31m*  [0m] Job snapd.seeded.service/start running (16min 25s / no limit)
  M[K[  [0;31m*[0;1;31m*[0m[0;31m* [0m] Job snapd.seeded.service/start running (16min 25s / no limit)
  M[K[   [0;31m*[0;1;31m*[0m[0;31m*[0m] Job snapd.seeded.service/start running (16min 26s / no limit)
  M[K[    [0;31m*[0;1;31m*[0m] Job snapd.seeded.service/start running (16min 26s / no limit)
  M[K[     [0;31m*[0m] Job snapd.seeded.service/start running (16min 27s / no limit)
  M[K[    [0;31m*[0;1;31m*[0m] Job snapd.seeded.service/start running (16min 27s / no limit)
  M[K[   [0;31m*[0;1;31m*[0m[0;31m*[0m] Job snapd.seeded.service/start running (16min 28s / no limit)
  M[K[  [0;31m*[0;1;31m*[0m[0;31m* [0m] Job snapd.seeded.service/start running (16min 28s / no limit)
  M[K[ [0;31m*[0;1;31m*[0m[0;31m*  [0m] Job snapd.seeded.service/start running (16min 29s / no limit)
  M[K[[0;31m*[0;1;31m*[0m[0;31m*   [0m] Job snapd.seeded.service/start running (16min 29s / no limit)
  M[K[[0;1;31m*[0m[0;31m*    [0m] Job snapd.seeded.service/start running (16min 30s / no limit)
  M[K[[0m[0;31m*     [0m] Job snapd.seeded.service/start running (16min 30s / no limit)
  M[K[[0;1;31m*[0m[0;31m*    [0m] Job snapd.seeded.service/start running (16min 31s / no limit)
  M[K[[0;31m*[0;1;31m*[0m[0;31m*   [0m] Job snapd.seeded.service/start running (16min 31s / no

  (sorry for the 'special' characters, but it's because I copied the
  content from the HMC console)

  I was told that using the kernel arg
  "systemd.mask=snapd.seeded.service" should help to workaround this,
  still need to try this out ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/2028862/+subscriptions