Description of problem: If a catalog item is created with a Retirement entry point as per the Lifecycle and Automation Guide, the default retirement entry point is still invoked. Version-Release number of selected component (if applicable): all releases How reproducible: 100% Steps to Reproduce: 1.Create a catalog item and configure a Retirement Entry Point named anything but Default (/Service/Retirement/StateMachines/ServiceRetirement/custom_instance) 2.Retire the Service Actual results: the /Service/Retirement/StateMachines/ServiceRetirement/Default is invoked regardless of the value in the Retirement Entry Point of the Catalog Expected results: The Retirement Entry Point that was entered when the catalog was created (/Service/Retirement/StateMachines/ServiceRetirement/custom_instance) should be invoked. Additional info: You are able to copy and override the Default Instance and make changes to it, which will be executed, but if the instance is named anything but Default, the Default instance will be invoked.
New commit detected on manageiq/master: https://github.com/ManageIQ/manageiq/commit/28418f8a64a8fd69c4cb6a54ebaf92f4c210796e commit 28418f8a64a8fd69c4cb6a54ebaf92f4c210796e Author: Madhu Kanoor <mkanoor> AuthorDate: Tue Mar 10 11:13:31 2015 -0400 Commit: Madhu Kanoor <mkanoor> CommitDate: Wed Mar 11 12:15:24 2015 -0400 Service Retirement Entry Point https://bugzilla.redhat.com/show_bug.cgi?id=1192039 Allows for customers to change the Automate state machine that gets called during Service Retirment. If one is not specified we default to /Service/Retirement/StateMachines/ServiceRetirement/Default .../__methods__/get_retirement_entrypoint.rb | 22 ++++++++-------------- .../System/Event.class/request_service_retire.yaml | 4 +++- 2 files changed, 11 insertions(+), 15 deletions(-)
Dave, The retirement model is different between 5.4 and 5.3 so it won't be a straight cherry pick, we would have to make a specific patch for 5.3 if its needed. Please let me know if this needs to be fixed in 5.3? Thanks, Madhu
retirement_entrypoint: /Default/Service/Retirement/StateMachines/ServiceRetirement/custome_instance is executed . Verified in 5.4.0.0.19.20150410165622_ad23806
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://rhn.redhat.com/errata/RHBA-2015-1100.html