OpenStack Cinder Integration Errors

1,083 views
Skip to first unread message

Duncan Wannamaker

unread,
Apr 2, 2015, 4:14:21 PM4/2/15
to quadst...@googlegroups.com

I have followed the documentation provided @ http://www.quadstor.com/openstack-cinder-volume-driver.html

 

This is the output from /var/log/cinder/volume.log when we attempt to attach a volume:

 

2015-04-02 15:52:30.858 4818 ERROR cinder.volume.manager [req-1a55e0fb-6298-4bbc-8a82-3e5f8dee26a8 db90e9f1516d498296454251da960d18 d19ba56998f147e49345178a6274b4e9 - - -] Unable to fetch connection information from backend: 'QUADStorSanISCSIDriver' object has no attribute 'target_helper'

2015-04-02 15:52:30.859 4818 ERROR oslo.messaging.rpc.dispatcher [req-1a55e0fb-6298-4bbc-8a82-3e5f8dee26a8 db90e9f1516d498296454251da960d18 d19ba56998f147e49345178a6274b4e9 - - -] Exception during message handling: Bad or unexpected response from the storage volume backend API: Unable to fetch connection information from backend: 'QUADStorSanISCSIDriver' object has no attribute 'target_helper'

2015-04-02 15:52:30.859 4818 TRACE oslo.messaging.rpc.dispatcher Traceback (most recent call last):

2015-04-02 15:52:30.859 4818 TRACE oslo.messaging.rpc.dispatcher   File "/usr/lib/python2.7/site-packages/oslo/messaging/rpc/dispatcher.py", line 134, in _dispatch_and_reply

2015-04-02 15:52:30.859 4818 TRACE oslo.messaging.rpc.dispatcher     incoming.message))

2015-04-02 15:52:30.859 4818 TRACE oslo.messaging.rpc.dispatcher   File "/usr/lib/python2.7/site-packages/oslo/messaging/rpc/dispatcher.py", line 177, in _dispatch

2015-04-02 15:52:30.859 4818 TRACE oslo.messaging.rpc.dispatcher     return self._do_dispatch(endpoint, method, ctxt, args)

2015-04-02 15:52:30.859 4818 TRACE oslo.messaging.rpc.dispatcher   File "/usr/lib/python2.7/site-packages/oslo/messaging/rpc/dispatcher.py", line 123, in _do_dispatch

2015-04-02 15:52:30.859 4818 TRACE oslo.messaging.rpc.dispatcher     result = getattr(endpoint, method)(ctxt, **new_args)

2015-04-02 15:52:30.859 4818 TRACE oslo.messaging.rpc.dispatcher   File "/usr/lib/python2.7/site-packages/osprofiler/profiler.py", line 105, in wrapper

2015-04-02 15:52:30.859 4818 TRACE oslo.messaging.rpc.dispatcher     return f(*args, **kwargs)

2015-04-02 15:52:30.859 4818 TRACE oslo.messaging.rpc.dispatcher   File "/usr/lib/python2.7/site-packages/cinder/volume/manager.py", line 902, in initialize_connection

2015-04-02 15:52:30.859 4818 TRACE oslo.messaging.rpc.dispatcher     raise exception.VolumeBackendAPIException(data=err_msg)

2015-04-02 15:52:30.859 4818 TRACE oslo.messaging.rpc.dispatcher VolumeBackendAPIException: Bad or unexpected response from the storage volume backend API: Unable to fetch connection information from backend: 'QUADStorSanISCSIDriver' object has no attribute 'target_helper'

2015-04-02 15:52:30.859 4818 TRACE oslo.messaging.rpc.dispatcher

2015-04-02 15:52:30.861 4818 ERROR oslo.messaging._drivers.common [req-1a55e0fb-6298-4bbc-8a82-3e5f8dee26a8 db90e9f1516d498296454251da960d18 d19ba56998f147e49345178a6274b4e9 - - -] Returning exception Bad or unexpected response from the storage volume backend API: Unable to fetch connection information from backend: 'QUADStorSanISCSIDriver' object has no attribute 'target_helper' to caller

