Extensions' CLI module in Cisco plugin is broken after packaging changes
Bug #891705 reported by
Sumit Naiksatam
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
Fix Released
|
Medium
|
Sumit Naiksatam | ||
| quantum (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
This module refers to "bin/cli" for the core API's CLI. However, that CLI has been renamed to "quantum". Hence it's breaking.
Revision history for this message
| Sumit Naiksatam (snaiksat) wrote | #1 |
| Changed in quantum: | |
| status: | New → In Progress |
Revision history for this message
| Openstack Gerrit (openstack-gerrit) wrote Fix merged to quantum (master) | #2 |
| Changed in quantum: | |
| status: | In Progress → Fix Committed |
| Changed in quantum: | |
| status: | Fix Committed → Fix Released |
| Changed in quantum: | |
| milestone: | essex-2 → 2012.1 |
| Changed in quantum (Ubuntu): | |
| status: | New → Fix Released |
To post a comment you must log in.
This is slightly bigger change than just pointing to the renamed cli script. The new script, from a process perspective, behaves in a slightly different way. Instead pointing to the renamed script, the new cli python module will be used.