zaqar max message size limit of 524288 is too small for plan management

[James Slagle]

While testing some of the custom roles patches that use jinja templating we are getting tracebacks from zaqar about the max message size when creating the defautl plan. This is happening in CI as well afaict, but we aren't getting logs since thejobs just eventually time out.

Example CI failure:
https://review.openstack.org/#/c/315679/

zaqar error from mistral-server.log in my local environment:
 ZaqarAction.queue_post failed: <class 'zaqarclient.transport.errors.MalformedRequest'>: Error response from Zaqar. Code: 400. Title: Invalid API request. Description: Message collection size is too large. Max size 524288.
] (execution_id=e36ebe4e-cce7-4ea6-be79-4ac64156fb62)

When this error occurs, the deployment just hangs the cli at:

Creating plan from template files in: tripleo-root/tripleo-heat-templates/

This is a separate issue that needs addressing (will file additional bug).

[James Slagle (james-slagle)]

raising the limit to 1M fixed the issue in my environment

[OpenStack Infra (hudson-openstack)]

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

[James Slagle (james-slagle)]

patch: https://review.openstack.org/368197

[James Slagle (james-slagle)]

the bug for the CLI hang is https://bugs.launchpad.net/tripleo/+bug/1621993

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/368197
Committed: https://git.openstack.org/cgit/openstack/instack-undercloud/commit/?id=80dbe734978baa5b16025de92cddf4793fb2b726
Submitter: Jenkins
Branch: master

commit 80dbe734978baa5b16025de92cddf4793fb2b726
Author: James Slagle <email address hidden>
Date: Fri Sep 9 15:40:29 2016 -0400

    Raise zaqar max message size

    We need to raise this limit again as we are exceeding the configured max
    message size when creating plans that use the jinja templating for
    custom roles.

    Change-Id: Ib76f028f06edf7dd44a4aadc7d3489b1c413cf57
    Closes-Bug: #1621991