From c821bbe2b7403bcb9ef7bf65a240cbbc7f65f9a3 Mon Sep 17 00:00:00 2001 From: Thomas Herve Date: Thu, 22 Nov 2018 15:16:54 +0100 Subject: [PATCH] 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 --- tripleoclient/workflows/scale.py | 5 ++++- tripleoclient/workflows/stack_management.py | 5 ++++- 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/tripleoclient/workflows/scale.py b/tripleoclient/workflows/scale.py index 1915e8e6a..a147a3b60 100644 --- a/tripleoclient/workflows/scale.py +++ b/tripleoclient/workflows/scale.py @@ -31,7 +31,10 @@ def delete_node(clients, **workflow_input): ) for payload in base.wait_for_messages(workflow_client, ws, execution): - if payload['status'] != "SUCCESS": + status = payload['status'] + if status == 'RUNNING': + continue + if status != 'SUCCESS': raise InvalidConfiguration(payload['message']) diff --git a/tripleoclient/workflows/stack_management.py b/tripleoclient/workflows/stack_management.py index 3b78ad002..bc325a196 100644 --- a/tripleoclient/workflows/stack_management.py +++ b/tripleoclient/workflows/stack_management.py @@ -40,5 +40,8 @@ def delete_stack(clients, stack): ) for payload in base.wait_for_messages(workflow_client, ws, execution): - if payload['status'] != "SUCCESS": + status = payload['status'] + if status == 'RUNNING': + continue + if status != 'SUCCESS': raise InvalidConfiguration(payload['message'])