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

[Andreas Hasenack]

I presume this is only happening in the arm64 desktop install because it
doesn't have the subiquity snap, correct?

I have some questions about the change, and please bear with me if these
are obvious, as I'm not familiar with the process of generating
installer images.

a) What in the changes added to livecd-rootfs makes these changes
exclusive to arm64? They are all under live-
build/ubuntu/includes.chroot.minimal.standard.live/*, is that only used
in non-subiquity installs?

a.1) If these changes are indeed also affecting other non-arm64
architectures, then the test plan should include them, unless it can be
demonstrated that testing in one arch is obviously enough (and granted,
we don't perform the SRU test plan in all architectures: I raised this
point only because of (a) above)).

b) 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)?

b.1) I presume this autologin is used in the virtual terminal during
text-mode installs (or even graphical ones) where you just hit enter and
get a shell. Shouldn't that be the ubuntu user? And what does it mean to
remove this file, will we still be able to open a terminal during
install, or will that stop working because there is no user with a
password set at all?


** Changed in: livecd-rootfs (Ubuntu Noble)
       Status: In Progress => Incomplete

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

  [ 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