OpenStack instances power off by itself

Final Edit

Not sure what I did to get it to work last time but the true cause of my misfortune was omitting this step,

http://docs.openstack.org/havana/install-guide/install/apt/content/basics-packages.html

which guides you through the process of installing the havana ubuntu cloud archive.

Thanks for reading!

old post starts here

I managed to fix the issue.

In the keystone database, the endpoints table more specifically there was a mix of localhoist/and ip address based entries in the "url" field, they look like this x.x.x.x:9292, x.x.x.x:8776/v1/%(tenant_id)s and so on. I replaced the ip address with localhost in all cases making it uniform and I'm now able to log into the dashboard from the machine itself. I can't login other than from localhost but I'm assuming this is a separate issue because I tried replacing localhost with other entries (the public ip address for example and I can still login via dashboard from localhost).

To summarize, although I could be misinterpreting what happened, I think the fact that the endpoints url fields weren't uniform was causing the initial connection refused issue. I believe the specific endpoints that were written out as localhost caused the problem, unfortunately I didn't take note of which were which at the time.

Edit: I tried accessing the dashboard from my browser in a incognito window using chrome and I could log in no problem, I tried internet explorer and it works great. But even after clearing out all my history/cache/etc from chrome I still get the error. Not sure why but at least I've narrowed things down a bit, and it works, kinda!

you can debug this by checking if the neutron service is up and running and registered correctly in your service catalog.

look at your keystone catalog

it will ouput the API endpoints

keystone catalog
WARNING: unsupported identity-api-version 3, falling back to 2.0
Service: compute
+-------------+-------------------------------------------------------------+
|   Property  |                            Value                            |
+-------------+-------------------------------------------------------------+
|   adminURL  | http://172.25.60.2:8774/v2/6cbc4e8a49af4fb1be9a4bf6dda8e373 |
|      id     |               15f3972a815642118f319301c01eac26              |
| internalURL | http://172.25.60.2:8774/v2/6cbc4e8a49af4fb1be9a4bf6dda8e373 |
|  publicURL  |  http://87.x.x.x:8774/v2/6cbc4e8a49af4fb1be9a4bf6dda8e373  |
|    region   |                          RegionOne                          |
+-------------+-------------------------------------------------------------+
Service: network
+-------------+----------------------------------+
|   Property  |              Value               |
+-------------+----------------------------------+
|   adminURL  |     http://172.25.60.2:9696/     |
|      id     | 15c3f13c2bd74cd38bbd48bcafe4ccb0 |
| internalURL |     http://172.25.60.2:9696/     |
|  publicURL  |      http://87.x.x.x:9696/      |
|    region   |            RegionOne             |
+-------------+----------------------------------+
Service: volumev2
+-------------+-------------------------------------------------------------+
|   Property  |                            Value                            |
+-------------+-------------------------------------------------------------+
|   adminURL  | http://172.25.60.2:8776/v2/6cbc4e8a49af4fb1be9a4bf6dda8e373 |
|      id     |               979fd7e2bb7a4fef82b9e975249decf5              |
| internalURL | http://172.25.60.2:8776/v2/6cbc4e8a49af4fb1be9a4bf6dda8e373 |
|  publicURL  |  http://87.x.x.x.:8776/v2/6cbc4e8a49af4fb1be9a4bf6dda8e373  |
|    region   |                          RegionOne                          |
+-------------+-------------------------------------------------------------+

then what is the output of the neutron net-list command

neutron net-list
+--------------------------------------+----------------------+-------------------------------------------------------+
| id                                   | name                 | subnets                                               |
+--------------------------------------+----------------------+-------------------------------------------------------+
| 2f97b5e6-e13b-47af-9cb7-f7e33344a788 | default              | f25c7778-33f9-48a7-9696-a19a01fc3e57 192.168.112.0/24 |
| 34263fbb-f93e-45d3-b65e-ab2afce3c1c9 | ruby-network         | 9360aeb5-2c05-431d-8e79-7052788db198 10.0.14.0/24     |
| 3650dbcb-b6d7-4220-8e6d-fa7c30914c57 | cloudfoundry-network | 24ed907f-476f-4440-97d4-9a1f2b7bd75d 10.0.26.0/24     |

in your neutron.conf are you binding to 127.0.0.1 ? - you should bind to all IP's

# Address to bind the API server to
# bind_host = 0.0.0.0
bind_host = 0.0.0.0

# Port the bind the API server to
# bind_port = 9696
bind_port = 9696

Neutron uses api extensions or 'plugins' and also agents for DHCP, security groups and NAT- can you go on to say what extension you are using?

probably this will be openvswitch as your plugin and network agents by default are usually dnsmaq, and iptables.

you can check the openvswitch services in /etc/ini.d/ and look at the switch database with the following show commands

ovs-vsctl show : Prints a brief overview of the switch database configuration.
ovs-vsctl list-br : Prints a list of configured bridges
ovs-vsctl list-ports <bridge> : Prints a list of ports on a specific bridge.
ovs-vsctl list interface : Prints a list of interfaces.

also, for debugging the extension http error, you can enable debug logging in the neutron conf or pass in the --debug option on the cli e.g.

nova --debug boot --image imageID --flavor flavorID --nic net-id=nicID