Description of problem: Incorrect Automate Message in 2 Profile Classes Version-Release number of selected component (if applicable): 5.5.5 How reproducible: 100% Steps to Reproduce: 1. Start Automate Explorer 2. Check the Message for the Automate Method Field get_dialog_name in the following classes 3. /ManageIQ/Cloud/VM/Provisioning/Profile /ManageIQ/Infrastructure/VM/Provisioning/Profile Actual results: Message is incorrectly set to get_state_machine Expected results: Message should be get_dialog_name Additional info:
https://github.com/ManageIQ/manageiq/pull/5519
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/99fe78b2147ce57a1a54d18de9f285afe5fa5e11 commit 99fe78b2147ce57a1a54d18de9f285afe5fa5e11 Author: Madhu Kanoor <mkanoor> AuthorDate: Thu Nov 19 11:52:17 2015 -0500 Commit: Madhu Kanoor <mkanoor> CommitDate: Thu Nov 19 11:52:17 2015 -0500 Fixed Automate Message in 2 classes https://bugzilla.redhat.com/show_bug.cgi?id=1283424 Incorrect message 'get_state_machine' should be 'get_dialog_name' .../ManageIQ/Cloud/VM/Provisioning/Profile.class/__class__.yaml | 2 +- .../Infrastructure/VM/Provisioning/Profile.class/__class__.yaml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
New commit detected on cfme/5.5.z: https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=ebf10bcd55f123b9ac62d81779beff306e6a53a7 commit ebf10bcd55f123b9ac62d81779beff306e6a53a7 Author: Madhu Kanoor <mkanoor> AuthorDate: Thu Nov 19 11:52:17 2015 -0500 Commit: Madhu Kanoor <mkanoor> CommitDate: Thu Dec 3 12:08:10 2015 -0500 Fixed Automate Message in 2 classes https://bugzilla.redhat.com/show_bug.cgi?id=1283424 Incorrect message 'get_state_machine' should be 'get_dialog_name' .../ManageIQ/Cloud/VM/Provisioning/Profile.class/__class__.yaml | 2 +- .../Infrastructure/VM/Provisioning/Profile.class/__class__.yaml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
Verified in 5.6.0.1-beta2
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-2016:1348