Bug #3978
closedkrbd qa: concurrent.sh test leaves something read-only
0%
Description
I don't know what exactly is happening here, but it appears
that after running the "rbd/concurrent.sh" workunit, if
you run a different workunit after that you end up with
failures because something is read-only. Presumably it
is the rbd image set up by the rbd task (which should
not be touched by the concurrent.sh workunit).
Anyway, this isn't urgent but it needs to be investigated
so this test can get put into regular use.
Updated by Alex Elder almost 11 years ago
- Status changed from New to In Progress
I've been running this test this morning and am finding it
is not exhibiting the problem that I originally reported.
One possibility is that the problem might occur if an image
unmap fails because it's busy or something, which might
prevent it from getting removed. A subsequent test cold
then run into some sort of trouble manifested by finding
something read-only.
If I could reproduce it now I'd have a little better insight.
Updated by Alex Elder almost 11 years ago
The cleanup routine run when concurrent.sh exits is
run after a call to "wait", so all background tasks
should be done at that point. The cleanup function
then unmaps any remaining mapped devices and removes
them. That should leave everything nice and clean.
I am still unable to reproduce the problem today.
I'm going to use this issue to track getting the
script activated for nightly runs and hope for the
best.
Updated by Alex Elder almost 11 years ago
The following has been committed to the ceph "master" branch:
f402568 rbd/concurrent.sh: probe rbd module at startIt ensure the rbd module is loaded before proceeding with
the test.
Updated by Alex Elder almost 11 years ago
- Status changed from In Progress to 7
The following has been committed to the ceph-qa-suite
"master" branch:
2957d68 rbd_concurrent: add new task to test concurrent.shIt adds a new yaml file that will initiate the concurrent.sh
test in nightly runs.
I'll close this issue when I have seen it get executed
successfully in a nightly run. Marking it "testing"
(though that may not be the right state) to keep track of
that.