Message collection size is too large for Zaqar
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
In Progress
|
High
|
Adriano Petrich |
Bug Description
Description of problem:
I tried to deploy 3 controllers + 2 computes + 3 ceph with network isolation in a virtual test environment from the GUI (OSP14). My only configuration mistake was that I forgot to change the Ceph defaults which give too many pages and pools, so the deployment failed.
From the GUI, I clicked open the failure details dialog - but the workflow got stuck. We see this in the executor.log:
# /var/log/
ZaqarAction.
2019-01-07 09:37:29.806 1 ERROR mistral.
2019-01-07 09:37:29.806 1 ERROR mistral.
2019-01-07 09:37:29.806 1 ERROR mistral.
2019-01-07 09:37:29.806 1 ERROR mistral.
2019-01-07 09:37:29.806 1 ERROR mistral.
2019-01-07 09:37:29.806 1 ERROR mistral.
Version-Release number of selected component (if applicable):
openstack-
How reproducible:
unknown
Steps to Reproduce:
1. Deploy a setup as described above
Proposed solution:
In general, we can remove deprecated 'execution' item from zaqar message payload [1]. This item can potentially contain a lot of data.
Specifically for this bug, the "deployment_
[1] https:/
[2] https:/
python-
Changed in tripleo: | |
status: | Triaged → In Progress |
Changed in tripleo: | |
milestone: | none → stein-3 |
Changed in tripleo: | |
milestone: | stein-3 → stein-rc1 |
Changed in tripleo: | |
milestone: | stein-rc1 → train-1 |
Changed in tripleo: | |
milestone: | train-1 → train-2 |
Changed in tripleo: | |
milestone: | train-2 → train-3 |
Changed in tripleo: | |
milestone: | train-3 → ussuri-1 |
Changed in tripleo: | |
milestone: | ussuri-1 → ussuri-2 |
Changed in tripleo: | |
milestone: | ussuri-2 → ussuri-3 |
Changed in tripleo: | |
milestone: | ussuri-3 → ussuri-rc3 |
Changed in tripleo: | |
milestone: | ussuri-rc3 → victoria-1 |
Changed in tripleo: | |
milestone: | victoria-1 → victoria-3 |
Reviewed: https:/ /review. openstack. org/630970 /git.openstack. org/cgit/ openstack/ python- tripleoclient/ commit/ ?id=cad7916ce8d 21295992c2efe0e 18657c6e56604d
Committed: https:/
Submitter: Zuul
Branch: master
commit cad7916ce8d2129 5992c2efe0e1865 7c6e56604d
Author: apetrich <email address hidden>
Date: Tue Jan 15 14:16:00 2019 +0100
Remove execution from workflow message send
Serializing all the execution in a message can make the message too big.
This change was done in tripleo-common. this supports that change
This change still supports the old format and is backwards compatible.
Partial-Bug: #1812172 38f5ba1db58d171 f98be75d009
Change-Id: I40ee028366222f