← Back to team overview

openstack team mailing list archive

Re: Essex volume attach issue on Debian Wheezy

 

Probably wheezy puts iscsiadm somewhere that rootwrap can't find it.

iscsiadm: CommandFilter, /sbin/iscsiadm, root                                                                                                                                                          
iscsiadm_usr: CommandFilter, /usr/bin/iscsiadm, root    

You should do a:

which iscsiadm

If it doesn't match the above you need to add a new filter to /etc/nova/rootwrap.d/volume.filters

Vish

On Dec 5, 2012, at 9:47 AM, Alberto Molina Coballes <alb.molina@xxxxxxxxx> wrote:

> Hi all,
> 
> We're facing an issue attaching a volume to a running instance in an Essex
> deployment on Debian Wheezy.
> 
> nova-volume is installed on the cloud controller, but nova-network is installed
> on the computes nodes in a multi_host setup.
> 
> The relevant configuration parameters in nova.conf are (nexentastor-ce is used
> for volume storage):
> 
> volume_driver=nova.volume.nexenta.volume.NexentaDriver
> use_local_volumes=false
> nexenta_host=172.22.222.2
> nexenta_volume=nova
> nexenta_user=admin
> nexenta_password=********
> 
> Volumes can be created properly:
> 
> $ nova volume-create --display_name demovol1 1
> $ nova volume-list
> +----+-----------+--------------+------+-------------+-------------+
> | ID |   Status  | Display Name | Size | Volume Type | Attached to |
> +----+-----------+--------------+------+-------------+-------------+
> | 1  | available | demovol1     | 1    | None        |             |
> +----+-----------+--------------+------+-------------+-------------+
> 
> But attaching to a volume fails with no error:
> 
> $ nova volume-attach 63abfd8a-...-...-... 1 /dev/vdc
> 
> and the volume still remains available.
> 
> It seems that the problem is related to these logs found in the compute node (nova-compute.log):
> 
> TRACE nova.rpc.amqp ProcessExecutionError: Unexpected error while running command.
> TRACE nova.rpc.amqp Command: sudo nova-rootwrap iscsiadm -m node -T iqn.1986-03.com.sun:02:nova-volume-0000001 -p 172.22.222.2:3260
> TRACE nova.rpc.amqp Exit code: 1
> TRACE nova.rpc.amqp Stdout: ''
> TRACE nova.rpc.amqp Stderr: 'Traceback (most recent call last):\n  File "/usr/bin/nova-rootwrap", line 69, in <module>\n    env=filtermatch.get_environment(userargs))\n  File "/usr/lib/python2.7/subprocess.py", line 679, in __init__\n    errread, errwrite)\n  File "/usr/lib/python2.7/subprocess.py", line 1249, in _execute_child\n    raise child_exception\nOSError: [Errno 2] No such file or directory\n'
> 
> Trying to execute this command from the command line (as nova user):
> 
> nova@calisto:~$ sudo nova-rootwrap iscsiadm -m node -T iqn.1986-03.com.sun:02:nova-volume-0000001 -p 172.22.222.2:3260
> Traceback (most recent call last):
>  File "/usr/bin/nova-rootwrap", line 69, in <module>
>    env=filtermatch.get_environment(userargs))
>  File "/usr/lib/python2.7/subprocess.py", line 679, in __init__
>    errread, errwrite)
>  File "/usr/lib/python2.7/subprocess.py", line 1249, in _execute_child
>    raise child_exception
> OSError: [Errno 2] No such file or directory
> 
> Whereas executing the same command as root without "sudo nova-rootwrap" seems to
> work ok:
> 
> root@calisto:~# iscsiadm -m node -T iqn.1986-03.com.sun:02:nova-volume-0000001 -p 172.22.222.2:3260
> # BEGIN RECORD 2.0-873
> node.name = iqn.1986-03.com.sun:02:nova-volume-0000001
> node.tpgt = 1
> node.startup = manual
> ...
> 
> Any tips on this?
> 
> Cheers!
> 
> Alberto
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp



Follow ups

References