3PAR host in different domain causes attach to fail.

[Walt Boring]

When someone manually creates a 3PAR host in a domain that is different than the 3par driver is configured to talk to, then attaches fail with a bogus exception of a VLUN not being found.

2013-03-22 14:27:26 ERROR [cinder.openstack.common.rpc.amqp] Exception during message handling
Traceback (most recent call last):
  File "/opt/stack/cinder/cinder/openstack/common/rpc/amqp.py", line 430, in _process_data
    rval = self.proxy.dispatch(ctxt, version, method, **args)
  File "/opt/stack/cinder/cinder/openstack/common/rpc/dispatcher.py", line 133, in dispatch
    return getattr(proxyobj, method)(ctxt, **kwargs)
  File "/opt/stack/cinder/cinder/volume/manager.py", line 633, in initialize_connection
    return self.driver.initialize_connection(volume_ref, connector)
  File "/opt/stack/cinder/cinder/volume/drivers/san/hp/hp_3par_fc.py", line 186, in initialize_connection
    vlun = self.common.create_vlun(volume, host, self.client)
  File "/opt/stack/cinder/cinder/volume/drivers/san/hp/hp_3par_common.py", line 447, in create_vlun
    return client.getVLUN(volume_name)
  File "/usr/local/lib/python2.7/dist-packages/hp3parclient/client.py", line 328, in getVLUN
    raise exceptions.HTTPNotFound({'code':'NON_EXISTENT_VLUN', 'desc': "VLUN '%s' was not found" % volumeName})
HTTPNotFound: Not found (HTTP 404) NON_EXISTENT_VLUN - VLUN 'osv-ksVNv0M5RH.tnYrC1IjdnA' was not found

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/25187
Committed: http://github.com/openstack/cinder/commit/3a20db0a739bc15e1beeb41910a6977381fd12f6
Submitter: Jenkins
Branch: master

commit 3a20db0a739bc15e1beeb41910a6977381fd12f6
Author: Walter A. Boring IV <email address hidden>
Date: Fri Mar 22 14:31:15 2013 -0700

    Fix bug with 3PAR host entry in wrong domain

    This patch exposes a more acurate exception message
    when a user has created a manual host entry on a
    3PAR system that is in an incorrect 3PAR domain than
    the domain that is configured for the 3PAR driver.

    The bug complained that it couldn't find a VLUN, when the
    actual problem was the host existed in the wrong 3PAR domain.

    Fixes bug #1158991

    Change-Id: I3f92e59ae43a10a0788d97d987785b6520f9f1be