Critical errors in the logs from udisks2

[Sergey Borovkov]

We are using udisk2 and while it works fine system journal has critical errors from udisks2. It tries to create /etc/udisks2 and fails because it's read only filesystem

[Michael Vogt (mvo)]

Could you please attach the exact error message that you see in the journal to this bugreport? This way we can check the udisks2 source more easily to see what exactly it is doing.

[Sergey Borovkov (serge-borovkov)]

Sure.
Jan 17 10:32:40 localhost.localdomain systemd-udevd[2023]: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda1' failed with exit code 1.
Jan 17 10:32:40 localhost.localdomain udisks2.udisksd[1345]: (udisksd:1345): udisks-CRITICAL **: [1345]: Error creating directory /etc/udisks2: Read-only file system [udiskslinuxdrive.c:244, configuration
Jan 17 10:32:39 localhost.localdomain kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk

[Michael Vogt (mvo)]

Thanks, this message is helpful! I looked at this and it seems udisks2 wants to create this dir if missing. We have two options:
1. ship the empty dir in the core snap
2. modify the udisks2 snap to set PACKAGE_SYSCONF_DIR to /var/snap/udisks2/current/etc
I think the later is preferable because this will make udisks2 actually able to store configuration there too.

[Michael Vogt (mvo)]

Adding morphis who did the last uploads of this package.

[Simon Fels (morphis)]

@Michael: Thanks. We will line up a fix for this.

[Konrad Zapałowicz (kzapalowicz)]

https://code.launchpad.net/~kzapalowicz/snappy-hwe-snaps/+git/udisks2/+merge/336423