Ask Your Question
1

Why will volume not attach to instance? [closed]

asked 2015-01-08 09:24:03 -0500

mickt gravatar image

updated 2015-01-20 04:41:24 -0500

Would anyone have an idea as to why volumes are failing to attach to instances in my system?

Storage node volume.log has following errors

2015-01-08 14:38:01.547 3386 TRACE oslo.messaging.rpc.dispatcher Traceback (most recent call last):
2015-01-08 14:38:01.547 3386 TRACE oslo.messaging.rpc.dispatcher   File "/usr/lib/python2.7/site-packages/oslo/messaging/rpc/dispatcher.py", line 134, in _dispatch_and_reply
2015-01-08 14:38:01.547 3386 TRACE oslo.messaging.rpc.dispatcher     incoming.message))
2015-01-08 14:38:01.547 3386 TRACE oslo.messaging.rpc.dispatcher   File "/usr/lib/python2.7/site-packages/oslo/messaging/rpc/dispatcher.py", line 177, in _dispatch
2015-01-08 14:38:01.547 3386 TRACE oslo.messaging.rpc.dispatcher     return self._do_dispatch(endpoint, method, ctxt, args)
2015-01-08 14:38:01.547 3386 TRACE oslo.messaging.rpc.dispatcher   File "/usr/lib/python2.7/site-packages/oslo/messaging/rpc/dispatcher.py", line 123, in _do_dispatch
2015-01-08 14:38:01.547 3386 TRACE oslo.messaging.rpc.dispatcher     result = getattr(endpoint, method)(ctxt, **new_args)
2015-01-08 14:38:01.547 3386 TRACE oslo.messaging.rpc.dispatcher   File "/usr/lib/python2.7/site-packages/osprofiler/profiler.py", line 105, in wrapper
2015-01-08 14:38:01.547 3386 TRACE oslo.messaging.rpc.dispatcher     return f(*args, **kwargs)
2015-01-08 14:38:01.547 3386 TRACE oslo.messaging.rpc.dispatcher   File "/usr/lib/python2.7/site-packages/cinder/volume/manager.py", line 875, in initialize_connection
2015-01-08 14:38:01.547 3386 TRACE oslo.messaging.rpc.dispatcher     volume)
2015-01-08 14:38:01.547 3386 TRACE oslo.messaging.rpc.dispatcher   File "/usr/lib/python2.7/site-packages/osprofiler/profiler.py", line 105, in wrapper
2015-01-08 14:38:01.547 3386 TRACE oslo.messaging.rpc.dispatcher     return f(*args, **kwargs)
2015-01-08 14:38:01.547 3386 TRACE oslo.messaging.rpc.dispatcher   File "/usr/lib/python2.7/site-packages/cinder/volume/drivers/lvm.py", line 548, in create_export
2015-01-08 14:38:01.547 3386 TRACE oslo.messaging.rpc.dispatcher     return self._create_export(context, volume)
2015-01-08 14:38:01.547 3386 TRACE oslo.messaging.rpc.dispatcher   File "/usr/lib/python2.7/site-packages/cinder/volume/drivers/lvm.py", line 560, in _create_export
2015-01-08 14:38:01.547 3386 TRACE oslo.messaging.rpc.dispatcher     self.configuration)
2015-01-08 14:38:01.547 3386 TRACE oslo.messaging.rpc.dispatcher   File "/usr/lib/python2.7/site-packages/cinder/volume/iscsi.py", line 61, in create_export
2015-01-08 14:38:01.547 3386 TRACE oslo.messaging.rpc.dispatcher     conf.iscsi_write_cache)
2015-01-08 14:38:01.547 3386 TRACE oslo.messaging.rpc.dispatcher   File "/usr/lib/python2.7/site-packages/cinder/brick/iscsi/iscsi.py", line 553, in create_iscsi_target
2015-01-08 14:38:01.547 3386 TRACE oslo.messaging.rpc.dispatcher     raise exception.NotFound()
2015-01-08 14:38:01.547 3386 TRACE oslo.messaging.rpc.dispatcher NotFound: Resource could not be found.
2015-01-08 14:38:01.547 3386 TRACE oslo.messaging.rpc.dispatcher
2015-01-08 14:38:01.549 3386 ERROR oslo.messaging._drivers.common [req-95cf5e4b-1171-4573-bdcb-a1bf6ebdb83d 55ab7688952a4cf8b7e868cdcef86c71 63833f288f4d4fe3a0524af597ffa053 - - -] Returning exception Resource could not be found. to caller
2015-01-08 14:38:01.550 3386 ERROR oslo ...
(more)
edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by mickt
close date 2015-01-28 06:34:00.055654

Comments

1

Dont add comments, try to edit the question instead. The error message is more useful than a bunch of details on the configuration. Did you find the solution?

smaffulli gravatar imagesmaffulli ( 2015-01-09 18:54:05 -0500 )edit

Moved error messages to top of question, configuration follows in support. No solution yet.

mickt gravatar imagemickt ( 2015-01-12 02:55:36 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2015-01-28 06:33:45 -0500

mickt gravatar image

Basically it was misconfiguration.

Each iscsi initiator must have a unique name; this was not the case. I also removed existing target configuration relating to target00 etc.

I also configured the following in storage host cinder.conf [DEFAULT] section:

iscsi_target_prefix, iscsi_ip_address, volume_backend_name, iscsi_helper, lio_initiator_iqns, iscsi_iotype

edit flag offensive delete link more

Comments

A further observation is that it seems fine if I launch an instance with create volume prior create a volumes and attaching to instances.

mickt gravatar imagemickt ( 2015-02-03 03:44:29 -0500 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2015-01-08 09:24:03 -0500

Seen: 883 times

Last updated: Jan 28 '15