Ask Your Question
0

launch my first instance - error 500

asked 2015-04-14 03:02:23 -0500

enojado gravatar image

updated 2015-04-14 03:03:31 -0500

Hi, im launch my first instance after install, keystone identity, nova and neutron. Every service up and run. Keystone and rabbitmq seem to be ok and all other logs says "connected". And gre-tunnel is up. (get som already exist in a )

vm1: keystone, db, identity, controll of nova, controller of neutron, glance with image
vm2: network node with 3 nics
host1: nova with kvm hypervisor

source demo.sh
nova --debug boot --flavor m1.tiny --image cirros-0.3.3-x86_64 --nic net-id=cc28d624-41d9-47e1-b9ff-77904f9ea2fd --security-group default --key-name demo-key demo-instance

controller. nova-api.log


2015-04-14 09:27:37.311 4892 INFO nova.osapi_compute.wsgi.server [req-e6083262-18d4-432d-9048-b2a327bb99e1 None] 10.55.0.37 "GET /v2/3e305f41eea241679f2f625efc3c9351/images/4c18c3f4-306f-45d0-ae18-b0ae6870223e HTTP/1.1" status: 200 len: 895 time: 0.0266211
2015-04-14 09:27:37.334 4892 INFO nova.api.openstack.wsgi [req-38ed07e5-7cf1-4970-a98e-405eaff8ba9c None] HTTP exception thrown: The resource could not be found.
2015-04-14 09:27:37.335 4892 INFO nova.osapi_compute.wsgi.server [req-38ed07e5-7cf1-4970-a98e-405eaff8ba9c None] 10.55.0.37 "GET /v2/3e305f41eea241679f2f625efc3c9351/flavors/m1.tiny HTTP/1.1" status: 404 len: 272 time: 0.0195370
2015-04-14 09:27:37.358 4892 INFO nova.osapi_compute.wsgi.server [req-43b05792-33e0-4cc8-973f-3627970b9d51 None] 10.55.0.37 "GET /v2/3e305f41eea241679f2f625efc3c9351/flavors?is_public=None HTTP/1.1" status: 200 len: 1383 time: 0.0192881
2015-04-14 09:27:37.380 4892 INFO nova.osapi_compute.wsgi.server [req-115be663-8972-476c-9ce6-93b164a97027 None] 10.55.0.37 "GET /v2/3e305f41eea241679f2f625efc3c9351/flavors?is_public=None HTTP/1.1" status: 200 len: 1383 time: 0.0167139
2015-04-14 09:27:37.402 4892 INFO nova.osapi_compute.wsgi.server [req-f4cfd1e1-6613-47d5-bf4a-7407c5d5f77b None] 10.55.0.37 "GET /v2/3e305f41eea241679f2f625efc3c9351/flavors/1 HTTP/1.1" status: 200 len: 591 time: 0.0144279
2015-04-14 09:28:37.528 4892 ERROR nova.api.openstack [req-3c28bb16-282c-438e-a919-0f24400137d5 None] Caught error: Timed out waiting for a reply to message ID d7fe79d8ce9b49ca93ef5460e59cbec1
2015-04-14 09:28:37.528 4892 TRACE nova.api.openstack Traceback (most recent call last):
2015-04-14 09:28:37.528 4892 TRACE nova.api.openstack   File "/usr/lib/python2.7/dist-packages/nova/api/openstack/__init__.py", line 124, in __call__
2015-04-14 09:28:37.528 4892 TRACE nova.api.openstack     return req.get_response(self.application)
2015-04-14 09:28:37.528 4892 TRACE nova.api.openstack   File "/usr/lib/python2.7/dist-packages/webob/request.py", line 1320, in send
2015-04-14 09:28:37.528 4892 TRACE nova.api.openstack     application, catch_exc_info=False)
2015-04-14 09:28:37.528 4892 TRACE nova.api.openstack   File "/usr/lib/python2.7/dist-packages/webob/request.py", line 1284, in call_application
2015-04-14 09:28:37.528 4892 TRACE nova.api.openstack     app_iter = application(self.environ, start_response)
2015-04-14 09:28:37.528 4892 TRACE nova.api.openstack   File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 144, in __call__
2015-04-14 09:28:37.528 4892 TRACE nova.api.openstack     return resp(environ, start_response)
2015-04-14 09:28:37.528 4892 TRACE nova.api.openstack   File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token.py", line 661, in __call__
2015-04-14 09:28:37.528 4892 TRACE nova.api.openstack     return self._app ...
(more)
edit retag flag offensive close merge delete

Comments

It looks like you have something down. The request you made received an timeout, which means that you either have a connectivity problem or have some service down on the compute

lnxslck gravatar imagelnxslck ( 2015-04-14 04:14:11 -0500 )edit

check your message bus, 2015-04-14 09:28:37.528 4892 ERROR nova.api.openstack [req-3c28bb16-282c-438e-a919-0f24400137d5 None] Caught error: Timed out waiting for a reply to message ID d7fe79d8ce9b49ca93ef5460e59cbec1 usually means messaging issues.

jdexter gravatar imagejdexter ( 2015-04-14 07:23:59 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2015-04-15 07:39:24 -0500

enojado gravatar image

updated 2015-04-15 07:40:56 -0500

Thank you Inxslck and jdexter!

I found a solution to the problem. And it's embarrassing!!
I used same subnet for tunnel nic and the management nic.

Linux kernel does not support that and I should know that from the beginning (unless you are using lacp etc) !!
The funny thing, all nic's work as normal. Even Gre tunnel was up.

edit flag offensive delete link more

Comments

Hi @enojado Could you please let me know where did you checked this( if both nics have the same subnet ) ?

tkekan gravatar imagetkekan ( 2015-04-15 13:56:16 -0500 )edit

Hi. An example. All nic's are in same physical vlan.
I used 10.0.0.10 and 10.0.0.11 for mng and tunnel network for network node. and 10.0.0.20 and 10.0.0.21 for mng and tunnel for nova host.
The tunnel need be 10.0.1.11 and 10.0.1.21.

enojado gravatar imageenojado ( 2015-04-15 15:50:39 -0500 )edit

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

2 followers

Stats

Asked: 2015-04-14 03:02:23 -0500

Seen: 1,032 times

Last updated: Apr 15 '15