port usage tracking not reliable anymore
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Salvatore Orlando |
Bug Description
Patch https:/
Patch https:/
It might be worth considering just handling the sqlalchemy orm exception in this case; alternatively usage tracking for ports might be disabled.
A related question is why the logic for deleting a port resides in the ipam module, but probably it should not be answered here.
Changed in neutron: | |
importance: | Medium → High |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | liberty-rc1 → 7.0.0 |
the impact of this bug is not really serious anyway.
After a delete the quota tracker is not marked as dirty, and therefore it reports an incorrect, but higher usage data.
As a result a tenant might not be allowed to use all of its quota (but just total - 1). This would however be fixed by the next get operation.
I'm therefore downgrading the severity to medium.