-1 vs. None w/ Unlimited Quotas
Bug #972034 reported by
Gabriel Hurley
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Dan Prince |
Bug Description
1. Nova uses -1 as its special value for configuring unlimited quotas.
2. The Nova API sends "None" for an unlimited quota.
3. Novaclient strips out "None" in the quota update code, so you can't send a None/null.
4. Sending a -1 through novaclient works, but isn't treated specially and thus -1 is sent back when the quota is retrieved instead of None.
This inconsistency makes working with unlimited quotas via the API very very difficult.
(Also, the quotas API happily accepts any negative number, which seems rather broken.)
Changed in nova: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in nova: | |
assignee: | nobody → Dan Prince (dan-prince) |
Changed in nova: | |
status: | Confirmed → In Progress |
Changed in nova: | |
milestone: | none → essex-rc3 |
tags: | removed: essex-rc-potential |
Changed in nova: | |
status: | Fix Released → In Progress |
no longer affects: | nova/folsom |
no longer affects: | nova/essex |
Changed in nova: | |
status: | In Progress → Fix Released |
Changed in nova: | |
milestone: | essex-rc3 → 2012.1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/6184
Review: https:/