Bug#1051507: grub-common.service fails on read-only root

[Julian Andres Klode]

Control: tag -1 wontfix

On Fri, Sep 08, 2023 at 09:50:23PM +0200, Jörg Sommer wrote:
> Package: grub-common
> Version: 2.12~rc1-9
> Severity: normal
> 
> Hi,
> 
> my root filesystem (including /boot) is mounted read-only, which makes the
> service grub-common fail:
> 
> ```text
> % journalctl -b -u grub-common
> Sep 08 21:15:44 systemd[1]: Starting grub-common.service - Record successful boot for GRUB...
> Sep 08 21:15:44 grub-editenv[865]: grub-editenv: Fehler: »/boot/grub/grubenv« kann nicht geöffnet werden: Das Dateisystem ist nur lesbar.
> Sep 08 21:15:44 systemd[1]: grub-common.service: Main process exited, code=exited, status=1/FAILURE
> Sep 08 21:15:44 systemd[1]: grub-common.service: Failed with result 'exit-code'.
> Sep 08 21:15:44 systemd[1]: Failed to start grub-common.service - Record successful boot for GRUB.
> ```
> 
> I've added an additional condition:
> 
> ```text
> [Unit]
> ConditionPathIsReadWrite=/boot/grub/gruben
> ```

Write access to the file is a necessity of recording a successful
boot, and hence a failure is the correct outcome here, otherwise
you don't notice the failure.

A write-only /boot should be considered unsupported.

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer                              i speak de, en
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-grub-devel/attachments/20230910/37f998a7/attachment.sig>