Mailing List Archive: OpenStack: Operators

A serious mistake on devstack guide frontpage (to cause the compute nodes's state to be XXX)

Index | Next | Previous | View Threaded

zhaoyi.luo at hotmail

Jul 15, 2012, 7:20 AM

Post #1 of 2 (252 views)
Permalink

A serious mistake on devstack guide frontpage (to cause the compute nodes's state to be XXX)

The problem was, when issue "nova-manage service list" all the compute nodes's state are XXX instead of :-), and they didn't work in fact too.
After 2 days' struggle, I find the configuration files in http://devstack.org/guides/multinode-lab.html have mistake: MYSQL_PASS should be MYSQL_PASSWORD, and RABBIT_PASS should be RABBIT_PASSWORD.
Devstack can be installed successfully without any notice if RABBIT_PASSWORD is not set(while there would be a prompt for MYSQL_PASSWORD), but compute nodes cannot work because they cannot access to the message queue, and you can only see the state is XXX.

hope my experience can help other operators to avoid this issue~

another problem: why I used --hint force_hosts option to specify host to boot instances on( http://docs.openstack.org/essex/openstack-compute/admin/content/specify-host-to-boot-instances-on.html) but it doesn't work?(it scheduled as this option is not set)

------------------
Best,
Zhaoyi Luo

jaypipes at gmail

Jul 16, 2012, 10:15 AM

Post #2 of 2 (252 views)
Permalink

Re: A serious mistake on devstack guide frontpage (to cause the compute nodes's state to be XXX) [In reply to]

On 07/15/2012 10:20 AM, zhaoyi.luo wrote:
> The problem was, when issue "nova-manage service list" all the compute
> nodes's state are XXX instead of :-), and they didn't work in fact too.
> After 2 days' struggle, I find the configuration files
> in http://devstack.org/guides/multinode-lab.html have mistake:
> MYSQL_PASS should be MYSQL_PASSWORD, and RABBIT_PASS should be
> RABBIT_PASSWORD.
> Devstack can be installed successfully without any notice if
> RABBIT_PASSWORD is not set(while there would be a prompt for
> MYSQL_PASSWORD), but compute nodes cannot work because they cannot
> access to the message queue, and you can only see the state is XXX.
>
> hope my experience can help other operators to avoid this issue~
>
> another problem: why I used --hint force_hosts option to specify host to
> boot instances
> on( http://docs.openstack.org/essex/openstack-compute/admin/content/specify-host-to-boot-instances-on.html) but
> it doesn't work?(it scheduled as this option is not set)

Hi Zhaoyi,

Please do report a bug in devstack with the above description.

https://bugs.launchpad.net/devstack/+filebug

Thanks!
-jay

_______________________________________________
OpenStack-operators mailing list
OpenStack-operators [at] lists
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads