New Kilo install - Unable to launch instance, no useful errors found
New installation of Kilo, 3 nodes, controller, network, compute. All CentOS 7. Followed the doc, fairly straight forward. This is the first instance I've tried to launch, I have not gotten any instance to successfully launch. Running as admin, and I haven't come across any other erorrs as I try to describe the various resources (image, nic, security group, etc) to try to isolate the problem. I have debugging on in all the components, and can't find any other errors in the other logs. I'm stumped.
edit - I see the same error as majiclamp when doing 'nova endpoints'. I get a list of endpoints for each service, one for each interface (internal, admin,public), all in RegionOne, but at the start of each service (glance, neutron,keystone, nova), I get
WARNING: nova has no endpoint in ! Available endpoints for this service:
-end edit
[root@bosscrm-os-controller1 nova]# nova boot --flavor 1 --image 046e1504-27d6-4732-88e5-db2fbee4d95f --nic port-id=d650dfab-3bf9-400f-8526-bc74e250623d --security-group default --key-name demo-key demo-instance1 ERROR (ClientException): The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-d7d25fa5-e991-46ce-9610-3a6e7db1d396)
With --debug:
[root@bosscrm-os-controller1 nova]# nova --debug boot --flavor 1 --image 046e1504-27d6-4732-88e5-db2fbee4d95f --nic port-id=d650dfab-3bf9-400f-8526-bc74e250623d --security-group default --key-name demo-key demo-instance1 DEBUG (session:195) REQ: curl -g -i -X GET http://bosscrm-os-controller1:35357/v3 -H "Accept: application/json" -H "User-Agent: python-keystoneclient" INFO (connectionpool:203) Starting new HTTP connection (1): bosscrm-os-controller1 DEBUG (connectionpool:383) "GET /v3 HTTP/1.1" 200 262 DEBUG (session:224) RESP: [200] content-length: 262 vary: X-Auth-Token keep-alive: timeout=5, max=100 server: Apache/2.4.6 (CentOS) mod_wsgi/3.4 Python/2.7.5 connection: Keep-Alive date: Thu, 21 May 2015 15:59:17 GMT content-type: application/json x-openstack-request-id: req-02482116-da33-4cd6-b093-b944e51ba95e RESP BODY: {"version": {"status": "stable", "updated": "2015-03-30T00:00:00Z", "media-types": [{"base": "application/json", "type": "application/vnd.openstack.identity-v3+json"}], "id": "v3.4", "links": [{"href": "http://bosscrm-os-controller1:35357/v3/", "rel": "self"}]}} DEBUG (base:178) Making authentication request to http://bosscrm-os-controller1:35357/v3/auth/tokens DEBUG (connectionpool:383) "POST /v3/auth/tokens HTTP/1.1" 201 2946 DEBUG (iso8601:184) Parsed 2015-05-21T16:59:17.293613Z into {'tz_sign': None, 'second_fraction': u'293613', 'hour': u'16', 'daydash': u'21', 'tz_hour': None, 'month': None, 'timezone': u'Z', 'second': u'17', 'tz_minute': None, 'year': u'2015', 'separator': u'T', 'monthdash': u'05', 'day': None, 'minute': u'59'} with default timezone <iso8601.iso8601.utc object="" at="" 0x27f0050=""> DEBUG (iso8601:140) Got u'2015' for 'year' with default None DEBUG (iso8601:140) Got u'05' for 'monthdash' with default 1 DEBUG (iso8601:140) Got 5 for 'month' with default 5 DEBUG (iso8601:140) Got u'21' for 'daydash' with default 1 DEBUG (iso8601:140) Got 21 for 'day' with default 21 DEBUG (iso8601:140) Got u'16' for 'hour' with default None DEBUG (iso8601:140) Got u'59' for 'minute' with default None DEBUG (iso8601:140) Got u'17' for 'second' with default None DEBUG (session:195) REQ: curl -g -i -X GET http://bosscrm-os-controller1:8774/v2/aaf543afac8143b9a4abd971325de12e/images/046e1504-27d6-4732-88e5-db2fbee4d95f -H "User-Agent: python-novaclient ...
I find error message in nova-api.log file that you attached
2015-05-21 11:54:40.450 23955 ERROR nova.api.openstack [req-d7d25fa5-e991-46ce-9610-3a6e7db1d396 387d1d9de32a423ebd7253b3504b1d33 aaf543afac8143b9a4abd971325de12e - - -] Caught error: Expecting to find username or userId in passwordCredent
Have you checked your nova.conf's [keystone_authtoken] and [neutron] sections to verify that the auth information supplied in both is correct?
I am having the same error. Also when I do
Passwords checked, tokens are issued successfully....