Ask Your Question
1

Failed to notify nova on events

asked 2014-08-31 09:18:46 -0500

FabianB gravatar image

updated 2014-09-01 10:55:36 -0500

Hello everyone,

I'm currently setting up a test environment to finally go live afterwards. After i got through hundreds of problems and reinstalling the controller node, some compute nodes I am now stuck with the neutron-server telling me that it couldn't notify nova on events.

This error occurs in var/log/neutron/neutron-server.log while creating a new instance.

2014-08-31 15:36:43.376 3501 TRACE neutron.notifiers.nova   File "/usr/lib/python2.7/dist-packages/neutron/notifiers/nova.py", line 221, in send_even$
2014-08-31 15:36:43.376 3501 TRACE neutron.notifiers.nova     batched_events)
2014-08-31 15:36:43.376 3501 TRACE neutron.notifiers.nova   File "/usr/lib/python2.7/dist-packages/novaclient/v1_1/contrib/server_external_events.py"$
2014-08-31 15:36:43.376 3501 TRACE neutron.notifiers.nova     return_raw=True)
2014-08-31 15:36:43.376 3501 TRACE neutron.notifiers.nova   File "/usr/lib/python2.7/dist-packages/novaclient/base.py", line 152, in _create
2014-08-31 15:36:43.376 3501 TRACE neutron.notifiers.nova     _resp, body = self.api.client.post(url, body=body)
2014-08-31 15:36:43.376 3501 TRACE neutron.notifiers.nova   File "/usr/lib/python2.7/dist-packages/novaclient/client.py", line 286, in post
2014-08-31 15:36:43.376 3501 TRACE neutron.notifiers.nova     return self._cs_request(url, 'POST', **kwargs)
2014-08-31 15:36:43.376 3501 TRACE neutron.notifiers.nova   File "/usr/lib/python2.7/dist-packages/novaclient/client.py", line 275, in _cs_request
2014-08-31 15:36:43.376 3501 TRACE neutron.notifiers.nova     raise e
2014-08-31 15:36:43.376 3501 TRACE neutron.notifiers.nova Unauthorized: Unauthorized (HTTP 401)
2014-08-31 15:36:43.376 3501 TRACE neutron.notifiers.nova

Error shown in the dashboard coming from the compute node:

Error: Failed to launch instance "test": Please try again later [Error: Virtual Interface creation failed].

/etc/neutron/neutron.conf file

notify_nova_on_port_status_changes = True

# Send notifications to nova when port data (fixed_ips/floatingips) change
# so nova can update it's cache.
notify_nova_on_port_data_changes = True

# URL for connection to nova (Only supports one nova region currently).
nova_url = http://[correctip]:8774/v2/%(tenant_id)s

# Name of nova region to use. Useful if keystone manages more than one region
nova_region_name = [correct name]

# Username for connection to nova in admin context
nova_admin_username = admin

# The uuid of the admin nova tenant
nova_admin_tenant_id = admin

# Password for connection to nova in admin context.
nova_admin_password = ADMIN_PASS

# Authorization URL for connection to nova in admin context.
nova_admin_auth_url = http://[correct ip]:35357/v2.0

I've seen a solution to tell the compute node that the interface creation error isn't fatal anymore, but that is not the solution I want. I need to know if I use the correct nova_admin_user and what I can check additionally to fix this error.

If you need more information, I will provide it

Thanks in advance,

Fabian

edit retag flag offensive close merge delete

Comments

1

Hey,

I got the same issue. I can't figure out how to fix it. If there's anyone who might have a solution, please post it. Even ideas would be appreciated.

Regards, Max

M1lk4h0l1c gravatar imageM1lk4h0l1c ( 2014-09-01 10:56:01 -0500 )edit

Error message depicts that neutron is unable to authenticate with keystone. Please look into neutron.conf and making sure keystone authenticating credentials are correct.

Khayam gravatar imageKhayam ( 2014-12-31 23:03:52 -0500 )edit

We seeing same issue on Icehouse :( Nothing helps except turning off callback wait in nova.conf. Credentials are fine (it's unauthorized, not un-authenticated). Maybe some

max-lobur gravatar imagemax-lobur ( 2015-01-09 18:22:03 -0500 )edit

2 answers

Sort by ยป oldest newest most voted
1

answered 2015-01-09 18:36:11 -0500

max-lobur gravatar image

Just solved:

  1. Make sure you have the following 2 lines in nova-api policy.json "compute_extension:os-server-external-events:create": "rule:admin_api", "compute_extension:v3:os-server-external-events:create": "rule:admin_api",
  2. Make sure you specifying tenant ID, not tenant name!: nova_admin_tenant_id = 666ff4ddedf24d7bb9a9da11df72b666
edit flag offensive delete link more

Comments

thanks for sharing

SGPJ gravatar imageSGPJ ( 2015-01-16 04:30:42 -0500 )edit
0

answered 2015-06-29 14:29:40 -0500

updated 2015-06-29 14:30:58 -0500

This helped me: https://bugzilla.redhat.com/show_bug.cgi?id=1087529 (bug on redhat bugzilla). Basically you'd have to make sure correct credentials set in neutron.conf.

edit flag offensive delete link more

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: 2014-08-31 09:18:46 -0500

Seen: 2,979 times

Last updated: Jun 29 '15