Convergence: nested stacks are not populated with correct nested_depth

[Steve Baker]

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.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/329263

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/329263
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=54caa859660f248d3d11f0c5b06f0cf36eacd0ee
Submitter: Jenkins
Branch: master

commit 54caa859660f248d3d11f0c5b06f0cf36eacd0ee
Author: Steve Baker <email address hidden>
Date: Tue Jun 14 15:53:45 2016 +1200

    Set nested_depth when creating Stack from db

    Without this, deeply nested stacks will all be given the nested_depth
    value of 1 instead of the actual nested_depth when convergence is
    enabled.

    This also means that max_nested_stack_depth currently isn't enforced
    for convergence created stacks.

    Change-Id: I34e90ae67e6ec2e235be6cc4a247673eaa7773cf
    Closes-Bug: #1592243

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/heat 7.0.0.0b2 development milestone.