Don't notify zaqar in publish_ui_logs_to_swift

We shouldn't notify the main event queue when publishing logs: those are
run in a cron, so we're not waiting for messages from it. When it fails,
it can interrupt regular workflows.

Change-Id: Ifb17352c4a89e2a1ea7c014cf64a586b4e5a2859
Closes-Bug: #1754061
(cherry picked from commit 3efc2f9f1b)
This commit is contained in:
Thomas Herve 2018-03-12 09:57:36 +01:00
parent 0166826b0d
commit 1624b9be5e
1 changed files with 0 additions and 28 deletions

View File

@ -555,7 +555,6 @@ workflows:
file in swift. This workflow is called by cron trigger.
input:
- queue_name: tripleo
- logging_queue_name: tripleo-ui-logging
- logging_container: tripleo-ui-logs
@ -574,11 +573,6 @@ workflows:
action: zaqar.claim_messages
on-success:
- format_messages: <% task().result.len() > 0 %>
- notify_zaqar: <% task().result.len() = 0 %>
on-error: notify_zaqar
publish-on-error:
status: FAILED
message: <% task().result %>
input:
queue_name: <% $.logging_queue_name %>
ttl: 60
@ -600,10 +594,6 @@ workflows:
upload_to_swift:
action: tripleo.logging_to_swift.publish_ui_log_to_swift
on-success: delete_messages
on-error: notify_zaqar
publish-on-error:
status: FAILED
message: <% task().result %>
input:
logging_data: <% $.formatted_messages %>
logging_container: <% $.logging_container %>
@ -613,30 +603,12 @@ workflows:
delete_messages:
action: zaqar.delete_messages
on-success: get_messages
on-error: notify_zaqar
publish-on-error:
status: FAILED
message: <% task().result %>
input:
queue_name: <% $.logging_queue_name %>
messages: <% $.message_ids %>
publish:
status: SUCCESS
notify_zaqar:
action: zaqar.queue_post
input:
queue_name: <% $.queue_name %>
messages:
body:
type: tripleo.plan_management.v1.publish_ui_logs_to_swift
payload:
status: <% $.status %>
message: <% $.get('message', '') %>
execution: <% execution() %>
on-success:
- fail: <% $.get('status') = "FAILED" %>
download_logs:
description: Creates a tarball with logging data
input: