Description of problem: ConfigureChildDialog is a method and state in the service state machine. It was created to be used as an example of how you could pass dialog information to a task. The ConfigureChildDialog service state relationship has always been commented out. The method is outdated and should be removed and the state entry should be cleared. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
https://github.com/ManageIQ/manageiq/pull/8757
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/9d7b45cdfdb3b23dcfff20173a71480359fe5e29 commit 9d7b45cdfdb3b23dcfff20173a71480359fe5e29 Author: william fitzgerald <wfitzger> AuthorDate: Tue May 17 09:51:49 2016 -0400 Commit: william fitzgerald <wfitzger> CommitDate: Tue May 17 12:56:23 2016 -0400 Automate | Services | Remove ConfigureChildDialog method and state value. https://bugzilla.redhat.com/show_bug.cgi?id=1333874 Removed instance, method and value in schema for ConfigureChildDialog in Service/Provisioning/StateMachines/Methods.class. .../__methods__/configurechilddialog.rb | 55 ---------------------- .../Methods.class/configurechilddialog.yaml | 12 ----- .../ServiceProvision_Template.class/__class__.yaml | 2 +- 3 files changed, 1 insertion(+), 68 deletions(-) delete mode 100644 db/fixtures/ae_datastore/ManageIQ/Service/Provisioning/StateMachines/Methods.class/__methods__/configurechilddialog.rb delete mode 100644 db/fixtures/ae_datastore/ManageIQ/Service/Provisioning/StateMachines/Methods.class/configurechilddialog.yaml
Milan, I have a followup PR to remove the configurechilddialog.yaml. https://github.com/ManageIQ/manageiq/pull/9080/files is being reviewed. Bill
Marking this bug as verified. Although the PR Bill mentioned has not made it to to 5.6.0.11-rc2.2 yet. I noticed that the Openshift Installer in the RedHat domain uses this method, I will file a bug against that.
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