Lefthand driver fails to attach a cloned volume

Bug #1418201 reported by Kurt Martin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Fix Released
High
Kurt Martin

Bug Description

When attempting to attached a cloned volume the following exception occurs in the LH driver

2015-02-04 11:56:17.642 ERROR cinder.volume.driver [req-714a595d-dfd2-46dc-96fd-14f462795a9f e4967289a9de4415930a2b0fa399bcd8 952a76d0163e479ea7f2d8d53ac8e5e4] ISCSI discovery attempt failed for:csim-demo1
2015-02-04 11:56:17.643 DEBUG cinder.volume.driver [req-714a595d-dfd2-46dc-96fd-14f462795a9f e4967289a9de4415930a2b0fa399bcd8 952a76d0163e479ea7f2d8d53ac8e5e4] Error from iscsiadm -m discovery: iscsiadm: Connection to Discovery Address 127.0.0.1 failed
iscsiadm: Login I/O error, failed to receive a PDU
iscsiadm: retrying discovery login to 127.0.0.1
iscsiadm: Connection to Discovery Address 127.0.0.1 failed
iscsiadm: Login I/O error, failed to receive a PDU
iscsiadm: retrying discovery login to 127.0.0.1
iscsiadm: Connection to Discovery Address 127.0.0.1 failed
iscsiadm: Login I/O error, failed to receive a PDU
iscsiadm: retrying discovery login to 127.0.0.1
iscsiadm: Connection to Discovery Address 127.0.0.1 failed
iscsiadm: Login I/O error, failed to receive a PDU
iscsiadm: retrying discovery login to 127.0.0.1
iscsiadm: Connection to Discovery Address 127.0.0.1 failed
iscsiadm: Login I/O error, failed to receive a PDU
iscsiadm: retrying discovery login to 127.0.0.1
iscsiadm: Connection to Discovery Address 127.0.0.1 failed
iscsiadm: Login I/O error, failed to receive a PDU
iscsiadm: retrying discovery login to 127.0.0.1
iscsiadm: connection login retries (reopen_max) 5 exceeded
iscsiadm: Could not perform SendTargets discovery: encountered iSCSI login failure
 from (pid=34374) _do_iscsi_discovery /opt/stack/cinder/cinder/volume/driver.py:922
