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

[Antoine Lassagne]

I'm not sure why it happened only with arm64 images but hope
that @Dan knows, since it's a bug that he fixed in plucky a few months
ago.

About the questions you have:

a) Subiquity is used in arm64 installation, so I'm not sure this is
correct. It seems to me that the changes are non-specific to arm64, but
since I don't know why it was happening only to arm64, I'm missing
something. Which make this SRU dangerous.

a.1) You are completely correct and we should include a minimal test of
an installation of Ubuntu desktop arm64 in the plan. I'm updating the
test plan.

b) See Dan's comment
earlier: https://bugs.launchpad.net/ubuntu/+source/livecd-
rootfs/+bug/2083554/comments/11

b.1) I tried and succeed logging in through a serial port console during
the subiquity installation. username ubuntu, no password. So this user
does exist.

Dan could you please give us more context about why would the bug and
the changes impact only arm64? Was there some relevant discussions at
the time the fix was investigated for Plucky?

** Description changed:

  [ 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.
+ 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 MAD64 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.

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