On 4 Aug 2020, at 13:48, Michal Skrivanek <mskrivan@redhat.com> wrote:

On 4 Aug 2020, at 10:52, Yedidyah Bar David <didi@redhat.com> wrote:

On Tue, Aug 4, 2020 at 6:40 AM <jenkins@jenkins.phx.ovirt.org> wrote:

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/
Build: https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/1696/

This is failing for a few days now, all with the same error:

FAILED:  004_basic_sanity.hotplug_disk

Error Message:
False != True after 180 seconds
-------------------- >> begin captured logging << --------------------
lago.ssh: DEBUG: start task:cef1ecf3-76fd-4aad-a1fb-093eeda8193a:Get ssh client for lago-he-basic-suite-master-host-1:
lago.ssh: DEBUG: end task:cef1ecf3-76fd-4aad-a1fb-093eeda8193a:Get ssh client for lago-he-basic-suite-master-host-1:
lago.ssh: DEBUG: Running 833afb8a on lago-he-basic-suite-master-host-1: ping -4 -c 1 192.168.200.90
lago.ssh: DEBUG: Command 833afb8a on lago-he-basic-suite-master-host-1 returned with 1
lago.ssh: DEBUG: Command 833afb8a on lago-he-basic-suite-master-host-1 output:
PING 192.168.200.90 (192.168.200.90) 56(84) bytes of data.
From 192.168.200.3 icmp_seq=1 Destination Host Unreachable

This is after Michal pushed a patch to restore the removed function
(and related) get_vm0_ip_address, which failed build 1691.

I guess this patch was not enough - either the VM now gets a different
IP address, not 192.168.200.90, or its network is down, or whatever.

on 4.3 it shouldn’t
on master if the configuration is shared with basic-suite-master (which it is in case of -he-basic-suite-master) it implicitly starts using CirrOS as well. That means cloud init network conf doesn’t work and it doesn’t get IP .90 (it quite reliably gets .111 now but I wouldn’t suggest that either:)

Any idea?

yes, just replace it with hostname instead.

Thanks,
-- 
Didi