Add workaround for mdmonitor.service #12104
Conversation
Due to bsc#1183229, newer versions of mdadm render the mdmonitor service unable to start and stay running. A workaround until the issue is fixed is to install the last version where mdadm allowed mdmonitor to run successfully.
| record_soft_failure("qaperf.service fails to start bsc#1182914"); | ||
| assert_script_run("systemctl reset-failed qaperf.service"); | ||
| # Reset the failed state of all units so that only new failures are recorded | ||
| assert_script_run("systemctl reset-failed"); |
There was a problem hiding this comment.
Don't you want to run this after mdadm is fixed ? Don't know if it matters
There was a problem hiding this comment.
No, this is really because there are already some recorded failures, eg for qaperf.service which fails because root/qaset/config is only available later. So instead of systemd testsuite to think those are failing, we need to reset the failed states and rerun them then.
There was a problem hiding this comment.
Also just to mention, mdmonitor.service, so mdadm with "--monitor" and "--scan", never fails, does start, but does not remain running, so it is not a failed state per se
|
Sorry, but you impacted multipath testing https://openqa.suse.de/tests/5657094#step/kernel_multipath/143. |
Due to bsc#1183229, newer versions of mdadm render the mdmonitor service unable to start and stay running.
A workaround until the issue is fixed is to install the last version where mdadm allowed mdmonitor to run successfully.