Failing to remove the module, means the testcase / systemd has failed. Which has been diagnosed and narrowed down to a bug in systemd.
Whilst the proposed improvements to the test case are ok, they make it skip a lot more without making it more fool proof. Ideally, I'd like to make the testcase more resilient and enforce more. Thus failing to remove the module should still be a hard failure. And upon starting the test case we do need to re-insert the module, as otherwise LUKS2 header creation would fail (that affects disco+ only). I do like the add_host usage, but I wonder if it's best be used with udevadm settle calls, rather than manual tight loops. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829347 Title: systemd autopkgtest 'storage' fails adding/rmmoding scsi_debug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1829347/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
