[ovirt-devel] GitHub Actions-based CI for vdsm

[Marcin Sobczyk]

Hi All,

I've been working on adding GitHub Actions-based CI to vdsm today.
Feel free to check out the patches here:

https://gerrit.ovirt.org/q/topic:%22github-actions-ci%22+(status:open%20OR%20status:merged)

Some comments:
- the linters work fine already, we can start using them

- RPM building works too in general. I think the RPM versions are not 
right yet, so I'll look into this. After the 'rpm' job is done we get a 
zipfile with all the built RPMs inside. In the future we may want to run 
'createrepo_c' on this dir as well, so we'll have a ready-to-be-used 
repository in that zip.


- 'tests' are working too, but we have a couple of failures we'd need to 
look at. This job, unlike the others, runs in GitHub's Ubuntu VM inside 
which we use a privileged container for running the tests.


- didn't try 'tests-storage' yet

- Not to waist precious free CI minutes and storage, we run linters 
first, tests after that, but only under the condition that the linters 
didn't fail, and finally we build RPMs, but this time under the 
condition that the tests didn't fail.


You can find some of the runs I made in my personal fork here:

https://github.com/tinez/vdsm/actions/workflows/ci.yml

Comments, remarks and reviews are highly appreciated.

Regards, Marcin
___
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/KNZMFTBRMTQOKNKNBKGASQ5QJFUNFRMJ/

[ovirt-devel] ovirt-engine dependency on ovirt-engine-extensions-api

[Sandro Bonazzola]

Hi,
In ovirt-engine pom.xml there's a requirement for build time
on ovirt-engine-extensions-api = 1.0.0.
This dependency is available on maven central so online build works.

Any clue on why we are not requiring 1.0.1

instead ?

We are packaging ovirt-engine-extensions-api during the development but it
ships 1.0.2.SNAPSHOT so when building in offline mode (needed for building
on CentOS Virt SIG) it fails as the 1.0.0 artifact was never downloaded.

I can rebuild ovirt-engine-extensions-api from 1.0.0 or 1.0.1 which are
available in maven central too as requiring explicitly 1.0.2.SNAPSHOT fails
with:
Failed to execute goal on project common-dependencies: Could not resolve
dependencies for project
org.ovirt.engine.core.manager:common-dependencies:jar:4.5.0-SNAPSHOT: The
following artifacts could not be resolved:
org.ovirt.engine.api:ovirt-engine-extensions-api:jar:1.0.2.SNAPSHOT,
org.ovirt.java-client-kubevirt:java-client-kubevirt:jar:0.5.0,
org.apache.sshd:sshd-common:jar:2.6.0, org.apache.sshd:sshd-core:jar:2.6.0,
net.i2p.crypto:eddsa:jar:0.3.0,
org.ovirt.engine.api:metamodel-server:jar:1.3.7,
org.ovirt.vdsm-jsonrpc-java:vdsm-jsonrpc-java-client:jar:1.6.0,
com.fasterxml.jackson.core:jackson-databind:jar:2.12.1,
org.jboss.resteasy:resteasy-jaxrs:jar:3.9.3.Final,
com.fasterxml.jackson.jaxrs:jackson-jaxrs-json-provider:jar:2.12.1,
org.apache.httpcomponents:httpclient:jar:4.5.13: Could not find artifact
org.ovirt.engine.api:ovirt-engine-extensions-api:jar:1.0.2.SNAPSHOT ->
[Help 1]

Any recommendations on how to proceed?

-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com


*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*
___
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/AXJWD5HKGTAQ2WHIUGWKLDOS6D7IS5YF/

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

