Hi JP,
my bet is that this is a writing permissions issue. Does nova has the
right to write within the mounted directory?
*Razique Mahroua** - **Nuage & Co*
razique.mahroua@xxxxxxxxx <mailto:razique.mahroua@xxxxxxxxx>
Tel : +33 9 72 37 94 15
Le 11 avr. 2013 à 16:36, John Paul Walters <jwalters@xxxxxxx
<mailto:jwalters@xxxxxxx>> a écrit :
Hi,
We've started implementing a Glusterfs-based solution for instance
storage in order to provide live migration. I've run into a strange
problem when using a multi-node Gluster setup that I hope someone has
a suggestion to resolve.
I have a 12 node distributed/replicated Gluster cluster. I can mount
it to my client machines, and it seems to be working alright. When I
launch instances, the nova-compute log on the client machines are
giving me two error messages:
First is a qemu-kvm error: could not open disk image
/exports/instances/instances/instance-00000242/disk: Invalid argument
(full output at http://pastebin.com/i8vzWegJ)
The second error message comes a short time later ending with
nova.openstack.common.rpc.amqp Invalid: Instance has already been created
(full output at http://pastebin.com/6Ta4kkBN)
This happens reliably with the multi-Gluster-node setup. Oddly,
after creating a test Gluster volume composed of a single brick and
single node, everything works fine.
Does anyone have any suggestions?
thanks,
JP
_______________________________________________
Mailing list: https://launchpad.net/~openstack
<https://launchpad.net/%7Eopenstack>
Post to : openstack@xxxxxxxxxxxxxxxxxxx
<mailto:openstack@xxxxxxxxxxxxxxxxxxx>
Unsubscribe : https://launchpad.net/~openstack
<https://launchpad.net/%7Eopenstack>
More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list:https://launchpad.net/~openstack
Post to :openstack@xxxxxxxxxxxxxxxxxxx
Unsubscribe :https://launchpad.net/~openstack
More help :https://help.launchpad.net/ListHelp