mirror of
https://github.com/systemd/systemd
synced 2024-10-15 04:24:19 +00:00
test: expect libdevmapper failure in TEST-50-DISSECT
libdevmapper/device mapper driver can return semi-random failures when opening verity devices, and we have fallback code to deal with it. But the test was not expecting the fallback path, so it became unreliable. Fixes https://github.com/systemd/systemd/issues/23866
This commit is contained in:
parent
87305b0fbf
commit
5ad8116a87
|
@ -285,7 +285,7 @@ Type=notify
|
||||||
RemainAfterExit=yes
|
RemainAfterExit=yes
|
||||||
MountAPIVFS=yes
|
MountAPIVFS=yes
|
||||||
PrivateTmp=yes
|
PrivateTmp=yes
|
||||||
ExecStart=/bin/sh -c 'systemd-notify --ready; while ! grep -q -F MARKER /tmp/img/usr/lib/os-release; do sleep 0.1; done; mount | grep -F "/dev/mapper/${roothash}-verity" | grep -q -F "nosuid"'
|
ExecStart=/bin/sh -c 'systemd-notify --ready; while ! grep -q -F MARKER /tmp/img/usr/lib/os-release; do sleep 0.1; done; mount | grep -e "/dev/mapper/${roothash}-verity" -e "/dev/mapper/loop[0-9]*-verity" | grep -q -F "nosuid"'
|
||||||
EOF
|
EOF
|
||||||
systemctl start testservice-50d.service
|
systemctl start testservice-50d.service
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue