Security Rules creation in a tight loop
Bug #1265937 reported by
yogesh-mehra
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Heat |
Triaged
|
Low
|
Tatiana Kholkina | ||
Bug Description
The Security Rules within a Security Group are not heat "resources" and are getting created in a tight loop which in some conditions becomes a cause for the nova over rate issue. One of the solutions is to split them into batches in the processing algo or give them a resource privilege syntactically.
Revision history for this message
| Steve Baker (steve-stevebaker) wrote | #1 |
| Changed in heat: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| Changed in heat: | |
| assignee: | nobody → Tetiana Lashchova (tlashchova) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to heat (master) | #2 |
| Changed in heat: | |
| status: | Triaged → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on heat (master) | #3 |
| Changed in heat: | |
| status: | In Progress → Triaged |
| Changed in heat: | |
| milestone: | none → no-priority-tag-bugs |
To post a comment you must log in.
The best solution will be to catch the OverLimit and retry until all rules are submitted. I would prefer novaclient to do these OverLimit retries automatically though, as I suggested in bug 1289035