yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1161190] Re: Fixed IPs quota can break upgrades

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Michael Still <mikal@xxxxxxxxxxx>
Date: Wed, 17 Jul 2013 07:34:13 -0000
Reply-to: Bug 1161190 <1161190@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

Essex is no longer supported by upstream.

** Changed in: nova/essex
       Status: In Progress => 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/1161190

Title:
  Fixed IPs quota can break upgrades

Status in OpenStack Compute (Nova):
  Fix Released
Status in OpenStack Compute (nova) essex series:
  Won't Fix
Status in OpenStack Compute (nova) folsom series:
  Fix Released
Status in OpenStack Manuals:
  Fix Released

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