Bug 44886 - Change "Start" button in the grid to "Pause" for running VMs
Change "Start" button in the grid to "Pause" for running VMs
Status: CLOSED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC - Virtual machines (UVMM)
UCS 4.2
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: UMC maintainers
UMC maintainers
:
: 25732 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-28 22:37 CEST by Michael Grandjean
Modified: 2023-06-28 10:51 CEST (History)
3 users (show)

See Also:
What kind of report is it?: Feature Request
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): External feedback
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Grandjean univentionstaff 2017-06-28 22:37:57 CEST
Feature Request during technical training:

When starting a VM via the "Play" (Start) button in the grid, this button disappears (and a "Monitor" (View) button to start a VNC connection appears right next to it).
The attendees expected that the "Play" button would change to a "Pause" button.

Although I agree that this would be expected behaviour, I am not sure which action a "Pause" button should actually take. Should it really pause the VM or better suspend or shutdown or even poweroff?
A short survey with the attendees showed a majority for pause.
Comment 1 Philipp Hahn univentionstaff 2017-07-27 16:32:22 CEST
*** Bug 25732 has been marked as a duplicate of this bug. ***
Comment 2 Philipp Hahn univentionstaff 2018-10-26 14:01:32 CEST
The functionality to show buttons was not ported to UCS-3 and got dropped with git:fc437c958e9786e6d00674192d166436b1449da6.

We don't show any pause/stop button as there are too many cases:
- just pause the VM (just does not get CPU time anymore but stays in RAM)
- graceful shutdown (notify the guest to shut down)
- forced shutdown (pull the plug and loose all runtime state)
- remove (throw away everything including the persistent data like HD)
Because of that we only show those actions in the context menu.
Comment 3 Ingo Steuwer univentionstaff 2020-07-03 20:55:02 CEST
This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.