Description of problem: I am trying to run a check-upgrade of a host from the ovirt engine. But it fails with the following error: [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (EE-ManagedThreadFactory-commandCoordinator-Thread-2) [b11be6f6-bbff-43d4-bfaa-7dd189501953] Executing Ansible command: ANSIBLE_STDOUT_CALLBACK=hostupgradeplugin /usr/bin/ansible-playbook --ssh-common-args=-F /var/lib/ovirt-engine/.ssh/config --check --private-key=/etc/pki/ovirt-engine/keys/engine_id_rsa --inventory=/tmp/ansible-inventory3865657362649992600 /usr/share/ovirt-engine/playbooks/ovirt-host-upgrade.yml [Logfile: null] 2019-05-29 15:13:49,014+02 INFO [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (EE-ManagedThreadFactory-commandCoordinator-Thread-2) [b11be6f6-bbff-43d4-bfaa-7dd189501953] Ansible playbook command has exited with value: 4 2019-05-29 15:13:49,014+02 ERROR [org.ovirt.engine.core.bll.host.HostUpgradeManager] (EE-ManagedThreadFactory-commandCoordinator-Thread-2) [b11be6f6-bbff-43d4-bfaa-7dd189501953] Failed to run check-update of host 'host_1'. Error: fatal: [host_1]: FAILED! => {"changed": false, "msg": "Failed to connect to the host via ssh: ssh: connect to host host_1 port 22: Network is unreachable", "unreachable": true} Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Click on check-upgrade Actual results: Failed Expected results: check-upgrade complete successfully Additional info: I am using a custom ssh port
Verified on ovirt-engine-4.3.6.1-0.1.el7.noarch With a host using a non standard ssh port.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Roni, isn't this bug a real regression?
Yes its a regression, I will add the Regression keyword
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Verified on ovirt-engine-4.3.6.5-0.1.el7.noarch Even with IPv6 address and random ssh port this works correctly now.
This bugzilla is included in oVirt 4.3.6 release, published on September 26th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.6 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.