Bug 1051388

Summary: [RFE] Do not disable actions in VM context menu if multiple VMs are selected
Product: Red Hat Enterprise Virtualization Manager Reporter: Petr Spacek <pspacek>
Component: ovirt-engineAssignee: Tal Nisan <tnisan>
Status: CLOSED ERRATA QA Contact: Shira Maximov <mshira>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.2.0CC: amureini, gklein, iheim, istein, lsurette, mavital, michal.skrivanek, mrao, mshira, rbalakri, Rhev-m-bugs, sherold, tnisan, yeylon, ykaul
Target Milestone: ovirt-3.6.0-rcKeywords: FutureFeature
Target Release: 3.6.0Flags: sherold: Triaged+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-09 20:42:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1217446, 1218172, 1218527, 1218541, 1295728    
Bug Blocks: 1213937, 1241589    
Attachments:
Description Flags
webadmin-vm-context-menu.png none

Description Petr Spacek 2014-01-10 08:23:55 UTC
Created attachment 848095 [details]
webadmin-vm-context-menu.png

Please see attachment webadmin-vm-context-menu.png. It shows VM list where multiple VMs are selected, some of them are running and some of them are stopped.

In this case, the context menu does not allow to shutdown selected running VMs at once because the selection contains VMs which are not running. I have to select first set of running VMs, then click to shutdown and then repeat the same action for the other set of running VMs.

It would be more comfortable if the context menu allowed to issue Shutdown command even if the selected set contains VMs which are not running. Shutdown on s VM which is not running is basically no-op, right? This applies to Suspend/Poweroff/Console/Migrate.

The same applies in the other way - "Run" on the running machine is basically no-op, right? So Run/Run Once could work if the selected set contains stopped VMs mixed with running VMs.

Please let me know if it is not clear what I mean :-) Have a nice day!

Comment 2 Michal Skrivanek 2014-07-01 09:39:03 UTC
I think this is one of the few remaining basic issues in UI (the other being missing actions in VM subtab in host view)
should be easy for most of them, however people asked for mass edit VM before and that's quite more complicated. So let's not consider all of them

Then we still have 2 possibilities

1) introduce an "initial state" and apply only if it matches
  takes care of Powering up and other intermediate states which we would need to enumerate carefully if we consider "end state" instead
2) fire it into commands queue and let it fail asynchronously
  this is going to happen anyway for 1) when the state changes in the meantime, but here it will be much more

1) seems more user friendly, 2) might be easier to implement


The actions which should be simple enough:
Run, Suspend, Shutdown, Power Off, Reboot, Migrate, Cancel Migration

These probably make sense but have another selection dialog when clicked, would need some more work: Export, Assign Tags, Console Options
well, and then ultimately Edit VM
I'd leave these for another time as it may become too complex...

@Petr - note Console is already a "mass command"

Comment 3 Michal Skrivanek 2014-08-25 07:55:15 UTC
*** Bug 1012101 has been marked as a duplicate of this bug. ***

Comment 4 Scott Herold 2015-02-05 14:48:21 UTC
Let's target option 2 and target this item for a 3.6 hackathon

Comment 9 errata-xmlrpc 2016-03-09 20:42:10 UTC
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/RHEA-2016-0376.html