Description of problem: The state machine for Orchestration Retirement is using the old values: Version-Release number of selected component (if applicable): 5.10.1 How reproducible: 100% Steps to Reproduce: 1. Create an orchestration catalog item and retire the service. 2. Edit the automate retirement emails to change the from Id. 3. Change does not take affect. Actual results: In automation log <AEMethod stack_retirement_emails> [DEPRECATION] This method will be deprecated. Please use similarly named method from System/Notification/Email class. Expected results: Email sent with proper values : Invoking [builtin] method [/$/Object/send_email] with inputs [{"to"=>"xxxxxx", "from"=>"from", "subject"=>"Stack Retirement Alert for : billyheat3.", "body"=>"Hello,<br/><br/>Your Stack named : billyheat3 has been retired.<br/><br/> Thank you<br/> Signature Virtualization Infrastructure Team"}] Additional info:
https://github.com/ManageIQ/manageiq-content/pull/518
New commit detected on ManageIQ/manageiq-content/master: https://github.com/ManageIQ/manageiq-content/commit/43f78f9f604bda3e79695ece194b7e7d22f013ed commit 43f78f9f604bda3e79695ece194b7e7d22f013ed Author: william fitzgerald <wfitzger> AuthorDate: Tue Mar 19 16:59:01 2019 -0400 Commit: william fitzgerald <wfitzger> CommitDate: Tue Mar 19 16:59:01 2019 -0400 Fixed State machine for Orchestration Retirement using old values. Modified Cloud/Orchestration Retirement class schema values to use new email Instance. Modified Email instance CloudOrchestrationVmRetired. ${/#orchestration_stack_retire_task.miq_request.requester.email} || ${/Configuration/Email/Default#default_recipient} fixes https://bugzilla.redhat.com/show_bug.cgi?id=1690508 @miq-bot add_label bug content/automate/ManageIQ/Cloud/Orchestration/Retirement/StateMachines/StackRetirement.class/__class__.yaml | 2 +- content/automate/ManageIQ/System/Notification/Email.class/cloudorchestrationvmretired.yaml | 10 +- 2 files changed, 6 insertions(+), 6 deletions(-)
Verified in Version 5.11.0.4.20190514210444_0c91ee1
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/RHBA-2019:4199