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

[Dan Bungert]

Thanks for the review Andreas.

> What in the changes added to livecd-rootfs makes these changes
exclusive to arm64?

Nothing at all, nor should there be.  Antoine has added an amd64 test
case here which I believe should help.

> They are all under live-
build/ubuntu/includes.chroot.minimal.standard.live/*, is that only used
in non-subiquity installs?

the live-build/ubuntu part means that this affects the Desktop ISO,
along with some similar flavor ISOs that inherit from the mainline
Ubuntu Desktop ISO.  Server is unaffected.

> You mentioned the autologin.conf file as not having any subiquity
reference, but removed it anyway, why? Because looks like it is using an
"ubuntu-server" user that doesn't exist, at least not in a desktop
(arm64)?

Yes, that's correct.  It relies on a user that doesn't exist so it could
not possibly be helpful.  We could leave this broken file in place and
not change the serial console portion of this bug but given that we know
it to be broken I thought it best to match the mainline behavior of
livecd-rootfs today and not include this file.  If that functionality
was desired then a fixed version would be needed, presumably with the
correct user at minimum.

> Was there some relevant discussions at the time the fix was
investigated for Plucky?

Not particularly, most of the history is on this bug.

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

Bug description:
  [ Impact ]

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

  [ Test Plan ]

  1. Download Noble ARM64 Desktop daily image from cdimage: https://cdimage.ubuntu.com/noble/daily-live/current/.
  2. Boot the ISO in a VM with no graphics. For example, use qemu with -nographic option.
  3. Observe that, after the boot succeed, the console is spamed with errors instead of asking for credentials.
  4. Create a Noble ARM64 Desktop and a Noble AMD64 Desktop with the proposed livecd-rootfs version. The method is similar than this one: https://docs.google.com/document/d/12eZa2BSbv4cWtj5YN0eoy4LYbEb0LpcW3BWyr1onDtU/edit?tab=t.0.
  5. Run the ARM image in a VM with qemu and -nographic option. after the boot, the console will not get spammed with the error message. The user can log in.
  6. Run this same image with an autoinstall configuration. The installation should succeed.
  7. Run this same image without -nographics. The UI installation should succeed.
  8. Run the AMD64 image without -nographics. The UI installation should succeed.

  [ 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