Bug 1540123 - [HE] failed to deploy hosted engine with --noansible
Summary: [HE] failed to deploy hosted engine with --noansible
Keywords:
Status: CLOSED DUPLICATE of bug 1517881
Alias: None
Product: ovirt-hosted-engine-setup
Classification: oVirt
Component: General
Version: 2.2.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Simone Tiraboschi
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-30 10:15 UTC by Kobi Hakimi
Modified: 2018-01-31 21:10 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-01-30 10:55:10 UTC
oVirt Team: Infra
Embargoed:

Attachments (Terms of Use)
host logs (1.83 MB, application/x-gzip)
2018-01-30 10:15 UTC, Kobi Hakimi 		no flags Details
engine logs (360.85 KB, application/x-gzip)
2018-01-30 10:16 UTC, Kobi Hakimi 		no flags Details
answer file (3.34 KB, text/plain)
2018-01-30 10:16 UTC, Kobi Hakimi 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1517881 0 unspecified CLOSED Deployment of SHE stuck on the appliance. 2021-02-22 00:41:40 UTC

Internal Links: 1517881

Description Kobi Hakimi 2018-01-30 10:15:19 UTC 
Created attachment 1388250 [details]
host logs

Description of problem:
[HE] failed to deploy hosted engine with --noansible

Version-Release number of selected component (if applicable):
ovirt-hosted-engine-ha-2.2.4-1.el7ev.noarch
ovirt-hosted-engine-setup-2.2.8-2.el7ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. Install the latest appliance rhvm-appliance-4.2-20180125.0.el7.noarch
2. Run the following deploy command: 
hosted-engine --deploy --config-append=/etc/ansible-ovirt/answers --noansible

Actual results:
The deploy failed with timeout exception
...
          |- [ INFO  ] Stage: Misc configuration
[ ERROR ] Engine setup got stuck on the appliance
[ ERROR ] Failed to execute stage 'Closing up': Engine setup is stalled on the appliance since 3600 seconds ago.
         Please check its log on the appliance.

Expected results:
Deploy succeed

Additional info:
attached answer file and log files from host and engine VM.
 
When I and didi investigated this issue we notice the following:
 - One time the /etc/hosts contain the line:
192.168.122.152 hosted-engine-02.scl.lab.tlv.redhat.com
 - the engine vm is up and running but the ovirt-engine service is disabled there.
 - The server.log and engine.log do not exist.
Comment 1 Kobi Hakimi 2018-01-30 10:16:07 UTC 
Created attachment 1388251 [details]
engine logs
Comment 2 Kobi Hakimi 2018-01-30 10:16:40 UTC 
Created attachment 1388252 [details]
answer file
Comment 3 Simone Tiraboschi 2018-01-30 10:41:57 UTC 
engine-setup hangs here:
2018-01-29 11:48:41,056+0200 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'enable', u'firewalld.service') stderr:


2018-01-29 11:48:41,057+0200 DEBUG otopi.plugins.otopi.network.firewalld plugin.executeRaw:813 execute: ('/usr/bin/firewall-cmd', '--list-all-zones'), executable='None', cwd='None', env=None

could you please check your SELinux status?
Comment 4 Simone Tiraboschi 2018-01-30 10:55:10 UTC 
I see that you are passing a custom cloud-init image:

OVEHOSTED_VM/cloudInitISO=str:existing
OVEHOSTED_VM/vmCDRom=str:/etc/ansible-ovirt/cloud_init/cloud.iso

Kobi, could you please ensure that you are disabling SELinux when you execute engine-setup?

*** This bug has been marked as a duplicate of bug 1517881 ***
Comment 5 Kobi Hakimi 2018-01-31 21:10:02 UTC 
When I added in setenforce 0 before engine-setup its worked for me.

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