VMware: Can't re-attach volume : 'NoneType' object has no attribute 'service_content'

[Kevin Tibi]

After upgrade juno to kilo, I have issue with cinder.

I use Vmware Backend. I can create volume, attach it then detach it.

But I can't Re-Attach this volume :

2015-07-29 16:42:16.323 9003 ERROR cinder.volume.manager [req-0a416b16-437e-43d7-a11b-f3abac8b4045 2d3e8f76f3f9429c869e5a085837d2f1 000411016ad847fa870e2c2246a24664 - - -] Unable to fetch connection information from backend: 'NoneType' object has no attribute 'service_content'
2015-07-29 16:42:16.325 9003 ERROR oslo_messaging.rpc.dispatcher [req-0a416b16-437e-43d7-a11b-f3abac8b4045 2d3e8f76f3f9429c869e5a085837d2f1 000411016ad847fa870e2c2246a24664 - - -] Exception during message handling: Bad or unexpected response from the storage volume backend API: Unable to fetch connection information from backend: 'NoneType' object has no attribute 'service_content'
2015-07-29 16:42:16.325 9003 TRACE oslo_messaging.rpc.dispatcher Traceback (most recent call last):
2015-07-29 16:42:16.325 9003 TRACE oslo_messaging.rpc.dispatcher File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 142, in _dispatch_and_reply
2015-07-29 16:42:16.325 9003 TRACE oslo_messaging.rpc.dispatcher executor_callback))
2015-07-29 16:42:16.325 9003 TRACE oslo_messaging.rpc.dispatcher File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 186, in _dispatch
2015-07-29 16:42:16.325 9003 TRACE oslo_messaging.rpc.dispatcher executor_callback)
2015-07-29 16:42:16.325 9003 TRACE oslo_messaging.rpc.dispatcher File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 130, in _do_dispatch
2015-07-29 16:42:16.325 9003 TRACE oslo_messaging.rpc.dispatcher result = func(ctxt, **new_args)
2015-07-29 16:42:16.325 9003 TRACE oslo_messaging.rpc.dispatcher File "/usr/lib/python2.7/site-packages/osprofiler/profiler.py", line 105, in wrapper
2015-07-29 16:42:16.325 9003 TRACE oslo_messaging.rpc.dispatcher return f(*args, **kwargs)
2015-07-29 16:42:16.325 9003 TRACE oslo_messaging.rpc.dispatcher File "/usr/lib/python2.7/site-packages/cinder/volume/manager.py", line 1118, in initialize_connection
2015-07-29 16:42:16.325 9003 TRACE oslo_messaging.rpc.dispatcher raise exception.VolumeBackendAPIException(data=err_msg)
2015-07-29 16:42:16.325 9003 TRACE oslo_messaging.rpc.dispatcher VolumeBackendAPIException: Bad or unexpected response from the storage volume backend API: Unable to fetch connection information from backend: 'NoneType' object has no attribute 'service_content'
2015-07-29 16:42:16.325 9003 TRACE oslo_messaging.rpc.dispatcher
2015-07-29 16:42:16.327 9003 ERROR oslo_messaging._drivers.common [req-0a416b16-437e-43d7-a11b-f3abac8b4045 2d3e8f76f3f9429c869e5a085837d2f1 000411016ad847fa870e2c2246a24664 - - -] Returning exception Bad or unexpected response from the storage volume backend API: Unable to fetch connection information from backend: 'NoneType' object has no attribute 'service_content' to caller
2015-07-29 16:42:16.328 9003 ERROR oslo_messaging._drivers.common [req-0a416b16-437e-43d7-a11b-f3abac8b4045 2d3e8f76f3f9429c869e5a085837d2f1 000411016ad847fa870e2c2246a24664 - - -] ['Traceback (most recent call last):\n', ' File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 142, in _dispatch_and_reply\n executor_callback))\n', ' File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 186, in _dispatch\n executor_callback)\n', ' File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 130, in _do_dispatch\n result = func(ctxt, **new_args)\n', ' File "/usr/lib/python2.7/site-packages/osprofiler/profiler.py", line 105, in wrapper\n return f(*args, **kwargs)\n', ' File "/usr/lib/python2.7/site-packages/cinder/volume/manager.py", line 1118, in initialize_connection\n raise exception.VolumeBackendAPIException(data=err_msg)\n', "VolumeBackendAPIException: Bad or unexpected response from the storage volume backend API: Unable to fetch connection information from backend: 'NoneType' object has no attribute 'service_content'\n"]

[Vipin Balachandran (vbala)]

This happens if SPBM is not supported by the underlying vCenter.

Kevin,
Is you vCenter version <= 5.1?

[Kevin Tibi (ktibi)]

I use Vcenter 5.1.0 u1.

I need to upgrade my Vcenter to 5.5 ?

Where I can found this requierement for openstack ?

[Xiangfei Zhu (xiangfeiz)]

This is a bug specific to vCenter version <= 5.1 which does not support SPBM. I will submit a patch for it.

[Vipin Balachandran (vbala)]

It is not a requirement yet. In 5.1, storage policies are not supported. Also, our testing is on VC 5.5 and VC 6.0.

[Kevin Tibi (ktibi)]

Xiangfei,

Your patch is for fix this issue or for add a new requierment for Vcenter ?

Vipin,

I see your new review (https://review.openstack.org/#/c/207321/), so 5.1 become the minimum required version of vCenter but with 5.1 I have this issue.

[Vipin Balachandran (vbala)]

Kevin,
You can apply this patch to fix the problem for VC 5.1.

[Kevin Tibi (ktibi)]

Vipin,

issue is fix with your patch.

Thx.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/207380
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=2bad1fb2cf73921259d967897f050b4ac258f71b
Submitter: Jenkins
Branch: master

commit 2bad1fb2cf73921259d967897f050b4ac258f71b
Author: Xiangfei Zhu <email address hidden>
Date: Thu Jul 30 18:03:46 2015 +0800

    VMware: Fix re-attach volume error for VC 5.1

    vCenter server version 5.1 does not support Storage Policy Based
    Management. This patch adds a check before retrieving storage profiles
    which depends on SPBM. Storage profiles are used to check datastore
    compliance.

    Change-Id: Iba465becdc3e7bac2f47c3984ea42cc6537911ae
    Closes-Bug: #1479402

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/kilo
Review: https://review.openstack.org/307018

[OpenStack Infra (hudson-openstack)]

Change abandoned by Dave Walker (<email address hidden>) on branch: stable/kilo
Review: https://review.openstack.org/307018
Reason:
stable/kilo closed for 2015.1.4

This release is now pending its final release and no freeze exception has
been seen for this changeset. Therefore, I am now abandoning this change.

If this is not correct, please urgently raise a thread on openstack-dev.

More details at: https://wiki.openstack.org/wiki/StableBranch