canonical-ubuntu-qa team mailing list archive

[Simon Poirier <2089380@xxxxxxxxxxxxxxxxxx>]

Actually, it looks like all focal images and seems non-arch specific.
Focal containers back to serial 20200609 exhibit this behaviour of having an fstab.

http://cloud-images-archive.ubuntu.com/releases/focal/release-20200609/


** Changed in: cloud-images
       Status: New => Confirmed

** Summary changed:

- focal armhf instances boot in degraded state
+ focal lxd containers boot in degraded state

** Description changed:

- Looks like Focal armhf instances boot in degraded state because the
- following systemd unit fails:
+ Looks like Focal instances boot in degraded state because the following
+ systemd unit fails:
  
  root@paride-test:~# systemctl status systemd-remount-fs.service
  ● systemd-remount-fs.service - Remount Root and Kernel File Systems
-      Loaded: loaded (/lib/systemd/system/systemd-remount-fs.service; enabled-runtime; vendor preset: enabled)
-      Active: failed (Result: exit-code) since Fri 2024-11-22 11:29:21 UTC; 53s ago
-        Docs: man:systemd-remount-fs.service(8)
-              https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
-     Process: 60 ExecStart=/lib/systemd/systemd-remount-fs (code=exited, status=1/FAILURE)
-    Main PID: 60 (code=exited, status=1/FAILURE)
+      Loaded: loaded (/lib/systemd/system/systemd-remount-fs.service; enabled-runtime; vendor preset: enabled)
+      Active: failed (Result: exit-code) since Fri 2024-11-22 11:29:21 UTC; 53s ago
+        Docs: man:systemd-remount-fs.service(8)
+              https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
+     Process: 60 ExecStart=/lib/systemd/systemd-remount-fs (code=exited, status=1/FAILURE)
+    Main PID: 60 (code=exited, status=1/FAILURE)
  
  Nov 22 11:29:21 paride-test systemd-remount-fs[71]: mount: /: can't find LABEL=cloudimg-rootfs.
  Nov 22 11:29:21 paride-test systemd-remount-fs[60]: /bin/mount for / exited with exit status 1.
  Nov 22 11:29:21 paride-test systemd[1]: systemd-remount-fs.service: Main process exited, code=exited, status=1/FAILURE
  Nov 22 11:29:21 paride-test systemd[1]: systemd-remount-fs.service: Failed with result 'exit-code'.
  Nov 22 11:29:21 paride-test systemd[1]: Failed to start Remount Root and Kernel File Systems.
  Warning: journal has been rotated since unit was started, output may be incomplete.
  
  We should figure out why this happens, and make instances boot again in
  'running' state.

-- 
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to Auto Package Testing.
https://bugs.launchpad.net/bugs/2089380

Title:
  focal lxd containers boot in degraded state

Status in Auto Package Testing:
  Invalid
Status in cloud-images:
  Confirmed

Bug description:
  Looks like Focal instances boot in degraded state because the
  following systemd unit fails:

  root@paride-test:~# systemctl status systemd-remount-fs.service
  ● systemd-remount-fs.service - Remount Root and Kernel File Systems
       Loaded: loaded (/lib/systemd/system/systemd-remount-fs.service; enabled-runtime; vendor preset: enabled)
       Active: failed (Result: exit-code) since Fri 2024-11-22 11:29:21 UTC; 53s ago
         Docs: man:systemd-remount-fs.service(8)
               https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
      Process: 60 ExecStart=/lib/systemd/systemd-remount-fs (code=exited, status=1/FAILURE)
     Main PID: 60 (code=exited, status=1/FAILURE)

  Nov 22 11:29:21 paride-test systemd-remount-fs[71]: mount: /: can't find LABEL=cloudimg-rootfs.
  Nov 22 11:29:21 paride-test systemd-remount-fs[60]: /bin/mount for / exited with exit status 1.
  Nov 22 11:29:21 paride-test systemd[1]: systemd-remount-fs.service: Main process exited, code=exited, status=1/FAILURE
  Nov 22 11:29:21 paride-test systemd[1]: systemd-remount-fs.service: Failed with result 'exit-code'.
  Nov 22 11:29:21 paride-test systemd[1]: Failed to start Remount Root and Kernel File Systems.
  Warning: journal has been rotated since unit was started, output may be incomplete.

  We should figure out why this happens, and make instances boot again
  in 'running' state.

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/2089380/+subscriptions