Availability zone ignored in ec2 api
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Vish Ishaya | ||
Diablo |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
The ec2 api parameter incorrectly parsed in api. When i use euca-run-instance with -z myzone, nova ignore this flag and start instance on random chosen host. In logs i can see that api receives that parameter:
2011-11-11 14:57:26,566 DEBUG nova.api [-] arg: Placement.
es/python2.
But then this value is thrown away and instance have started on host 'server-118'.
I suppose there is a mistake in nova/api/
instances = self.compute_
While all parameters, retreived from ec2 have lowercase and underscore-
instances = self.compute_
all works fine.
Changed in nova: | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → Vish Ishaya (vishvananda) |
tags: | added: diablo-backport |
Changed in nova: | |
milestone: | none → essex-2 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | essex-2 → 2012.1 |
Reviewed: https:/ /review. openstack. org/1560 github. com/openstack/ nova/commit/ b6644ffe4360a9d 55e138e20e0d453 e8ffb2c718
Committed: http://
Submitter: Jenkins
Branch: master
status fixcommitted
done
commit b6644ffe4360a9d 55e138e20e0d453 e8ffb2c718
Author: Vishvananda Ishaya <email address hidden>
Date: Fri Nov 11 11:37:03 2011 -0800
Make run instances respect availability zone
* includes test
* fixes bug 888918
Change-Id: I40985e9dcc153f ae53675f3da5e2d 5b5763cfca3