nova boot shows many ERRORS - can someone explain? [closed]
still following the tutorial YUM Centos7 Juno
Why would m1.tiny generate a 404? - AND why call glance service on a compute node?
- trying to create an instance BUT it goes in ERROR
- So I try again with "--debug"
* Question 1: Why would m1.tiny generate a 404 ?*
- nova flavor-list
- nova flavor-show
m1.tiny works just fine (me confuse)
here is the command line for nova boot
scripts/demo-openrc.sh; nova --debug boot --flavor m1.tiny --image cirros-0.3.3-x86_64 --nic net-id=a34ef2c0-a3f1-4d6c-a1a1-11629b602a86 --security-group default --key-name demo-key demo-instance1
here is the 404 in /var/log/nova/nova-api.log
REQ: curl -i 'http://controller:8774/v2/6ed7381c7afc4cceb698a143205c4ae7/flavors/m1.tiny' -X GET -H "Accept: application/json" -H "User-Agent: python-novaclient" -H "X-Auth-Project-Id: demoVLAN" -H "X-Auth-Token: {SHA1}153aed62c84ad29b441a3aaacd43b7c109cb5390"
INFO (connectionpool:187) Starting new HTTP connection (1): controller
DEBUG (connectionpool:357) "GET /v2/6ed7381c7afc4cceb698a143205c4ae7/flavors/m1.tiny HTTP/1.1" 404 78
RESP: [404] {'date': 'Wed, 07 Jan 2015 15:00:38 GMT', 'content-length': '78', 'content-type': 'application/json; charset=UTF-8', 'x-compute-request-id': 'req-de19279f-10be-4d64-b375-39b93553d4f2'}
RESP BODY: {"itemNotFound": {"message": "The resource could not be found.", "code": 404}}
here are the results
+--------------------------------------+------------------------------------------------------------+
| Property | Value |
+--------------------------------------+------------------------------------------------------------+
| OS-DCF:diskConfig | MANUAL |
| OS-EXT-AZ:availability_zone | nova |
| OS-EXT-STS:power_state | 0 |
| OS-EXT-STS:task_state | scheduling |
| OS-EXT-STS:vm_state | building |
| OS-SRV-USG:launched_at | - |
| OS-SRV-USG:terminated_at | - |
| accessIPv4 | |
| accessIPv6 | |
| adminPass | zuh2Z8CdKCYc |
| config_drive | |
| created | 2015-01-07T15:00:38Z |
| flavor | m1.tiny (1) |
| hostId | |
| id | 35bb8a2b-2df4-465d-93dd-6ab098847555 |
| image | cirros-0.3.3-x86_64 (b66602f8-0c84-4e6e-b37a-9a6e0d483909) |
| key_name | demo-key |
| metadata | {} |
| name | demo-instance1 |
| os-extended-volumes:volumes_attached | [] |
| progress | 0 |
| security_groups | default |
| status | BUILD |
| tenant_id | 6ed7381c7afc4cceb698a143205c4ae7 |
| updated | 2015-01-07T15:00:39Z |
| user_id | eb8b23e62f22461c82aa5a6aad0e7216 |
+--------------------------------------+------------------------------------------------------------+
[root@controller ~]# nova list
+--------------------------------------+----------------+--------+------------+-------------+----------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+----------------+--------+------------+-------------+----------+
| 4e85261e-bcd5-47cc-be41-cb96dd6c21a9 | demo-instance1 | ERROR | - | NOSTATE | |
+--------------------------------------+----------------+--------+------------+-------------+----------+
after reading some other questions I have added export OS_REGION_NAME=regionOne
to demo-openrc.sh
It made no change Status = ERROR
Question #2 Why would nova make a call to the compute node? when no listener were ever installed in the tutorial 10.0.70.90 and 10.0.70.91 are the 2 compute node to the image service port 9292?
in the /var/log/nova/nova-conductor.log
2015-01-09 09:00:25.740 5605 ERROR nova.scheduler.utils [req-f56bcf35-16f1-4e0c-87ab-29b982891771 None] [instance: 2adc30ab-9f24-4aa6-94d0-8a0ededd8406] Error from last host: compute1.ececloud (node compute1.ececloud): [u'Traceback (most recent call last):\n', u' File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2030, in _do_build_and_run_instance\n filter_properties)\n', u' File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2161, in _build_and_run_instance\n instance_uuid=instance.uuid, reason=six.text_type(e))\n', u"RescheduledException: Build of instance 2adc30ab-9f24-4aa6-94d0-8a0ededd8406 was re-scheduled: Connection to glance host 10.0.70.90:9292 failed: Error finding address for http://10.0.70.90:9292/v1/images/b66602f8-0c84-4e6e-b37a-9a6e0d483909: HTTPConnectionPool(host='10.0.70.90', port=9292): Max retries exceeded with url: /v1/images/b66602f8-0c84-4e6e-b37a-9a6e0d483909 (Caused by <class 'socket.error'>: [Errno 111] ECONNREFUSED)\n"]
2015-01-09 09:00:26.966 5605 ERROR nova.scheduler.utils [req-f56bcf35-16f1-4e0c-87ab-29b982891771 None] [instance: 2adc30ab-9f24-4aa6-94d0-8a0ededd8406] Error from last host: compute2.ececloud (node compute2.ececloud): [u'Traceback (most recent call last):\n', u' File "/usr/lib/python2.7/site-packages/nova/compute/manager.py ...
i got the same exact error. mine it's an icehouse where installation is done from the tutorial. same issue for the 404 on the flavor, and same connection on the compute nodes on port 9292 which is btw not available. did you find a solution for this? adding a new flavor does the same result.
I am still working on this frederic0
I try to enter a bug - I was told that was a user issue - I reply the documentation was in error - but no feedback
From my reading it looks like either Glance(9292) , Swift(), or Cinder(8776) needs to run on the computeNode let me know what you find
Thanks
what did the glance image-list say? have you tried to use the flavor id instead of flavor name to boot the vm instance?
i've solved by adding explicitly glance host:port and glance_api addresses in nova.conf on the compute node. now compute node connects to glance server that runs on the controller. hope this helps.