[ovirt-devel] Re: CI failing all the time

2021-11-28 Thread Nir Soffer 
On Sun, Nov 28, 2021 at 10:59 AM Nir Soffer  wrote:
>
> On Fri, Nov 26, 2021 at 12:57 PM Ehud Yonasi  wrote:
> >
> > Hi Nir,
> >
> > There was a problem in jenkins to switch to the new k8s stack on IBM cloud, 
> > a restart was required and now it’s solved.
>
> The queue is increasing again, currently 12 jobs in the queue:
>
> Build Queue (12)
> system-mk_mirrors_index-yum
> part of vdsm_standard-check-patch #31073 vdsm [check-patch]
> jenkins_master_check-patch-el7-ppc64le
> jenkins_master_check-patch-el7-ppc64le
> part of jenkins_standard-check-patch #5550
> part of jenkins_standard-check-patch #5548
> jenkins_master_check-patch-el7-ppc64le
> jenkins_master_check-patch-el7-ppc64le
> jenkins_master_check-patch-el7-ppc64le
> jenkins_master_check-patch-el7-ppc64le
> part of ovirt-appliance_standard-check-patch #385 ovirt-appliance
> [check-patch]
> lago-demo_master_github_timed-el7-x86_64

Queue size is 24 now

Build Queue (24)
ovirt-engine_standard-on-merge
ovirt-engine_standard-on-merge
standard-enqueue
standard-enqueue
ovirt-engine_standard-on-merge
standard-enqueue
ovirt-engine_standard-on-merge
standard-enqueue
part of ovirt-engine_standard-check-patch #15338
part of ovirt-engine_standard-check-patch #15337
part of ovirt-engine_standard-check-patch #15336
part of ovirt-engine_standard-check-patch #15335
jenkins_master_check-patch-el7-ppc64le
jenkins_master_check-patch-el7-ppc64le
part of jenkins_standard-check-patch #5550
part of jenkins_standard-check-patch #5548
jenkins_master_check-patch-el7-ppc64le
jenkins_master_check-patch-el7-ppc64le
jenkins_master_check-patch-el7-ppc64le
jenkins_master_check-patch-el7-ppc64le
part of ovirt-appliance_standard-check-patch #385 ovirt-appliance
[check-patch]
lago-demo_master_github_timed-el7-x86_64
part of ovirt-engine_standard-on-merge #2664
part of ovirt-engine_standard-check-patch #15334

>
>
> >
> >
> > On 25 Nov 2021, at 21:53, Nir Soffer  wrote:
> >
> > On Thu, Nov 25, 2021 at 9:15 PM Michal Skrivanek
> >  wrote:
> >
> >
> >
> >
> > On 25. 11. 2021, at 16:45, Evgheni Dereveanchin  wrote:
> >
> > Hi Milan,
> >
> > Indeed, this is related to the Jenkins move: all pre-existing nodes are no 
> > longer usable so new ones have been created.
> > We're looking into the reasons new nodes fail to initialize and bringing up 
> > new ones in parallel to help with processing the build queue.
> >
> > Sorry for the inconvenience. Please report any other issues if you see them 
> > as there may be quite some instability due to the rebuild.
> >
> >
> > Hi Evgheni,
> > the queue is now 53 builds long, and it seems nothing is building, perhaps 
> > there's no worker or the labelling is wrong?
> >
> >
> > Looks like jobs are stuck for several hours
> > https://jenkins.ovirt.org/job/vdsm_standard-check-patch/31036/
> >
> > at the "loading code" stage:
> > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/31036/pipeline
> >
> > With this error:
> >
> >There are no nodes with the label 
> > ‘jenkins-vdsm_standard-check-patch-31036’
> >
> > The label looks wrong. vdsm requires nodes with "el8" label.
> >
> >
> > Thanks,
> > michal
> >
> >
> > Regards.
> > Evgheni
> >
> > On Thu, Nov 25, 2021 at 4:24 PM Nir Soffer  wrote:
> >
> >
> > On Thu, Nov 25, 2021 at 3:48 PM Milan Zamazal  wrote:
> >
> >
> > Hi,
> >
> > all patches uploaded today I've seen (for Engine and Vdsm) fail due to
> > problems with availability of packages when preparing the el7
> > environment.  For example:
> > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/15291/
> >
> > Additionally, Vdsm tests are not run on PSI.
> >
> > Does anybody know what's wrong and how to fix it?  Can it be related to
> > the Jenkins move?
> >
> >
> > Looking at
> > https://jenkins.ovirt.org/
> >
> > There are 33 jobs in the queue, and only 3 jobs running.
> >
> > Maybe we did not restore all the nodes?
> >
> >
> > ___
> > Devel mailing list -- devel@ovirt.org
> > To unsubscribe send an email to devel-le...@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/ZLH3ILKHC3YPZWQFA2SG4GS3QSIALUXZ/
> >
> >
> > ___
> > Devel mailing list -- devel@ovirt.org
> > To unsubscribe send an email to devel-le...@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/RZ7H4L26DU6LAKFQXJE4W3D4C5HP76CX/
> >
> > ___
> > Devel mailing list -- devel@ovirt.org
> > To unsubscribe send an email to devel-le...@ovirt.org
> > Privacy Statement:

[ovirt-devel] Re: CI failing all the time

