mount nbd hangs because of previous umount failure
Bug #973413 reported by
Unmesh Gurjar
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Davanum Srinivas (DIMS) |
Bug Description
Scenario:
While injecting data in an instance, if the umount command fails, the
qemu-nbd disconnect command also fails and the device becomes unusable.
However, the device (/dev/nbd15) gets added back to the available device list.
So, if another instance is launched (with some injected data), it tries to use the
same nbd device (/dev/nbd15) which contains a stale connection.
Changed in nova: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in nova: | |
status: | Confirmed → Incomplete |
importance: | Medium → Undecided |
Changed in nova: | |
status: | Incomplete → Invalid |
Changed in nova: | |
assignee: | nobody → Davanum Srinivas (DIMS) (dims-v) |
Changed in nova: | |
milestone: | none → icehouse-2 |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | icehouse-2 → 2014.1 |
To post a comment you must log in.
Why does the umount command fail (any errors in logs)?
Looking at the code, if "qemu-nbd -d" fails, then an exception is thrown
and we will _not_ add that nbd device into the available list.
Similarly if the umount commands fails, we won't even try
to run the "qemu-nbd -d" command.
So both "umount" and "qemu-nbd -d" would have to fail silently for this to happen?
What kernel/distro was this on?