Bug 1349049
Summary: | User portal reports Internal error when taking a pool VM | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Roman Hodain <rhodain> | |
Component: | ovirt-engine | Assignee: | Shmuel Melamud <smelamud> | |
Status: | CLOSED ERRATA | QA Contact: | Israel Pinto <ipinto> | |
Severity: | urgent | Docs Contact: | ||
Priority: | urgent | |||
Version: | 3.6.6 | CC: | ahadas, bgraveno, gveitmic, hkim, lsurette, mgoldboi, michal.skrivanek, mkalinin, rbalakri, Rhev-m-bugs, sbonazzo, smelamud, srevivo, tnisan, ykaul | |
Target Milestone: | ovirt-4.0.1 | Keywords: | ZStream | |
Target Release: | 4.0.1 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: |
Previously, when the Manager tried to prestart a virtual machine from a virtual machine pool, it was possible that a user could try to run the same virtual machine at the same time. In this case, the User Portal displayed an 'Internal error' message. This issue was fixed and now it is not possible for a user to run the same virtual machine that is being prestarted by the Manager.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1350403 (view as bug list) | Environment: | ||
Last Closed: | 2016-08-23 20:43:32 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: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1350403 |
Description
Roman Hodain
2016-06-22 15:24:24 UTC
In order to be included in 4.0.1 a patch has to be posted and merged on 4.0.1 branch as well, please either post the patch or move to 4.0.2 and MODIFIED Verified on version: 4.0.2.6-0.1.el7ev Verified steps: 1)Create VM pool with 3 prestart VMs 2)In the user portal-> try to run one of the VMs before the Engine try - succeeded 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-1743.html |