2021-11-28 Thread Yedidyah Bar David 
On Sun, Nov 28, 2021 at 11:49 AM Nir Soffer  wrote:
>
> On Sun, Nov 28, 2021 at 11:35 AM Nir Soffer  wrote:
> >
> > On Sun, Nov 28, 2021 at 10:59 AM Nir Soffer  wrote:
> > >
> > > On Fri, Nov 26, 2021 at 12:57 PM Ehud Yonasi  wrote:
> > > >
> > > > Hi Nir,
> > > >
> > > > There was a problem in jenkins to switch to the new k8s stack on IBM 
> > > > cloud, a restart was required and now it’s solved.
> > >
> > > The queue is increasing again, currently 12 jobs in the queue:
> >
> > Vdsm jobs requires el8 nodes, but we have only one:
> > https://jenkins.ovirt.org/label/el8/
> >
> > we also have only one el9stream node:
> > https://jenkins.ovirt.org/label/el9stream/
> >
> > I posted this to use all nodes in vdsm, instead of only the el8 nodes:
> > https://gerrit.ovirt.org/c/vdsm/+/117826
> >
> > It did not work in the old data center, but maybe the issue with  the 
> > el9stream
> > nodes is solved now.
>
> It does not work yet, el9stream fails quickly in global_setup.sh:
>
> [2021-11-28T09:35:20.829Z] + sudo -n systemctl start libvirtd haveged 
> firewalld
> [2021-11-28T09:35:21.086Z] Failed to start libvirtd.service: Unit
> libvirtd.service not found.
> [2021-11-28T09:35:21.086Z] Failed to start haveged.service: Unit
> haveged.service not found.
>
> See https://ovirt-jira.atlassian.net/browse/OVIRT-3126

+1, happens to me as well. Pushed a workaround disabling el9 for my case:

https://gerrit.ovirt.org/c/ovirt-hosted-engine-setup/+/117828

Best regards,
-- 
Didi
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@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/H7RLODBYSR3AAAI7DPSGWK5VYLTESGQ4/

[ovirt-devel] Re: CI failing all the time

2021-11-28 Thread Nir Soffer 
On Sun, Nov 28, 2021 at 11:35 AM Nir Soffer  wrote:
>
> On Sun, Nov 28, 2021 at 10:59 AM Nir Soffer  wrote:
> >
> > On Fri, Nov 26, 2021 at 12:57 PM Ehud Yonasi  wrote:
> > >
> > > Hi Nir,
> > >
> > > There was a problem in jenkins to switch to the new k8s stack on IBM 
> > > cloud, a restart was required and now it’s solved.
> >
> > The queue is increasing again, currently 12 jobs in the queue:
>
> Vdsm jobs requires el8 nodes, but we have only one:
> https://jenkins.ovirt.org/label/el8/
>
> we also have only one el9stream node:
> https://jenkins.ovirt.org/label/el9stream/
>
> I posted this to use all nodes in vdsm, instead of only the el8 nodes:
> https://gerrit.ovirt.org/c/vdsm/+/117826
>
> It did not work in the old data center, but maybe the issue with  the 
> el9stream
> nodes is solved now.

It does not work yet, el9stream fails quickly in global_setup.sh:

[2021-11-28T09:35:20.829Z] + sudo -n systemctl start libvirtd haveged firewalld
[2021-11-28T09:35:21.086Z] Failed to start libvirtd.service: Unit
libvirtd.service not found.
[2021-11-28T09:35:21.086Z] Failed to start haveged.service: Unit
haveged.service not found.

See https://ovirt-jira.atlassian.net/browse/OVIRT-3126

>
> >
> > Build Queue (12)
> > system-mk_mirrors_index-yum
> > part of vdsm_standard-check-patch #31073 vdsm [check-patch]
> > jenkins_master_check-patch-el7-ppc64le
> > jenkins_master_check-patch-el7-ppc64le
> > part of jenkins_standard-check-patch #5550
> > part of jenkins_standard-check-patch #5548
> > jenkins_master_check-patch-el7-ppc64le
> > jenkins_master_check-patch-el7-ppc64le
> > jenkins_master_check-patch-el7-ppc64le
> > jenkins_master_check-patch-el7-ppc64le
> > part of ovirt-appliance_standard-check-patch #385 ovirt-appliance
> > [check-patch]
> > lago-demo_master_github_timed-el7-x86_64
> >
> >
> > >
> > >
> > > On 25 Nov 2021, at 21:53, Nir Soffer  wrote:
> > >
> > > On Thu, Nov 25, 2021 at 9:15 PM Michal Skrivanek
> > >  wrote:
> > >
> > >
> > >
> > >
> > > On 25. 11. 2021, at 16:45, Evgheni Dereveanchin  
> > > wrote:
> > >
> > > Hi Milan,
> > >
> > > Indeed, this is related to the Jenkins move: all pre-existing nodes are 
> > > no longer usable so new ones have been created.
> > > We're looking into the reasons new nodes fail to initialize and bringing 
> > > up new ones in parallel to help with processing the build queue.
> > >
> > > Sorry for the inconvenience. Please report any other issues if you see 
> > > them as there may be quite some instability due to the rebuild.
> > >
> > >
> > > Hi Evgheni,
> > > the queue is now 53 builds long, and it seems nothing is building, 
> > > perhaps there's no worker or the labelling is wrong?
> > >
> > >
> > > Looks like jobs are stuck for several hours
> > > https://jenkins.ovirt.org/job/vdsm_standard-check-patch/31036/
> > >
> > > at the "loading code" stage:
> > > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/31036/pipeline
> > >
> > > With this error:
> > >
> > >There are no nodes with the label 
> > > ‘jenkins-vdsm_standard-check-patch-31036’
> > >
> > > The label looks wrong. vdsm requires nodes with "el8" label.
> > >
> > >
> > > Thanks,
> > > michal
> > >
> > >
> > > Regards.
> > > Evgheni
> > >
> > > On Thu, Nov 25, 2021 at 4:24 PM Nir Soffer  wrote:
> > >
> > >
> > > On Thu, Nov 25, 2021 at 3:48 PM Milan Zamazal  wrote:
> > >
> > >
> > > Hi,
> > >
> > > all patches uploaded today I've seen (for Engine and Vdsm) fail due to
> > > problems with availability of packages when preparing the el7
> > > environment.  For example:
> > > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/15291/
> > >
> > > Additionally, Vdsm tests are not run on PSI.
> > >
> > > Does anybody know what's wrong and how to fix it?  Can it be related to
> > > the Jenkins move?
> > >
> > >
> > > Looking at
> > > https://jenkins.ovirt.org/
> > >
> > > There are 33 jobs in the queue, and only 3 jobs running.
> > >
> > > Maybe we did not restore all the nodes?
> > >
> > >
> > > ___
> > > Devel mailing list -- devel@ovirt.org
> > > To unsubscribe send an email to devel-le...@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/ZLH3ILKHC3YPZWQFA2SG4GS3QSIALUXZ/
> > >
> > >
> > > ___
> > > Devel mailing list -- devel@ovirt.org
> > > To unsubscribe send an email to devel-le...@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/RZ7H4L26DU6LAKFQXJE4W3D4C5HP76CX/
> > >
> > >

[ovirt-devel] Re: CI failing all the time

2021-11-28 Thread Nir Soffer 
On Sun, Nov 28, 2021 at 10:59 AM Nir Soffer  wrote:
>
> On Fri, Nov 26, 2021 at 12:57 PM Ehud Yonasi  wrote:
> >
> > Hi Nir,
> >
> > There was a problem in jenkins to switch to the new k8s stack on IBM cloud, 
> > a restart was required and now it’s solved.
>
> The queue is increasing again, currently 12 jobs in the queue:

Vdsm jobs requires el8 nodes, but we have only one:
https://jenkins.ovirt.org/label/el8/

we also have only one el9stream node:
https://jenkins.ovirt.org/label/el9stream/

I posted this to use all nodes in vdsm, instead of only the el8 nodes:
https://gerrit.ovirt.org/c/vdsm/+/117826

It did not work in the old data center, but maybe the issue with  the el9stream
nodes is solved now.

>
> Build Queue (12)
> system-mk_mirrors_index-yum
> part of vdsm_standard-check-patch #31073 vdsm [check-patch]
> jenkins_master_check-patch-el7-ppc64le
> jenkins_master_check-patch-el7-ppc64le
> part of jenkins_standard-check-patch #5550
> part of jenkins_standard-check-patch #5548
> jenkins_master_check-patch-el7-ppc64le
> jenkins_master_check-patch-el7-ppc64le
> jenkins_master_check-patch-el7-ppc64le
> jenkins_master_check-patch-el7-ppc64le
> part of ovirt-appliance_standard-check-patch #385 ovirt-appliance
> [check-patch]
> lago-demo_master_github_timed-el7-x86_64
>
>
> >
> >
> > On 25 Nov 2021, at 21:53, Nir Soffer  wrote:
> >
> > On Thu, Nov 25, 2021 at 9:15 PM Michal Skrivanek
> >  wrote:
> >
> >
> >
> >
> > On 25. 11. 2021, at 16:45, Evgheni Dereveanchin  wrote:
> >
> > Hi Milan,
> >
> > Indeed, this is related to the Jenkins move: all pre-existing nodes are no 
> > longer usable so new ones have been created.
> > We're looking into the reasons new nodes fail to initialize and bringing up 
> > new ones in parallel to help with processing the build queue.
> >
> > Sorry for the inconvenience. Please report any other issues if you see them 
> > as there may be quite some instability due to the rebuild.
> >
> >
> > Hi Evgheni,
> > the queue is now 53 builds long, and it seems nothing is building, perhaps 
> > there's no worker or the labelling is wrong?
> >
> >
> > Looks like jobs are stuck for several hours
> > https://jenkins.ovirt.org/job/vdsm_standard-check-patch/31036/
> >
> > at the "loading code" stage:
> > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/31036/pipeline
> >
> > With this error:
> >
> >There are no nodes with the label 
> > ‘jenkins-vdsm_standard-check-patch-31036’
> >
> > The label looks wrong. vdsm requires nodes with "el8" label.
> >
> >
> > Thanks,
> > michal
> >
> >
> > Regards.
> > Evgheni
> >
> > On Thu, Nov 25, 2021 at 4:24 PM Nir Soffer  wrote:
> >
> >
> > On Thu, Nov 25, 2021 at 3:48 PM Milan Zamazal  wrote:
> >
> >
> > Hi,
> >
> > all patches uploaded today I've seen (for Engine and Vdsm) fail due to
> > problems with availability of packages when preparing the el7
> > environment.  For example:
> > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/15291/
> >
> > Additionally, Vdsm tests are not run on PSI.
> >
> > Does anybody know what's wrong and how to fix it?  Can it be related to
> > the Jenkins move?
> >
> >
> > Looking at
> > https://jenkins.ovirt.org/
> >
> > There are 33 jobs in the queue, and only 3 jobs running.
> >
> > Maybe we did not restore all the nodes?
> >
> >
> > ___
> > Devel mailing list -- devel@ovirt.org
> > To unsubscribe send an email to devel-le...@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/ZLH3ILKHC3YPZWQFA2SG4GS3QSIALUXZ/
> >
> >
> > ___
> > Devel mailing list -- devel@ovirt.org
> > To unsubscribe send an email to devel-le...@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/RZ7H4L26DU6LAKFQXJE4W3D4C5HP76CX/
> >
> > ___
> > Devel mailing list -- devel@ovirt.org
> > To unsubscribe send an email to devel-le...@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/UK4KVTPITCAWHWUR5QPGN3RSNFYQSH34/
> >
> >
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@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:

