Ask Your Question
0

juno nova instance stuck in BUILD scheduling

asked 2014-11-27 02:21:55 -0600

cunningr69 gravatar image

I am following the install guides for Juno on Ubuntu 14.04 however I should point out one variation. I only have two physical nodes; contoller+network and compute.

I have limited resources so I am trying to combine the controller and the network node however I have dedicated compute node:

    cisco@kermit:~$ nova service-list
    +----+------------------+--------+----------+---------+-------+----------------------------+-----------------+
    | Id | Binary           | Host   | Zone     | Status  | State | Updated_at                 | Disabled Reason |
    +----+------------------+--------+----------+---------+-------+----------------------------+-----------------+
    | 1  | nova-cert        | kermit | internal | enabled | up    | 2014-11-26T20:04:57.000000 | -               |
    | 2  | nova-consoleauth | kermit | internal | enabled | up    | 2014-11-26T20:04:58.000000 | -               |
    | 3  | nova-scheduler   | kermit | internal | enabled | up    | 2014-11-26T20:04:55.000000 | -               |
    | 4  | nova-conductor   | kermit | internal | enabled | up    | 2014-11-26T20:04:57.000000 | -               |
    | 5  | nova-compute     | gonzo  | nova     | enabled | up    | 2014-11-26T20:04:56.000000 | -               |
    +----+------------------+--------+----------+---------+-------+----------------------------+-----------------+

The neutron part also seems to be working and I can ping my demo router ext-net from outside the cluster:

cisco@kermit:~$ neutron agent-list
+--------------------------------------+--------------------+--------+-------+----------------+---------------------------+
| id                                   | agent_type         | host   | alive | admin_state_up | binary                    |
+--------------------------------------+--------------------+--------+-------+----------------+---------------------------+
| 267b6cff-e1f1-4a08-8184-5b1c7f0d9a88 | Open vSwitch agent | kermit | :-)   | True           | neutron-openvswitch-agent |
| aa4ec4df-fc3a-4a54-8918-e8f2b77398e8 | L3 agent           | kermit | :-)   | True           | neutron-l3-agent          |
| c92cfef0-b3e0-4056-ba5d-4cf6bd3f9611 | DHCP agent         | kermit | :-)   | True           | neutron-dhcp-agent        |
| d077ef64-decc-462e-af8c-57a8e165074e | Metadata agent     | kermit | :-)   | True           | neutron-metadata-agent    |
| fa28402e-f374-4e0e-b277-f4b21737aabb | Open vSwitch agent | gonzo  | :-)   | True           | neutron-openvswitch-agent |
+--------------------------------------+--------------------+--------+-------+----------------+---------------------------+


DCN-N7K-3-OldAdmin# ping 192.168.102.10
PING 192.168.102.10 (192.168.102.10): 56 data bytes
64 bytes from 192.168.102.10: icmp_seq=0 ttl=63 time=1.486 ms
64 bytes from 192.168.102.10: icmp_seq=1 ttl=63 time=0.893 ms
64 bytes from 192.168.102.10: icmp_seq=2 ttl=63 time=0.616 ms
64 bytes from 192.168.102.10: icmp_seq=3 ttl=63 time=0.692 ms
64 bytes from 192.168.102.10: icmp_seq=4 ttl=63 time=0.626 ms

When I do a nova create as per juno install docs, my instance doesn't get passed BUILD|scheduling and eventually moves to ERROR:

cisco@kermit:~$ nova list
+--------------------------------------+----------------+--------+------------+-------------+----------+
| ID                                   | Name           | Status | Task State | Power State | Networks |
+--------------------------------------+----------------+--------+------------+-------------+----------+
| b9b77f5f-5420-4d03-b489-fcaed1d8698d | demo-instance1 | ERROR  | -          | NOSTATE     |          |
+--------------------------------------+----------------+--------+------------+-------------+----------+
cisco@kermit:~$

Can someone help me please, where do I start to debug this?

edit retag flag offensive close merge delete

Comments

I tried to tail the logs during the nova create. the nova-api log output is here:

