oVirt infra daily report - unstable production jobs - 861

2019-06-19 Thread jenkins
Good morning!

Attached is the HTML page with the jenkins status report. You can see it also 
here:
 - 
http://jenkins.ovirt.org/job/system_jenkins-report/861//artifact/exported-artifacts/upstream_report.html

Cheers,
Jenkins
 
 
 
 RHEVM CI Jenkins Daily Report - 19/06/2019
 
00 Unstable Critical
 
   
   ovirt-system-tests_hc-basic-suite-master
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   ovirt-system-tests_master_standard-poll-upstream-sources
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   ___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/BWBYT5TZ5ILIUS4FAOJGFTCDYHXULHQ3/


[JIRA] (OVIRT-2740) upgrade Gerrit to 2.14.20

2019-06-19 Thread Evgheni Dereveanchin (oVirt JIRA)

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Evgheni Dereveanchin reassigned OVIRT-2740:
---

Assignee: Evgheni Dereveanchin  (was: infra)

> upgrade Gerrit to 2.14.20
> -
>
> Key: OVIRT-2740
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2740
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Evgheni Dereveanchin
>Assignee: Evgheni Dereveanchin
>
> In order to proceed with OVIRT-1777 we need Gerrit at the latest 4.12 release 
> which is 4.12.20
> Since this is a minor release it only includes bug fixes and doesn't change 
> workflows so no major obstacles are expected. I've already upgraded Staging 
> the following way:
>  wget https://gerrit-releases.storage.googleapis.com/gerrit-2.14.20.war
>  systemctl stop gerrit
> 
>  java -jar gerrit-2.14.20.war init -d /home/gerrit2/review_site/
> start gerrit or reboot the system to apply updates



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100104)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/MBFDABQOW4LEKDDOQMBXGT5QP5SMIDZ6/


[JIRA] (OVIRT-2740) upgrade Gerrit to 2.14.20

2019-06-19 Thread Evgheni Dereveanchin (oVirt JIRA)
Evgheni Dereveanchin created OVIRT-2740:
---

 Summary: upgrade Gerrit to 2.14.20
 Key: OVIRT-2740
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2740
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: Evgheni Dereveanchin
Assignee: infra


In order to proceed with OVIRT-1777 we need Gerrit at the latest 4.12 release 
which is 4.12.20

Since this is a minor release it only includes bug fixes and doesn't change 
workflows so no major obstacles are expected. I've already upgraded Staging the 
following way:

 wget https://gerrit-releases.storage.googleapis.com/gerrit-2.14.20.war
 systemctl stop gerrit

 java -jar gerrit-2.14.20.war init -d /home/gerrit2/review_site/
start gerrit or reboot the system to apply updates



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100104)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/I6OQCCU2G4AIHBBPQN7TITU5HMQIXD2B/


Re: [CQ]: 087bbdf (v2v-conversion-host) failed "ovirt-master" system tests, but isn't the failure root cause

2019-06-19 Thread Dafna Ron
the failure is due to a build artifacts failure and its now have a passing
builds.


On Tue, Jun 18, 2019 at 11:19 PM oVirt Jenkins  wrote:

> A system test invoked by the "ovirt-master" change queue including change
> 087bbdf (v2v-conversion-host) failed. However, this change seems not to be
> the
> root cause for this failure. Change 8dd62a4 (v2v-conversion-host) 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 8dd62a4
> (v2v-conversion-host)
> 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://github.com/oVirt/v2v-conversion-host/commit/087bbdf3b804c1299edac1d1db5afe6207732a68
>
> For further details about the change that seems to be the root cause
> behind the
> testing failures see:
>
> https://github.com/oVirt/v2v-conversion-host/commit/8dd62a4ba67acf89e10b09d3c122413fe5592a11
>
> For failed test results see:
> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14613/
> ___
> Infra mailing list -- infra@ovirt.org
> To unsubscribe send an email to infra-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/infra@ovirt.org/message/RFYL4K4GEXKG72LBY5WPME3I4QV5HVQO/
>
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/AEBQRJOCFXDOSBFVWB73SDI4MCNE533V/


Re: [CQ]: 100778, 6 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause

2019-06-19 Thread Dafna Ron
this was a failed build-artifacts.
its now fixed as there are several passing builds after this one

On Wed, Jun 19, 2019 at 3:16 AM oVirt Jenkins  wrote:

> A system test invoked by the "ovirt-master" change queue including change
> 100778,6 (vdsm) failed. However, this change seems not to be the root
> cause for
> this failure. Change 100783,7 (vdsm) 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 100783,7 (vdsm) 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/100778/6
>
> For further details about the change that seems to be the root cause
> behind the
> testing failures see:
> https://gerrit.ovirt.org/#/c/100783/7
>
> For failed test results see:
> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14624/
> ___
> Infra mailing list -- infra@ovirt.org
> To unsubscribe send an email to infra-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/infra@ovirt.org/message/CHXVUBUQZO3OS2OQ2FWEGSFB2KS7F33V/
>
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/FNSPEESXJOPRYBRKKABJ3PUGILZ2R53X/


[JIRA] (OVIRT-2739) Builds on s390x fail again

2019-06-19 Thread Barak Korren (oVirt JIRA)

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren reassigned OVIRT-2739:
---

Assignee: Barak Korren  (was: infra)

> Builds on s390x fail again
> --
>
> Key: OVIRT-2739
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2739
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: Barak Korren
>
> I cannot see any reason for the failure in the pipeline logs, and there are
> no
> build logs.
> https://jenkins.ovirt.org/job/standard-manual-runner/329/
> https://jenkins.ovirt.org/job/standard-manual-runner/329//artifact/build-artifacts.build-py27.fc29.s390x/mock_logs/script/stdout_stderr.log
> The el7 x86_64 repo was created, so I can still use this build to run OST,
> but we need to fix this
> quickly, or disable the s390x builds until we have a stable solution.
> Nir



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100104)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/JUFNK7H322HJF73OOQNOYKD4RI2BVQHE/