yahoo-eng-team team mailing list archive

[jichenjc <jichenjc@xxxxxxxxxx>]

liberty is EOL, and you may refer to this change for further info

commit de1583b09c73e78772afb145c6f7cad052c7ffe5
Author: Roman Podoliaka <rpodolyaka@xxxxxxxxxxxx>
Date:   Mon Jan 18 16:40:49 2016 +0200

    Issue an info log msg when port quota is exceeded

    When booting multiple instances at once using max_count it's possible
    to exceed the port quota in Neutron. Currently, we proceed with
    booting min(quota_value, max_count) number of instances and only
    issue a debug message to Nova logs. It may be unclear to an operator,
    why a fewer number of VMs were booted, and there will be nothing
    useful in logs, if debug wasn't enabled.

    Issue an info level log message instead, so that it's visible in
    production logs without debug logging enabled (oslo.log now defaults
    to verbose=True).

    TrivialFix

    Change-Id: I1e5edf17ce7d5a3bc2ac9403c7a8d492de274789


** Changed in: nova
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1642500

Title:
  nova boot min_count and max_count not limited by neutron port quota

Status in OpenStack Compute (nova):
  Won't Fix

Bug description:
  openstack-liberty

  1) set user quota:
  neutron-port:  10（4 used by network:router_interface and network:dhcp）
  nova instance: 10
  nova cores:    10
  nova rams:     51200M

  2) want to create 10 vms in a request
  # nova boot --flavor m1.tiny --image xxx --min-count 10 --max-count 10 --nic net-id=yyy instance

  
  i thought nova boot would fail because only 6 ports left. Actually, 6 instances are created and no error happened.

  is it reasonable?

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1642500/+subscriptions