Fails to detach a volume if the UDID information is missing

Bug #1778939 reported by Chhavi Agarwal on 2018-06-27
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nova-powervm
Undecided
Unassigned

Bug Description

Since target_UDID information is filled by the nova-powervm driver, there can be scenarios when this information is missing in the BDM connection_info, since it get refreshed and populated by cinder for the destination host, in such scenario if user tries to detach the volume it fails as there is no UDID.

When UDID is missing nova-powervm should re-discover the volume and get the UDID to perform detach.

Reviewed: https://review.openstack.org/576034
Committed: https://git.openstack.org/cgit/openstack/nova-powervm/commit/?id=44671813c2b2bdc482e3d1b192f0a6b4f4f30b40
Submitter: Zuul
Branch: master

commit 44671813c2b2bdc482e3d1b192f0a6b4f4f30b40
Author: Chhavi Agarwal <email address hidden>
Date: Mon Jun 18 01:47:03 2018 -0400

    iSCSI volume detach with no UDID

    fixes the issue to preserve the UDID information in BDM during
    the live migration.

    Closes-Bug: 1778939
    Change-Id: I81aee924093ebcbf1e43ec8c7e330b7d4a973420

Changed in nova-powervm:
status: New → Fix Released

This issue was fixed in the openstack/nova-powervm 7.0.0.0b3 development milestone.

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

Other bug subscribers