[ovirt-devel] OST basic suite failing on el8 physical server

Hi all, I'm trying to run OST basic suite on CentOS 8 based physical server with lago running on py3. I'm currently stuck at 'verify_add_hosts' step. The engine continously tries to run: org.ovirt.engine.core.vdsbroker.vdsbroker.CollectVdsNetworkDataAfterInstallationVDSCommand but it ends up with a failure: 2020-02-18 05:29:01,386-05 DEBUG [org.ovirt.engine.core.dal.dbbroker.CustomSQLErrorCodeSQLExceptionTranslator] (EE-ManagedThreadFactory-engine-Thread-1) [39a236fd] Translating SQLException with SQL state '23505', error code '0', message [ERROR: duplicate key value violates unique constraint "name_server_pkey"   Detail: Key (dns_resolver_configuration_id, address)=(98794c52-8364-4909-bbaf-a7ac16a1bf2a, 192.168.201.1) already exists. Here's part of my lago prefix status:         [lago-basic-suite-master-host-0]:             [NICs]:                 [eth0]:                     ip: 192.168.200.3                     network: lago-basic-suite-master-net-management                 [eth1]:                     ip: 192.168.202.3                     network: lago-basic-suite-master-net-storage                 [eth2]:                     ip: 192.168.201.2                     network: lago-basic-suite-master-net-bonding                 [eth3]:                     ip: 192.168.201.3                     network: lago-basic-suite-master-net-bonding             distro: el8             [metadata]:                 deploy-scripts: $LAGO_PREFIX_PATH/scripts/_root_ovirt-system-tests_basic-suite-master_deploy-scripts_add_local_repo_no_ext_access.sh $LAGO_PREFIX_PATH/scripts/_root_ovirt-system-tests_basic-suite-master_deploy-scripts_setup_sar_stat.sh $LAGO_PREFIX_PATH/scripts/_root_ovirt-system-tests_basic-suite-master_deploy-scripts_setup_host_el7.sh $LAGO_PREFIX_PATH/scripts/_root_ovirt-system-tests_basic-suite-master_deploy-scripts_setup_1st_host_el7.sh             root password: 123456             status: running         [lago-basic-suite-master-host-1]:             [NICs]:                 [eth0]:                     ip: 192.168.200.4                     network: lago-basic-suite-master-net-management                 [eth1]:                     ip: 192.168.202.4                     network: lago-basic-suite-master-net-storage                 [eth2]:                     ip: 192.168.201.4                     network: lago-basic-suite-master-net-bonding                 [eth3]:                     ip: 192.168.201.5                     network: lago-basic-suite-master-net-bonding So it seems the two bonding NICs indeed share the same dns resolver address - 192.168.201.1, but I suppose that's how it looks for all basic suite runs, right? Does anyone know what could be wrong in this setup and why the engine is complaining? Thanks, Marcin