tripleo

  1. Bug #1757372
  2. Comment #27

Comment 27 for bug 1757372

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

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

commit b1be9bf25b45932372a9acc699d187a703fbb2b2
Author: Dougal Matthews <email address hidden>
Date: Mon Jun 18 16:30:50 2018 +0100

    Use the standard messaging in the support workbook

    Update the support workbook to use the standard message sending
    workflow. This workflow reduces the boilerplate that is copied between
    workflows by defining the message structure, providing the retry logic
    and ensuring the task on a "FAILED" message.

    The workflow also offers optional persistence in Swift. If the plan name
    is given to the workflow it will store the messages in a Swift container
    named <plan_name>-messages.

    Change-Id: I9f914489630b9de59ffa819093b8b54e135877e8
    Related-Bug: #1757372