LVM driver initialisation race between cinder-volume and cinder-backup
Bug #1410341 reported by
Duncan Thomas
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Medium
|
Duncan Thomas | ||
Juno |
Fix Released
|
Medium
|
Jordan Pittier |
Bug Description
On an LVM thin provisioned based system, on first startup:
If cinder-volume and cinder-backup both call driver check_setup_
There should be either a retry if the create fails (to see if we just lost a race) or a filesystem based local lock around the check/create.
I prefer a simple retry-the-check if the create fails.
Changed in cinder: | |
assignee: | nobody → Duncan Thomas (duncan-thomas) |
status: | New → In Progress |
Changed in cinder: | |
importance: | Undecided → Medium |
Changed in cinder: | |
assignee: | Duncan Thomas (duncan-thomas) → nobody |
milestone: | none → kilo-3 |
Changed in cinder: | |
status: | In Progress → Triaged |
Changed in cinder: | |
assignee: | nobody → Duncan Thomas (duncan-thomas) |
status: | Triaged → In Progress |
Changed in cinder: | |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | kilo-3 → 2015.1.0 |
To post a comment you must log in.
Should we even be calling this here? Shouldn't we just be checking if the volume-driver is initialized and that's it? We can surely retry that, but I don't think we should have multiple managers trying to perform setup and init on the same object.