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

Antoine Lassagne 2083554 at bugs.launchpad.net
Wed Apr 30 16:17:04 UTC 2025


** Description changed:

  [ Impact ]
  
-  * On arm64 Desktop install ISOs, the message `error: snap "subiquity"
+  * 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.
-  * ???
+  * 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.
+  * To reproduce the issue: create a Ubuntu Desktop noble ARM64 image with livecd-rootfs / ubuntu-cdimage. It's the same image than the one that is published daily, but with the latest livecd-rootfs version. The method can be found here: https://docs.google.com/document/d/12eZa2BSbv4cWtj5YN0eoy4LYbEb0LpcW3BWyr1onDtU/edit?tab=t.0.
+ Run the image in a VM with qemu and --nographic option. after the boot, the console will get spammed with the error message.
+ 
  
  [ 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.
+  * 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:
  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.
   * To reproduce the issue: create a Ubuntu Desktop noble ARM64 image with livecd-rootfs / ubuntu-cdimage. It's the same image than the one that is published daily, but with the latest livecd-rootfs version. The method can be found here: https://docs.google.com/document/d/12eZa2BSbv4cWtj5YN0eoy4LYbEb0LpcW3BWyr1onDtU/edit?tab=t.0.
  Run the image in a VM with qemu and --nographic option. after the boot, the console will get spammed with the error message.

  
  [ 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




More information about the foundations-bugs mailing list