Description of problem: ovirt-host package is removed on deployed hosts Version-Release number of selected component (if applicable): ovirt-engine-4.2.0-0.0.master.20170920172148.git8366a0b.el7.centos.noarch ovirt-host-deploy-1.7.0-0.0.master.20170912090102.git1eeb5a2.el7.centos.noarch How reproducible: tried only once Steps to Reproduce: Using CentOS minimal. 1. Install from http://resources.ovirt.org/pub/yum-repo/ovirt-release42-pre.rpm 2. Deploy an host 3. check if ovirt-host is installed Actual results: rpm -qv ovirt-host package ovirt-host is not installed Expected results: ovirt-host should be installed. Additional info: I installed the host withi a firewalld cluster. Manually installing ovirt-host: ================================================================================================================= Package Arch Version Repository Size ================================================================================================================= Installing: ovirt-host noarch 4.2.0-0.0.master.20170913090858.git0bfa7ab.el7.centos ovirt-4.2-pre 7.6 k Installing for dependencies: cockpit-ovirt-dashboard noarch 0.11.1-0.0.master.el7.centos ovirt-4.2-pre 3.3 M iptables-services x86_64 1.4.21-18.0.1.el7.centos base 51 k ovirt-hosted-engine-setup noarch 2.2.0-0.0.master.20170919052946.git896e399.el7.centos ovirt-4.2-pre 331 k Transaction Summary ================================================================================================================= Install 1 Package (+3 Dependent packages) I've the feeling this is caused by some ansible command in post-deploy phase. Note that this cause also not being able to deploy additional hosts for hosted engine on clusters with firewalld enabled.
# yum list ovirt-engine ovirt-engine.noarch 4.2.1.1-0.1.el7 @rhv-4.2x # yum list ovirt-host ovirt-host.x86_64 4.2.1-1.el7ev @rhv-4-mgmt-agentx Host added succesfully
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:1534
BZ<2>Jira Resync