Murano deployment failed with error Unexpected stack state CREATE_COMPLETE

[Victor Ryzhenkin]

Steps:
1. Create murano environment
2. Add any application
3. Deploy environment

Actual result:
2015-08-06 22:57:49.658 23111 ERROR murano.common.engine [-]
  exceptions.EnvironmentError: Unexpected stack state CREATE_COMPLETE: Stack CREATE completed successfully

More logs:
http://paste.openstack.org/show/411919/

Note: This bug is race condition. Chance to reproduce it depends on your hardware.

[Kirill Zaitsev (kzaitsev)]

Demoting to high, since it only happens on rare occasions and does not render the whole system unusable.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/211157
Committed: https://git.openstack.org/cgit/openstack/murano/commit/?id=8d52384fd35fc240dd9f3d8e7c782e8b7dfd90ee
Submitter: Jenkins
Branch: master

commit 8d52384fd35fc240dd9f3d8e7c782e8b7dfd90ee
Author: Stan Lagun <email address hidden>
Date: Mon Aug 10 16:32:18 2015 +0300

    Do not confuse terminal stack statuses

    When stack update issued HeatStack waits for terminal
    status to arrive. However if operation hasn't started yet
    status of previous operation may be returned which can
    be CREATE_COMPLETE which leaded to exception to be
    raised or UPDATE_COMPLETE of previous update which
    caused stack.push() to exit early.

     Now update operation will wait until stack status change
     from the state it was before update was issued. This is tracked
     by comparing previous and current tuple(creation time, update time)

    Change-Id: I3829f6945b590b942506d4b512e902939053d107
    Closes-Bug: #1482989

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/kilo
Review: https://review.openstack.org/260526

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/260526
Committed: https://git.openstack.org/cgit/openstack/murano/commit/?id=cb92070f163d0c9152221673b7d235788398f4f5
Submitter: Jenkins
Branch: stable/kilo

commit cb92070f163d0c9152221673b7d235788398f4f5
Author: Stan Lagun <email address hidden>
Date: Tue Dec 22 16:17:52 2015 +0300

    Do not confuse terminal stack statuses

    When stack update issued HeatStack waits for terminal
    status to arrive. However if operation hasn't started
    yet status of previous operation may be returned which
    can be CREATE_COMPLETE which leaded to exception to be
    raised or UPDATE_COMPLETE of previous update which
    caused stack.push() to exit early.

    Now update operation will wait until stack status change
    from the state it was before update was issued. This is
    tracked by comparing previous and current
    tuple (creation time, update time)

    Change-Id: I4fbc718ea81a98b3811641b97362d171a417f80a
    Closes-Bug: #1482989

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/murano 2015.1.1 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/murano 2015.1.1 release.