Bug 37201

Summary: UVMM blocks during operations
Product: UCS Reporter: Florian Best <best>
Component: UMC - Virtual machines (UVMM)Assignee: UMC maintainers <umc-maintainers>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P5 CC: damrose, gohmann, hahn
Version: UCS 4.2   
Target Milestone: ---   
Hardware: Other   
OS: Linux   
See Also: https://forge.univention.org/bugzilla/show_bug.cgi?id=36380
https://forge.univention.org/bugzilla/show_bug.cgi?id=21717
What kind of report is it?: Bug Report What type of bug is this?: 2: Improvement: Would be a product improvement
Who will be affected by this bug?: 1: Will affect a very few installed domains How will those affected feel about the bug?: 3: A User would likely not purchase the product
User Pain: 0.034 Enterprise Customer affected?:
School Customer affected?: ISV affected?:
Waiting Support: Flags outvoted (downgraded) after PO Review:
Ticket number: Bug group (optional): Roadmap discussion (moved), Usability
Max CVSS v3 score:

Description Florian Best univentionstaff 2014-12-05 12:03:43 CET 
Currently UVMM blocks the user to do any other operations while another operation is running. I want e.g. while I start some VM's open some others in VNC but I have to wait for all instances to be started. This takes most often very long (especially if there are broken VM's in that list).

An alternative would be to block only the actions for the VM's which executes already another action. The progressbar should not block the whole module. It could be shown above at a specific place.
Some root-server management interfaces do it this way.
Comment 1 Erik Damrose univentionstaff 2014-12-05 12:12:39 CET 
We should discuss what our goal is. Both stances are valid - make asynchronous requests, or block until the requested action is done. See #36380

We currently block in most cases so that an error can be shown as a direct result of the users previous action.
Comment 2 Ingo Steuwer univentionstaff 2020-07-03 20:54:50 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.