Ask Your Question

Why does my nova boot command Fail?

asked 2016-10-13 06:29:38 -0500

h4harshith gravatar image

I have installed 2 instances on Openstack Controller Running Mitaka. I have 2 COMPUTE nodes

[root@tripoli ~]# nova service-list +----+------------------+---------+----------+---------+-------+- | Id | Binary | Host | Zone | Status | State | +----+------------------+---------+----------+---------+-------+- | 1 | nova-scheduler | tripoli | internal | enabled | up | | 2 | nova-consoleauth | tripoli | internal | enabled | up | | 3 | nova-conductor | tripoli | internal | enabled | up | | 21 | nova-compute | tripoli | nova | enabled | up | | 22 | nova-compute | cobolt | nova | enabled | up | +----+------------------+---------+----------+---------+-------+-

The RAM on one of my COMPUTE node is FULL The other COMPUTE node has resources

But when i launch an instance using nova

I get this error

nova boot --flavor CONFDR.SMALL --nic net-id=59be3044-cecf-45e4-bf7d-17aab0270d99 --image cPSX_V10.00.03A406 --security-groups SONUS --user-data my_user_data.txt --availability-zone nova:cobolt slavemonacovm1 --poll ERROR (ClientException): Unexpected API Error. Please report this at and attach the Nova API log if possible. (HTTP 500) (Request-ID: req-42f8b911-0367-4ad0-88ac-fc8a195feaa3)

How do i solve this Error? and how do i make nova to boot from other COMPUTE node?

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2016-10-13 07:01:38 -0500

hkominos gravatar image

I have installed 2 instances on Openstack Controller Running Mitaka-->what does that mean? If you have 2 controllers then I would advice to delete one or add one. I think you should always have an odd number of Controllers in any setup.

So By default the scheduler will look at the available resources in your compute nodes and pick one to spawn your machines. The only way to force it to check elsewhere is to have more availability zones. (which you do),maybe make a new one with only the compute node #2 in it and try to spawn. As for the problem it self this usually means that some service is down or that for some reason your command is malformed. (did you try to boot throught UI ?)

I would check /var/log/nova-all.log and neutron.log at the compute nodes to see what might be the problem.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2016-10-13 06:29:38 -0500

Seen: 118 times

Last updated: Oct 13 '16