Murano

Murano deployment failed with error Unexpected stack state CREATE_COMPLETE

  1. Series kilo
  2. Bug #1482989
Bug #1482989 reported by Victor Ryzhenkin
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Murano
Fix Released
High
Stan Lagun
Murano 1.0.1
Kilo
Fix Committed
High
Stan Lagun
Murano 2015.1.1

Bug Description

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.

See original description
Victor Ryzhenkin (vryzhenkin)
description: updated
Revision history for this message
Kirill Zaitsev (kzaitsev) wrote :

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

Changed in murano:
importance: Critical → High
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to murano (master)

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

Changed in murano:
assignee: nobody → Stan Lagun (slagun)
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to murano (master)

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

Changed in murano:
status: In Progress → Fix Committed
Serg Melikyan (smelikyan)
Changed in murano:
status: Fix Committed → Fix Released
Serg Melikyan (smelikyan)
Changed in murano:
milestone: liberty-3 → 1.0.0
Kirill Zaitsev (kzaitsev)
Changed in murano:
milestone: 1.0.0 → 1.0.1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to murano (stable/kilo)

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to murano (stable/kilo)

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

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/murano 2015.1.1

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

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

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.