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

[Dan Bungert]

@Frank - please retest when you get a moment, should be working now.
Marking invalid for snapd, aside from extra logging or something I'm not sure what snapd would do.
Marking invalid for subiquity, as the code change for this is outside the subiquity codebase.

** Changed in: snapd
       Status: New => Invalid

** Changed in: subiquity
       Status: In Progress => Invalid

-- 
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:
  Invalid
Status in subiquity:
  Invalid
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