Dear Didi,

We had issues with this previously when the Bios Type and Emulation Machine chipsets are not compatible, mixing Q35 Bios Types with i440fx Emulation Machine Types for example. We fixed the defaults and adjusted the OST tests accordingly. Maybe something else changed that brought the issue back.

With Best Regards.

Steven.

On Sun, May 17, 2020 at 4:36 PM Yedidyah Bar David <didi@redhat.com> wrote:
On Fri, May 15, 2020 at 4:24 PM Artem Hrechanychenko
<ahrechan@redhat.com> wrote:
>
> Hi,
> I'm getting failure on ci check for my patch for network suite changes
> https://gerrit.ovirt.org/#/c/108317/
>
> CI failures
> https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/9350/
>
> My patch does not change the basic-suite master and local run passed locally. Does anybody know or get something similar ?

engine.log has:

https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/9350/artifact/check-patch.compat-4.3_suite_master.el7.x86_64/test_logs/compat-4.3-suite-master/post-004_basic_sanity_pytest.py/lago-compat-4-3-suite-master-engine/_var_log/ovirt-engine/

2020-05-15 08:38:25,062-04 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(ForkJoinPool-1-worker-23) [2e5b2649] EVENT_ID: VM_DOWN_ERROR(119), VM
vm2 is down with error. Exit message: XML error: Invalid PCI address
0000:02:01.0. slot must be <= 0.

Perhaps it's this, or a similar/related one (found simply by searching
for "Invalid PCI address"):

https://bugzilla.redhat.com/show_bug.cgi?id=1770697

Best regards,
--
Didi
_______________________________________________
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/M367YCTWZLTCTUTV745QCR6R4ON7RKHY/