tripleo

client exits on RUNNING messages

Bug #1804660 reported by Thomas Herve on 2018-11-22

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	tripleo	Fix Released	High	Unassigned	tripleo stein-2

Bug Description

The worflows tripleo.stack.v1.delete_stack and tripleo.scale.v1.delete_node calls heat stack list in a loop to check for stack status. Unfortunately stack list puts a message in the zaqar queue, and we don't consume correctly on the client side. We should ignore the "RUNNING" messages, and wait for final result.

Tags:

Thomas Herve (therve) on 2018-11-22

summary:	- client exists on RUNNING messages + client exits on RUNNING messages
Changed in tripleo:
importance:	Undecided → High
milestone:	none → stein-2

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2018-11-29: Change abandoned on python-tripleoclient (master)

Change abandoned by Alex Schultz (<email address hidden>) on branch: master
Review: https://review.openstack.org/619583
Reason: Clearing the gate. Do not retore this until being given the all clear. See http://lists.openstack.org/pipermail/openstack-discuss/2018-November/000368.html

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2018-12-04: Fix merged to python-tripleoclient (master)

Reviewed: https://review.openstack.org/619583
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=c821bbe2b7403bcb9ef7bf65a240cbbc7f65f9a3
Submitter: Zuul
Branch: master

commit c821bbe2b7403bcb9ef7bf65a240cbbc7f65f9a3
Author: Thomas Herve <email address hidden>
Date: Thu Nov 22 15:16:54 2018 +0100

Don't exit on RUNNING status on delete

    In delete node and delete stack, we exit on non SUCCESS messages, but
    mistral also sends us RUNNING messages when calling stack list, that we
    should consume.

Change-Id: I45442ef2c622463a957c84be47f38ec4528001ac
Closes-Bug: #1804660

Changed in tripleo:
status:	New → Fix Released

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2018-12-17: Fix proposed to python-tripleoclient (stable/rocky)

Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/625713

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2018-12-19: Fix merged to python-tripleoclient (stable/rocky)

Reviewed: https://review.openstack.org/625713
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=425736d65269a349a46696c8c92f5dcae3236fc5
Submitter: Zuul
Branch: stable/rocky

commit 425736d65269a349a46696c8c92f5dcae3236fc5
Author: Thomas Herve <email address hidden>
Date: Thu Nov 22 15:16:54 2018 +0100

Don't exit on RUNNING status on delete

    In delete node and delete stack, we exit on non SUCCESS messages, but
    mistral also sends us RUNNING messages when calling stack list, that we
    should consume.

    Change-Id: I45442ef2c622463a957c84be47f38ec4528001ac
    Closes-Bug: #1804660
    (cherry picked from commit c821bbe2b7403bcb9ef7bf65a240cbbc7f65f9a3)