[ovirt-devel] Re: CI failing all the time

2021-11-28 Thread Nir Soffer 
On Fri, Nov 26, 2021 at 12:57 PM Ehud Yonasi  wrote:
>
> Hi Nir,
>
> There was a problem in jenkins to switch to the new k8s stack on IBM cloud, a 
> restart was required and now it’s solved.

The queue is increasing again, currently 12 jobs in the queue:

Build Queue (12)
system-mk_mirrors_index-yum
part of vdsm_standard-check-patch #31073 vdsm [check-patch]
jenkins_master_check-patch-el7-ppc64le
jenkins_master_check-patch-el7-ppc64le
part of jenkins_standard-check-patch #5550
part of jenkins_standard-check-patch #5548
jenkins_master_check-patch-el7-ppc64le
jenkins_master_check-patch-el7-ppc64le
jenkins_master_check-patch-el7-ppc64le
jenkins_master_check-patch-el7-ppc64le
part of ovirt-appliance_standard-check-patch #385 ovirt-appliance
[check-patch]
lago-demo_master_github_timed-el7-x86_64


>
>
> On 25 Nov 2021, at 21:53, Nir Soffer  wrote:
>
> On Thu, Nov 25, 2021 at 9:15 PM Michal Skrivanek
>  wrote:
>
>
>
>
> On 25. 11. 2021, at 16:45, Evgheni Dereveanchin  wrote:
>
> Hi Milan,
>
> Indeed, this is related to the Jenkins move: all pre-existing nodes are no 
> longer usable so new ones have been created.
> We're looking into the reasons new nodes fail to initialize and bringing up 
> new ones in parallel to help with processing the build queue.
>
> Sorry for the inconvenience. Please report any other issues if you see them 
> as there may be quite some instability due to the rebuild.
>
>
> Hi Evgheni,
> the queue is now 53 builds long, and it seems nothing is building, perhaps 
> there's no worker or the labelling is wrong?
>
>
> Looks like jobs are stuck for several hours
> https://jenkins.ovirt.org/job/vdsm_standard-check-patch/31036/
>
> at the "loading code" stage:
> https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/31036/pipeline
>
> With this error:
>
>There are no nodes with the label ‘jenkins-vdsm_standard-check-patch-31036’
>
> The label looks wrong. vdsm requires nodes with "el8" label.
>
>
> Thanks,
> michal
>
>
> Regards.
> Evgheni
>
> On Thu, Nov 25, 2021 at 4:24 PM Nir Soffer  wrote:
>
>
> On Thu, Nov 25, 2021 at 3:48 PM Milan Zamazal  wrote:
>
>
> Hi,
>
> all patches uploaded today I've seen (for Engine and Vdsm) fail due to
> problems with availability of packages when preparing the el7
> environment.  For example:
> https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/15291/
>
> Additionally, Vdsm tests are not run on PSI.
>
> Does anybody know what's wrong and how to fix it?  Can it be related to
> the Jenkins move?
>
>
> Looking at
> https://jenkins.ovirt.org/
>
> There are 33 jobs in the queue, and only 3 jobs running.
>
> Maybe we did not restore all the nodes?
>
>
> ___
> Devel mailing list -- devel@ovirt.org
> To unsubscribe send an email to devel-le...@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/ZLH3ILKHC3YPZWQFA2SG4GS3QSIALUXZ/
>
>
> ___
> Devel mailing list -- devel@ovirt.org
> To unsubscribe send an email to devel-le...@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/RZ7H4L26DU6LAKFQXJE4W3D4C5HP76CX/
>
> ___
> Devel mailing list -- devel@ovirt.org
> To unsubscribe send an email to devel-le...@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/UK4KVTPITCAWHWUR5QPGN3RSNFYQSH34/
>
>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@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/MREDOKMNI4K5RYQ24ASWNYHGJML2QCFI/

[ovirt-devel] Re: CI failing all the time

2021-11-26 Thread Martin Perina 
Sorry, but I don't see any improvements since morning, all engine
check-patch jobs are still failing:

17:50:07 Initialized empty Git repository in
/home/jenkins/agent/workspace/ovirt-engine_standard-check-patch/ovirt-engine/.git/
17:50:51
stdci-production/jenkins-ovirt-engine-standard-check-patch-15330-61vhd-63q48
Container jnlp was terminated (Exit Code: 137, Reason: OOMKilled)
17:50:53 Cannot contact
jenkins-ovirt-engine-standard-check-patch-15330-61vhd-63q48:
hudson.remoting.ChannelClosedException: Channel
"hudson.remoting.Channel@55ad1988:JNLP4-connect connection from
a2.15.3ea9.ip4.static.sl-reverse.com/169.62.21.162:1024": Remote call on
JNLP4-connect connection from
a2.15.3ea9.ip4.static.sl-reverse.com/169.62.21.162:1024 failed. The channel
is closing down or has closed down
17:51:41
stdci-production/jenkins-ovirt-engine-standard-check-patch-15330-61vhd-63q48
Container jnlp was terminated (Exit Code: 137, Reason: OOMKilled)
17:52:07
stdci-production/jenkins-ovirt-engine-standard-check-patch-15330-61vhd-63q48
Pod just failed (Reason: null, Message: null)
17:52:07
stdci-production/jenkins-ovirt-engine-standard-check-patch-15330-61vhd-63q48
Pod just failed (Reason: null, Message: null)
17:57:07 Agent jenkins-ovirt-engine-standard-check-patch-15330-61vhd-63q48
was deleted; cancelling node body
17:57:07 Agent jenkins-ovirt-engine-standard-check-patch-15330-61vhd-63q48
was deleted; cancelling node body
17:57:07 Could not connect to
jenkins-ovirt-engine-standard-check-patch-15330-61vhd-63q48 to send
interrupt signal to process
17:57:07 Could not connect to
jenkins-ovirt-engine-standard-check-patch-15330-61vhd-63q48 to send
interrupt signal to process




On Fri, Nov 26, 2021 at 12:00 PM Ehud Yonasi  wrote:

> Hi Nir,
>
> There was a problem in jenkins to switch to the new k8s stack on IBM
> cloud, a restart was required and now it’s solved.
>
>
> On 25 Nov 2021, at 21:53, Nir Soffer  wrote:
>
> On Thu, Nov 25, 2021 at 9:15 PM Michal Skrivanek
>  wrote:
>
>
>
>
> On 25. 11. 2021, at 16:45, Evgheni Dereveanchin 
> wrote:
>
> Hi Milan,
>
> Indeed, this is related to the Jenkins move: all pre-existing nodes are no
> longer usable so new ones have been created.
> We're looking into the reasons new nodes fail to initialize and bringing
> up new ones in parallel to help with processing the build queue.
>
> Sorry for the inconvenience. Please report any other issues if you see
> them as there may be quite some instability due to the rebuild.
>
>
> Hi Evgheni,
> the queue is now 53 builds long, and it seems nothing is building, perhaps
> there's no worker or the labelling is wrong?
>
>
> Looks like jobs are stuck for several hours
> https://jenkins.ovirt.org/job/vdsm_standard-check-patch/31036/
>
> at the "loading code" stage:
>
> https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/31036/pipeline
>
> With this error:
>
>There are no nodes with the label
> ‘jenkins-vdsm_standard-check-patch-31036’
>
> The label looks wrong. vdsm requires nodes with "el8" label.
>
>
> Thanks,
> michal
>
>
> Regards.
> Evgheni
>
> On Thu, Nov 25, 2021 at 4:24 PM Nir Soffer  wrote:
>
>
> On Thu, Nov 25, 2021 at 3:48 PM Milan Zamazal  wrote:
>
>
> Hi,
>
> all patches uploaded today I've seen (for Engine and Vdsm) fail due to
> problems with availability of packages when preparing the el7
> environment.  For example:
> https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/15291/
>
> Additionally, Vdsm tests are not run on PSI.
>
> Does anybody know what's wrong and how to fix it?  Can it be related to
> the Jenkins move?
>
>
> Looking at
> https://jenkins.ovirt.org/
>
> There are 33 jobs in the queue, and only 3 jobs running.
>
> Maybe we did not restore all the nodes?
>
>
> ___
> Devel mailing list -- devel@ovirt.org
> To unsubscribe send an email to devel-le...@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/ZLH3ILKHC3YPZWQFA2SG4GS3QSIALUXZ/
>
>
> ___
> Devel mailing list -- devel@ovirt.org
> To unsubscribe send an email to devel-le...@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/RZ7H4L26DU6LAKFQXJE4W3D4C5HP76CX/
>
> ___
> Devel mailing list -- devel@ovirt.org
> To unsubscribe send an email to devel-le...@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:
>

[ovirt-devel] Re: CI failing all the time

2021-11-26 Thread Ehud Yonasi 
Hi Nir,

There was a problem in jenkins to switch to the new k8s stack on IBM cloud, a 
restart was required and now it’s solved.


> On 25 Nov 2021, at 21:53, Nir Soffer  wrote:
> 
> On Thu, Nov 25, 2021 at 9:15 PM Michal Skrivanek
> mailto:michal.skriva...@redhat.com>> wrote:
>> 
>> 
>> 
>> On 25. 11. 2021, at 16:45, Evgheni Dereveanchin  wrote:
>> 
>> Hi Milan,
>> 
>> Indeed, this is related to the Jenkins move: all pre-existing nodes are no 
>> longer usable so new ones have been created.
>> We're looking into the reasons new nodes fail to initialize and bringing up 
>> new ones in parallel to help with processing the build queue.
>> 
>> Sorry for the inconvenience. Please report any other issues if you see them 
>> as there may be quite some instability due to the rebuild.
>> 
>> 
>> Hi Evgheni,
>> the queue is now 53 builds long, and it seems nothing is building, perhaps 
>> there's no worker or the labelling is wrong?
> 
> Looks like jobs are stuck for several hours
> https://jenkins.ovirt.org/job/vdsm_standard-check-patch/31036/ 
> 
> 
> at the "loading code" stage:
> https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/31036/pipeline
>  
> 
> 
> With this error:
> 
>There are no nodes with the label ‘jenkins-vdsm_standard-check-patch-31036’
> 
> The label looks wrong. vdsm requires nodes with "el8" label.
> 
>> 
>> Thanks,
>> michal
>> 
>> 
>> Regards.
>> Evgheni
>> 
>> On Thu, Nov 25, 2021 at 4:24 PM Nir Soffer  wrote:
>>> 
>>> On Thu, Nov 25, 2021 at 3:48 PM Milan Zamazal  wrote:
 
 Hi,
 
 all patches uploaded today I've seen (for Engine and Vdsm) fail due to
 problems with availability of packages when preparing the el7
 environment.  For example:
 https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/15291/
 
 Additionally, Vdsm tests are not run on PSI.
 
 Does anybody know what's wrong and how to fix it?  Can it be related to
 the Jenkins move?
>>> 
>>> Looking at
>>> https://jenkins.ovirt.org/
>>> 
>>> There are 33 jobs in the queue, and only 3 jobs running.
>>> 
>>> Maybe we did not restore all the nodes?
>>> 
>> 
>> ___
>> Devel mailing list -- devel@ovirt.org
>> To unsubscribe send an email to devel-le...@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/ZLH3ILKHC3YPZWQFA2SG4GS3QSIALUXZ/
>> 
>> 
>> ___
>> Devel mailing list -- devel@ovirt.org
>> To unsubscribe send an email to devel-le...@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/RZ7H4L26DU6LAKFQXJE4W3D4C5HP76CX/
> ___
> Devel mailing list -- devel@ovirt.org 
> To unsubscribe send an email to devel-le...@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/UK4KVTPITCAWHWUR5QPGN3RSNFYQSH34/
>  
> 
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@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/APB6NEWFR2RN7WWOLWTG5HHJF25X4BL5/

[ovirt-devel] Re: CI failing all the time

2021-11-25 Thread Nir Soffer 
On Thu, Nov 25, 2021 at 9:15 PM Michal Skrivanek
 wrote:
>
>
>
> On 25. 11. 2021, at 16:45, Evgheni Dereveanchin  wrote:
>
> Hi Milan,
>
> Indeed, this is related to the Jenkins move: all pre-existing nodes are no 
> longer usable so new ones have been created.
> We're looking into the reasons new nodes fail to initialize and bringing up 
> new ones in parallel to help with processing the build queue.
>
> Sorry for the inconvenience. Please report any other issues if you see them 
> as there may be quite some instability due to the rebuild.
>
>
> Hi Evgheni,
> the queue is now 53 builds long, and it seems nothing is building, perhaps 
> there's no worker or the labelling is wrong?

Looks like jobs are stuck for several hours
https://jenkins.ovirt.org/job/vdsm_standard-check-patch/31036/

at the "loading code" stage:
https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/31036/pipeline

With this error:

There are no nodes with the label ‘jenkins-vdsm_standard-check-patch-31036’

The label looks wrong. vdsm requires nodes with "el8" label.

>
> Thanks,
> michal
>
>
> Regards.
> Evgheni
>
> On Thu, Nov 25, 2021 at 4:24 PM Nir Soffer  wrote:
>>
>> On Thu, Nov 25, 2021 at 3:48 PM Milan Zamazal  wrote:
>> >
>> > Hi,
>> >
>> > all patches uploaded today I've seen (for Engine and Vdsm) fail due to
>> > problems with availability of packages when preparing the el7
>> > environment.  For example:
>> > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/15291/
>> >
>> > Additionally, Vdsm tests are not run on PSI.
>> >
>> > Does anybody know what's wrong and how to fix it?  Can it be related to
>> > the Jenkins move?
>>
>> Looking at
>> https://jenkins.ovirt.org/
>>
>> There are 33 jobs in the queue, and only 3 jobs running.
>>
>> Maybe we did not restore all the nodes?
>>
>
> ___
> Devel mailing list -- devel@ovirt.org
> To unsubscribe send an email to devel-le...@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/ZLH3ILKHC3YPZWQFA2SG4GS3QSIALUXZ/
>
>
> ___
> Devel mailing list -- devel@ovirt.org
> To unsubscribe send an email to devel-le...@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/RZ7H4L26DU6LAKFQXJE4W3D4C5HP76CX/
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@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/UK4KVTPITCAWHWUR5QPGN3RSNFYQSH34/

[ovirt-devel] Re: CI failing all the time

2021-11-25 Thread Michal Skrivanek 


> On 25. 11. 2021, at 16:45, Evgheni Dereveanchin  wrote:
> 
> Hi Milan,
> 
> Indeed, this is related to the Jenkins move: all pre-existing nodes are no 
> longer usable so new ones have been created.
> We're looking into the reasons new nodes fail to initialize and bringing up 
> new ones in parallel to help with processing the build queue.
> 
> Sorry for the inconvenience. Please report any other issues if you see them 
> as there may be quite some instability due to the rebuild.

Hi Evgheni,
the queue is now 53 builds long, and it seems nothing is building, perhaps 
there's no worker or the labelling is wrong?

Thanks,
michal

