3PAR vlun could be wrong for multi-attach

[Walt Boring]

When the 3PAR driver creates a vlun and then has to fetch it, the fetching could return the wrong vlun.

When a volume is exported to the same host more than once, we will have multiple LUN ids associated with that volume.
We have to make sure we get the correct LUN for the VLUN we just created. This is especially important
 in a multi-attach scenario.

[Openstack Gerrit (openstack-gerrit)]

Reviewed: https://review.openstack.org/90830
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=32bac00ea003015add0d33be262cb3002e4c43af
Submitter: Jenkins
Branch: master

commit 32bac00ea003015add0d33be262cb3002e4c43af
Author: Walter A. Boring IV <email address hidden>
Date: Mon Apr 28 14:30:47 2014 -0700

    Fixed 3PAR driver issue finding correct vlun

    This patch fixes an issue that happens when
    a volume is attached to the same host
    more than once. The driver wasn't looking
    for the correct VLUN on the 3par after the
    VLUN was created. We now get the VLUN
    information in the return of the creation call.

    Change-Id: Id570094f29900c0adcffe6c9d4145c9ad5e3ce4e
    Closes-Bug: #1313894