New commit detected on ManageIQ/manageiq/euwe: https://github.com/ManageIQ/manageiq/commit/6075195a4d82e1163fa5062a10711a81a41a9852 commit 6075195a4d82e1163fa5062a10711a81a41a9852 Author: Martin Povolny <mpovolny> AuthorDate: Fri Nov 11 14:49:28 2016 +0100 Commit: Oleg Barenboim <chessbyte> CommitDate: Thu Nov 17 14:35:32 2016 -0500 Merge pull request #12577 from skateman/automate-tree-regression-fix Fixed regression in automate tree node selectability (cherry picked from commit 6eb346b2ce79af793427938ee0309fa3bb0b2e32) https://bugzilla.redhat.com/show_bug.cgi?id=1394848 app/controllers/application_controller.rb | 10 ++++---- app/presenters/tree_builder.rb | 4 ++-- app/presenters/tree_builder_ae_class.rb | 9 ------- app/presenters/tree_builder_automate.rb | 9 +++++++ app/presenters/tree_node_builder_ae_class.rb | 28 ---------------------- .../tree_node_builder_ae_class_catalog.rb | 11 --------- app/presenters/tree_node_builder_automate.rb | 28 ++++++++++++++++++++++ .../tree_node_builder_automate_catalog.rb | 11 +++++++++ spec/presenters/tree_builder_automate_spec.rb | 17 +++++++++++++ 9 files changed, 73 insertions(+), 54 deletions(-) delete mode 100644 app/presenters/tree_node_builder_ae_class.rb delete mode 100644 app/presenters/tree_node_builder_ae_class_catalog.rb create mode 100644 app/presenters/tree_node_builder_automate.rb create mode 100644 app/presenters/tree_node_builder_automate_catalog.rb create mode 100644 spec/presenters/tree_builder_automate_spec.rb
Hello David, Can you please tell me the exact verification steps as given Steps are confusing to me. Also attaching screenshot of catalog items. Thanks, Satyajit Bulage.
Created attachment 1224177 [details] Screenshot showing actual results
Hello Satyajit, the point is that if you have node in blue as in your screenshot Apply button has to be active. In your screenshot it looks like it works correctly. Let me know if you need more info :) Zita
"Apply" button is appearing when selecting only nodes. See attached screenshot in comment 4. Verified Version:- 5.7.0.12-rc2.20161123111642_a4a65ce
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-2017-0012.html