[Bug 2083554] Re: error: snap "subiquity" is not installed

[Antoine Lassagne]

About the test:
- To reproduce I create a noble Desktop ARM 64 ISO the latest livecd-rootfs. I boot it on a machine which has a zapper connected on the serial port. When opening the serial tty, it's spammed with "error: snap "subiquity" is not installed".
- To fix: I applied this fix on livecd-rootfs and created the image again. Now the serial tty is clean a leaves me space to login, run commands, etc.
- It may be useful to note that I did not test the daily arm64 images, which should have the same issues, but these will not boot on the ARM machines I have. Let me get back to you with some VM attempts.

About noble-proposed:
I did not try this one, but I'm afraid my tests used the latest livecd-rotfs from the `ubuntu/noble` branch of the repo, so I don't think there is a more recent version.

About the whole SRU process:
>From what I am reading, an SRU fix should be minimal. Since my error only involves subiquity, is the fix of `serial-getty` also necessary? Should I build new images to try both approaches?

-- 
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/2083554

Title:
  error: snap "subiquity" is not installed

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Noble:
  New

Bug description:
  [ Impact ]

   * On arm64 Desktop install ISOs, the message `error: snap "subiquity"
  is not installed` can be observed repeatedly.

  [ Test Plan ]

   * Testing something like this prior to merge to the archive is difficult.  We can demonstrate that builds in a PPA succeed, but that fails to provide full confirmation that the resulting ISO is healthy.
   * ???

  [ Where problems could occur ]

   * As usual, the risk is never zero
   * We are deleting files not in use by the desktop install ISO.  If this was done incorrectly, we could harm the install.

  Original bug report follows.

  ---

  On arm64, using the Oracular daily build "20241001", the message
  `error: snap "subiquity" is not installed` can be observed repeatedly.

  ...
  Oct 02 16:03:19 ubuntu systemd[1]: Started serial-getty at ttyAMA0.service - Subiquity, the installer for Ubuntu Server ttyAMA0.
  Oct 02 16:03:19 ubuntu systemd[1]: serial-getty at ttyAMA0.service: Main process exited, code=exited, status=1/FAILURE
  Oct 02 16:03:19 ubuntu systemd[1]: serial-getty at ttyAMA0.service: Failed with result 'exit-code'.
  Oct 02 16:03:19 ubuntu systemd[1]: run-credentials-serial\x2dgetty\x40ttyAMA0.service.mount: Deactivated successfully.
  Oct 02 16:03:20 ubuntu systemd[1]: serial-getty at ttyAMA0.service: Scheduled restart job, restart counter is at 3155.
  Oct 02 16:03:20 ubuntu systemd[1]: Started serial-getty at ttyAMA0.service - Subiquity, the installer for Ubuntu Server ttyAMA0.
  Oct 02 16:03:20 ubuntu systemd[1]: serial-getty at ttyAMA0.service: Main process exited, code=exited, status=1/FAILURE
  Oct 02 16:03:20 ubuntu systemd[1]: serial-getty at ttyAMA0.service: Failed with result 'exit-code'.
  Oct 02 16:03:20 ubuntu systemd[1]: run-credentials-serial\x2dgetty\x40ttyAMA0.service.mount: Deactivated successfully.
  Oct 02 16:03:20 ubuntu systemd[1]: serial-getty at ttyAMA0.service: Scheduled restart job, restart counter is at 3156.
  ...

  If `serial-getty at ttyAMA0.service` is masked, the situation improves.
  References to the subiquity snap should be removed from chroot overlay files for Ubuntu Desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2083554/+subscriptions