Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1220690 - New VM dialog should not show Memory Balloon Device Enabled when using template that has this disabled
New VM dialog should not show Memory Balloon Device Enabled when using templa...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine (Show other bugs)
3.6.0
All Linux
medium Severity medium
: ovirt-3.6.0-rc
: 3.6.0
Assigned To: Tomas Jelinek
Shira Maximov
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-05-12 04:30 EDT by Paul Dwyer
Modified: 2016-03-09 16:06 EST (History)
11 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, the resource allocation tab was not correctly handled for templates. This meant that when creating a virtual machine using a template in the GUI, the 'New Virtual Machine' window would display 'Memory Balloon Device Enabled' regardless of whether or not this was disabled in the template. Now, these template properties are handled properly and creating a virtual machine from a template in the GUI accurately reflects the configuration of the template properties.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-03-09 16:06:25 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Virt
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 41391 master MERGED frontend: fixes in resource allocation tab Never
Red Hat Product Errata RHEA-2016:0376 normal SHIPPED_LIVE Red Hat Enterprise Virtualization Manager 3.6.0 2016-03-09 20:20:52 EST

  None (edit)
Comment 3 Max Kovgan 2015-06-28 10:13:02 EDT
ovirt-3.6.0-3 release
Comment 6 errata-xmlrpc 2016-03-09 16:06:25 EST
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-0376.html

Note You need to log in before you can comment on or make changes to this bug.