Enable debug in nova.conf on compute2 host, restart nova-compute and try
again. You should see the reason in the log. It can be bad connection to
glance, or problem with networking on the host.
On 05/22/2015 12:04 PM, Abhishek Talwar wrote:
Hi Folks,
I know this is not the place to ask usage questions and doubts
regarding my deployment but no one is answering my questions on
ask.openstack.org. So I thought of asking the same here.
Problem:
I have a multi-node set up with 2 compute nodes( *Compute1 and
Compute2*). When I boot VM's on *compute 1* they go to *ACTIVE* status
but when I try to boot VM's on *Compute2* host they are stuck in
*BUILD* status. I can see both the compute nodes *UP* in “*nova
service-list*” and both the host are present in “*nova
hypervisor-list*” So what could be the reason that VM's are not going
to ACTIVE status in Compute2 host.
The latest scheduler logs shows:
*nova.scheduler.host_manager [req-a4debdff-0ad5-4fb8-afd4-e0dc255c3c78
None] Host filter forcing available hosts to compute1
*There is no error in the logs of scheduler so what could be the
possible reason.*
Regards
Abhishek Talwar
*
=-=-=
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
