yahoo-eng-team team mailing list archive

[OpenStack Hudson <1161190@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/25665
Committed: http://github.com/openstack/nova/commit/a31211325be7242000f5fd1e44104e9799b21b63
Submitter: Jenkins
Branch:    milestone-proposed

commit a31211325be7242000f5fd1e44104e9799b21b63
Author: Michael Still <mikal@xxxxxxxxxxx>
Date:   Fri Mar 29 09:00:46 2013 +1100

    Set default fixed_ip quota to unlimited.
    
    DocImpact: our previous default quota of ten was poorly thought through
    and resulted in upgrade problems. Instead, let's have operators opt into
    fixed IP quotas. This change should be mentioned in release notes please.
    
    Resolves bug 1161190.
    
    Change-Id: I2f066a0129461899fe330a628cf49ee5273eaba4


** Changed in: nova
       Status: Fix Committed => Fix Released

-- 
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/1161190

Title:
  Fixed IPs quota can break upgrades

Status in OpenStack Compute (Nova):
  Fix Released
Status in OpenStack Compute (nova) essex series:
  In Progress
Status in OpenStack Compute (nova) folsom series:
  In Progress
Status in OpenStack Manuals:
  In Progress

Bug description:
  When upgrading our folsom cloud to latest stable/folsom it added
  support for fixed ip quota.

  The default is 10 which means all of a sudden my instances weren't
  getting IP's.

  I think the default should be -1 so it doesn't break existing clouds.

  Also need something in the release notes/ upgrade notes

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