novaclient does not work properly when instance_names are re-used
Bug #931605 reported by
Anthony Young
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python-novaclient |
Fix Released
|
Medium
|
Rick Harris | ||
Bug Description
Novaclient accepts names instead of ids when specifying instances. However, nova does not enforce uniqueness for names. Thus, if a user creates two servers with the name "my_server", the user can find herself in situations where this ambiguity can cause breakage. For example:
1) user launches instance with name my_server
2) user attaches volume to my_server
3) user launches another instance named my_server
4) user tries to detach volume from my_server
Expected:
Not really sure! But the desired behavior would be to detach the volume from the first instance.
Actual:
Fails with a 404, since apparently my_server #2 gets selected for the detach operation.
| tags: | added: python-novaclient |
Revision history for this message
| Thierry Carrez (ttx) wrote | #1 |
| Changed in nova: | |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to python-novaclient (master) | #2 |
| Changed in nova: | |
| assignee: | nobody → Rick Harris (rconradharris) |
| status: | Confirmed → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to python-novaclient (master) | #3 |
| Changed in nova: | |
| status: | In Progress → Fix Committed |
| Changed in nova: | |
| milestone: | none → folsom-1 |
| Changed in nova: | |
| status: | Fix Committed → Fix Released |
| affects: | nova → python-novaclient |
| Changed in python-novaclient: | |
| milestone: | folsom-1 → none |
To post a comment you must log in.
Linked to bug 954489