> 
> Regards.
> Evgheni
> 
> On Thu, Nov 25, 2021 at 4:24 PM Nir Soffer  > wrote:
> On Thu, Nov 25, 2021 at 3:48 PM Milan Zamazal  > wrote:
> >
> > Hi,
> >
> > all patches uploaded today I've seen (for Engine and Vdsm) fail due to
> > problems with availability of packages when preparing the el7
> > environment.  For example:
> > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/15291/ 
> > 
> >
> > Additionally, Vdsm tests are not run on PSI.
> >
> > Does anybody know what's wrong and how to fix it?  Can it be related to
> > the Jenkins move?
> 
> Looking at
> https://jenkins.ovirt.org/ 
> 
> There are 33 jobs in the queue, and only 3 jobs running.
> 
> Maybe we did not restore all the nodes?
> 
> 
> ___
> Devel mailing list -- devel@ovirt.org
> To unsubscribe send an email to devel-le...@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/ZLH3ILKHC3YPZWQFA2SG4GS3QSIALUXZ/

___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@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/RZ7H4L26DU6LAKFQXJE4W3D4C5HP76CX/

[ovirt-devel] Re: CI failing all the time

2021-11-25 Thread Evgheni Dereveanchin 
Hi Milan,

Indeed, this is related to the Jenkins move: all pre-existing nodes are no
longer usable so new ones have been created.
We're looking into the reasons new nodes fail to initialize and bringing up
new ones in parallel to help with processing the build queue.

Sorry for the inconvenience. Please report any other issues if you see them
as there may be quite some instability due to the rebuild.

Regards.
Evgheni

On Thu, Nov 25, 2021 at 4:24 PM Nir Soffer  wrote:

> On Thu, Nov 25, 2021 at 3:48 PM Milan Zamazal  wrote:
> >
> > Hi,
> >
> > all patches uploaded today I've seen (for Engine and Vdsm) fail due to
> > problems with availability of packages when preparing the el7
> > environment.  For example:
> > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/15291/
> >
> > Additionally, Vdsm tests are not run on PSI.
> >
> > Does anybody know what's wrong and how to fix it?  Can it be related to
> > the Jenkins move?
>
> Looking at
> https://jenkins.ovirt.org/
>
> There are 33 jobs in the queue, and only 3 jobs running.
>
> Maybe we did not restore all the nodes?
>
>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@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/ZLH3ILKHC3YPZWQFA2SG4GS3QSIALUXZ/

[ovirt-devel] Re: CI failing all the time

2021-11-25 Thread Nir Soffer 
On Thu, Nov 25, 2021 at 3:48 PM Milan Zamazal  wrote:
>
> Hi,
>
> all patches uploaded today I've seen (for Engine and Vdsm) fail due to
> problems with availability of packages when preparing the el7
> environment.  For example:
> https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/15291/
>
> Additionally, Vdsm tests are not run on PSI.
>
> Does anybody know what's wrong and how to fix it?  Can it be related to
> the Jenkins move?

Looking at
https://jenkins.ovirt.org/

There are 33 jobs in the queue, and only 3 jobs running.

Maybe we did not restore all the nodes?
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@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/J72NKWHRPW7JXYN6DRUTLCTGKAOYHBWG/

[ovirt-devel] Re: CI failing

2019-07-24 Thread Eyal Edri 
The check patch for 4.3 was using external url ( that can be down ),
This patch [1] adds mirror to the repo, so it will access our local mirror
before trying the external one, which should reduce the amount of times a
failure happens.

[1] https://gerrit.ovirt.org/#/c/102155/1/automation/check-patch.repos.fc28

On Wed, Jul 24, 2019 at 3:49 PM Michal Skrivanek <
michal.skriva...@redhat.com> wrote:

>
>
> On 24 Jul 2019, at 11:18, Eyal Edri  wrote:
>
> Looks like external repo that is failing, which job is it? can it use the
> ovirt mirrors instead of using the external repos?
>
>
> just the regular check-patch thingie on vdsm.
>
>
> On Wed, Jul 24, 2019 at 11:36 AM Michal Skrivanek <
> michal.skriva...@redhat.com> wrote:
>
>> it’s been on and off in the past ~2 weeks, it’s still failing way too
>> often. Right now with:
>>
>> 10:12:25  failure:
>> repodata/0b87a97f332e1a7bf059abebf295df6a785df123470cc371c2b6c1a7b8f87f95-primary.sqlite.bz2
>> from updates-testing: [Errno 256] No more mirrors to try.
>> 10:12:25
>> http://download.fedoraproject.org/pub/fedora/linux/updates/testing/29/Everything/x86_64/repodata/0b87a97f332e1a7bf059abebf295df6a785df123470cc371c2b6c1a7b8f87f95-primary.sqlite.bz2:
>> [Errno 14] HTTPS Error 404 - Not Found
>>
>> Thanks,
>> michal
>>
>> ___
>> Devel mailing list -- devel@ovirt.org
>> To unsubscribe send an email to devel-le...@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/devel@ovirt.org/message/ECO7Y7TTYV6TZITDNDVCG7VDZB3I52LD/
>>
>
>
> --
> Eyal edri
> He / Him / His
>
> MANAGER
>
> CONTINUOUS PRODUCTIZATION
>
> SYSTEM ENGINEERING
>
> Red Hat 
> 
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ #cp-devel)
>
>
>

-- 

Eyal edri

He / Him / His


MANAGER

CONTINUOUS PRODUCTIZATION

SYSTEM ENGINEERING

Red Hat 

phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ #cp-devel)
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@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/devel@ovirt.org/message/GGIBUDO73USFIWJM4MJWGDBRNDZJ7HJV/

[ovirt-devel] Re: CI failing

2019-07-24 Thread Michal Skrivanek 


