Public bug reported:
Looks like Focal armhf 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.
** Affects: auto-package-testing
Importance: Undecided
Status: New
--
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 armhf instances boot in degraded state
Status in Auto Package Testing:
New
Bug description:
Looks like Focal armhf 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
--
Mailing list: https://launchpad.net/~canonical-ubuntu-qa
Post to : canonical-ubuntu-qa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa
More help : https://help.launchpad.net/ListHelp
