HPE 3PAR : With single path FC configuration, multiple vluns were created, after volume attached

[Vivek Soni]

Description
===========
HPE 3PAR : With single path FC configuration, multiple vluns were created, after volume attached

Steps to reproduce
==================
1) use 3parfc backend and create volume
2) make sure nova.conf DO NOT have 'volume_use_multipath=True' in libvirt section (i.e. we should have single path configuration)
3) attach that volume to an instance

Actual result
=============
multiple vluns were created in 3par

Expected
===========
since its a single path configuration. only one vlun must be created.

[Matt Riedemann (mriedem)]

Which release of nova-compute and os-brick are you using?

[Vivek Soni (viveksoni)]

$ nova-compute --version
17.0.0

$ pip list | grep os-brick
os-brick (1.15.3)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/519979
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=907fc3d7869a8dd049368b55b8c40f7c3da221ed
Submitter: Zuul
Branch: stable/pike

commit 907fc3d7869a8dd049368b55b8c40f7c3da221ed
Author: Vivek Soni <email address hidden>
Date: Wed Nov 15 12:03:57 2017 +0530

    HPE 3PAR: Handle single path in FC configuration

    Issue :- With single path configuration, post
    volume attach multiple vluns are created,
    instead of one vlun.

    Added check to create host with single initiator,
    which will use single target wwn to create a vlun

    Change-Id: I093da81fb9a0021e4fedff7eb48d3245957e787a
    Closes-Bug: #1727176
    (cherry picked from commit d265cc5a2d4edf5bdaecb34feb6d7c35a76ec526)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/cinder 12.0.0.0b2 development milestone.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Vivek Soni (<email address hidden>) on branch: master
Review: https://review.openstack.org/514952
Reason: Abandoning this, as it is a duplicate of patch created, while facing some merge conflict issue.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/cinder 11.0.2 release.