create volume from image failed, the residual device in host cause we can't find the multipath device to copy image
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
os-brick |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
Batch create volumes form image using SAN, then we find some volumes create error.
The error is after initial_volume before copy_image_
Multipath device is exist, but it is not in the initial connection generated, it is a residual device, there is a problem.
The reason of Residual device generating, mainly because of batch operation to create the volume form image, there will be a large number of concurrent operation. The host side will initialize
and terminate volumes at the same time, and at the same time to rescan and remove the host devices.
Host to remove the equipment and SAN to remove mapping group is asynchronous atomic operations, concurrent, once inserted among the rescan device operation will generate garbage device on the host, this multipath device would be a bug.
After that, create volume from image use the same lunid, will reuse the device, and this device can't normal use, will lead to create error.
To sum up, the causes of the abnormal is relatively complex. To solve it, it is necessary to take into account from the source, clean up the residual device.
Changed in cinder: | |
assignee: | nobody → Zhang Hao (zhang-hao16) |
Changed in cinder: | |
assignee: | Zhang Hao (zhang-hao16) → yuyafei (yu-yafei) |
affects: | cinder → os-brick |
affects: | os-brick → cinder |
affects: | cinder → os-brick |
Changed in os-brick: | |
assignee: | yuyafei (yu-yafei) → nobody |
Changed in os-brick: | |
status: | In Progress → Incomplete |
Fix proposed to branch: master /review. openstack. org/293259
Review: https:/