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

Bug 1959273

Summary: Add the option to pause Hosted-Engine deployment before running engine-setup
Product: [oVirt] ovirt-ansible-collection Reporter: Asaf Rachmani <arachman>
Component: hosted-engine-setupAssignee: Asaf Rachmani <arachman>
Status: CLOSED CURRENTRELEASE QA Contact: Nikolai Sednev <nsednev>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.4.2CC: bugs, sbonazzo
Target Milestone: ovirt-4.4.7Keywords: FutureFeature, Triaged, ZStream
Target Release: 1.5.0Flags: sbonazzo: ovirt-4.4+
sbonazzo: planning_ack?
sbonazzo: devel_ack+
sbonazzo: testing_ack?
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-ansible-collection-1.5.0 Doc Type: Enhancement
Doc Text:
Feature: Allow to pause Hosted-Engine deployment before running engine-setup Reason: This allows to make changes in the bootstrap VM Result: Changes can be made on the Hosted-Engine VM during the deployment and before engine-setup
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-07-06 07:27:57 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: 1960188    

Description Asaf Rachmani 2021-05-11 07:08:03 UTC
Add the option to pause Hosted-Engine deployment before running engine-setup in order to make changes in the bootstrap engine VM.

Comment 1 RHEL Program Management 2021-05-11 07:08:05 UTC
The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.

Comment 2 Sandro Bonazzola 2021-05-12 06:33:03 UTC
Please also open documentation bug for updating relevant docs where this new feature may be used.

Comment 3 Asaf Rachmani 2021-05-13 09:41:30 UTC
Documentation bug - bug 1960188

Comment 4 Nikolai Sednev 2021-06-15 09:37:11 UTC
Deployment stops as follows:

alma03 ~]# hosted-engine --deploy --ansible-extra-vars=he_pause_before_engine_setup=true
[ INFO  ] You can now connect from this host to the bootstrap engine VM using ssh as root and the temporary IP address - 192.168.222.167
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : include_tasks]
[ INFO  ] ok: [localhost]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Create temporary lock file]
[ INFO  ] changed: [localhost]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Pause execution until /tmp/ansible.6gdygzto_he_setup_lock is removed, delete it once ready to proceed]
alma03 ~]# rm -rf /tmp/ansible.6gdygzto_he_setup_lock

[ INFO  ] ok: [localhost]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : include_tasks]
[ INFO  ] skipping: [localhost]
[ INFO  ] TASK [redhat.rhv.engine_setup : Perform pre-install checks]
[ INFO  ] ok: [localhost]
.
.
.
.
.

Tested on:
ovirt-hosted-engine-setup-2.5.1-1.el8ev.noarch
ovirt-hosted-engine-ha-2.4.7-1.el8ev.noarch
Linux 4.18.0-305.6.1.el8_4.x86_64 #1 SMP Mon Jun 7 10:18:09 EDT 2021 x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux release 8.4 (Ootpa)

On engine OS coming with the rhvm-appliance-4.4-20210527.0.el8ev.x86_64 I saw that engine-setup was not yet executed as expected:
ovirt-engine-setup-4.4.6.8-0.1.el8ev.noarch
nsednev-he-1 ~]# ll -lsha /var/log/ovirt-engine/setup/
total 0
0 drwx------.  2 root  root    6 May 13 22:52 .
0 drwx------. 12 ovirt ovirt 205 Jun 15 12:26 ..
[root@nsednev-he-1 ~]# systemctl status ovirt-engine
● ovirt-engine.service - oVirt Engine
   Loaded: loaded (/usr/lib/systemd/system/ovirt-engine.service; disabled; vendor preset: disabled)
   Active: inactive (dead)
[root@nsednev-he-1 ~]# 

Moving to verified.

Comment 5 Sandro Bonazzola 2021-07-06 07:27:57 UTC
This bugzilla is included in oVirt 4.4.7 release, published on July 6th 2021.

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