2015-02-04 11:56:17.660 ERROR cinder.volume.manager [req-714a595d-dfd2-46dc-96fd-14f462795a9f e4967289a9de4415930a2b0fa399bcd8 952a76d0163e479ea7f2d8d53ac8e5e4] Unable to fetch connection information from backend: Invalid volume: Could not find iSCSI export for volume volume-7ae5ce82-7a6d-49ce-9daf-51d350370fc3
2015-02-04 11:56:17.663 ERROR oslo_messaging.rpc.dispatcher [req-714a595d-dfd2-46dc-96fd-14f462795a9f e4967289a9de4415930a2b0fa399bcd8 952a76d0163e479ea7f2d8d53ac8e5e4] Exception during message handling: Bad or unexpected response from the storage volume backend API: Unable to fetch connection information from backend: Invalid volume: Could not find iSCSI export for volume volume-7ae5ce82-7a6d-49ce-9daf-51d350370fc3
2015-02-04 11:56:17.663 TRACE oslo_messaging.rpc.dispatcher Traceback (most recent call last):
2015-02-04 11:56:17.663 TRACE oslo_messaging.rpc.dispatcher File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 142, in _dispatch_and_reply
2015-02-04 11:56:17.663 TRACE oslo_messaging.rpc.dispatcher executor_callback))
2015-02-04 11:56:17.663 TRACE oslo_messaging.rpc.dispatcher File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 186, in _dispatch
2015-02-04 11:56:17.663 TRACE oslo_messaging.rpc.dispatcher executor_callback)
2015-02-04 11:56:17.663 TRACE oslo_messaging.rpc.dispatcher File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 130, in _do_dispatch
2015-02-04 11:56:17.663 TRACE oslo_messaging.rpc.dispatcher result = func(ctxt, **new_args)
2015-02-04 11:56:17.663 TRACE oslo_messaging.rpc.dispatcher File "/usr/local/lib/python2.7/dist-packages/osprofiler/profiler.py", line 105, in wrapper
2015-02-04 11:56:17.663 TRACE oslo_messaging.rpc.dispatcher return f(*args, **kwargs)
2015-02-04 11:56:17.663 TRACE oslo_messaging.rpc.dispatcher File "/usr/local/lib/python2.7/dist-packages/osprofiler/profiler.py", line 105, in wrapper
2015-02-04 11:56:17.663 TRACE oslo_messaging.rpc.dispatcher return f(*args, **kwargs)
2015-02-04 11:56:17.663 TRACE oslo_messaging.rpc.dispatcher File "/usr/local/lib/python2.7/dist-packages/osprofiler/profiler.py", line 105, in wrapper
2015-02-04 11:56:17.663 TRACE oslo_messaging.rpc.dispatcher return f(*args, **kwargs)
2015-02-04 11:56:17.663 TRACE oslo_messaging.rpc.dispatcher File "/opt/stack/cinder/cinder/volume/manager.py", line 927, in initialize_connection
2015-02-04 11:56:17.663 TRACE oslo_messaging.rpc.dispatcher raise exception.VolumeBackendAPIException(data=err_msg)
2015-02-04 11:56:17.663 TRACE oslo_messaging.rpc.dispatcher VolumeBackendAPIException: Bad or unexpected response from the storage volume backend API: Unable to fetch connection information from backend: Invalid volume: Could not find iSCSI export for volume volume-7ae5ce82-7a6d-49ce-9daf-51d350370fc3
2015-02-04 11:56:17.663 TRACE oslo_messaging.rpc.dispatcher
2015-02-04 11:56:17.669 ERROR oslo_messaging._drivers.common [req-714a595d-dfd2-46dc-96fd-14f462795a9f e4967289a9de4415930a2b0fa399bcd8 952a76d0163e479ea7f2d8d53ac8e5e4] Returning exception Bad or unexpected response from the storage volume backend API: Unable to fetch connection information from backend: Invalid volume: Could not find iSCSI export for volume volume-7ae5ce82-7a6d-49ce-9daf-51d350370fc3 to caller
2015-02-04 11:56:17.669 ERROR oslo_messaging._drivers.common [req-714a595d-dfd2-46dc-96fd-14f462795a9f e4967289a9de4415930a2b0fa399bcd8 952a76d0163e479ea7f2d8d53ac8e5e4] ['Traceback (most recent call last):\n', ' File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 142, in _dispatch_and_reply\n executor_callback))\n', ' File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 186, in _dispatch\n executor_callback)\n', ' File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 130, in _do_dispatch\n result = func(ctxt, **new_args)\n', ' File "/usr/local/lib/python2.7/dist-packages/osprofiler/profiler.py", line 105, in wrapper\n return f(*args, **kwargs)\n', ' File "/usr/local/lib/python2.7/dist-packages/osprofiler/profiler.py", line 105, in wrapper\n return f(*args, **kwargs)\n', ' File "/usr/local/lib/python2.7/dist-packages/osprofiler/profiler.py", line 105, in wrapper\n return f(*args, **kwargs)\n', ' File "/opt/stack/cinder/cinder/volume/manager.py", line 927, 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: Invalid volume: Could not find iSCSI export for volume volume-7ae5ce82-7a6d-49ce-9daf-51d350370fc3\n']

Changed in cinder:
status: New → Confirmed
assignee: nobody → Kurt Martin (kurt-f-martin)
tags: added: driver lefthand
tags: added: drivers
removed: driver
description: updated
summary: - Lefthand driver fails to attached a cloned volume
+ Lefthand driver fails to attach a cloned volume
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (master)

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

Changed in cinder:
status: Confirmed → In Progress
Changed in cinder:
importance: Undecided → High
milestone: none → kilo-3
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to cinder (master)

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

commit f71a2c535eaed8aec77354e1737618897fc2cbd0
Author: Kurt Martin <email address hidden>
Date: Wed Feb 4 16:09:44 2015 -0800

    Lefthand driver fails to attach a cloned volume

    The provider location was not being populated for cloned volumes.
    This patch is updating the provider location for cloned volumes
    resulting in successful volume attachments.

    Change-Id: I86ef7935ed7233377aa4745dc4b45fcab5703f0a
    Closes-Bug: 1418201

Changed in cinder:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in cinder:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in cinder:
milestone: kilo-3 → 2015.1.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.