Murano

  1. Bug #1500200
  2. Comment #7

Comment 7 for bug 1500200

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

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

commit 4a3fc9b07775313e9802c2e11e4f388d75731950
Author: Stan Lagun <email address hidden>
Date: Sun Sep 27 18:22:40 2015 +0300

    Murano waited indefinitely for UPDATE_COMPLETE stack status

    On recent Heat version last modification timestamp changes on
    update start rather than finish. As a result when stack exits from
    IN_PROGRESS state timestamp doesn't change any longer.
    But Murano also waited for timestamp to change. As a result
    Murano waited indefinitely and deployment hung.

    With this change IN_PROGRESS status will no longer set
    last modification timestamps. So now we will be comparing
    timestamps between 2 terminal statuses rather than between
    last UPDATE_IN_PROGRESS and UPDATE_COMPLETE that
    now have the same timestamp.

    Change-Id: Idd933d453ef7715e409439a53a3baf9eaa202370
    Closes-Bug: #1500200