Univention Bugzilla – Full Text Bug Listing |
Summary: | Wrong state handling: PAUSED, VNC | ||
---|---|---|---|
Product: | UCS | Reporter: | Philipp Hahn <hahn> |
Component: | UMC - Virtual machines (UVMM) | Assignee: | Philipp Hahn <hahn> |
Status: | CLOSED FIXED | QA Contact: | Erik Damrose <damrose> |
Severity: | normal | ||
Priority: | P5 | CC: | degroot, gohmann, jmm, wiesenthal |
Version: | UCS 3.2 | Flags: | hahn:
Patch_Available+
|
Target Milestone: | UCS 3.2-4-errata | ||
Hardware: | All | ||
OS: | Linux | ||
What kind of report is it?: | --- | 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): | ||
Max CVSS v3 score: | |||
Attachments: | Fix PAUSED handling |
*** Bug 19712 has been marked as a duplicate of this bug. *** Patch commited r51772 with two additional fixed: 4. paused VMs could not be shut-down 5. canStart() returned TRUE wile the host was unavailable. r51773: 2014-07-02-univention-virtual-machine-manager-daemon.yaml * Paused VMs are now handled more similar to running VMs, which allows, for exmaple, VNC to be used for paused VMs, too. Package: univention-virtual-machine-manager-daemon Version: 3.0.17-12.498.201407141047 Branch: ucs_3.2-0 Scope: errata3.2-2 For QA: # virsh start --paused $VM VNC is usable. VM can be shut-down. VM can be powered off. Clicking on "Start" does "virsh resume" the VM. Clicking on "Pause" again should "virsh suspend" the VM; VNC should still be usable. VMs on unavailable hosts should not be startable (but migrateable). (In reply to Philipp Hahn from comment #2) > Patch commited r51772 with two additional fixed: > 4. paused VMs could not be shut-down > 5. canStart() returned TRUE wile the host was unavailable. > > r51773: 2014-07-02-univention-virtual-machine-manager-daemon.yaml > * Paused VMs are now handled more similar to running VMs, which allows, for > exmaple, VNC to be used for paused VMs, too. OK > Package: univention-virtual-machine-manager-daemon > Version: 3.0.17-12.498.201407141047 > Branch: ucs_3.2-0 > Scope: errata3.2-2 OK > For QA: > # virsh start --paused $VM > VNC is usable. > VM can be shut-down. > VM can be powered off. > Clicking on "Start" does "virsh resume" the VM. > Clicking on "Pause" again should "virsh suspend" the VM; VNC should still be > usable. > > VMs on unavailable hosts should not be startable (but migrateable). OK => Verified Reverting... please check again for 3.2-3 Re-applied patch to UCS-3.2-3 branch - only the changelog was updated: r53113 | Bug #35107 UVMM: Fix paused VM handling Package: univention-virtual-machine-manager-daemon Version: 3.0.18-1.502.201408281207 Branch: ucs_3.2-0 Scope: errata3.2-3 r53114 | Bug #35107 UVMM: Fix paused VM handling ucs-3.2-3/doc/errata/staging/2014-08-28-univention-virtual-machine-manager-daemon.yaml Patch is already part of UCS-4.0-0; no additional patching needed. (In reply to Philipp Hahn from comment #5) > Re-applied patch to UCS-3.2-3 branch - only the changelog was updated: > r53113 | Bug #35107 UVMM: Fix paused VM handling > Package: univention-virtual-machine-manager-daemon > Version: 3.0.18-1.502.201408281207 > Branch: ucs_3.2-0 > Scope: errata3.2-3 OK: Patch reapplied, still working > r53114 | Bug #35107 UVMM: Fix paused VM handling > ucs-3.2-3/doc/errata/staging/2014-08-28-univention-virtual-machine-manager- > daemon.yaml OK > Patch is already part of UCS-4.0-0; no additional patching needed. OK => Verified |
Created attachment 5952 [details] Fix PAUSED handling PAUSED VMs should be handled as running VMs: They have everything to run, but don't get any CPU time assigned. The VNC button should be shown. Fix one mis-typed PAUSE. This change is required for debugging VM start issued.