Revision history [back]

click to hide/show revision 1
initial version

juno nova instance stuck in BUILD scheduling

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?