Mulitpath scsi devices are not removed if there is an error in multipath command stdout
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Medium
|
Patrick East | ||
OpenStack Compute (nova) |
Invalid
|
Medium
|
Lee Yarwood |
Bug Description
In cinder/
Inside of find_multipath_
3624a9370590474
size=1.0G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=-1 status=active
|- 34:0:0:1 sdc 8:32 active undef running
`- 33:0:0:1 sdb 8:16 active undef running
But with a slight misconfiguration you can get a string back that looks like:
Oct 13 10:24:01 | /lib/udev/scsi_id exitted with 1
3624a9370590474
size=1.0G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=-1 status=active
|- 34:0:0:1 sdc 8:32 active undef running
`- 33:0:0:1 sdb 8:16 active undef running
Which is then unable to be parsed with the code in there currently, and we just bail out of disconnecting 'dm-0'. We probably should support being able to pick out the device from the string regardless of the extra line in stdout.
Changed in cinder: | |
assignee: | Walt Boring (walter-boring) → Patrick East (patrick-east) |
status: | Triaged → In Progress |
Changed in cinder: | |
milestone: | none → kilo-1 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | kilo-1 → 2015.1.0 |
Thanks for the bug report Patrick. There is something up with your multipath daemon puking on something prior to showing the multipath device. You should try and resolve that issue.
That being said, brick should be a bit more resilient to these types of issues and try and overcome this.