create volume from image failed, the residual device in host cause we can't find the multipath device to copy image

Bug #1553730 reported by Zhang Hao
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
os-brick
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_to_volume, the detail is we can't find the multipath device in host, so we can't move on to 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.

Zhang Hao (zhang-hao16)
Changed in cinder:
assignee: nobody → Zhang Hao (zhang-hao16)
Yafei Yu (yu-yafei)
Changed in cinder:
assignee: Zhang Hao (zhang-hao16) → yuyafei (yu-yafei)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (master)

Fix proposed to branch: master
Review: https://review.openstack.org/293259

Changed in cinder:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on cinder (master)

Change abandoned by yuyafei (<email address hidden>) on branch: master
Review: https://review.openstack.org/293259

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (master)

Fix proposed to branch: master
Review: https://review.openstack.org/297582

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on cinder (master)

Change abandoned by yuyafei (<email address hidden>) on branch: master
Review: https://review.openstack.org/293259

Yafei Yu (yu-yafei)
affects: cinder → os-brick
affects: os-brick → cinder
affects: cinder → os-brick
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to os-brick (master)

Fix proposed to branch: master
Review: https://review.openstack.org/298497

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on os-brick (master)

Change abandoned by yuyafei (<email address hidden>) on branch: master
Review: https://review.openstack.org/298497

Yafei Yu (yu-yafei)
Changed in os-brick:
assignee: yuyafei (yu-yafei) → nobody
Changed in os-brick:
status: In Progress → Incomplete
Revision history for this message
Alexander Bozhenko (alexbozhenko) wrote :

Does anybody faces this bug too?
Description looks similar to what I see when booting multiple instances from images to volume:
http://paste.openstack.org/show/620894/

Revision history for this message
Alexander Bozhenko (alexbozhenko) wrote :

Gorka, do you think it supposed to be fixed in your commit
https://bugs.launchpad.net/os-brick/+bug/1608614
?

I am facing this bug(intermittent " Unable to find a Fibre Channel volume device" errors) with latest pike os-brick.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers