Description of problem: VM Compliance: Error when trying to access Status/History screens Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Go to a VM summary screen and click on Compliance Status or Compliance History links 2. 3. Actual results: Screen stays on VM summary screen, seeing error in logs: [----] I, [2019-03-25T15:53:22.525519 #27557:5485698] INFO -- : Started POST "/vm_infra/show/2252?display=compliance_history" for ::1 at 2019-03-25 15:53:22 -0400 [----] I, [2019-03-25T15:53:22.572299 #27557:5485698] INFO -- : Processing by VmInfraController#show as JS [----] I, [2019-03-25T15:53:22.572450 #27557:5485698] INFO -- : Parameters: {"authenticity_token"=>"BguxLfm5F9eJvUE0+l4UVabU5OiXwu/LNoTrWXj91vc7p3XYQmSfC4aXmyh5/WjqFIrFPdUDlLlYa+vPRzXlXQ==", "display"=>"compliance_history", "id"=>"2252"} [----] F, [2019-03-25T15:53:22.592182 #27557:5485698] FATAL -- : Error caught: [ArgumentError] wrong number of arguments (given 5, expected 3..4) /home/hkataria/dev/manageiq-ui-classic/app/presenters/tree_builder_compliance_history.rb:9:in `initialize' /home/hkataria/dev/manageiq-ui-classic/app/controllers/vm_common.rb:232:in `new' /home/hkataria/dev/manageiq-ui-classic/app/controllers/vm_common.rb:232:in `show' /home/hkataria/.rvm/gems/ruby-2.4.4/gems/actionpack-5.0.7.2/lib/action_controller/metal/basic_implicit_render.rb:4:in `send_action' /home/hkataria/.rvm/gems/ruby-2.4.4/gems/actionpack-5.0.7.2/lib/abstract_controller/base.rb:188:in `process_action' /home/hkataria/.rvm/gems/ruby-2.4.4/gems/actionpack-5.0.7.2/lib/action_controller/metal/rendering.rb:30:in `process_action' /home/hkataria/.rvm/gems/ruby-2.4.4/gems/actionpack-5.0.7.2/lib/abstract_controller/callbacks.rb:20:in `block in process_action' /home/hkataria/.rvm/gems/ruby-2.4.4/gems/activesupport-5.0.7.2/lib/active_support/callbacks.rb:126:in `call' /home/hkataria Expected results: Compliance Status or History screens should load respectively Additional info:
Please assess the impact of this issue and update the severity accordingly. Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition. If it's something like a tracker bug where it doesn't matter, please set the severity to Low.
https://github.com/ManageIQ/manageiq-ui-classic/pull/5376
New commit detected on ManageIQ/manageiq-ui-classic/master: https://github.com/ManageIQ/manageiq-ui-classic/commit/9f1b233ab5288a5e50733e25ed490e22436f910d commit 9f1b233ab5288a5e50733e25ed490e22436f910d Author: Dávid Halász <dhalasz> AuthorDate: Tue Mar 26 05:53:56 2019 -0400 Commit: Dávid Halász <dhalasz> CommitDate: Tue Mar 26 05:53:56 2019 -0400 Fix missed argument change for compliance history tree Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1692537 app/controllers/vm_common.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Verified the navigation works in CFME 5.11.0.1.20190424210327_58b5dbd Steps of verification: 1) Add Infra provider with at least 1 VM 2) Create a VM compliance policy and profile 3) Apply profile to a VM 4) Check the compliance of the VM 5) Refresh page, so that the compliance is shown in the table 6) Click the "Compliance Status" and the "Compliance History" Both of these links lead to the "Compliance History" page. Are these pages meant to be different? The hover text for "Status" vs "History" suggests that the pages are distinct. Leaving this ON_QA until NEEDINFO is fulfilled.
Based on above discussion, marking this as verified and reopening BZ 1430279 so that we can track the fix for these pages being distinct.
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