max_net_count doesn't interact properly with min_count when booting multiple instances
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Chris Friesen | ||
Liberty |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
In compute.
We calculate max_net_count based on networking constraints.
Currently we error out if max_net_count is zero, but we don't check it against min_count. If the end user specifies a min_count that is greater than the calculated max_net_count the resulting error isn't very useful.
We know that min_count is guaranteed to be at least 1, so we can replace the existing test against zero with one against min_count. Doing this gives a much more reasonable error message:
controller-0:~$ nova boot --image myimage --flavor simple --min-count 2 --max-count 3 test
ERROR (Forbidden): Maximum number of ports exceeded (HTTP 403) (Request-ID: req-f7ff28bf-
tags: | added: api |
Changed in nova: | |
importance: | Undecided → Medium |
tags: | added: liberty-backport-potential |
Fix proposed to branch: master /review. openstack. org/283861
Review: https:/