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

Bug #1456291 reported by David Britton
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Neutron API Charm
Invalid
Undecided
Unassigned
neutron-api (Juju Charms Collection)
Invalid
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).

Tags: landscape
Revision history for this message
David Britton (dpb) wrote :
Revision history for this message
James Page (james-page) wrote :

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

David Britton (dpb)
tags: added: kanban-cross-team
David Britton (dpb)
tags: removed: kanban-cross-team
James Page (james-page)
Changed in neutron-api (Juju Charms Collection):
status: New → Invalid
Revision history for this message
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  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.