Actions
action #35524
closed[functional][u][sporadic][medium] test fails in snapper_cleanup because of "config is in use" - should we wait in subsequent snapper calls for the previous to finish?
Start date:
2018-04-25
Due date:
% Done:
0%
Estimated time:
Difficulty:
medium
Description
Observation¶
openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_filesystem@64bit fails in
snapper_cleanup
with "config is in use". So it seems that snapper itself is still busy from the previous call and we did not wait long enough before calling the next command.
Reproducible¶
Fails since (at least) Build 20180424
Expected result¶
Last good: 20180423 (or more recent)
Suggestion¶
I think we just need to wait until we can call snapper again, e.g. try again after some waiting time until it finishes, e.g.
my $failed;
my $max_retries = 7;
for (1 .. $max_retries) {
$failed = script_run 'snapper cleanup …';
last unless $failed;
report_info "Retry $_/$max_retries", 'Retrying …';
sleep 1;
}
die "snapper cleanup did not finish successfully even after $max_retries tries" if $failed;
Further details¶
Always latest result in this scenario: latest
Actions