zaqar throw a ServiceUnavailableError on minor update

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

Bug Description

There is some timing issue with zaqar on minor update, zaqar throw a ServiceUnavailableError 503:
When the execution state is finished but is still on 'running' state, in the while loop we try to claim messages but there is nothing to claim in the queue at this particular stage, so we have to catch the exception to not print it to the client

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to python-tripleoclient (master)

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

Changed in tripleo:
status: New → In Progress
Changed in tripleo:
milestone: none → queens-3
Changed in tripleo:
assignee: mathieu bultel (mat-bultel) → Dougal Matthews (d0ugal)
Changed in tripleo:
assignee: Dougal Matthews (d0ugal) → mathieu bultel (mat-bultel)
Changed in tripleo:
assignee: mathieu bultel (mat-bultel) → Dougal Matthews (d0ugal)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to python-tripleoclient (master)

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

commit c102747c8d8ec175831c2c35f83876c5e0d0c511
Author: Mathieu Bultel <email address hidden>
Date: Tue Nov 28 19:44:47 2017 +0100

    Catch zaqar exception when no message to claim

    On minor update, when the execution is still running
    but there is no claim message anymore, we should
    capture the zaqar exception to not print it to the
    console

    Change-Id: I802ffd553c54e4a4f9998420645aa078f508b9f0
    Closes-Bug: #1734957

Changed in tripleo:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to python-tripleoclient (stable/pike)

Fix proposed to branch: stable/pike
Review: https://review.openstack.org/524128

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to python-tripleoclient (stable/pike)

Reviewed: https://review.openstack.org/524128
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=6bde4603fc0c1edfc70c1ae01353cec44b527ce9
Submitter: Zuul
Branch: stable/pike

commit 6bde4603fc0c1edfc70c1ae01353cec44b527ce9
Author: Mathieu Bultel <email address hidden>
Date: Tue Nov 28 19:44:47 2017 +0100

    Catch zaqar exception when no message to claim

    On minor update, when the execution is still running
    but there is no claim message anymore, we should
    capture the zaqar exception to not print it to the
    console

    Change-Id: I802ffd553c54e4a4f9998420645aa078f508b9f0
    Closes-Bug: #1734957
    (cherry picked from commit c102747c8d8ec175831c2c35f83876c5e0d0c511)

tags: added: in-stable-pike
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/python-tripleoclient 8.1.0

This issue was fixed in the openstack/python-tripleoclient 8.1.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/python-tripleoclient 7.3.6

This issue was fixed in the openstack/python-tripleoclient 7.3.6 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.