I don't think IPv6 is the cause. When the engine checks for updates
there is a yum error shown in the debug logs as follows.
2017-02-01 10:38:39 INFO otopi.plugins.ovirt_host_mgmt.packages.update update.info:98 Yum:
Performing yum transaction rollback
2017-02-01 10:38:39 DEBUG otopi.context context._executeMethod:142 method exception
Traceback (most recent call last):
File "/tmp/ovirt-J9X39w5eHd/pythonlib/otopi/context.py", line 132, in
_executeMethod
method['method']()
File "/tmp/ovirt-J9X39w5eHd/otopi-plugins/ovirt-host-mgmt/packages/update.py",
line 110, in _packagesCheck
packages=self.environment[omgmt.PackagesEnv.PACKAGES],
File "/tmp/ovirt-J9X39w5eHd/pythonlib/otopi/miniyum.py", line 851, in install
**kwargs
File "/tmp/ovirt-J9X39w5eHd/pythonlib/otopi/miniyum.py", line 500, in _queue
package=package,
RuntimeError: Package ovirt-imageio-daemon cannot be found
I've searched for a repo that provides this package but it looks like
this package is part of oVirt 4.0 instead of 3.6 which is what we are using.
On 02/01/2017 12:18 PM, Nicolas Ecarnot wrote:
Hello Michael,
Last time we spoke about this issue, it was the fault of ipV6 that had
to be turn down (I let you search the relevant posts).
-----------------------------------------
cat /etc/sysctl.d/noipv6.conf
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
-----------------------------------------