[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

[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: Failed CI for engine patches - java-client-kubevirt otopi

[Martin Perina]

On Fri, Nov 26, 2021 at 10:34 AM Sandro Bonazzola 
wrote:

>
>
> Il giorno gio 25 nov 2021 alle ore 20:46 Ehud Yonasi 
> ha scritto:
>
>> Indeed Martin, I can see it now.
>> We have an issue reflecting the new resources server, probably dns or
>> something related.
>>
>> Meanwhile Shani, I suggest that you change the resources server in your
>> automation/*.repos file to:
>> https://resources02.phx.ovirt.org/repos/ovirt/tested/master/rpm/el8
>>
>> We have someone already looking into it already and we hope CI will be
>> fixed soon.
>> Apologies.
>>
>
> Please don't require any ovirt.org repository anymore in build roots of
> any test or build job.
> Either use CentOS Virt SIG repos or COPR repos.
> We are dismissing ovirt-master-snapshot completely.
>

So we have a couple of packages to use this repos in automations repos, it
will take some time to switch ...

>
>
>
>
>>
>> On 25 Nov 2021, at 18:03, Martin Perina  wrote:
>>
>>
>>
>> On Thu, Nov 25, 2021 at 2:04 PM Ehud Yonasi  wrote:
>>
>>> So I am not sure where the dependency came from, but as I can see from
>>> otopi repo it is only realsing to ovirt-4.3 on resources at the moment.
>>>
>>
>> Not true, otopi is configured correctly:
>>
>> master -> ovirt-master
>> https://github.com/oVirt/otopi/blob/master/.ovirtci.yaml
>>
>> otopi-1..9 -> ovirt-4.4
>> https://github.com/oVirt/otopi/blob/otopi-1.9/.ovirtci.yaml
>>
>> Similar situation is with java-client-kubevirt, which should also be
>> correctly setup:
>>
>> master -> ovirt-master, ovirt-4.4
>> https://github.com/oVirt/java-client-kubevirt/blob/master/.stdci.yaml
>>
>> And I had to mention that similar situation we had for
>> ovirt-jboss-modules-maven-plugin, which magically disappeared from tested
>> repo cca 2 weeks ago and I needed to re-merge last patch to get the build
>> there again. And also here everything seems correct to me:
>>
>>
>> https://github.com/oVirt/ovirt-jboss-modules-maven-plugin/blob/master/automation.yaml
>>
>>
>> All of those packages are included in oVirt project for quite long time,
>> so the issue is somewhere in the Jenkins CI
>>
>>
>>> Maybe Sandro can help with that?
>>>
>>> On Thu, Nov 25, 2021 at 2:46 PM Shani Leviim  wrote:
>>>
 Hi Ehud,
 Honestly - I have no idea.
 This failure is from today, but in the patches, there is a series of CI
 failures while trying to build the patch - all failures while trying to
 build the engine.


 *Regards,*

 *Shani Leviim*


 On Thu, Nov 25, 2021 at 2:19 PM Ehud Yonasi  wrote:

> Hi Shani and Artur,
>
> I didn't find otopi and that java-client-kubevirt package in the repos
> listed inside the run. was it there in the first place?
>
> Artur, It seems the centos mirrors were not available during the time
> of the build, could you please re-trigger it and update if it's working 
> for
> you now?
>
> Thanks,
> Ehud.
>
> On Thu, Nov 25, 2021 at 1:28 PM Artur Socha  wrote:
>
>> I could also add that I am currently having an issue with accessing
>> Centos stream 8 AppStream repo (timed out). See [1] . Perhaps that 
>> somehow
>> related?
>>
>> [1]
>> https://jenkins.ovirt.org/job/vdsm-jsonrpc-java_standard-check-patch/187/console
>>
>> Artur
>>
>> On Thu, Nov 25, 2021 at 11:50 AM Shani Leviim 
>> wrote:
>>
>>> Hi,
>>> I have a series of engine patches that keep failing although the
>>> chain is rebased on the latest master.
>>> I ran 'ci build' a couple of minutes ago and it failed with this one:
>>> 11:08:45 No match for argument: otopi
>>> 11:08:45 Error: Unable to find a match: java-client-kubevirt otopi
>>>
>>> https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/15286/console
>>>
>>> The engine patches:
>>>
>>> https://gerrit.ovirt.org/q/topic:%22copy-template-mbs-disk%22+(status:open%20OR%20status:merged)
>>>
>>> Can someone assist, please?
>>>
>>>
>>> *Regards,*
>>>
>>> *Shani Leviim*
>>> ___
>>> 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/VUYJRGNY6X7UYZ6PQBQGVENE5LVFGN3O/
>>>
>>
>>
>> --
>> Artur Socha
>> Senior Software Engineer, RHV
>> Red Hat
>> ___
>> 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: java-client-kubevirt in 4.5

[Sandro Bonazzola]

Il giorno lun 15 nov 2021 alle ore 11:55 Sandro Bonazzola <
sbona...@redhat.com> ha scritto:

>
>
> Il giorno lun 15 nov 2021 alle ore 10:22 Artur Socha 
> ha scritto:
>
>> Ack.
>> @Sandro, please let me know if ~EOY timeline is good enough.
>>
>
> Should be good enough
>

I rebuilt the needed packages within CentOS Virt SIG so the broken
dependency issue is gone.
But please keep the task in the backlog, we should stop using maven2
dependencies there.



>
>
>>
>> Artur
>>
>> On Thu, Nov 11, 2021 at 6:09 PM Martin Perina  wrote:
>>
>>> Hi,
>>>
>>> Artur could try to resolve this once Keycloak RFE is finished and I
>>> don't expect this will be ready before the end of year. If we can't wait
>>> that long, then we will need to figure out some temporary solution.
>>>
>>> Martin
>>>
>>>
>>> On Thu, Nov 11, 2021 at 5:06 PM Sandro Bonazzola 
>>> wrote:
>>>
 hi,
 java-client-kubevirt is failing on missing dependencies:
 package: java-client-kubevirt-0.5.0-1.20211108071009.gite0a0fe8.el9.src
 from copr:copr.fedorainfracloud.org:ovirt:ovirt-master-snapshot
   unresolved deps:
 maven-plugin-registry
 maven-profile
 maven-shade-plugin

 I'm providing those dependencies temporarily with
 ovirt-master-snapshot-static repo.
 I kindly asked for them to be added to CentOS Stream 9
 (see as example Bug 2017712
  - Missing
 maven-shade-plugin in CentOS Stream 9 )
 But the request was rejected.
 We have a few options:
 1) Ask for building on CentOS Stream 9 Koji instance at
 https://kojihub.stream.centos.org/koji/ as that dependency is
 available there in build roots.
 2) Change java-client-kubevirt for not requiring those packages
 (bundling the needed jar files within the .src.rpm?)
 3) Drop java-client-kubevirt completely in oVirt 4.5
 4) Rebuild the whole maven stack up to those dependencies within CentOS
 Virt SIG and COPR.
 5) Keep the "temporary" solution as-is

 How should we proceed?

 --

 Sandro Bonazzola

 MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

 Red Hat EMEA 

 sbona...@redhat.com
 

 *Red Hat respects your work life balance. Therefore there is no need to
 answer this email out of your office hours.*


 ___
 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/T5BDLYXQISTVGCQNFVOPH7KRMCHNA3VR/

>>>
>>>
>>> --
>>> Martin Perina
>>> Manager, Software Engineering
>>> Red Hat Czech s.r.o.
>>>
>>
>>
>> --
>> Artur Socha
>> Senior Software Engineer, RHV
>> Red Hat
>>
>
>
> --
>
> Sandro Bonazzola
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>
> Red Hat EMEA 
>
> sbona...@redhat.com
> 
>
> *Red Hat respects your work life balance. Therefore there is no need to
> answer this email out of your office hours.*
>
>
>

-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com


*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*
___
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/YPDAG2AY425PUNXJRTOEY6BZ6OCOFQL3/

[ovirt-devel] Re: Failed CI for engine patches - java-client-kubevirt otopi

[Sandro Bonazzola]

Il giorno gio 25 nov 2021 alle ore 20:46 Ehud Yonasi 
ha scritto:

> Indeed Martin, I can see it now.
> We have an issue reflecting the new resources server, probably dns or
> something related.
>
> Meanwhile Shani, I suggest that you change the resources server in your
> automation/*.repos file to:
> https://resources02.phx.ovirt.org/repos/ovirt/tested/master/rpm/el8
>
> We have someone already looking into it already and we hope CI will be
> fixed soon.
> Apologies.
>

Please don't require any ovirt.org repository anymore in build roots of any
test or build job.
Either use CentOS Virt SIG repos or COPR repos.
We are dismissing ovirt-master-snapshot completely.




>
> On 25 Nov 2021, at 18:03, Martin Perina  wrote:
>
>
>
> On Thu, Nov 25, 2021 at 2:04 PM Ehud Yonasi  wrote:
>
>> So I am not sure where the dependency came from, but as I can see from
>> otopi repo it is only realsing to ovirt-4.3 on resources at the moment.
>>
>
> Not true, otopi is configured correctly:
>
> master -> ovirt-master
> https://github.com/oVirt/otopi/blob/master/.ovirtci.yaml
>
> otopi-1..9 -> ovirt-4.4
> https://github.com/oVirt/otopi/blob/otopi-1.9/.ovirtci.yaml
>
> Similar situation is with java-client-kubevirt, which should also be
> correctly setup:
>
> master -> ovirt-master, ovirt-4.4
> https://github.com/oVirt/java-client-kubevirt/blob/master/.stdci.yaml
>
> And I had to mention that similar situation we had for
> ovirt-jboss-modules-maven-plugin, which magically disappeared from tested
> repo cca 2 weeks ago and I needed to re-merge last patch to get the build
> there again. And also here everything seems correct to me:
>
>
> https://github.com/oVirt/ovirt-jboss-modules-maven-plugin/blob/master/automation.yaml
>
>
> All of those packages are included in oVirt project for quite long time,
> so the issue is somewhere in the Jenkins CI
>
>
>> Maybe Sandro can help with that?
>>
>> On Thu, Nov 25, 2021 at 2:46 PM Shani Leviim  wrote:
>>
>>> Hi Ehud,
>>> Honestly - I have no idea.
>>> This failure is from today, but in the patches, there is a series of CI
>>> failures while trying to build the patch - all failures while trying to
>>> build the engine.
>>>
>>>
>>> *Regards,*
>>>
>>> *Shani Leviim*
>>>
>>>
>>> On Thu, Nov 25, 2021 at 2:19 PM Ehud Yonasi  wrote:
>>>
 Hi Shani and Artur,

 I didn't find otopi and that java-client-kubevirt package in the repos
 listed inside the run. was it there in the first place?

 Artur, It seems the centos mirrors were not available during the time
 of the build, could you please re-trigger it and update if it's working for
 you now?

 Thanks,
 Ehud.

 On Thu, Nov 25, 2021 at 1:28 PM Artur Socha  wrote:

> I could also add that I am currently having an issue with accessing
> Centos stream 8 AppStream repo (timed out). See [1] . Perhaps that somehow
> related?
>
> [1]
> https://jenkins.ovirt.org/job/vdsm-jsonrpc-java_standard-check-patch/187/console
>
> Artur
>
> On Thu, Nov 25, 2021 at 11:50 AM Shani Leviim 
> wrote:
>
>> Hi,
>> I have a series of engine patches that keep failing although the
>> chain is rebased on the latest master.
>> I ran 'ci build' a couple of minutes ago and it failed with this one:
>> 11:08:45 No match for argument: otopi
>> 11:08:45 Error: Unable to find a match: java-client-kubevirt otopi
>>
>> https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/15286/console
>>
>> The engine patches:
>>
>> https://gerrit.ovirt.org/q/topic:%22copy-template-mbs-disk%22+(status:open%20OR%20status:merged)
>>
>> Can someone assist, please?
>>
>>
>> *Regards,*
>>
>> *Shani Leviim*
>> ___
>> 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/VUYJRGNY6X7UYZ6PQBQGVENE5LVFGN3O/
>>
>
>
> --
> Artur Socha
> Senior Software Engineer, RHV
> Red Hat
> ___
> 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/M6XM7FS4PD4E6USDK433IQDYIS7LJLQ2/
>
 ___
>> 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:
>>