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

[Dan Bungert]

> About the test:
> - To reproduce I create a noble Desktop ARM 64 ISO the latest livecd-rootfs. 

Great!  Would you update the test plan part of the bug with a reference
to creating the arm 64 ISO like that?  I really wasn't sure what to
write there for the test plan.

> 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.

I can solve this part more or less, but I didn't want to do that until
the SRU portion, particularly the test plan, was in order.

> an SRU fix should be minimal

This is quite true.  It would be a better SRU in that sense to constrain
the changes to just the necessary part to address `error: snap
"subiquity" is not installed`, even at the cost of leaving some cruft
around.  I will work on this part.

So if you can update the test plan part, Antoine, even though you're
likely the only one who will actually run the test, then I will help
with the rest and we can proceed with the SRU.

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