HA deploy: one neutron-api unit had wrong credentials in memory

Bug #1456291 reported by David Britton on 2015-05-18
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack neutron-api charm
Undecided
Unassigned
neutron-api (Juju Charms Collection)
Undecided
Unassigned

Bug Description

A simple `sudo service neutron-server restart` fixed the problem. All credentials on disk looked identical between the three units, crm status was clean.

The error that tipped me off was `neutron floatingip-list` occasionally getting a 500, traced to neutron-api which showed this:

2015-05-18 16:55:47.592 57957 WARNING keystonemiddleware.auth_token [-] Invalid user token. Keystone response: {u'error': {u'message': u'The request you have made requires authentication.', u'code': 401, u'title': u'Unauthorized'}}
2015-05-18 16:55:47.593 57957 WARNING keystonemiddleware.auth_token [-] Authorization failed for token

I'll attach charm logs for all three units (juju and neutron).

David Britton (davidpbritton) wrote :
James Page (james-page) wrote :

Hmm - this sounds familiar - I think there was a packaging fix in keystonemiddleware to resolve this

tags: added: kanban-cross-team
tags: removed: kanban-cross-team
James Page (james-page) on 2017-02-23
Changed in neutron-api (Juju Charms Collection):
status: New → Invalid
James Page (james-page) wrote :

As this bug has not had an update in two years, and we've seen no further duplicates of this problem I'm marking this bug as 'Invalid'; I suspect that its been fixed in a new OpenStack release.

Changed in charm-neutron-api:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers