Hide Forgot
In earlier RHEV and RHV versions, I could right-click a VM and select "power off." But in 4.2, I must select the VM, go to the General tab, click the dropdown next to the "Shutdown" button and click "Power off." The navigation is more complicated than earlier versions, presumably because we want to encourage orderly shutdowns and discourage virtual power cycling. But changing the navigation this way only complicates admins' jobs in stressful situations with hung VMs and used to the original navigation. Besides, if the popup shows both choices, shutdown VM and power off VM, it should be easy to tell which is which. Please add "Power off" to the right-click popup menu in the Compute...Virtual Machines screen.
Sure. I believe the change wasn’t really intentional
Thanks Michal. Should I take [RFE] out of the title?
(In reply to Michal Skrivanek from comment #1) > Sure. I believe the change wasn’t really intentional This change was actually intentional, fwiw. We wanted to simplify the menus such that if it's in the context menu, it's also up top. No thinking about where something should go. I'm fine changing that, though.
WARN: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Found non-acked flags: '{'rhevm-4.2.z': '?'}', ] For more info please contact: rhv-devops: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Found non-acked flags: '{'rhevm-4.2.z': '?'}', ] For more info please contact: rhv-devops
Verified on: ovirt-engine-4.3.0-0.0.master.20181014151735.git18593d9.el7.noarch
Verified again on: ovirt-engine-4.3.0-0.2.master.20181120211612.git51027b1.el7.noarch
WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{'rhevm-4.3-ga': '?'}', ] For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{'rhevm-4.3-ga': '?'}', ] For more info please contact: rhv-devops
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/RHEA-2019:1085