RPC_API_VERSION out of sync
Bug #1317202 reported by
Lucas Alvares Gomes
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ironic |
Fix Released
|
High
|
Ruby Loo | ||
Bug Description
The commit https:/
A unittest should be added to avoid the same problem to happen in the future.
| Changed in ironic: | |
| assignee: | nobody → Ruby Loo (rloo) |
| importance: | Undecided → High |
| Changed in ironic: | |
| status: | New → In Progress |
| description: | updated |
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: | |
| milestone: | none → juno-1 |
| status: | Fix Committed → Fix Released |
| Changed in ironic: | |
| milestone: | juno-1 → 2014.2 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 5df503222ce4e39
Author: Ruby Loo <email address hidden>
Date: Wed May 7 16:58:43 2014 +0000
RPC_API_VERSION out of sync
This sets the RPC_API_VERSION for the conductor manager to be 1.15,
which is the same as the version on the API/client side.
A unit test was added to check that the RPC_API_VERSIONs are equal.
Comments in rpcapi.py and manager.py were added to remind readers
that the versions need to be in sync.
Change-Id: I047603d2d11173
Closes-Bug: #1317202