Fixed IPs quota can break upgrades
Bug #1161190 reported by
Sam Morrison
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Critical
|
Michael Still | ||
Essex |
Won't Fix
|
Critical
|
Michael Still | ||
Folsom |
Fix Released
|
Critical
|
Vish Ishaya | ||
openstack-manuals |
Fix Released
|
Critical
|
Tom Fifield |
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
Changed in nova: | |
assignee: | nobody → Michael Still (mikalstill) |
tags: | added: ops |
Changed in nova: | |
status: | Triaged → In Progress |
Changed in openstack-manuals: | |
milestone: | none → grizzly |
status: | New → Confirmed |
importance: | Undecided → Critical |
Changed in openstack-manuals: | |
status: | Confirmed → In Progress |
assignee: | nobody → Tom Fifield (fifieldt) |
Changed in nova: | |
milestone: | grizzly-rc2 → 2013.1 |
To post a comment you must log in.
The default quota was set to the same value as the default instance quota in the code. However, I can see that it would be better to set it to the current value of the default instances quota -- i.e. if you changed the default instance quota, this should change too.
Would that mitigate your concern? It wouldn't work for users where you have grown their instance quota though...
I'm hesitant to allow an unlimited quota here because that reopens the DoS window that this quota was added to close.