[Crowbar] Stuck on 'build' status
kbringard at atti.com
Fri Jan 13 09:30:26 CST 2012
For what it's worth, I personally have found that installing OpenStack
manually a few times is tremendously helpful. Not only does it help you to
know what your hardware can and can't do, how your network should look
(from the hardware layer and the OpenStack side), etc. but it will help
you determine what is a crowbar issue and what is an OpenStack issue.
Plus, if you intend to use OpenStack long term you'll want to know how it
works so you can put out the inevitable fires that come with production :-)
Just my $0.02
On 1/13/12 8:18 AM, "Paul Regan" <me at paulregan.co.uk> wrote:
>To follow up with a conclusion for the list archive :
>MySQL was not the problem. Following Chris' advice and knowing to
>look for 'cast' I found the following on the compute node logs
>ERROR nova.compute.manager [-] Instance '5' failed to spawn. Is
>virtualization enabled in the BIOS? Details: internal error no
>supported architecture for os type 'hvm'
>These are old servers with no cpu virtuali[s/z]ation so I switched the
>Nova barclamp barclamp from kvm to qemu and I now have some active
>instances. Also some odd crowbar behaviour but at least active
>instances .. onto the next step. Thanks for the help ...
>On 12 January 2012 16:37, Paul Regan <me at paulregan.co.uk> wrote:
>> Thanks to Kevins advice and more importantly use of the word 'cast' I
>> managed to follow the process in the logs.
>>>>2012-01-12 07:38:17,926 CRITICAL nova [-] (OperationalError) (2003,
>>>>"Can't connect to MySQL server on '192.168.124.81' (111)") None None
>> One line says it all - will work on why thats failing now. MySQL
>> appears up so I'm guessing an authentication problem maybe. Will look
>> and come back if needed.
>> Chris, thanks for that, useful debug method .. the logs quickly get
>> crazy, even in this tiny poc ..
>Crowbar mailing list
>Crowbar at dell.com
>For more information: https://github.com/dellcloudedge/crowbar/wiki
More information about the Crowbar