tripleo

Updates hanging after resources faild in Heat

Bug #1677548 reported by Julie Pichon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
Thomas Herve
tripleo pike-1 "pike-1"

Bug Description

Since https://review.openstack.org/#/c/435520/ got merged in Heat, we can get into a state where a failed resource is recreated during update after clearing a hook. That means that when we poll for events, we need to check for that additional action and not limit to updates.

There is patch up to fix this at https://review.openstack.org/#/c/451725/

Concretely it means when re-starting a stack update after a failure, the tripleo client gets stuck to IN_PROGRESS until the hook is manually cleared.

OpenStack Infra (hudson-openstack)
Changed in tripleo:
assignee: Thomas Herve (therve) → Julie Pichon (jpichon)
Julie Pichon (jpichon)
Changed in tripleo:
assignee: Julie Pichon (jpichon) → Thomas Herve (therve)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-common (master)

Reviewed: https://review.openstack.org/451725
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=ba113ca18825cf2eeafa7011b329aa96262d27e8
Submitter: Jenkins
Branch: master

commit ba113ca18825cf2eeafa7011b329aa96262d27e8
Author: Thomas Herve <email address hidden>
Date: Thu Mar 30 11:48:41 2017 +0200

    Handle re-created resources in StackUpdateManager

    Since Iaacc585b9806c08fd5a57c80c10eeb31cb0a8f71 got merged in Heat, we
    can get into a state where a failed resource is recreated during update
    after clearing a hook. That means that when we poll for events, we need
    to check for that additional action and not limit to updates.

    Change-Id: I2191a3f3df426eaa91fdd5b00299193a32efe366
    Closes-Bug: #1677548

Changed in tripleo:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-common (stable/ocata)

Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/452626

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-common (stable/newton)

Fix proposed to branch: stable/newton
Review: https://review.openstack.org/452639

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-common (stable/ocata)

Reviewed: https://review.openstack.org/452626
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=dc75ed6c336f1eca00fcfdafb7d85dc6c333d27f
Submitter: Jenkins
Branch: stable/ocata

commit dc75ed6c336f1eca00fcfdafb7d85dc6c333d27f
Author: Thomas Herve <email address hidden>
Date: Thu Mar 30 11:48:41 2017 +0200

    Handle re-created resources in StackUpdateManager

    Since Iaacc585b9806c08fd5a57c80c10eeb31cb0a8f71 got merged in Heat, we
    can get into a state where a failed resource is recreated during update
    after clearing a hook. That means that when we poll for events, we need
    to check for that additional action and not limit to updates.

    Change-Id: I2191a3f3df426eaa91fdd5b00299193a32efe366
    Closes-Bug: #1677548
    (cherry picked from commit ba113ca18825cf2eeafa7011b329aa96262d27e8)

tags: added: in-stable-ocata
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-common 7.0.0.0b1

This issue was fixed in the openstack/tripleo-common 7.0.0.0b1 development milestone.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-common 6.1.0

This issue was fixed in the openstack/tripleo-common 6.1.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-common (stable/newton)

Reviewed: https://review.openstack.org/452639
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=078105651b8ae60d4fffa2c2727446a9195acd71
Submitter: Jenkins
Branch: stable/newton

commit 078105651b8ae60d4fffa2c2727446a9195acd71
Author: Thomas Herve <email address hidden>
Date: Thu Mar 30 11:48:41 2017 +0200

    Handle re-created resources in StackUpdateManager

    Since Iaacc585b9806c08fd5a57c80c10eeb31cb0a8f71 got merged in Heat, we
    can get into a state where a failed resource is recreated during update
    after clearing a hook. That means that when we poll for events, we need
    to check for that additional action and not limit to updates.

    Change-Id: I2191a3f3df426eaa91fdd5b00299193a32efe366
    Closes-Bug: #1677548
    (cherry picked from commit ba113ca18825cf2eeafa7011b329aa96262d27e8)

tags: added: in-stable-newton
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-common 5.4.3

This issue was fixed in the openstack/tripleo-common 5.4.3 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.