Cant attach volume to instance (Icehouse)

asked 2014-09-30 15:46:34 -0600

AmitA gravatar image

updated 2014-10-15 17:14:36 -0600


Some more trouble shooting on this (and still no progress) I see this when I reboot (or use targetcli which is below this log):

[root@block1 Python-2014-09-30-15:11:51-7481]# more backtrace Could not create NetworkPortal in configFS.

Traceback (most recent call last): File "/bin/cinder-rtstool", line 238, in <module> sys.exit(main()) File "/bin/cinder-rtstool", line 203, in main create(backing_device, name, userid, password, initiator_iqns) File "/bin/cinder-rtstool", line 95, in create rtslib.NetworkPortal(tpg_new, '', 3260, mode='any') File "/usr/lib/python2.7/site-packages/rtslib/", line 694, in __init__ self._create_in_cfs_ine(mode) File "/usr/lib/python2.7/site-packages/rtslib/", line 60, in _create_in_cfs_ine % self.__class__.__name__)

RTSLibError: Could not create NetworkPortal in configFS.

Local variables in innermost frame:

self: <networkportal"" port="" 3260="">

mode: 'any'

FROM targetcli:

/iscsi/iqn.20.../tpg1/portals> ls

o- portals ............................................................................................................ [Portals: 0]

/iscsi/iqn.20.../tpg1/portals> create ip_address=

Using default IP port 3260

Could not create NetworkPortal in configFS.


Hi all,

Im keeping on keeping on with this - now this error. Ive created volumes just fine on another node (block1):

[block1 etc]# cinder list


|                  ID                  |   Status  | Display Name | Size | Volume Type | Bootable | Attached to |


| 4c6e1b15-2c7e-4bca-aae4-925cc054db8d | available |   myVolume   |  1   |     None    |  false   |             |

| 5c19f39c-445f-4de3-8f79-266f16bc1f01 | available |    test2     |  5   |     None    |  false   |             |

| b8df2a1a-48df-443c-a078-bec907d8462d | available |   amitvol    |  10  |     None    |  false   |             |


But when I goto try and add to an existing instance it always fails with the same errors below. Ive been searching around to see if I could find anything to help but no luck. Anyone solve the same issue I would really appreciate the insight. Just an fyi, I believe everything is working in my stack except for name resolution (I cant nslookup from my instances so dont know if anything is incorrect with the networking still working on that as well) which I dont think is interfering with any of this.

From the lhe logs the things that standout the most: 2

014-09-30 16:15:20.724 9380 WARNING cinder.context [-] Arguments dropped when creating context: {'user': u'8748be7fb9d544c088a7192137422231', 'tenant': u'bb
7ce560d1e9482b862679cefaf5ae69', 'user_identity': u'8748be7fb9d544c088a7192137422231 bb7ce560d1e9482b862679cefaf5ae69 - - -'}

2014-09-30 16:15:21.163 9380 ERROR cinder.brick.iscsi.iscsi [req-6e2a240b-0dbe-4bc1-a999-140390fc881a 8748be7fb9d544c088a7192137422231 bb7ce560d1e9482b862679
cefaf5ae69 - - -] Failed to create iscsi target for volume id:volume-5c19f39c-445f-4de3-8f79-266f16bc1f01.

2014-09-30 16:15:21.164 9380 ERROR cinder.brick.iscsi.iscsi [req-6e2a240b-0dbe-4bc1-a999-140390fc881a 8748be7fb9d544c088a7192137422231 bb7ce560d1e9482b862679
cefaf5ae69 - - -] Unexpected error while running command.
Command: sudo cinder-rootwrap /etc/cinder/rootwrap.conf cinder-rtstool create /dev/cinder-volumes/volume-5c19f39c-445f-4de3-8f79-266f16bc1f01
.openstack:volume-5c19f39c-445f-4de3-8f79-266f16bc1f01 8mF2aKotgGESWTjo9ker H9bXAoYd42HummFomiTc

Exit code: 1
Stdout: 'Error creating NetworkPortal: ensure port 3260 is not in use by another service.\n'
Stderr: 'Traceback (most recent call last):\n  File "/bin/cinder-rtstool", line 238, in <module>\n    sys.exit(main())\n  File "/bin/cinder-rtstool", line 20
3, in main\n    create(backing_device, name, userid, password, initiator_iqns)\n  File "/bin/cinder-rtstool", line 95, in create\n    rtslib.NetworkPortal(tp
g_new, \'\', 3260, mode=\'any\')\n  File "/usr/lib/python2.7 ...
edit retag flag offensive close merge delete


are you trying to attach the volume before the instance is finished booting? I've run into timing issues around that. If you do a soft reboot of the instance does it then attach?

Heather gravatar imageHeather ( 2014-10-02 12:28:44 -0600 )edit

HI Bob thanks for helping. Yeah tried that and just to make sure tried it again (soft reboot) and made sure instance is up but same errors.

AmitA gravatar imageAmitA ( 2014-10-02 13:16:42 -0600 )edit

I had a different problem with iscsiadm port 3260 because cinder was not usin the neutron management network but instead a different external address for the cinder host causing firwall to block the port. I added my_ip=10.0.0.xx to /etc/cinder/cinder.conf and verified firewall allowed access.

rl.eaton gravatar imagerl.eaton ( 2014-10-24 14:33:30 -0600 )edit

Thanks rl - I have that defined as well and still same error. I defined the following to the block node ip:




Keep getting the same error! Very confusing.

AmitA gravatar imageAmitA ( 2014-11-03 11:17:30 -0600 )edit

One other thing not mentioned in the install guide that I needed to do to get cinder to work is add iscsi_helper=tgtadm to cinder.conf on the cinder hosts.

rl.eaton gravatar imagerl.eaton ( 2014-11-05 22:06:15 -0600 )edit