http://paste.openstack.org/show/139370/ one thing I note is: 2014-11-26 20:39:23.125 8863 INFO nova.api.openstack.wsgi [req-892288ab-9277-49bd-ab98-c514daecad66 None] HTTP exception thrown: The resource could not be

cunningr69 gravatar imagecunningr69 ( 2014-11-27 02:42:30 -0600 )edit

What's the result when you run nova image-list?

splucena gravatar imagesplucena ( 2014-11-27 02:52:36 -0600 )edit
add a comment

2 answers

Sort by ยป oldest newest most voted
0

answered 2016-07-08 15:35:40 -0600

fifi gravatar image

I had the same problem as yours. I reinstalled the rabbitmq and set the access list as instructed in the rabbitmq website. It solved my problem. what I did was as follow:

1- uninstall rabbitmq: 

sudo apt-get remove --auto-remove rabbitmq-server

sudo apt-get purge --auto-remove rabbitmq-server

2- install rabbitmq again:

echo 'deb http://www.rabbitmq.com/debian/ testing main' | sudo tee /etc/apt/sources.list.d/rabbitmq.list

wget -O- https://www.rabbitmq.com/rabbitmq-release-signing-key.asc | sudo apt-key add -

sudo apt-get update

sudo apt-get install rabbitmq-server

3- Edit /etc/rabbitmq/rabbitmq.config file and configure loopback_users to reference an empty list by inserting the following line into the config file. [If /etc/rabbitmq/rabbitmq.config file does not exist, create it.]

[{rabbit, [{loopback_users, []}]}].

4- change rabbitmq guest password. Use the password you used before uninstalling the rabbitmq.

rabbitmqctl  change_password  guest  [your desired password]

5- finally restart the rabbitmq:

service  rabbitmq-server  restart
edit flag offensive delete link more
add a comment
0

answered 2014-11-27 02:37:16 -0600

splucena gravatar image

Could you post logs from these locations:

Controller-Node: /var/log/nova/nova-api.log, nova-scheduler.log

Compute-Node: /var/log/nova/nova-compute.log

edit flag offensive delete link more

Comments

there is not much in the controller nova-api or the schedular however the conductor seems eventually to be hitting some timeout:

http://paste.openstack.org/show/139377/

cunningr69 gravatar imagecunningr69 ( 2014-11-27 02:57:02 -0600 )edit

I tried to tail the logs during the nova create. the nova-api log output is here:

http://paste.openstack.org/show/139370/ one thing I note is: 2014-11-26 20:39:23.125 8863 INFO nova.api.openstack.wsgi [req-892288ab-9277-49bd-ab98-c514daecad66 None] HTTP exception thrown: The resource could not be

cunningr69 gravatar imagecunningr69 ( 2014-11-27 02:57:27 -0600 )edit
1

at the same time during image create the nova-compute on the compute node is throwing an ERROR regarding the RPC version:

http://paste.openstack.org/show/139398/

cunningr69 gravatar imagecunningr69 ( 2014-11-27 03:01:28 -0600 )edit

check this link:

https://ask.openstack.org/en/question/51800/endpoint-does-not-support-rpc-version-333/ (https://ask.openstack.org/en/question...)

splucena gravatar imagesplucena ( 2014-11-27 03:04:46 -0600 )edit

Thanks! Yes that was my issue. I hadn't finished the upgrade/install on my compute node.

cunningr69 gravatar imagecunningr69 ( 2014-11-27 04:50:34 -0600 )edit
see more comments

Get to know Ask OpenStack

Resources for moderators

Question Tools

3 followers

subscribe to rss feed

Stats

Asked: 2014-11-27 02:21:55 -0600

Seen: 5,635 times

Last updated: Jul 08 '16

Related questions

Cannot delete instances using "nova delete <instance id>"

juno vm stuck at spawning state

How to check what user terminated instance? [closed]

unable ping google from instance

Update instances metadata with cli

Juno KVM bandwidth quota issue

Error Project RDO

Neutron with two external network attach floating ip to wrong router namespace

Problem with glance (timed out)

VM sends DHCPREQUEST through bridge that has no correct member interface