The 3PAR FC and iSCSI drivers will sometimes not remove all VLUNs from the backend after a volume detach has occured.
One situation where this can happen is if multiple VLUNs are connected to a volume. Currently the 3PAR driver will only call the backend with a request to remove the first VLUN associated with the volume. The other VLUNs will usually be removed, but sometimes not all will be deleted. A change needs to be made to make sure an attempt to remove all VLUNs is done in order to ensure none are left over.
Another situation where VLUNs end up being left over after a volume detach is during live migration. Nova calls initialize_connection several times during live migration. Currently the 3PAR FC and iSCSI drivers will create a new VLUN each time initialize_connection is called. This results in possible dangling VLUNs once the live migration process has completed. A change is needed to only return connection info if a VLUN is already attached to a volume (as this is what Nova currently assumes initialize_connection will do).
Reviewed: https:/ /review. openstack. org/196164 /git.openstack. org/cgit/ openstack/ cinder/ commit/ ?id=b068ae93e26 d21cb94504ac2f7 0231361acd38e6
Committed: https:/
Submitter: Jenkins
Branch: master
commit b068ae93e26d21c b94504ac2f70231 361acd38e6
Author: Anthony Lee <email address hidden>
Date: Fri Jun 26 10:38:33 2015 -0700
Improve 3PAR driver VLUN creation and deletion
This patch improves the creation and deletion logic for VLUNs connection is called
for the 3PAR drivers. The changes will help to prevent VLUNs
from being left behind after volume detaches. It also prevents
extra VLUNs being created when initialize_
multiple times for the same volume and host.
Closes-Bug: #1469816 252570eb2e69962 f7d5f3c07da
Change-Id: I497564cb4bd661