Remove checking for already running config_download_deploy

This patch removes the checking for already running instances of the
tripleo.deployment.v1.config_download_deploy workflow from the workflow
itself as it's been moved to tripleoclient.

It is better handled in tripleoclient where the workflow inputs can be
checked to see if any of the other running workflows are also for the
current stack. That functionality would have required a custom action to
do in the workflow itself.

Change-Id: I6195068a42bfc2469a0b8b006e339e3ca5056dff
Partial-Bug: #1852314
Depends-On: Ic8dbf28b5796ff998165b6b73b941f21c65f1dfa
(cherry picked from commit 101bff0021)
This commit is contained in:
James Slagle 2019-11-12 11:03:11 -05:00
parent 5b3517cd08
commit 74159dc11d
1 changed files with 0 additions and 22 deletions

View File

@ -395,28 +395,6 @@ workflows:
tasks:
check_for_deploy_in_progress:
action: mistral.executions_find
input:
workflow_name: tripleo.deployment.v1.config_download_deploy
state: RUNNING
publish:
running_config_download_workflows: <% task().result.where($.id != execution().id) %>
on-success:
- fail_deploy_in_progress: <% $.running_config_download_workflows.len() > 0 %>
- get_blacklisted_hostnames: <% $.running_config_download_workflows.len() = 0 %>
fail_deploy_in_progress:
workflow: tripleo.messaging.v1.send
input:
queue_name: <% $.queue_name %>
type: <% execution().name %>
status: <% $.get('status', 'FAILED') %>
execution: <% execution() %>
message: Deployment already in progress with execution <% $.running_config_download_workflows[0].id %>
plan_name: <% $.plan_name %>
on-complete: fail
get_blacklisted_hostnames:
action: heat.stacks_output_show
input: