novaclient not raising an exception when receiving 503 response from service endpoint
Bug #962454 reported by
Joseph Heck
This bug affects 4 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python-novaclient |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
Found this in dashboard with a screwed up configuration.
Accidentally set a bad password in the nova/api-paste.conf for the service password. Keystone, Nova, and Dashboard all otherwise operational.
NovaClient used from dashboard to request API services from Nova - with the broken password, the auth_token middleware returned a 503 response. Nova client parsed that and handed back the req/response, but didn't generate an exception.
I thought it would/should generate an exception (my opinion) when receiving a 5** response. In keystoneclient, we're popping equivalent relevant exceptions on NotAuthorized (401) and NotFound (404).
Not sure we've standardized on this pattern across clients though.
| tags: | added: python-novaclient |
| Changed in nova: | |
| assignee: | nobody → yong sheng gong (gongysh) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to python-novaclient (master) | #1 |
| Changed in nova: | |
| status: | New → In Progress |
| Changed in nova: | |
| assignee: | yong sheng gong (gongysh) → nobody |
| Changed in nova: | |
| importance: | Undecided → Medium |
| status: | In Progress → Confirmed |
| affects: | nova → python-novaclient |
Revision history for this message
| Andy McCrae (andrew-mccrae) wrote | #2 |
| Changed in python-novaclient: | |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/