Description of problem: By default, installing ovirt-hosted-engine-setup does not include the vdsm-gluster nor glusterfs-server packages, which are required to be installed separately Version-Release number of selected component (if applicable): Installing from the ovirt 3.5 yum repo. Installing: -ovirt-hosted-engine-setup-1.2.4-1.el6.noarch Attempting to install: -vdsm-gluster.noarch 0:4.16.20-0.el6 How reproducible: Multiple CentOS 6.6 servers Steps to Reproduce: 1. Reinstall/clean install a Centos 6.6 server 2. Install ovirt-release35.rpm to add ovirt repositories 3. Attempt to install ovirt-hosted-engine-setup, glusterfs-server, and vdsm-gluster Actual results: Resolving Dependencies --> Running transaction check ---> Package ovirt-hosted-engine-setup.noarch 0:1.2.4-1.el6 will be installed --> Processing Dependency: vdsm >= 4.16.16 for package: ovirt-hosted-engine-setup-1.2.4-1.el6.noarch --> Processing Dependency: ovirt-hosted-engine-ha >= 1.2.6 for package: ovirt-hosted-engine-setup-1.2.4-1.el6.noarch ---> Package vdsm-gluster.noarch 0:4.16.20-0.el6 will be installed --> Processing Dependency: vdsm = 4.16.20-0.el6 for package: vdsm-gluster-4.16.20-0.el6.noarch --> Processing Dependency: python-magic for package: vdsm-gluster-4.16.20-0.el6.noarch --> Running transaction check ---> Package ovirt-hosted-engine-ha.noarch 0:1.2.6-2.el6 will be installed ---> Package python-magic.x86_64 0:5.04-21.el6 will be installed ---> Package vdsm.x86_64 0:4.16.20-1.git3a90f62.el6 will be installed ---> Package vdsm-gluster.noarch 0:4.16.20-0.el6 will be installed --> Processing Dependency: vdsm = 4.16.20-0.el6 for package: vdsm-gluster-4.16.20-0.el6.noarch --> Finished Dependency Resolution Error: Package: vdsm-gluster-4.16.20-0.el6.noarch (ovirt-3.5) Requires: vdsm = 4.16.20-0.el6 Available: vdsm-4.16.7-1.gitdb83943.el6.x86_64 (ovirt-3.5) vdsm = 4.16.7-1.gitdb83943.el6 Available: vdsm-4.16.10-0.el6.x86_64 (ovirt-3.5) vdsm = 4.16.10-0.el6 Available: vdsm-4.16.10-8.gitc937927.el6.x86_64 (ovirt-3.5) vdsm = 4.16.10-8.gitc937927.el6 Available: vdsm-4.16.14-0.el6.x86_64 (ovirt-3.5) vdsm = 4.16.14-0.el6 Available: vdsm-4.16.20-0.el6.x86_64 (ovirt-3.5) vdsm = 4.16.20-0.el6 Installing: vdsm-4.16.20-1.git3a90f62.el6.x86_64 (epel) vdsm = 4.16.20-1.git3a90f62.el6 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Expected results: I would expect both of these packages to be installed properly. Additional info: This failure causes running `hosted-engine --deploy` to fail when installing the host as it also attempts to install the vdsm-gluster package.
Please either remove epel-release RPM or add: exclude=vdsm* in the epel.repo config file. Someone pushed vdsm to EPEL in contrast with EPEL policy and without gluster support with a release version newer than the one we ship in ovirt repo, breaking the dependency tree.
Please orphan VDSM in EPEL since it's violating EPEL policy.
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version. Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version. Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version, you are encouraged to change the 'version' to a later version prior this bug is closed as described in the policy above.
EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of EPEL please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.