tripleo

ansible-playbook action: messages can exceed max message size for zaqar queue

Bug #1737026 reported by James Slagle
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
James Slagle
tripleo queens-3

Bug Description

Messages posted back to a zaqar queue by the ansible-playbook action
could easily exceed the max message size for the queue. Instead of
posting a single message each time, break it up based on the max message
size and post a separate message for each.

James Slagle (james-slagle)
Changed in tripleo:
status: New → In Progress
importance: Undecided → High
assignee: nobody → James Slagle (james-slagle)
milestone: none → queens-3
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/526492

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-common (master)

Reviewed: https://review.openstack.org/526492
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=680050dcbe2127a40c7aea473cfa3dd8443daa70
Submitter: Zuul
Branch: master

commit 680050dcbe2127a40c7aea473cfa3dd8443daa70
Author: James Slagle <email address hidden>
Date: Thu Dec 7 14:47:22 2017 -0500

    Break up messages to avoid max message size

    Messages posted back to a zaqar queue by the ansible-playbook action
    could easily exceed the max message size for the queue. Instead of
    posting a single message each time, break it up based on the max message
    size and post a separate message for each.

    Change-Id: If51416120b690c28cff4e909799246c16cd96fc0
    Closes-Bug: #1737026

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

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

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

Other bug subscribers

Remote bug watches

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