if using nova boot --num-instances and neutron instances count are truncated to port quota
Bug #1309244 reported by
Aaron Rosen
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Invalid
|
Undecided
|
Unassigned | ||
python-novaclient |
Fix Released
|
Medium
|
Joe Gordon |
Bug Description
If using nova with neutron and you run the following command:
nova boot --image cirros-
and you do not have enough quota it would be nice if nova-api would raise an error or perhaps actually try and launch 30 instances. Instead you get some number of instances up to your port-quota.
tags: | added: network |
Changed in python-novaclient: | |
status: | New → Triaged |
assignee: | nobody → Joe Gordon (jogo) |
importance: | Undecided → Medium |
Changed in python-novaclient: | |
milestone: | none → 2.18.0 |
Changed in python-novaclient: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This is a novaclient bug, the nova API has min_count and max_count. if min_count is over the quota limit the command will fail. So novaclient should be updated to support min_count and max_count flags and deprecate num-instances (as an alias for max count)