Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1662632

Summary: Missing the option to install hosted-engine without requirements check
Product: [oVirt] ovirt-hosted-engine-setup Reporter: Ido Rosenzwig <irosenzw>
Component: GeneralAssignee: Ido Rosenzwig <irosenzw>
Status: CLOSED CURRENTRELEASE QA Contact: Nikolai Sednev <nsednev>
Severity: high Docs Contact:
Priority: high    
Version: 2.3.0CC: bugs
Target Milestone: ovirt-4.3.0Keywords: Triaged
Target Release: ---Flags: rule-engine: ovirt-4.3+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-hosted-engine-setup-2.3.0 Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-13 07:43:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ido Rosenzwig 2018-12-31 07:45:37 UTC
Description of problem:

Hosted-engine setup new flow (with the ansible role) doesn't have the functionality 
to install without requirement check - e.g. check for a minimum memory size for the engine vm.

This option was enabled before for testing purposes and in the new transition to ansible was removed.

How reproducible:
100%

Steps to Reproduce:
1. Install hosted-engine with an answerfile
2. The answerfile should contain the following keys 

OVEHOSTED_CORE/checkRequirements=bool:False
OVEHOSTED_VM/vmMemSizeMB=int:3171

(OVEHOSTED_CORE/checkRequirements=bool:True is the default)
(OVEHOSTED_VM/vmMemSizeMB minimum requirement is 4096)

3. Run  # hosted-engine --deploy --config-append=answerfile.conf

Actual results:
The setup fails with : 
[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Memory size must be at least 4096MB, while you selected only 3171MB"}


Expected results:
Setup should succeed

Comment 1 Nikolai Sednev 2019-02-10 16:04:18 UTC
ovirt-ansible-repositories-1.1.4-2.el7ev.noarch
ovirt-ansible-engine-setup-1.1.7-1.el7ev.noarch
ansible-2.7.7-1.el7ae.noarch
ovirt-ansible-hosted-engine-setup-1.0.8-1.el7ev.noarch

Works for me just fine with answerfile parameters as were described above.
Moving to verified.

Comment 2 Sandro Bonazzola 2019-02-13 07:43:06 UTC
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.