datastore selection bug - fills first disk only
Bug #1227825 reported by
Shawn Hartsock
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Shawn Hartsock | ||
Havana |
Fix Released
|
High
|
Gary Kotton | ||
VMwareAPI-Team |
In Progress
|
Critical
|
Unassigned |
Bug Description
Currently the vmwareapi drivers will only select the first
available datastore it finds on a host or in a cluster,
even when there are other datastores with capacity,
it will fill the first datastore completely
and then fail on all subsequent attempts to place an instance.
Changed in nova: | |
status: | New → In Progress |
importance: | Undecided → High |
summary: |
- fixes datastore selection bug + datastore selection bug - fills first disk only |
Changed in openstack-vmwareapi-team: | |
status: | New → In Progress |
importance: | Undecided → Critical |
Changed in nova: | |
milestone: | havana-rc1 → none |
tags: | added: havana-rc-potential |
tags: |
added: havana-backport-potential removed: havana-rc-potential |
tags: | removed: havana-backport-potential |
Changed in nova: | |
milestone: | none → icehouse-1 |
Changed in nova: | |
status: | Fix Committed → Fix Released |
tags: | removed: in-stable-havana |
tags: | added: grizzly-backport-potential |
tags: | removed: grizzly-backport-potential |
Changed in nova: | |
milestone: | icehouse-1 → 2014.1 |
To post a comment you must log in.
See: https:/ /review. openstack. org/#/c/ 47289/