Forwarder incorrectly logs token expirations as API down.
Bug #1423376 reported by
Ryan Bak
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Monasca |
Fix Committed
|
Undecided
|
Unassigned | ||
Bug Description
If a the token the forwarder is using isn't valid it requests a new token and puts the message back in the queue. This is expected behavior, however queueing the message causes the warning "Monasca API or Keystone API are down or unreachable. Queuing the messages to send later..." to be logged, which is not correct as neither the monasca api nor the keystone api are down or unreachable.
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to monasca-agent (master) | #1 |
| Changed in monasca: | |
| status: | New → Fix Committed |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit f50d93addc3ef37
Author: Gary Hessler <email address hidden>
Date: Fri Feb 27 09:21:37 2015 -0700
Added more specific error messages when messages need to be queued for tha API
The error message when queueing messages to send to the monasca-api was not specific
enough to troubleshoot the issue. Added specific error messages for the 3 types of
Change-Id: Ib5d51d47add133
Closes-Bug: #1423376