The Mistral workflows should retry sending messages to Zaqar

Bug #1626103 reported by Dougal Matthews
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
Dougal Matthews

Bug Description

"Error response from Zaqar. Code: 503. Title: Service temporarily unavailable. Description: Messages could not be enqueued. Please try again in a few seconds.."

Sometimes workflows are failing with this error message. It sounds like we should add retrying to the Zaqar message sending.

Tags: workflows
Changed in tripleo:
status: Confirmed → Triaged
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-common (master)

Fix proposed to branch: master
Review: https://review.openstack.org/377827

Changed in tripleo:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-common (master)

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

commit 7ee66120acf48a069905aacd8e92367bd47ac11b
Author: Dougal Matthews <email address hidden>
Date: Tue Sep 27 17:07:57 2016 +0100

    Retry sending messages to Zaqar if it fails

    Sometimes messages to Zaqar fail with with the following error.

    > Error response from Zaqar. Code: 503. Title: Service temporarily
    > unavailable. Description: Messages could not be enqueued. Please
    > try again in a few seconds..

    When this happens we should retry as it states. This change has
    the task retry calling the queue_post action a maximum of 5 times
    with a 1 second delay between each attempt.

    Closes-Bug: #1626103
    Change-Id: Iba272004a8adb7ebc5122fc47764dbf81925bc62

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

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

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.