Comment by rbowen for Hello there, after an update yesterday I'm now unable to attach volumes to instances. Volumes are created correctly but they can't be attached. I'm currently using CentOS 7 + OpenStack Kilo installed through RDO. The strange thing is that everything worked fine (I can't really tell if it was the update or not) and the attached volumes still work fine, however when I create a new one it won't attach. Detaching a previously-working volume and trying to attach it once again won't work. I'm pretty sure it's a iSCSI problem. 2015-09-20 19:25:36.914 3220 ERROR cinder.volume.targets.lio [req-a76f9cc4-ff35-461f-81bc-326359516746 1a685c0e9df94fe78dddb1bc5be76aff 0caf7ad6941043d6af3a7da92f86f1f4 - - -] Failed to create iscsi target for volume id:volume-2cf00add-b960-4928-b23c-d2450ec06ce6. 2015-09-20 19:25:36.916 3220 ERROR cinder.volume.targets.lio [req-a76f9cc4-ff35-461f-81bc-326359516746 1a685c0e9df94fe78dddb1bc5be76aff 0caf7ad6941043d6af3a7da92f86f1f4 - - -] Unexpected error while running command. 2015-09-20 19:25:36.917 3220 ERROR cinder.volume.manager [req-a76f9cc4-ff35-461f-81bc-326359516746 1a685c0e9df94fe78dddb1bc5be76aff 0caf7ad6941043d6af3a7da92f86f1f4 - - -] Unable to create export for volume 2cf00add-b960-4928-b23c-d2450ec06ce6 2015-09-20 19:25:36.921 3220 ERROR oslo_messaging.rpc.dispatcher [req-a76f9cc4-ff35-461f-81bc-326359516746 1a685c0e9df94fe78dddb1bc5be76aff 0caf7ad6941043d6af3a7da92f86f1f4 - - -] Exception during message handling: Bad or unexpected response from the storage volume backend API: Unable to create export for volume 2cf00add-b960-4928-b23c-d2450ec06ce6 2015-09-20 19:25:36.924 3220 ERROR oslo_messaging._drivers.common [req-a76f9cc4-ff35-461f-81bc-326359516746 1a685c0e9df94fe78dddb1bc5be76aff 0caf7ad6941043d6af3a7da92f86f1f4 - - -] Returning exception Bad or unexpected response from the storage volume backend API: Unable to create export for volume 2cf00add-b960-4928-b23c-d2450ec06ce6 to caller 2015-09-20 19:25:36.925 3220 ERROR oslo_messaging._drivers.common [req-a76f9cc4-ff35-461f-81bc-326359516746 1a685c0e9df94fe78dddb1bc5be76aff 0caf7ad6941043d6af3a7da92f86f1f4 - - -] ['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/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 1091, in initialize_connection\n raise exception.VolumeBackendAPIException(data=err_msg)\n', 'VolumeBackendAPIException: Bad or unexpected response from the storage volume backend API: Unable to create export for volume 2cf00add-b960-4928-b23c-d2450ec06ce6\n'] The configuration used uses LVMVolumeDriver (also tried LVMISCSIDriver with no luck, same output), iscsi_helper set to lioadm. EDIT: After some trial and error I tried to initialize the iSCSI target manually and this was the result: Sep 23 13:36:10 HOSTNAME kernel: iSCSI Login negotiation failed. Sep 23 13:36:11 HOSTNAME cinder-volume: 2015-09-23 13:36:11.103 3202 INFO cinder.volume.manager [req-2e77d78f-ed04-4a1d-bc5d-3fabd424a47b - - - - -] Updating volume status Sep 23 13:36:11 HOSTNAME iscsid: conn 0 login rejected: target error (03/01) Sep 23 13:36:12 HOSTNAME kernel: Unable to locate Target Portal Group on iqn.2010-10.org.openstack:volume-a19cbad8-8dfa-46a9-871c-126421cc87a2

$