Hi Dan,

Sorry if I was unclear but I was not asking for help to debug the issue
but rather alerting people that there is an issue which we are aware of
and are working to fix.

I think that this confusion has showed me that perhaps we should have a
message template for infrastructure related issues which I will create :)

Again, Sorry for any confusion this might have caused.

Dafna



On 11/02/2017 03:49 PM, Eyal Edri wrote:
> It looks like its related to KubeVirt jobs running Vagrant on the same
> hosts, we're working on a better cleanup for it. 
>
> On Thu, Nov 2, 2017 at 5:46 PM, Dan Kenigsberg <[email protected]
> <mailto:[email protected]>> wrote:
>
>     Dafna, I suspect the answers to my questions lie somewhere in the
>     logs, but may I ask you to do some of the foot work?
>     Which libvirt is this? On your Jenkins slave? or in the lago
>     virtual host?
>     What calls libvirt and sees this error? Who tries to create the
>     virbr2 network?
>
>     It smells like a lago/ost problem, not an ovirt one.
>
>
>     On Thu, Nov 2, 2017 at 5:39 PM, Dafna Ron <[email protected]
>     <mailto:[email protected]>> wrote:
>
>         Hi,
>
>         We have an ongoing issue with some builds failing due to
>         failure to clean network from libvirt.
>
>         the error is:
>
>         libvirtError: internal error: Network is already in use by
>         interface virbr2
>
>         we are working to fix the issue and will update once it's resolved. 
>
>         Thanks, 
>         Dafna
>
>
>
>
>         -------- Forwarded Message --------
>         Subject:      [CQ]: 82219, 14 (ovirt-engine) failed "ovirt-master"
>         system tests, but isn't the failure root cause
>         Date:         Thu, 2 Nov 2017 14:55:41 +0000 (UTC)
>         From:         oVirt Jenkins <[email protected]>
>         <mailto:[email protected]>
>         To:   [email protected] <mailto:[email protected]>
>
>
>
>         A system test invoked by the "ovirt-master" change queue including 
> change
>         82219,14 (ovirt-engine) failed. However, this change seems not to be 
> the root
>         cause for this failure. Change 83472,4 (ovirt-engine) that this 
> change depends
>         on or is based on, was detected as the cause of the testing failures.
>
>         This change had been removed from the testing queue. Artifacts built 
> from this
>         change will not be released until either change 83472,4 
> (ovirt-engine) is fixed
>         and this change is updated to refer to or rebased on the fixed 
> version, or this
>         change is modified to no longer depend on it.
>
>         For further details about the change see:
>         https://gerrit.ovirt.org/#/c/82219/14
>         <https://gerrit.ovirt.org/#/c/82219/14>
>
>         For further details about the change that seems to be the root cause 
> behind the
>         testing failures see:
>         https://gerrit.ovirt.org/#/c/83472/4
>         <https://gerrit.ovirt.org/#/c/83472/4>
>
>         For failed test results see:
>         http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3594/
>         <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3594/>
>         _______________________________________________
>         Infra mailing list
>         [email protected] <mailto:[email protected]>
>         http://lists.ovirt.org/mailman/listinfo/infra
>         <http://lists.ovirt.org/mailman/listinfo/infra>
>
>
>         _______________________________________________
>         Devel mailing list
>         [email protected] <mailto:[email protected]>
>         http://lists.ovirt.org/mailman/listinfo/devel
>         <http://lists.ovirt.org/mailman/listinfo/devel>
>
>
>
>
>
> -- 
>
> Eyal edri
>
>
> MANAGER
>
> RHV DevOps
>
> EMEA VIRTUALIZATION R&D
>
>
> Red Hat EMEA <https://www.redhat.com/>
>
> <https://red.ht/sig>  TRIED. TESTED. TRUSTED.
> <https://redhat.com/trusted>
>
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)


_______________________________________________
Devel mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/devel

Reply via email to