Bug 1578231 - Derive parameters: Incorrect plan name in send_message task
Summary: Derive parameters: Incorrect plan name in send_message task
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-common
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Upstream M3
: 14.0 (Rocky)
Assignee: Adriano Petrich
QA Contact: grozov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-15 05:28 UTC by Jaganathan Palanisamy
Modified: 2019-01-11 11:50 UTC (History)
5 users (show)

Fixed In Version: openstack-tripleo-common-9.1.1-0.20180710151736.8e8dabd.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-11 11:49:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1770089 0 None None None 2018-05-15 05:28:56 UTC
OpenStack gerrit 567130 0 None None None 2018-05-15 06:05:33 UTC
Red Hat Product Errata RHEA-2019:0045 0 None None None 2019-01-11 11:50:35 UTC

Description Jaganathan Palanisamy 2018-05-15 05:28:57 UTC 
Description of problem:

In derive parameters workflow, plan name is not correctly passed
to workflow 'tripleo.messaging.v1.send' in send_message task.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
plan name is not passed in send_message task.


Expected results:
Plan name needs to be passed in send_message task.


Additional info:
Comment 1 Jaganathan Palanisamy 2018-05-15 06:07:25 UTC 
Upstream patch is merged.
https://review.openstack.org/#/c/567130/
Comment 5 grozov 2018-10-23 08:39:49 UTC 
started the workflow with my plan and saw that the plan name is correctly passed
Comment 8 errata-xmlrpc 2019-01-11 11:49:53 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.

https://access.redhat.com/errata/RHEA-2019:0045
Note You need to log in before you can comment on or make changes to this bug.