Bug 1594008

Summary: Provisioning to RHV 4.1 Max Memory Size Needs to be Adjusted as Necesary
Product: Red Hat CloudForms Management Engine Reporter: Satoe Imaishi <simaishi>
Component: ProvisioningAssignee: Moti Asayag <masayag>
Status: CLOSED ERRATA QA Contact: Ilanit Stein <istein>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.7.0CC: cbudzilo, greartes, ikaur, jcutter, jhardy, masayag, mgoldboi, mperina, obarenbo, sacpatil, simaishi
Target Milestone: GAKeywords: ZStream
Target Release: 5.8.5   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: rhev
Fixed In Version: 5.8.5.0 Doc Type: If docs needed, set a value
Doc Text:
This update of CloudForms includes a VM Limit field, under the Hardware tab in the provisioning dialog. This feature is only supported when using ovirt-engine-sdk. With this update,the VM Limit field contains a default value of the template's maximum memory. Users can then adjust the value to their own specifcations.
Story Points: ---
Clone Of: 1461560 Environment:
Last Closed: 2018-09-26 18:36:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: RHEVM Target Upstream Version:
Embargoed:
Bug Depends On: 1461560    
Bug Blocks:    

Comment 4 Ilanit Stein 2018-09-05 08:44:48 UTC
Verified on: CFME-5.8.5/RHV-4.2.5.3-0.1.el7ev

As CFME-5.8 do not use ovirt-engine-sdk, need to enable it by:

1. Set: ':use_ovirt_engine_sdk: true' in /var/www/miq/vmdb/config/settings.yml.
2. Run: systemctl restart evmserverd

For a template with memory 2G, max memory 8G,
CFME VM provision, setting VM memory to 12G, and VM limit to 12G (or above),
succeeded.

Comment 6 errata-xmlrpc 2018-09-26 18:36:30 UTC
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://access.redhat.com/errata/RHSA-2018:2745