Description of problem: RHV doesn't support teaming devices, as stated in the following KCS and BZ: - https://access.redhat.com/solutions/2852031 - https://bugzilla.redhat.com/show_bug.cgi?id=1549300 But trying to deploy a hosted-engine bridging over a teaming device will attempt to proceed and fail with this error: [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The host has been set in non_operational status, please check engine logs, fix accordingly and re-deploy.\n"} Please consider extending the playbook for checking teaming devices on the Host, and rejecting the deployment with a clear error message. Version-Release number of selected component (if applicable): Tested with RHVH-4.2-20180627.1-RHVH-x86_64-dvd1.iso.
It seams an ansible bug: ansible doesn't really discriminate team interface from plain ones. https://github.com/ansible/ansible/issues/43129
re-targeting to 4.3.1 since this BZ has not been proposed as blocker for 4.3.0. If you think this bug should block 4.3.0 please re-target and set blocker flag.
Moving to 4.3.2 not being identified as blocker for 4.3.1.
Moving to 4.4.0
Closing low severity bugs, based on QE capacity, if you would like to still verify this issue please reopen.
Feature: Filter Team devices in Hosted-Engine deployment Reason: Teaming is not supported on RHV Result: Rejecting the deployment with a clear error message in case that only Team devices are available