Auto scaling nested stack loses its owner_id on stack update

[Steve Baker]

After the first scaling event occurs, when the nested stack is updated, the owner_id of the nested stack is being set to NULL. This means that the nested stack starts showing up in "heat stack-list" calls.

MariaDB [heat]> select id, name, owner_id from stack where deleted_at is null;
+--------------------------------------+---------------------------------------------------------+----------+
| id | name | owner_id |
+--------------------------------------+---------------------------------------------------------+----------+
| 7852023f-c8ba-4e22-8c0f-51a643d48db4 | AutoScalingTest-775215682 | NULL |
| a988aaa5-2a5b-4561-b6bd-5a26681e48d8 | AutoScalingTest-775215682-SmokeServerGroup-oo265nn2pemn | NULL |
+--------------------------------------+---------------------------------------------------------+----------+
2 rows in set (0.00 sec)

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/41812
Committed: http://github.com/openstack/heat/commit/4a4a0656f8ba7db8d41e781ce692ffef90a6fa99
Submitter: Jenkins
Branch: master

commit 4a4a0656f8ba7db8d41e781ce692ffef90a6fa99
Author: Christopher Armstrong <email address hidden>
Date: Tue Aug 13 23:40:12 2013 +0000

    Store owner_id on Stack so updates maintain it

    Instead of passing owner to the store() method of parser.Stack,
    it is now maintained as an attribute of the Stack instance,
    and store() will use that saved attribute when saving.

    This fixes the problem of losing the owner_id on updates to
    a stack.

    Fixes bug 1212013

    Change-Id: I1e3b7832291ca0f5cda24c1995ab782824e48943