Bug 37201 - UVMM blocks during operations
UVMM blocks during operations
Status: NEW
Product: UCS
Classification: Unclassified
Component: UMC - Virtual machines (UVMM)
UCS 4.2
Other Linux
: P5 normal (vote)
: ---
Assigned To: UMC maintainers
Depends on:
  Show dependency treegraph
Reported: 2014-12-05 12:03 CET by Florian Best
Modified: 2018-10-02 16:17 CEST (History)
3 users (show)

See Also:
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 after Product Owner Review:
Ticket number:
Bug group (optional): Roadmap discussion (moved), Usability
Max CVSS v3 score:


Note You need to log in before you can comment on or make changes to this bug.
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.