> On 24 Jul 2019, at 11:18, Eyal Edri  wrote:
> 
> Looks like external repo that is failing, which job is it? can it use the 
> ovirt mirrors instead of using the external repos?

just the regular check-patch thingie on vdsm. 

> 
> On Wed, Jul 24, 2019 at 11:36 AM Michal Skrivanek 
> mailto:michal.skriva...@redhat.com>> wrote:
> it’s been on and off in the past ~2 weeks, it’s still failing way too often. 
> Right now with:
> 
> 10:12:25  failure: 
> repodata/0b87a97f332e1a7bf059abebf295df6a785df123470cc371c2b6c1a7b8f87f95-primary.sqlite.bz2
>  from updates-testing: [Errno 256] No more mirrors to try.
> 10:12:25  
> http://download.fedoraproject.org/pub/fedora/linux/updates/testing/29/Everything/x86_64/repodata/0b87a97f332e1a7bf059abebf295df6a785df123470cc371c2b6c1a7b8f87f95-primary.sqlite.bz2
>  
> :
>  [Errno 14] HTTPS Error 404 - Not Found
> 
> Thanks,
> michal
> 
> ___
> Devel mailing list -- devel@ovirt.org 
> To unsubscribe send an email to devel-le...@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/devel@ovirt.org/message/ECO7Y7TTYV6TZITDNDVCG7VDZB3I52LD/
>  
> 
> 
> 
> -- 
> EYAL EDRI
> He / Him / His
> 
> MANAGER
> CONTINUOUS PRODUCTIZATION
> SYSTEM ENGINEERING
> RED HAT 
>  
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ #cp-devel)

___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@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/devel@ovirt.org/message/FIZTJFKE5XR2H35MXV4LFZ4PDK4T34TR/

[ovirt-devel] Re: CI failing

2019-07-24 Thread Eyal Edri 
Looks like external repo that is failing, which job is it? can it use the
ovirt mirrors instead of using the external repos?

On Wed, Jul 24, 2019 at 11:36 AM Michal Skrivanek <
michal.skriva...@redhat.com> wrote:

> it’s been on and off in the past ~2 weeks, it’s still failing way too
> often. Right now with:
>
> 10:12:25  failure:
> repodata/0b87a97f332e1a7bf059abebf295df6a785df123470cc371c2b6c1a7b8f87f95-primary.sqlite.bz2
> from updates-testing: [Errno 256] No more mirrors to try.
> 10:12:25
> http://download.fedoraproject.org/pub/fedora/linux/updates/testing/29/Everything/x86_64/repodata/0b87a97f332e1a7bf059abebf295df6a785df123470cc371c2b6c1a7b8f87f95-primary.sqlite.bz2:
> [Errno 14] HTTPS Error 404 - Not Found
>
> Thanks,
> michal
>
> ___
> Devel mailing list -- devel@ovirt.org
> To unsubscribe send an email to devel-le...@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/devel@ovirt.org/message/ECO7Y7TTYV6TZITDNDVCG7VDZB3I52LD/
>


-- 

Eyal edri

He / Him / His


MANAGER

CONTINUOUS PRODUCTIZATION

SYSTEM ENGINEERING

Red Hat 

phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ #cp-devel)
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@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/devel@ovirt.org/message/BZCETMLPZHSNQWXNL4RIFRK6CTYTQTSD/

[ovirt-devel] Re: CI failing: /usr/sbin/groupadd -g 1000 mock

2018-06-18 Thread Barak Korren 
On 17 June 2018 at 23:03, Yuval Turgeman  wrote:

> IIRC we hit this issue before when trying to install a mock rpm of a
> specific version inside an env that was created with a different version of
> mock (group names have changed from mock to mockbuild or vice versa)
>
> On Jun 17, 2018 22:53, "Nir Soffer"  wrote:
>
> 2 Fedora builds failed recently with this error:
>
> 19:40:34 ERROR: Command failed: 19:40:34 # /usr/sbin/groupadd -g 1000 mock
>
> See latest builds of this patch:
> https://gerrit.ovirt.org/#/c/91834/
>
> I merged the patch regardless, but please take a look.
>
>

Looks like an updated mock was  pushed to FC28 and introduced some
breakage.
We should have had package gating setup for FC28 before introducing the
FC28 slaves.

Hers is a tracker ticket:
https://ovirt-jira.atlassian.net/browse/OVIRT-2208

We will probably downgrade mock back to 1.4.10 at this point and do an
orderly upgrade later.

-- 
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@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/devel@ovirt.org/message/VC3C5OCTAAWMUDLBYQEMSN5JJINLVKT6/

[ovirt-devel] Re: CI failing: /usr/sbin/groupadd -g 1000 mock

2018-06-17 Thread Yuval Turgeman 
IIRC we hit this issue before when trying to install a mock rpm of a
specific version inside an env that was created with a different version of
mock (group names have changed from mock to mockbuild or vice versa)

On Jun 17, 2018 22:53, "Nir Soffer"  wrote:

2 Fedora builds failed recently with this error:

19:40:34 ERROR: Command failed: 19:40:34 # /usr/sbin/groupadd -g 1000 mock

See latest builds of this patch:
https://gerrit.ovirt.org/#/c/91834/

I merged the patch regardless, but please take a look.

Nir
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@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/devel@ovirt.org/message/Y3REN743FHTRGOLVSJD66JTX34FJLQ5S/
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@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/devel@ovirt.org/message/W3SESKPKUXHO27TVIS2XD5DQFW3ZIFUP/