On Fri, Feb 10, 2017 at 12:56 PM, Arman Khalatyan <arm2arm(a)gmail.com> wrote:
After upgrade to ovirt 4.1 the epel has an conflicts in the collectd
part:
if you disable epel from the hosts it is ok.
the hosts are not able to check or update because of this:
017-02-10 11:51:17,056+01 INFO
[org.ovirt.engine.core.bll.scheduling.policyunits.EvenGuestDistributionBalancePolicyUnit]
(DefaultQuartzScheduler6) [a13d0a89-a1d4-495c-9ed4-5e30aae11ae8] There is no
host with more than 10 running guests, no balancing is needed
2017-02-10 11:51:17,069+01 WARN
[org.ovirt.engine.core.bll.scheduling.policyunits.CpuAndMemoryBalancingPolicyUnit]
(DefaultQuartzScheduler6) [a13d0a89-a1d4-495c-9ed4-5e30aae11ae8] All
candidate hosts have been filtered, can't balance the cluster 'clei' based
on the CPU usage, will try memory based approach
2017-02-10 11:51:17,099+01 INFO
[org.ovirt.engine.core.bll.scheduling.policyunits.PowerSavingBalancePolicyUnit]
(DefaultQuartzScheduler6) [a13d0a89-a1d4-495c-9ed4-5e30aae11ae8] Automatic
power management is disabled for cluster 'clei'.
2017-02-10 11:51:27,278+01 ERROR
[org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (VdsDeploy) [a9265eb]
Yum: [u'collectd-write_http-5.7.0-2.el7.x86_64 requires collectd(x86-64) =
5.7.0-2.el7', u'collectd-disk-5.7.0-2.el7.x86_64 requires collectd(x86-64) =
5.7.0-2.el7']
2017-02-10 11:51:27,278+01 INFO
[org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (VdsDeploy) [a9265eb]
Yum: Performing yum transaction rollback
2017-02-10 11:51:27,281+01 ERROR
[org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (VdsDeploy) [a9265eb]
Failed to execute stage 'Package installation':
[u'collectd-write_http-5.7.0-2.el7.x86_64 requires collectd(x86-64) =
5.7.0-2.el7', u'collectd-disk-5.7.0-2.el7.x86_64 requires collectd(x86-64) =
5.7.0-2.el7']
2017-02-10 11:51:27,281+01 INFO
[org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (VdsDeploy) [a9265eb]
Yum Performing yum transaction rollback
2017-02-10 11:51:27,378+01 INFO
[org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (VdsDeploy) [a9265eb]
Stage: Pre-termination
2017-02-10 11:51:27,400+01 INFO
[org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (VdsDeploy) [a9265eb]
Retrieving installation logs to:
'/var/log/ovirt-engine/host-deploy/ovirt-host-mgmt-20170210115127-clei36.cls-a9265eb.log'
2017-02-10 11:51:27,533+01 INFO
[org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (VdsDeploy) [a9265eb]
Stage: Termination
2017-02-10 11:51:27,708+01 ERROR
[org.ovirt.engine.core.uutils.ssh.SSHDialog] (pool-5-thread-3) [a9265eb] SSH
error running command root@clei36.cls:'umask 0077;
MYTMP="$(TMPDIR="${OVIRT_TMPDIR}" mktemp -d -t ovirt-XXXXXXXXXX)";
trap
"chmod -R u+rwX \"${MYTMP}\" > /dev/null 2>&1; rm -fr
\"${MYTMP}\" >
/dev/null 2>&1" 0; tar --warning=no-timestamp -C "${MYTMP}" -x
&&
"${MYTMP}"/ovirt-host-mgmt DIALOG/dialect=str:machine
DIALOG/customization=bool:True': Command returned failure code 1 during SSH
session 'root(a)clei36.cls'
2017-02-10 11:51:27,708+01 ERROR
[org.ovirt.engine.core.uutils.ssh.SSHDialog] (pool-5-thread-3) [a9265eb]
Exception: java.io.IOException: Command returned failure code 1 during SSH
session 'root(a)clei36.cls'
This is a known issue, mentioned in:
https://www.ovirt.org/release/4.1.0/
(search for EPEL).
Best,
--
Didi