* Chris Hofstaedtler <zeha@xxxxxxxxxx> [240429 15:24]: > > udisks2's autopkgtest fails when tried together with util-linux 2.40. An > > example can be seen here: > > https://ci.debian.net/packages/u/udisks2/testing/amd64/46012968/ > > > > 537s ====================================================================== > > 537s FAIL: test_ext4 (__main__.FS.test_ext4) > > 537s fs: ext4 > > 537s ---------------------------------------------------------------------- > > 537s Traceback (most recent call last): > > 537s File "/tmp/autopkgtest.btnhgm/build.cz4/src/src/tests/integration-test", line 1107, in _do_udisks_check > > 537s cd_fs.call_mount_sync(ro_options, None) > > 537s gi.repository.GLib.GError: udisks-error-quark: GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error mounting /dev/sr1 at /media/root/41b1acb1-744c-422a-9071-2dba5368a683: fsconfig system call failed: /dev/sr1: Can't open blockdev (0) > > 537s > > 537s During handling of the above exception, another exception occurred: > > 537s > > 537s Traceback (most recent call last): > > 537s File "/tmp/autopkgtest.btnhgm/build.cz4/src/src/tests/integration-test", line 725, in test_ext4 > > 537s self._do_fs_check('ext4') > > 537s File "/tmp/autopkgtest.btnhgm/build.cz4/src/src/tests/integration-test", line 894, in _do_fs_check > > 537s self._do_udisks_check(fs_type) > > 537s File "/tmp/autopkgtest.btnhgm/build.cz4/src/src/tests/integration-test", line 1112, in _do_udisks_check > > 537s self.fail('Mounting read-only device with \'rw\' option failed' > > 537s AssertionError: Mounting read-only device with 'rw' option failedwith an unexpected error. > > 537s Got: udisks-error-quark: GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error mounting /dev/sr1 at /media/root/41b1acb1-744c-422a-9071-2dba5368a683: fsconfig system call failed: /dev/sr1: Can't open blockdev (0) > > 537s Expected: 'is write-protected but explicit read-write mode requested' or 'is write-protected but `rw' option given' > I won't get to it this week (also re: stable v2.40.1), but maybe > someone else has seen this failure already? Having said that, it seems likely the test was broken by this change in util-linux: libmount: report kernel message from new API https://github.com/util-linux/util-linux/commit/9da5644e414cdc318f0311260dabc6035c85b58e I don't know if the error messages are supposed to be stable or not, but it looks like a very intentional change :-) Orthogonally, "/dev/sr1: Can't open blockdev" seems not very informative if it's supposed to mean "write-protected but `rw' option given". Chris
