Fix backwards compatibility
Bug #1438478 reported by
Michael Davies
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ironic |
Fix Released
|
High
|
Michael Davies | ||
Bug Description
As part of the changes we made for Kilo, we didn't pay enough attention to backwards compatibility.
Consequently, we should attempt to the best of our ability to preserve pre-Kilo behaviour when interacting with a pre-Kilo client.
One such area of change that's been discovered has been where a UUID has been specified as part of an API call and the UUID either cannot be found or is invalid. We are currently raising InvalidUuidOrName, when in Juno we raised NodeNotFound.
| Changed in ironic: | |
| assignee: | nobody → Michael Davies (mrda) |
| Changed in ironic: | |
| status: | New → In Progress |
| Changed in ironic: | |
| importance: | Undecided → High |
| milestone: | none → kilo-rc1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to ironic (master) | #1 |
| Changed in ironic: | |
| status: | In Progress → Fix Committed |
| Changed in ironic: | |
| status: | Fix Committed → Fix Released |
| Changed in ironic: | |
| milestone: | kilo-rc1 → 2015.1.0 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit a4f3c84b02a6735
Author: Michael Davies <email address hidden>
Date: Wed Mar 25 22:27:49 2015 -0700
Improve backwards compat on API behaviour
As part of other changes for this release, we prioritised
descriptiveness over backwards compatibility. In subsequent
discussions we've agreed this is incorrect. This change
ensures that the same exception is raised on UUID not found.
Closes-Bug: #1438478
Change-Id: I44bb8041867330