Hi,
you should also check your neutron auth configs and the respective log
files since nova reports "Instance failed network setup after 1
attempt(s)". Set nova and neutron to debug mode to get more output.
You could also try to run different neutron commands with the same
credentials and see if there occur any errors. Breaking it down to a
specific service will help identifying the issue.
Regards
Zitat von Andrea Gatta <andrea.ga...@gmail.com>:
Hello there,
as for the subject I am stuck trying to create/start a cirros imange.
At first I didn't notice but I can now say that while creating the image
keystone logs the following warning:
/var/log/keystone/keystone.log
2018-03-05 21:02:45.961 2120 INFO keystone.common.wsgi [
req-5c4c9e26-dbe2-429f-b414-f6262b451392 - - - - -] POST
http://controller1:35357/v3/auth/tokens
2018-03-05 21:02:46.740 2120 WARNING keystone.common.wsgi
[req-5c4c9e26-dbe2-429f-b414-f6262b451392 - - - - -] Authorization failed.
The request you have mad
at the same time nova throws the following error:
/var/log/nova/nova-compute.log
45ec8a6ff - - -] [instance: 7a789397-8fbd-47a7-a5f6-8b274f77ca72] Creating
image
2018-03-05 21:26:34.716 1225 ERROR nova.compute.manager
[req-b9f9e984-6f5f-4869-9290-63ca145d19e1 e35fc188170d4144a9cd4d30f9eab65c
bad15e4bc5714298b275e2f45e
c8a6ff - - -] Instance failed network setup after 1 attempt(s)
2018-03-05 21:26:34.716 1225 ERROR nova.compute.manager Traceback (most
recent call last):
.......
2018-03-05 21:26:34.716 1225 ERROR nova.compute.manager Unauthorized: The
request you have made requires authentication. (HTTP 401) (Request-ID:
req-5c4c9e26-dbe2-429f-b414-f6262b451392)
2018-03-05 21:26:34.736 1225 ERROR nova.compute.manager [instance:
7a789397-8fbd-47a7-a5f6-8b274f77ca72] Unauthorized: The request you have
made requires authentication. (HTTP 401) (Request-ID:
req-5c4c9e26-dbe2-429f-b414-f6262b451392)
So basically the compute node sends req-5c4c9e26-dbe2-429f-b414-f6262b451392
that hasn't gotten a reply since keystone on the controller node denies it
(reqs match).
To this point I've checked auth_uri and nova user password in
/etc/nova/nova.conf for both controller and compute nodes. Moreover I've
checked nova openstack user password with the command 'openstack user
password set' (with appropriate env). Crendentials are ok all across the
board.
Here's the [keystone_authtoken] section for both controller and compute
nodes
[keystone_authtoken]
auth_uri = http://controller1:5000
auth_url = http://controller1:35357
memcached_servers = controller1:11211
auth_type = password
project_domain_name = Default
user_domain_name = Default
project_name = service
username = nova
password = xxxxxxxx
auth_uri = http://controller1:5000
auth_url = http://controller1:35357
memcached_servers = controller1:11211
auth_type = password
project_domain_name = Default
user_domain_name = Default
project_name = service
username = nova
password = xxxxxxxx
Thanks in advance for any light you could shed on this.
Regards
Andrea
--
Eugen Block voice : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg e-mail : ebl...@nde.ag
Vorsitzende des Aufsichtsrates: Angelika Mozdzen
Sitz und Registergericht: Hamburg, HRB 90934
Vorstand: Jens-U. Mozdzen
USt-IdNr. DE 814 013 983
_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
