Ask Your Question
0

Cinder Error - Volume Not Attaching to Instance

asked 2017-02-01 06:59:50 -0600

Subiendo gravatar image

updated 2017-02-01 07:00:25 -0600

Hi guys,

Im trying to attach a volume to an instance and im not getting the volume when fdisk -l

Dont know how to follow this step at openstack

In the [lvm] section, configure the LVM back end with the LVM driver, cinder-volumes volume group, iSCSI protocol, and appropriate iSCSI service:

[lvm] ... volume_driver = cinder.volume.drivers.lvm.LVMVolumeDriver volume_group = cinder-volumes iscsi_protocol = iscsi iscsi_helper = lioadm

I dont find the [lvm] section and no [lvm] section is in the file.

Here is the cinder.conf file on the storage node => filedropper.com/cinder_1

Here's the log which displays the error.

2017-02-01 13:41:29.752 3064 ERROR oslo_messaging.rpc.dispatcher [req-8ca989fe-3b12-4cf0-bd14-9a26923ec9e4 7ead70b5918b4e3c97ca8cce96d41978 9b77bb7a532d4b40a06323640a811b67 - - -] Exception during message handling: Unexpected error while running command.
Command: sudo cinder-rootwrap /etc/cinder/rootwrap.conf tgtadm --lld iscsi --op show --mode target
Exit code: 96
Stdout: u''
Stderr: u'/usr/bin/cinder-rootwrap: Executable not found: tgtadm (filter match = tgtadm)\n'
2017-02-01 13:41:29.752 3064 ERROR oslo_messaging.rpc.dispatcher Traceback (most recent call last):
2017-02-01 13:41:29.752 3064 ERROR oslo_messaging.rpc.dispatcher   File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 138, in _dispatch_and_reply
2017-02-01 13:41:29.752 3064 ERROR oslo_messaging.rpc.dispatcher     incoming.message))
2017-02-01 13:41:29.752 3064 ERROR oslo_messaging.rpc.dispatcher   File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 185, in _dispatch
2017-02-01 13:41:29.752 3064 ERROR oslo_messaging.rpc.dispatcher     return self._do_dispatch(endpoint, method, ctxt, args)
2017-02-01 13:41:29.752 3064 ERROR oslo_messaging.rpc.dispatcher   File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 127, in _do_dispatch
2017-02-01 13:41:29.752 3064 ERROR oslo_messaging.rpc.dispatcher     result = func(ctxt, **new_args)
2017-02-01 13:41:29.752 3064 ERROR oslo_messaging.rpc.dispatcher   File "/usr/lib/python2.7/site-packages/cinder/volume/manager.py", line 1442, in initialize_connection
2017-02-01 13:41:29.752 3064 ERROR oslo_messaging.rpc.dispatcher     volume, connector)
2017-02-01 13:41:29.752 3064 ERROR oslo_messaging.rpc.dispatcher   File "/usr/lib/python2.7/site-packages/cinder/volume/drivers/lvm.py", line 760, in create_export
2017-02-01 13:41:29.752 3064 ERROR oslo_messaging.rpc.dispatcher     volume_path)
2017-02-01 13:41:29.752 3064 ERROR oslo_messaging.rpc.dispatcher   File "/usr/lib/python2.7/site-packages/cinder/volume/targets/iscsi.py", line 210, in create_export
2017-02-01 13:41:29.752 3064 ERROR oslo_messaging.rpc.dispatcher     **portals_config)
2017-02-01 13:41:29.752 3064 ERROR oslo_messaging.rpc.dispatcher   File "/usr/lib/python2.7/site-packages/cinder/volume/targets/tgt.py", line 140, in create_iscsi_target
2017-02-01 13:41:29.752 3064 ERROR oslo_messaging.rpc.dispatcher     run_as_root=True)
2017-02-01 13:41:29.752 3064 ERROR oslo_messaging.rpc.dispatcher   File "/usr/lib/python2.7/site-packages/cinder/utils.py", line 148, in execute
2017-02-01 13:41:29.752 3064 ERROR oslo_messaging.rpc.dispatcher     return processutils.execute(*cmd, **kwargs)
2017-02-01 13:41:29.752 3064 ERROR oslo_messaging.rpc.dispatcher   File "/usr/lib/python2.7/site-packages/oslo_concurrency/processutils.py", line 389, in execute
2017-02-01 13:41:29.752 3064 ERROR oslo_messaging.rpc.dispatcher     cmd ...
(more)
edit retag flag offensive close merge delete
add a comment

1 answer

Sort by ยป oldest newest most voted
0

answered 2017-02-01 08:30:45 -0600

Bernd Bausch gravatar image

Executable not found: tgtadm means that your Cinder is configured to use tgtadm for managing iSCSI targets, but the command is not found. Probably not installed. You need to fix your Cinder installation.

Regarding the lvm section in cinder.conf: If it's not in the file, just add it.

edit flag offensive delete link more

Comments

I thought tgt was not supported for Centos7?

Subiendo gravatar imageSubiendo ( 2017-02-02 05:42:13 -0600 )edit

If so, use LIO: http://docs.openstack.org/admin-guide....

Bernd Bausch gravatar imageBernd Bausch ( 2017-02-02 18:39:44 -0600 )edit

is not installed via this order yum install openstack-cinder targetcli python-oslo-policy ? I also have my cinder-volume on controller node status as "down" and I dont know why...

Subiendo gravatar imageSubiendo ( 2017-02-06 05:33:03 -0600 )edit

I don't know how to install tgtadm on Centos, but it's certainly not in openstack-cinder or python-oslo-policy.

On Fedora 23, tgtadm is in the scsi-target-utils package.

Bernd Bausch gravatar imageBernd Bausch ( 2017-02-07 18:30:06 -0600 )edit

Regarding your other problem, cinder-volume not running on the controller: There is only one cinder-volume process per Cinder backend. Did you create a backend on the controller? If so, again check the cinder-volume log to find out why the service is down.

Bernd Bausch gravatar imageBernd Bausch ( 2017-02-07 18:31:20 -0600 )edit
see more comments

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

subscribe to rss feed

Stats

Asked: 2017-02-01 06:59:50 -0600

Seen: 1,270 times

Last updated: Feb 01 '17

Related questions

attach volume, how to post `os-initialize_connection`

No Valid Host Was Found Cinder Volume Create

unicode object has no attribute get

snapshots fail to delete / volume unable to be deleted (mitaka) [closed]

Issue with creating a volume from image via cinder

keystone v3 is not working in python-cinderclient directly

what does "source volid" mean in Cinder? [closed]

Migration attached volume between cinder pools

Problem Creating Volume Backups

Which cinder service restart, when I added new backend