I am not sure since I have never opened a ticket for them.
I am adding Sandro, Barak and ovirt dev so that perhaps someone with more experience can offer a better advice.

On Thu, Sep 20, 2018 at 8:37 AM Miguel Duarte de Mora Barroso <mdbarroso@redhat.com> wrote:

On Thu, Sep 20, 2018 at 8:02 AM, Dominik Holler <dholler@redhat.com> wrote:
> On Wed, 19 Sep 2018 17:53:32 +0100
> Dafna Ron <dron@redhat.com> wrote:
>
>> it failed on build-artifacts:
>> http://pastebin.test.redhat.com/649015
>>
>
> Thanks, I did not find this error message.
>
>
> 13:03:03 [build-artifacts.fc27.x86_64] Failed to synchronize cache for repo 'mdbarroso-python-ovsdbapp', disabling.
> 13:03:03 [build-artifacts.fc27.x86_64] Last metadata expiration check: 0:00:00 ago on Wed Sep 19 13:01:34 2018.
> 13:03:03 [build-artifacts.fc27.x86_64] No match for argument: python2-ovsdbapp
> 13:03:03 [build-artifacts.fc27.x86_64] Error: Unable to find a match
>
> looks like
> https://copr-be.cloud.fedoraproject.org/
> is unstable.
> Miguel, do you expect that the reference to this repo is removed next
> days, or should we ask someone from copr-be.cloud.fedoraproject.org for
> help?

Hi Dafna,

I'm forced to agree that copr has been unstable for the past few days.

I'll contact the openstack release guys to get an update on the
deliver on the python2-ovsdbapp-0.12.1, but I think we should also
open the copr track.

Can you elaborate on what needs to be done Dafna? Just drop them an
email saying this repo fails every now and then?


>
>>
>> On Wed, Sep 19, 2018 at 5:09 PM Dominik Holler <dholler@redhat.com>
>> wrote:
>>
>> > Hi Marcin,
>> > the test looks like succeeded, but the return failed.
>> > Do you have an idea why?
>> > Dominik
>> >
>> >
>> > Begin forwarded message:
>> >
>> > Date: Wed, 19 Sep 2018 16:48:45 +0100
>> > From: Dafna Ron <dron@redhat.com>
>> > To: Dominik Holler <dholler@redhat.com>
>> > Subject: Fwd: [CQ]: 94345,3 (ovirt-provider-ovn) failed "ovirt-4.2"
>> > system tests
>> >
>> >
>> > hi, ?
>> >
>> > I am seeing that the check-merge job that failed is still broken. so
>> > guessing you guys are looking into it?
>> >
>> > Thanks,
>> > Dafna
>> >
>> >
>> > ---------- Forwarded message ---------
>> > From: oVirt Jenkins <jenkins@ovirt.org>
>> > Date: Wed, Sep 19, 2018 at 4:26 PM
>> > Subject: [CQ]: 94345,3 (ovirt-provider-ovn) failed "ovirt-4.2"
>> > system tests To: <infra@ovirt.org>
>> >
>> >
>> > Change 94345,3 (ovirt-provider-ovn) is probably the reason behind
>> > recent system
>> > test failures in the "ovirt-4.2" change queue and needs to be fixed.
>> >
>> > This change had been removed from the testing queue. Artifacts build
>> > from this
>> > change will not be released until it is fixed.
>> >
>> > For further details about the change see:
>> > https://gerrit.ovirt.org/#/c/94345/3
>> >
>> > For failed test results see:
>> > http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3150/
>> > _______________________________________________
>> > Infra mailing list -- infra@ovirt.org
>> > To unsubscribe send an email to infra-leave@ovirt.org
>> > Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> > oVirt Code of Conduct:
>> > https://www.ovirt.org/community/about/community-guidelines/
>> > List Archives:
>> >
>> > https://lists.ovirt.org/archives/list/infra@ovirt.org/message/VGTE6K3DMBCBMFP3XW5ZS2CVHJB3AP55/
>> >
>