Activity log for bug #1592243
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2016-06-14 03:52:47 | Steve Baker | bug | added bug | ||
| 2016-06-14 03:52:55 | Steve Baker | heat: status | New | Triaged | |
| 2016-06-14 03:53:00 | Steve Baker | heat: importance | Undecided | High | |
| 2016-06-14 03:53:02 | Steve Baker | heat: assignee | Steve Baker (steve-stevebaker) | ||
| 2016-06-14 03:53:06 | Steve Baker | heat: milestone | newton-2 | ||
| 2016-06-14 04:17:23 | OpenStack Infra | heat: status | Triaged | In Progress | |
| 2016-06-14 04:36:12 | Steve Baker | summary | Nested stacks are not populated with correct nested_depth | Convergence: nested stacks are not populated with correct nested_depth | |
| 2016-06-14 04:36:23 | Steve Baker | tags | convergence-bugs | ||
| 2016-06-14 04:36:39 | Steve Baker | description | Observing the database records for existing stacks with deeply nested stacks shows that all stack records have a nested_depth of 0 or 1. This is very wrong, and will result in max_nested_stack_depth config policy not being enforced. | Observing the database records for existing convergence stacks with deeply nested stacks shows that all stack records have a nested_depth of 0 or 1. This is very wrong, and will result in max_nested_stack_depth config policy not being enforced. | |
| 2016-06-14 12:25:26 | OpenStack Infra | heat: status | In Progress | Fix Released |
