it is ost_dc_version = os.environ.get('OST_DC_VERSION', None)
OST_DC_VERSION is 4.3 (it is parse from the name of suite script)
On Mon, May 18, 2020 at 5:31 PM Michal Skrivanek <
michal.skrivanek(a)redhat.com> wrote:
On 18 May 2020, at 11:59, Galit Rosenthal <grosenth(a)redhat.com> wrote:
This is from last night
https://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.3-suite-master/...
How does compat-4.3-suite-master work?
i.e. what is the actual engine and host version and which exact
002_bootstrap file is being used?
*2020-05-17 21:43:46,410-04 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(ForkJoinPool-1-worker-17) [1769ac4b] *
*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.
*
On Mon, May 18, 2020 at 11:21 AM Yedidyah Bar David <didi(a)redhat.com>
wrote:
> On Mon, May 18, 2020 at 10:47 AM Steven Rosenberg <srosenbe(a)redhat.com>
> wrote:
> >
> > 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.
> >
>
> OK. We do not have the logs anymore to check which version it ran.
> Artem - I suggest to just rebase and try again, and ping if it fails
> again.
>
> Good luck and best regards,
>
> > With Best Regards.
> >
> > Steven.
> >
> > On Sun, May 17, 2020 at 4:36 PM Yedidyah Bar David <didi(a)redhat.com>
> wrote:
> >>
> >> On Fri, May 15, 2020 at 4:24 PM Artem Hrechanychenko
> >> <ahrechan(a)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/935...
> >>
> >> 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(a)ovirt.org
> >> To unsubscribe send an email to devel-leave(a)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/M367YCTWZLT...
>
>
>
> --
> Didi
>
>
--
GALIT ROSENTHAL
SOFTWARE ENGINEER
Red Hat
<
https://www.redhat.com/>
galit(a)redhat.com T: 972-9-7692230
<
https://red.ht/sig>
_______________________________________________
Devel mailing list -- devel(a)ovirt.org
To unsubscribe send an email to devel-leave(a)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/4YR6KWH2BMW...