Revision history [back]

Good morning everyone!

Following my white rabbit on the wonderfull world of OS, I just came with a really strange issue on my Nova Compute/Network node.

As soon as I create an Instance, the creation fail because of a Nova Network error.

My node is compose of the following:

2xXeon E5520. 32Gb Ram. 67Gb Local HDD. 1Tb iSCSI Equallogic node (Cinder volume). Fedora 19 Schrodinger's Cat. Openstack Grizzly release.

I have installed the Qpidd C++ AMQP Broker, which is working great as cinder is available to fast and quickly create volume from Horizon Dashboard and/or from the local CLI.

Every nova module seems to working great, except the nova-volume which crash with the following stack on logs:

Nova Network Crash

Yeah, this is a big bad stack :D From my own search, it seems to be a bug, but all that I found is a bug coming from the Havana release that I do not use and a man which have the exact same error with the exact same image used.

Man with same error

Bug in havana

Explanation of the bug

If anyone have a clue, I'm on it :D I'll try with a CirrusOS image.

Good morning everyone!

Following my white rabbit on the wonderfull world of OS, I just came with a really strange issue on my Nova Compute/Network node.

As soon as I create an Instance, the creation fail because of a Nova Network error.

My node is compose of the following:

2xXeon E5520. 32Gb Ram. 67Gb Local HDD. 1Tb iSCSI Equallogic node (Cinder volume). Fedora 19 Schrodinger's Cat. Openstack Grizzly release.

I have installed the Qpidd C++ AMQP Broker, which is working great as cinder is available to fast and quickly create volume from Horizon Dashboard and/or from the local CLI.

Every nova module seems to working great, except the nova-volume which crash with the following stack on logs:

Nova Network Crash

Yeah, this is a big bad stack :D :D

Here is my Nova.conf file:

nova.conf

CLUNODE01 is the Cloud Controller which host Horizon/Glance/MySQL CLUNODE02 is the Compute Node which host Nova-Compute/Volume/Scheduler/Network/VNCConsole/etc

My local lan is on a 192.168.0.0/24 network, I've a bridge br100 link to my em1 network card and it address is 10.2.0.1/24.

My network on OS is the 10.2.0.0/24 network where 10.2.0.1 (br100) is the default gateway.

From my own search, it seems to be a bug, but all that I found is a bug coming from the Havana release that I do not use and a man which have the exact same error with the exact same image used.

Man with same error

Bug in havana

Explanation of the bug

If anyone have a clue, I'm on it :D I'll try with a CirrusOS image.:D

Good morning everyone!

Following my white rabbit on the wonderfull world of OS, I just came with a really strange issue on my Nova Compute/Network node.

As soon as I create an Instance, the creation fail because of a Nova Network error.

My node is compose of the following:

2xXeon E5520. 32Gb Ram. 67Gb Local HDD. 1Tb iSCSI Equallogic node (Cinder volume). Fedora 19 Schrodinger's Cat. Openstack Grizzly release.

The Fedora 19 is a fresh minimal install, and OpenStack component are coming from the default Fedora Repository. All installation are proceeds using yum packet manager and then all configuration steps are those explain on the official OpenStack Grizzly installation manual for YUM Distribution.

I even double check the procedure with the RDO Installation manual and the RedHat installation manual.

I have installed the Qpidd C++ AMQP Broker, which is working great as cinder is available to fast and quickly create volume from Horizon Dashboard and/or from the local CLI.

Every nova module seems to working great, except the nova-volume which crash with the following stack on logs:

Nova Network Crash

Yeah, this is a big bad stack :D

Here is my Nova.conf file:

nova.conf

CLUNODE01 is the Cloud Controller which host Horizon/Glance/MySQL CLUNODE02 is the Compute Node which host Nova-Compute/Volume/Scheduler/Network/VNCConsole/etc

My local lan is on a 192.168.0.0/24 network, I've a bridge br100 link to my em1 network card and it address is 10.2.0.1/24.

My network on OS is the 10.2.0.0/24 network where 10.2.0.1 (br100) is the default gateway.

From my own search, it seems to be a bug, but all that I found is a bug coming from the Havana release that I do not use and a man which have the exact same error with the exact same image used.

Man with same error

Bug in havana

Explanation of the bug

If anyone have a clue, I'm on it :D

Good morning everyone!

Following my white rabbit on the wonderfull world of OS, I just came with a really strange issue on my Nova Compute/Network node.

As soon as I create an Instance, the creation fail because of a Nova Network error.

My node is compose of the following:

2xXeon E5520. 32Gb Ram. 67Gb Local HDD. 1Tb iSCSI Equallogic node (Cinder volume). Fedora 19 Schrodinger's Cat. Openstack Grizzly release.

The Fedora 19 is a fresh minimal install, and OpenStack component are coming from the default Fedora Repository. All installation are proceeds using yum packet manager and then all configuration steps are those explain on the official OpenStack Grizzly installation manual for YUM Distribution.

I even double check the procedure with the RDO Installation manual and the RedHat installation manual.

I have installed the Qpidd C++ AMQP Broker, which is working great as cinder is available to fast and quickly create volume from Horizon Dashboard and/or from the local CLI.

Every nova module seems to working great, except the nova-volume which crash with the following stack on logs:

Nova Network Crash

Yeah, this is a big bad stack :D

Here is my Nova.conf file:

nova.conf

CLUNODE01 is the Cloud Controller which host Horizon/Glance/MySQL CLUNODE02 is the Compute Node which host Nova-Compute/Volume/Scheduler/Network/VNCConsole/etc

My local lan is on a 192.168.0.0/24 network, I've a bridge br100 link to my em1 network card and it address is 10.2.0.1/24.

My network on OS is the 10.2.0.0/24 network where 10.2.0.1 (br100) is the default gateway.

From my own search, it seems to be a bug, but all that I found is a bug coming from the Havana release that I do not use and a man which have the exact same error with the exact same image used.

Man with same error

Bug in havana

Explanation of the bug

If anyone have a clue, I'm on it :D