Bug 1715435 - Failed to run check-update of host
Summary: Failed to run check-update of host
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: ovirt-host-deploy-ansible
Version: 4.3.3
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ovirt-4.3.6
: 4.3.6
Assignee: Ondra Machacek
QA Contact: Petr Matyáš
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-30 11:03 UTC by Noua Toukourou
Modified: 2019-09-26 19:43 UTC (History)
6 users (show)

Fixed In Version: ovirt-engine-4.3.6
Clone Of:
Environment:
Last Closed: 2019-09-26 19:43:13 UTC
oVirt Team: Infra
Embargoed:
pm-rhel: ovirt-4.3+
pm-rhel: blocker?


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 100498 0 master MERGED ansible: Use ssh port to connect 2021-02-02 14:07:09 UTC
oVirt gerrit 101739 0 ovirt-engine-4.3 MERGED ansible: Use ssh port to connect 2021-02-02 14:06:24 UTC
oVirt gerrit 102914 0 master MERGED ansible: Fix IPv6 address in Ansible deploy 2021-02-02 14:06:24 UTC
oVirt gerrit 103048 0 ovirt-engine-4.3 MERGED ansible: Fix IPv6 address in Ansible deploy 2021-02-02 14:06:24 UTC

Description Noua Toukourou 2019-05-30 11:03:17 UTC
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

Comment 1 Petr Matyáš 2019-08-09 11:09:10 UTC
Verified on ovirt-engine-4.3.6.1-0.1.el7.noarch

With a host using a non standard ssh port.

Comment 3 RHEL Program Management 2019-08-21 14:24:12 UTC
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.

Comment 5 Dominik Holler 2019-08-28 11:13:53 UTC
Roni, isn't this bug a real regression?

Comment 6 Roni 2019-08-28 11:21:30 UTC
Yes its a regression, I will add the Regression keyword

Comment 7 RHEL Program Management 2019-08-28 11:21:35 UTC
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.

Comment 10 Petr Matyáš 2019-09-06 12:18:49 UTC
Verified on ovirt-engine-4.3.6.5-0.1.el7.noarch

Even with IPv6 address and random ssh port this works correctly now.

Comment 11 Sandro Bonazzola 2019-09-26 19:43:13 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.