Re: [Openstack] Stderr: "qemu-nbd: Failed to bdrv_open when attempting to boot from cinder volume

Hi Mark, Thanks for your answer. What I noticed is that this issue happens only when I try to start a VMfrom a bootable volume. I created the colume with cinder create --image-id __image_id__ volume_name. I don't see it when I boot a VM from an image in glance (nova boot --image __image_id__ --f

[Openstack] Stderr: "qemu-nbd: Failed to bdrv_open when attempting to boot from cinder volume

Hi all, After loading nbd module in compute node, I continued trying to boot from a bootable cinder volume but this is what I see in nova-compute.log. I checked in the archive and I found that this bug (1126348) has been fixed in grizzly 2013.1 which I am running. Thanks for your help. Amine. C

[Openstack] nova-compute : nbd module not loaded

Hi All, I have had time to investigate why booting from volume doesn't work and I found the following trace in /var/log/nova/nova-compute.log. I took a look at nova.conf but I couldn't find any relevent entry for nova.virt.disk.mount.disk. Is it normal to have this trace? It occurs every time I

[Openstack] Booting from a volume makes the VM unreachable from controller node

Hi all, I finally managed to boot a VM, ping it and even ssh into it on my modest openstack cloud (Three machines only). Very proud of it :-))) So I moved to the next level which is to boot a VM on a volume and things got a little bit cloudy. I created a volume with cinder and followed the " Manu

Re: [Openstack] controller and network node, same machine?

Hi Steve, Why do you say that? I am curious to learn about the difficulties you have had. I also tried to have controller node and network node running on the same machine but I have never managed to ping a running VM in this configuration with FOLSOM release. Everything was working fine but impo

Re: [Openstack] grizzly's cinder-api is not starting : Couldn't find urlmap package

wrote: > Please post the contents of your /etc/cinder directory, I think this is > related to an issue I saw during grenade testing. > > -Sean > > > On 04/12/2013 08:29 AM, Mohammed Amine SAYA wrote: > >> Hi All, >> >> I am trying to start cinde

[Openstack] grizzly's cinder-api is not starting : Couldn't find urlmap package

Hi All, I am trying to start cinder-api but it complains about urlmap module. I checked in "/usr/lib/python2.7/dist-packages/paste/" directory and I found urlmap.py and urlmap.pyc. Have you heard about this behavior in cinder-api? I didn't have it with FOLSOM. Here is the error I found in cinder

Re: [Openstack] Can't log in grizzly's dashboard

> > do you have sync the db with keystone-manage sync_db ? > > Do you see any errors in your keystone.log? > > Greetings > Heiko > > On 11.04.2013 14:17, Mohammed Amine SAYA wrote: > > Hi all, > > I upgraded my install from folsom to grizzly but I can&#x

[Openstack] Can't log in grizzly's dashboard

Hi all, I upgraded my install from folsom to grizzly but I can't log in dashboard. I keep getting this error : HTTPConnectionPool(host='192.168.0.1', port=8776): Max retries exceeded with url: /v1/5690876e82414117b80e64167a3ee3f8/os-quota-sets/5690876e82414117b80e64167a3ee3f8 I haven't changed t

Re: [Openstack] How to get around bug 1135948

ent; sudo pkill dnsmaq ; start quantum-dhcp > agent that should do the clean up I believe. But I don't think this is > stopping you from pinging. > > Aaron > > On Thu, Mar 28, 2013 at 7:46 AM, Mohammed Amine SAYA < > asaya.openst...@gmail.com> wrote: > >> Hi A

[Openstack] How to get around bug 1135948

Hi All, I am trying to find out how to get around this bug : https://bugs.launchpad.net/quantum/+bug/1135948 in FOLSOM release. I saw in the bug's history that it was fixed and released on 2013-03-13, which means that it's has been included in grizzly-rc1 but unfortunately grizzly-rc1 packages a

[Openstack] Openstack grizzly rc1 packages availability for Debian

Hi All, I ran into quantum dhcp issue described in bug 1135948 and I also learned that it has been fixed in quantum grizzly-rc1. Does somebody know something about grizzly-rc1 package availability for DEBIAN ? Thanks for your help, Amine. ___ Mailing li

[Openstack] Fwd: Can't ping my VM after associating a floating IP address

rvice quantum-XXX-agent restart' instead of 'sudo > /etc/init.d/quantum-X-agent restart' directly. > > -Sylvain > > Le 20/03/2013 14:29, Mohammed Amine SAYA a écrit : > > Hi Sylvain, > > Thanks for your answer. > > No I am not. I am actually logged in

Re: [Openstack] Can't ping my VM after associating a floating IP address

27;, '/usr/bin/quantum-rootwrap', '/etc/quantum/rootwrap.conf', 'ovs-vsctl', '--', '--may-exist', 'add-port', 'br-int', 'tap8d6cc6c4-d1', '--', 'set', 'Interface', 'tap8d6cc6c4-d1&#

Re: [Openstack] Failed to log into dashboard web interface

set to metadata only. I fixed the issue by setting enabled_apis to ec2,osapi_compute,metadata. I would be glad if this could help anybody. Amine. On Sat, Mar 9, 2013 at 2:30 AM, Mohammed Amine SAYA < asaya.openst...@gmail.com> wrote: > After many hours investigating sign in error in h

[Openstack] Failed to log into dashboard web interface

After many hours investigating sign in error in horizon, I found the last line responsible for this issue in /var/log/apache2/error.log : [Sat Mar 09 01:12:18 2013] [error] File "/usr/lib/python2.7/dist-packages/novaclient/client.py", line 195, in request [Sat Mar 09 01:12:18 2013] [error] r

[Openstack] Failed to log into dashboard

Hi all, I am trying to install openstack and I can't log into dashboard. In fact, to be accurate, this problem surfaced after I updated openstack packages for debian from http://33.apt-proxy.gplhost.com/debian. It was working before. I don't what went wrong with this upgrade. nova, keystone, gla

[Openstack] glance-api and glance-registry startup error

Hi all, I am new to openstack and I managed to get two servers to manage and install openstack on debian distros. I managed to install MySQL, keystone and glance. The later still causes some headaches because this line keeps showing up in glance-api.log and glance-registry.log : 2013-02-11 23:22