I've jut checked the log of volume.py module and I couldn't find any version containing that extra whitespace mentioned in your report. Could it be that it was introduced by mistake in your local checkout?
See https://github.com/openstack/nova/blob/master/nova/virt/libvirt/volume.py#L810 ** Changed in: nova Status: Triaged => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1254007 Title: Error attaching a cinder glousterfs volume with libvirt Status in OpenStack Compute (Nova): Invalid Bug description: I quite investigating it. The problem seams to be related to nova/virt/libvirt/volume.py function _mount_glusterfs prepares a command to locally mount a glusterfs volume with this line of code: gluster_cmd.extend([glusterfs_share, mount_path, ' ']) the trailing white spaces causes mount error on my system. Using the original code i get: 2013-11-22 13:32:23.272 6686 TRACE nova.openstack.common.rpc.amqp File "/usr/lib/python2.6/site-packages/nova/utils.py", line 177, in execute 2013-11-22 13:32:23.272 6686 TRACE nova.openstack.common.rpc.amqp return processutils.execute(*cmd, **kwargs) 2013-11-22 13:32:23.272 6686 TRACE nova.openstack.common.rpc.amqp File "/usr/lib/python2.6/site-packages/nova/openstack/common/processutils.py", line 178, in execute 2013-11-22 13:32:23.272 6686 TRACE nova.openstack.common.rpc.amqp cmd=' '.join(cmd)) 2013-11-22 13:32:23.272 6686 TRACE nova.openstack.common.rpc.amqp ProcessExecutionError: Unexpected error while running command. 2013-11-22 13:32:23.272 6686 TRACE nova.openstack.common.rpc.amqp Command: sudo nova-rootwrap /etc/nova/rootwrap.conf mount -t glusterfs 10.101.101.120:v_cinder /var/lib/cinder/mnt/8bf7d2294d80777975e85e1905255721 2013-11-22 13:32:23.272 6686 TRACE nova.openstack.common.rpc.amqp Exit code: 1 2013-11-22 13:32:23.272 6686 TRACE nova.openstack.common.rpc.amqp Stdout: '' 2013-11-22 13:32:23.272 6686 TRACE nova.openstack.common.rpc.amqp Stderr: "Usage: mount -V : print version\n mount -h : print this help\n mount : list mounted filesystems\n mount -l : idem, including volume labels\nSo far the informational part. Next the mounting.\nThe command is `mount [-t fstype] something somewhere'.\nDetails found in /etc/fstab may be omitted.\n mount -a [-t|-O] ... : mount all stuff from /etc/fstab\n mount device : mount device at the known place\n mount directory : mount known device here\n mount -t type dev dir : ordinary mount command\nNote that one does not really mount a device, one mounts\na filesystem (of the given type) found on the device.\nOne can also mount an already visible directory tree elsewhere:\n mount --bind olddir newdir\nor move a subtree:\n mount --move olddir newdir\nOne can change the type of mount containing the directory dir:\n mount --make-shared dir\n mount --make-slave dir\n mount --make-private dir\n mount --make-unbindable dir\nOne can change the type of all the mounts in a mount subtree\ncontaining the directory dir:\n mount --make-rshared dir\n mount --make-rslave dir\n mount --make-rprivate dir\n mount --make-runbindable dir\nA device can be given by name, say /dev/hda1 or /dev/cdrom,\nor by label, using -L label or by uuid, using -U uuid .\nOther options: [-nfFrsvw] [-o options] [-p passwdfd].\nFor many more details, say man 8 mount .\n" 2013-11-22 13:32:23.272 6686 TRACE nova.openstack.common.rpc.amqp Simply replacing this line gluster_cmd.extend([glusterfs_share, mount_path, ' ']) with this gluster_cmd.extend([glusterfs_share, mount_path]) it works correctly and it mount and attach my cinder glouster volume I don't understand why a trailing space can cause this kind of problem. I'm using havana vanilla distribution on CENTOS 6.4 ciao To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1254007/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