2015-04-02 15:52:30.862 4818 ERROR oslo.messaging._drivers.common [req-1a55e0fb-6298-4bbc-8a82-3e5f8dee26a8 db90e9f1516d498296454251da960d18 d19ba56998f147e49345178a6274b4e9 - - -] ['Traceback (most recent call last):\n', '  File "/usr/lib/python2.7/site-packages/oslo/messaging/rpc/dispatcher.py", line 134, in _dispatch_and_reply\n    incoming.message))\n', '  File "/usr/lib/python2.7/site-packages/oslo/messaging/rpc/dispatcher.py", line 177, in _dispatch\n    return self._do_dispatch(endpoint, method, ctxt, args)\n', '  File "/usr/lib/python2.7/site-packages/oslo/messaging/rpc/dispatcher.py", line 123, in _do_dispatch\n    result = getattr(endpoint, method)(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 902, 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: 'QUADStorSanISCSIDriver' object has no attribute 'target_helper'\n"]

 

This is from OpenStack icehouse installed with packstack on CentOS7.

 

We are able to create volumes without issue and they show up in the vDisks list, but attaching volumes and copying glance images to volumes produces the above error.

 

Thanks,

Duncan Wannamaker

 

QUADStor Support

unread,
Apr 2, 2015, 4:19:31 PM4/2/15
to quadstor-virt
Possibly this issue https://bugs.launchpad.net/cinder/+bug/1400804 ?
Seems to be a bug which probably is yet to be merged to juno (used by
the RHEL
7)

Does commenting out iscsi_helper in cinder.conf help ? (if you are not
using LIO)
> --
> You received this message because you are subscribed to the Google Groups
> "QUADStor Storage Virtualization" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to quadstor-vir...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



--
Storage Virtualization Features
http://www.quadstor.com/storage-virtualization.html
Offloaded Data Transfers (ODX) Introduction
http://www.quadstor.com/offloaded-data-transfers-odx.html
vStorage APIs for Array Integration (VAAI)
http://www.quadstor.com/vstorage-apis-for-array-integration-vaai.html
Documentation http://www.quadstor.com/storage-virtualization-documentation.html

Duncan Wannamaker

unread,
Apr 2, 2015, 4:38:51 PM4/2/15
to quadst...@googlegroups.com
Thanks for the quick response. I believe you're right about that bug being the issue. I did uncomment the iscsi_helper line from the [lvm] volume driver section:

[lvm]
#iscsi_helper=lioadm

Also lvm is not currently enabled in the enabled_backends= configuration setting. Only the quadstor-1 and quadstor-2 backends as described in the configuration example.

Unfortunately, I still get the same error:

ImageCopyFailure: Failed to copy image to volume: Bad or unexpected response from the storage volume backend API: Unable to fetch connection information from backend: 'QUADStorSanISCSIDriver' object has no attribute 'target_helper'

QUADStor Support

unread,
Apr 2, 2015, 4:55:03 PM4/2/15
to quadstor-virt
On Fri, Apr 3, 2015 at 2:03 AM, Duncan Wannamaker
<Duncan.W...@globalknowledge.com> wrote:
> Thanks for the quick response. I believe you're right about that bug being the issue. I did uncomment the iscsi_helper line from the [lvm] volume driver section:
>
> [lvm]
> #iscsi_helper=lioadm
>
> Also lvm is not currently enabled in the enabled_backends= configuration setting. Only the quadstor-1 and quadstor-2 backends as described in the configuration example.
The stack trace should occur even if lvm isn't enabled in the backends
>
> Unfortunately, I still get the same error:
Were the cinder services restarted ?

>
> ImageCopyFailure: Failed to copy image to volume: Bad or unexpected response from the storage volume backend API: Unable to fetch connection information from backend: 'QUADStorSanISCSIDriver' object has no attribute 'target_helper'
You could try applying the patch and see if it helps.
Secondly we are yet to investigate how you can use a volume with an
image as source. As of now empty volumes will work fine. Maybe that is
the issue here.

Duncan Wannamaker

unread,
Apr 3, 2015, 2:42:00 PM4/3/15
to quadst...@googlegroups.com
Hey, thanks again for the assistance.

I have restarted the cinder-volume and cinder-scheduler services. I get the target_helper error even when attaching an empty volume to an instance. I am able to create empty volumes and snapshots without any issues. The problem comes when attaching the iSCSI volume to anything.

I have not been able to test applying the patch to our code yet. It will likely be several days before I have another opportunity. If I am able to get any progress I will update the thread.

Thanks,
Duncan
Reply all
Reply to author
Forward
0 new messages