Bug 1774364 - RHVH 4.1 cannot register to RHVM 4.3.7 and displays the error message "Failed to execute Ansible host-deploy role"
Summary: RHVH 4.1 cannot register to RHVM 4.3.7 and displays the error message "Failed...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: redhat-virtualization-host
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Yuval Turgeman
QA Contact: peyu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-20 06:51 UTC by peyu
Modified: 2019-11-20 10:00 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-20 09:52:53 UTC
oVirt Team: Node
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description peyu 2019-11-20 06:51:19 UTC 
Created attachment 1638019 [details]
/var/log/ovirt-engine/host-deploy

Description of problem:
RHVH 4.1 failed to register to RHVM 4.3.7, the error message is as follows:
Failed to execute Ansible host-deploy role. 


Version-Release number of selected component (if applicable):
1. rhvh-4.1-0.20180425.0
2. RHVM 4.3.7.2-0.1.el7

How reproducible:
100%

Steps to Reproduce:
1. Install RHVH-4.1-20180426.0-RHVH-x86_64-dvd1.iso and reboot
2. Log in to RHVM 4.3.7 from "Administrator Portal"
3. Add "Data Centers" and "Clusters" with "Compatibility Version" as 4.1, set cluster's "CPU Type" to "Intel Conroe Family"
4. Add rhvh-4.1-0.20180425.0 to RHVM cluster
5. Check host status from RHVM

Actual results:
Register RHVH 4.1 to RHVM 4.3.7 failed with a message: 
Host peyu-1120-01 installation failed. Failed to execute Ansible host-deploy role. Please check logs for more details: /var/log/ovirt-engine/host-deploy/ovirt-host-deploy-ansible-20191119215650-10.73.130.225-757a6009.log

Expected results:
RHVH 4.1 can register to RHVM 4.3.7

Additional info:
Comment 1 Qin Yuan 2019-11-20 07:11:17 UTC 
peyu, the log says "VDSM version 4.19.51 is not supported for FirewallD.", how about changing the firewall type of cluster to iptables?
Note You need to log in before you can comment on or make changes to this bug.