Fedora Account System
Red Hat Associate
Red Hat Customer
Created attachment 1514075 [details] issue.png Description of problem: No cancel button in mentioned steps Version-Release number of selected component (if applicable): 5.9.6.5.20181130162459_7977a85 How reproducible: 100% Steps to Reproduce: 1. Add cloud provider first (Openstack OSP14 I used, I think it doesn't matter) 2. Navigate to Compute -> Cloud -> Tenants 3. Click on 'admin' from 'Cloud Tenants' table 4. Click on Images from 'Relationship' table 5. Click 2/3 images from 'All Images' table (all page) 6. From 'Policy' select 'Policy Simulation' No cancel button. Actual results: Cancel button is not there Expected results: Cancel button should be there Additional info:
https://github.com/ManageIQ/manageiq-ui-classic/pull/5341
New commit detected on ManageIQ/manageiq-ui-classic/master: https://github.com/ManageIQ/manageiq-ui-classic/commit/086bb64d69f5a9e36851fff0705691264a748793 commit 086bb64d69f5a9e36851fff0705691264a748793 Author: Hilda Stastna <hstastna> AuthorDate: Thu Mar 14 10:19:10 2019 -0400 Commit: Hilda Stastna <hstastna> CommitDate: Thu Mar 14 10:19:10 2019 -0400 Add Cancel button to policy simulation page Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1659088 Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1686617 Add the button to the page for policy simulation of vms/instances which were displayed as a nested list. app/controllers/application_controller/policy_support.rb | 6 + app/views/layouts/_policy_sim.html.haml | 12 + app/views/layouts/_x_edit_buttons.html.haml | 2 +- config/routes.rb | 1 + 4 files changed, 20 insertions(+), 1 deletion(-)
Verified in CFME 5.11.0.1.20190424210327_58b5dbd Steps of verification: 1. Go to Compute > Cloud > Providers 2. Choose some provider, click on it to display its dashboard or summary page 3. Click on VMs in the page from step 2 4. Check the checkbox(es) of some VM(s) 5. In the toolbar, choose Policy > Policy Simulation 6. Verified that the cancel button is present on this page.
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