Bug 1712278 - [OSP13 Backport] Message collection size is too large for Zaqar
Summary: [OSP13 Backport] Message collection size is too large for Zaqar
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-common
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
Target Milestone: z9
: 13.0 (Queens)
Assignee: Adriano Petrich
QA Contact: Alexander Chuzhoy
Depends On: 1664055
TreeView+ depends on / blocked
Reported: 2019-05-21 08:34 UTC by Adriano Petrich
Modified: 2020-03-27 01:45 UTC (History)
22 users (show)

Fixed In Version: python-tripleoclient-9.3.1-1.el7ost openstack-tripleo-common-8.7.1-1.el7ost
Doc Type: No Doc Update
Doc Text:
Clone Of: 1664055
Last Closed: 2019-11-07 14:01:17 UTC
Target Upstream Version:
apetrich: needinfo-

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
OpenStack gerrit 663688 None MERGED Remove execution from workflow message send 2020-04-08 04:10:19 UTC
OpenStack gerrit 680688 None MERGED Stop sending execution object via Zaqar message 2020-04-08 04:10:19 UTC
Red Hat Knowledge Base (Solution) 4396231 None None None 2019-09-06 02:31:06 UTC
Red Hat Product Errata RHBA-2019:3794 None None None 2019-11-07 14:01:36 UTC

Comment 2 Adriano Petrich 2019-09-11 08:36:35 UTC
Everything has been backported upstream

Comment 3 August Simonelli 2019-09-26 04:42:43 UTC
Hello. Is there a target milestone for this backport to land in OSP 13?

Comment 5 Adriano Petrich 2019-10-04 14:41:26 UTC
It depends on QE avaiability but besides that I don't see why not.

Comment 7 Alex McLeod 2019-10-31 11:28:56 UTC
If this bug requires doc text for errata release, please set the 'Doc Type' and provide draft text according to the template in the 'Doc Text' field. The documentation team will review, edit, and approve the text.

If this bug does not require doc text, please set the 'requires_doc_text' flag to -.

Comment 8 Jad Haj Yahya 2019-10-31 12:30:29 UTC
No regression issues found

Comment 10 errata-xmlrpc 2019-11-07 14:01:17 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Comment 11 Chris Smart 2020-03-24 23:28:38 UTC
I just hit this again, deploying z11 update at converge step.

queue_post failed: Error response from Zaqar. Code: 400. Title: Invalid API request. Description: Message collection size is too large. Max size 1048576.\\n\"}, \"result\": \"Failure caused by error in tasks: send_message\\n\\n  send_message [task_ex_id=2df6a3f6-0aa0-4b0f-9546-f8efb9c36d0b] -> Workflow failed due to message status\\n    [wf_ex_id=5ca8156c-cc5c-4e74-b057-7971cc773f71, idx=0]: Workflow failed due to message status\\n\", \"deployment_status\": \"DEPLOY_FAILED\"}", "input": "{\"run_validations\": false, \"skip_deploy_identifier\": false, \"container\": \"overcloud\", \"queue_name\": \"tripleo\", \"timeout\": 480}", "created_at": "2020-03-24 22:43:39", "project_id": "6829dc9650ef411ca67cd1654d5774df", "id": "6e069679-612c-4bab-a7c6-00a84651c322"}

Director is at z11 and has:


For now I'm applying my previous work around to increase the sizes even more and trying again.

Comment 12 Chris Smart 2020-03-27 01:45:52 UTC
Just to follow up, increasing the size further worked.

sudo crudini --set /etc/zaqar/zaqar.conf transport max_messages_post_size 2097152
sudo crudini --set /etc/zaqar/zaqar.conf oslo_messaging_kafka producer_batch_size 32768
sudo crudini --set /etc/mistral/mistral.conf engine execution_field_size_limit_kb 32768
sudo reboot

Note You need to log in before you can comment on or make changes to this bug.