Bug 1840756

Summary:	An endless loop occurs when using autoAcceptDefault=True
Product:	[oVirt] ovirt-setup-lib	Reporter:	Asaf Rachmani <arachman>
Component:	RFEs	Assignee:	Asaf Rachmani <arachman>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Nikolai Sednev <nsednev>
Severity:	medium	Docs Contact:
Priority:	high
Version:	1.3.0	CC:	bugs
Target Milestone:	ovirt-4.4.1	Keywords:	Triaged
Target Release:	1.3.1	Flags:	sbonazzo: ovirt-4.4? sbonazzo: planning_ack? sbonazzo: devel_ack+ sbonazzo: testing_ack?
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-hosted-engine-setup-2.4.5, ovirt-setup-lib-1.3.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-08 08:27:24 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:
Bug Depends On:
Bug Blocks:	1701526

Description Asaf Rachmani 2020-05-27 14:43:38 UTC

Description of problem:
When using DIALOG/autoAcceptDefault=bool:True in an answer file, the operation might get stuck in an endless loop that inflates log files

Version-Release number of selected component (if applicable):
python3-ovirt-setup-lib-1.3.0-1.el8.noarch

Comment 1 Nikolai Sednev 2020-06-24 09:21:32 UTC

Only ovirt-hosted-engine-setup-2.4.4-1.el8ev.noarch.rpm is available for QA at the moment.

Comment 2 Nikolai Sednev 2020-06-28 14:00:26 UTC

Works for me on these components:
ovirt-hosted-engine-setup-2.4.5-1.el8ev.noarch
ovirt-hosted-engine-ha-2.4.3-1.el8ev.noarch
python3-ovirt-setup-lib-1.3.1-1.el8ev.noarch
Linux 4.18.0-193.10.1.el8_2.x86_64 #1 SMP Fri Jun 19 15:31:45 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux release 8.2 (Ootpa)


2020-06-28 16:52:02,125+0300 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:107 fat
al: [localhost]: FAILED! => {"changed": false, "msg": "Memory size must be at least 4096MB, while you selected only 20
00MB"}
2020-06-28 16:52:02,326+0300 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:103 PLA
Y RECAP [localhost] : ok: 68 changed: 15 unreachable: 0 skipped: 31 failed: 1
2020-06-28 16:52:02,427+0300 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:215 ansible-playboo
k rc: 2
2020-06-28 16:52:02,427+0300 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:222 ansible-playboo
k stdout:
2020-06-28 16:52:02,427+0300 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:225 ansible-playboo
k stderr:
2020-06-28 16:52:02,428+0300 DEBUG otopi.context context._executeMethod:145 method exception
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in _executeMethod
    method['method']()
  File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-ansiblesetup/core/misc.py", line 395, in _closeu
p
    self.initial_clean_up(bootstrap_vars, inventory_source)
  File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-ansiblesetup/core/misc.py", line 437, in initial
_clean_up
    r = ah.run()
  File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_setup/ansible_utils.py", line 229, in run
    raise RuntimeError(_('Failed executing ansible-playbook'))
RuntimeError: Failed executing ansible-playbook
2020-06-28 16:52:02,430+0300 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Closing up': Fail
ed executing ansible-playbook

Forth to our conversation with Didi, I've set HE-VM's RAM size to 2000 to have an unacceptable ammount of RAM for the deployment, and to get system ask me about changing the RAM size, then I also added "DIALOG/autoAcceptDefault=bool:True" to the end of the answerfile, in order to answer the system that I want to continue with the low RAM size to check if it'll get in to the loop. System aborted after unsuccessful numerous attempts and didn't got in to endless loop as required.

Moving to verified.

Comment 3 Sandro Bonazzola 2020-07-08 08:27:24 UTC

This bugzilla is included in oVirt 4.4.1 release, published on July 8th 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.1 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.