Ask Your Question
0

Newly created instance always have status=error and powerstate=nostate because of authentication on compute node

asked 2016-01-15 04:28:51 -0500

NileshB gravatar image

updated 2016-01-15 06:44:37 -0500

Hi, I have started OpenStack liberty installation on CentOS7. I have followed each step on installation guide till last step. At each step verified operation successfully. I have two node Controller (with two network interfaces) and Compute (again with two network interfaces) as mentioned in guide.

I have installed Keystone, Nova-compute, Neutron successfully.

When I am creating instance it always created with status=error and powerstate=nostate.

Keystone is issuing token successfully on Controller node. All logs files on Controller don't have any error. Following are error logs on Compute node in "/etc/nova/nova.conf" file.

----------------------------------Error messages

2016-01-14 20:59:47.602 16974 INFO nova.compute.claims [req-7585288c-39a1-4920-913b-23fb4658d1f6 caa811f6476e402aa27bc0c82b738d4b 10a350f60ed7436882b1180aba3237bf - - -] [instance: ed962f0b-2d62-408f-811f-1ffa3195f049] Claim successful

2016-01-14 20:59:47.961 16974 WARNING keystoneclient.auth.identity.generic.base [-] Discovering versions from the identity service failed when creating the password plugin. Attempting to determine version from URL.

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager [-] Instance failed network setup after 1 attempt(s)

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager Traceback (most recent call last):

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager   File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 1564, in _allocate_network_async

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager     dhcp_options=dhcp_options)

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager   File "/usr/lib/python2.7/site-packages/nova/network/neutronv2/api.py", line 620, in allocate_for_instance

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager     get_client(context, admin=True))

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager   File "/usr/lib/python2.7/site-packages/nova/network/neutronv2/api.py", line 237, in get_client

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager     auth_token = _ADMIN_AUTH.get_token(_SESSION)

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager   File "/usr/lib/python2.7/site-packages/keystoneclient/auth/identity/base.py", line 200, in get_token

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager     return self.get_access(session).auth_token

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager   File "/usr/lib/python2.7/site-packages/keystoneclient/auth/identity/base.py", line 240, in get_access

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager     self.auth_ref = self.get_auth_ref(session)

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager   File "/usr/lib/python2.7/site-packages/keystoneclient/auth/identity/generic/base.py", line 184, in get_auth_ref

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager     self._plugin = self._do_create_plugin(session)

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager   File "/usr/lib/python2.7/site-packages/keystoneclient/auth/identity/generic/base.py", line 180, in _do_create_plugin

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager     raise exceptions.DiscoveryFailure(msg)

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager DiscoveryFailure: Could not determine a suitable URL for the plugin

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager 

2016-01-14 20:59:48.238 16974 INFO nova.virt.libvirt.driver [req-7585288c-39a1-4920-913b-23fb4658d1f6 caa811f6476e402aa27bc0c82b738d4b 10a350f60ed7436882b1180aba3237bf - - -] [instance ...
(more)
edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted
0

answered 2016-06-08 16:20:38 -0500

jjose gravatar image

I do have the same issue. Every log files seems working fine on Controller Node. But nova-compute.log throws the following error. Please do let me know if you figure out some way to get out of this error.

edit flag offensive delete link more
0

answered 2016-01-18 23:38:54 -0500

NileshB gravatar image

updated 2016-01-18 23:44:44 -0500

In my case, it was a same problem mentioned in link https://ask.openstack.org/en/question/54526/amqp-server-on-1000115672-is-unreachable/

Add firewall rule to allow keystone and glance ports.

Execute following command on controller node:

-----------------Allow keystone ports on controller node

sudo iptables -A IN_public_allow -p tcp -m tcp --dport 5000 -m conntrack --ctstate NEW -j ACCEPT

sudo iptables -A IN_public_allow -p tcp -m tcp --dport 35357 -m conntrack --ctstate NEW -j ACCEPT

-----------------Allow glance port on controller node

sudo iptables -A IN_public_allow -p tcp -m tcp --dport 9292 -m conntrack --ctstate NEW -j ACCEPT

edit flag offensive delete link more

Comments

This gives the error: No Chan/target/match by that name

jjose gravatar imagejjose ( 2016-06-08 16:24:23 -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

1 follower

Stats

Asked: 2016-01-15 04:28:51 -0500

Seen: 1,170 times

Last updated: Jun 08 '16