Invalid engine server resource validation does not work with nova Noopquotadriver
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Max Rasskazov | ||
Murano |
Invalid
|
Undecided
|
Unassigned | ||
OpenStack Heat |
Fix Released
|
High
|
Dmitry Borodaenko | ||
Icehouse |
Fix Released
|
High
|
Dmitry Borodaenko |
Bug Description
How to reproduce:
Deploy openstack with Nova configured to use NoopQuotaDriver.
Try to create simple stack, e.g. use this as template file contents:
{
"AWSTemplateF
"Outputs": {},
"Description": "Hadoop Cluster by Sahara",
"Resources": {
"instance1": {
"Type": "OS::Nova::Server",
"Properties": {
"name": "instance1",
"flavor": "1",
"image": "af72cf5c-
}
}
}
}
The problem is for example here:
https:/
It is easy to see that in case of '-1's returned by nova NoopQuotaDriver, even empty values will exceed the quota.
The workaround is to either change the quota driver to DbQuotaDriver or to comment out these checks.
Changed in fuel: | |
status: | New → Triaged |
milestone: | none → 5.0 |
assignee: | nobody → Fuel Library Team (fuel-library) |
importance: | Undecided → High |
Changed in fuel: | |
assignee: | Fuel Library Team (fuel-library) → Fuel OSCI Team (fuel-osci) |
Changed in fuel: | |
assignee: | Fuel OSCI Team (fuel-osci) → Max Rasskazov (mrasskazov) |
Changed in heat: | |
status: | Confirmed → Fix Committed |
status: | Fix Committed → New |
status: | New → Confirmed |
Changed in heat: | |
importance: | Undecided → High |
assignee: | nobody → Dmitry Borodaenko (dborodaenko) |
Changed in heat: | |
milestone: | none → juno-1 |
status: | Fix Committed → Fix Released |
Changed in heat: | |
milestone: | juno-1 → 2014.2 |
Fix proposed to branch: stable/icehouse /review. openstack. org/89388
Review: https:/