Users can fill up the events table
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
High
|
Clint Byrum |
Bug Description
A user can very easily create an infinite amount of logs if they have access to Heat, leading to a very large events table.
- Create stack with many thousands of AWS::AutoScalin
- Update stack changing something that requires replacement of the launchconfiguration in a loop.
- Every update will involve 4 events for every resource, delete in progress, delete complete, create in progress, create complete.
Testing with Heat running on a single vcpu VM on my i7 laptop with a slow disk and an intentionally poorly tuned mysql (to amplify mysql performance problems):
With a 10 resource yaml, I was able to create 200 events in 1 minute.
With a 100 resource yaml, I was able to create 500 events in 1 minute.
With a 1000 resource yaml, Heat had problems updating it, and mysql started having issues because the table got fairly large at around 2000 events (working set exceeded innodb_
After around 3500 evensts, event-list started giving odd json errors.
Changed in heat: | |
milestone: | none → havana-rc1 |
description: | updated |
Changed in heat: | |
status: | Triaged → In Progress |
assignee: | nobody → Clint Byrum (clint-fewbar) |
Changed in heat: | |
status: | Fix Committed → Fix Released |
Changed in heat: | |
milestone: | havana-rc1 → 2013.2 |
Related fix proposed to branch: master /review. openstack. org/48154
Review: https:/