Jenkins build is back to normal : system-sync_mirrors-centos-updates-el7-x86_64 #897

[jenkins]

See 


___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

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

[oVirt Jenkins]

A system test invoked by the "ovirt-master" change queue including change
81892,6 (ovirt-engine) failed. However, this change seems not to be the root
cause for this failure. Change 82615,5 (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 82615,5 (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/81892/6

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/82615/5

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3289/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 82859, 4 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

[oVirt Jenkins]

A system test invoked by the "ovirt-master" change queue including change
82859,4 (ovirt-engine) failed. However, this change seems not to be the root
cause for this failure. Change 82615,5 (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 82615,5 (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/82859/4

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/82615/5

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3286/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 82769, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

[oVirt Jenkins]

A system test invoked by the "ovirt-master" change queue including change
82769,3 (ovirt-engine) failed. However, this change seems not to be the root
cause for this failure. Change 82615,5 (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 82615,5 (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/82769/3

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/82615/5

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3282/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 82558, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

[oVirt Jenkins]

A system test invoked by the "ovirt-master" change queue including change
82558,2 (ovirt-engine) failed. However, this change seems not to be the root
cause for this failure. Change 82615,5 (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 82615,5 (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/82558/2

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/82615/5

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3278/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

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

[oVirt Jenkins]

A system test invoked by the "ovirt-master" change queue including change
82001,6 (ovirt-engine) failed. However, this change seems not to be the root
cause for this failure. Change 82615,5 (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 82615,5 (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/82001/6

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/82615/5

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3274/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

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

[oVirt Jenkins]

A system test invoked by the "ovirt-master" change queue including change
82000,6 (ovirt-engine) failed. However, this change seems not to be the root
cause for this failure. Change 82615,5 (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 82615,5 (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/82000/6

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/82615/5

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3270/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 81995, 7 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

[oVirt Jenkins]

A system test invoked by the "ovirt-master" change queue including change
81995,7 (ovirt-engine) failed. However, this change seems not to be the root
cause for this failure. Change 82615,5 (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 82615,5 (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/81995/7

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/82615/5

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3266/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] ovirt-release_4.2_build-artifacts-fc27-x86_64 - Build # 11 - Fixed!

[jenkins]

Project: 
http://jenkins.ovirt.org/job/ovirt-release_4.2_build-artifacts-fc27-x86_64/ 
Build: 
http://jenkins.ovirt.org/job/ovirt-release_4.2_build-artifacts-fc27-x86_64/11/
Build Number: 11
Build Status:  Fixed
Triggered By: Started by timer

-
Changes Since Last Success:
-
Changes for Build #10
No changes

Changes for Build #11
[Sandro Bonazzola] packaging: add f27 support

[Barak Korren] Enable GitHub post-merge jobs in production




-
Failed Tests:
-
No tests ran.___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] ovirt-release_4.2_build-artifacts-fc26-x86_64 - Build # 45 - Fixed!

[jenkins]

Project: 
http://jenkins.ovirt.org/job/ovirt-release_4.2_build-artifacts-fc26-x86_64/ 
Build: 
http://jenkins.ovirt.org/job/ovirt-release_4.2_build-artifacts-fc26-x86_64/45/
Build Number: 45
Build Status:  Fixed
Triggered By: Started by timer

-
Changes Since Last Success:
-
Changes for Build #44
No changes

Changes for Build #45
[Sandro Bonazzola] packaging: add f27 support

[Barak Korren] Enable GitHub post-merge jobs in production




-
Failed Tests:
-
No tests ran.___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] ovirt-release_master_build-artifacts-el7-x86_64 - Build # 542 - Fixed!

[jenkins]

Project: 
http://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-el7-x86_64/ 
Build: 
http://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-el7-x86_64/542/
Build Number: 542
Build Status:  Fixed
Triggered By: Started by timer

-
Changes Since Last Success:
-
Changes for Build #541
No changes

Changes for Build #542
[Sandro Bonazzola] packaging: add f27 support

[Eyal Edri] remove getbadges Jenkins integration

[Barak Korren] Enable GitHub post-merge jobs in production




-
Failed Tests:
-
No tests ran.___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 81946, 5 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

[oVirt Jenkins]

A system test invoked by the "ovirt-master" change queue including change
81946,5 (ovirt-engine) failed. However, this change seems not to be the root
cause for this failure. Change 82615,5 (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 82615,5 (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/81946/5

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/82615/5

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3262/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

oVirt infra daily report - unstable production jobs - 477

[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/477//artifact/exported-artifacts/upstream_report.html

Cheers,
Jenkins
 
 
 
 RHEVM CI Jenkins Daily Report - 17/10/2017
 
00 Unstable Critical
 
   
   ovirt-master_change-queue-tester
   
   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.

   
   
   
   system-sync_mirrors-centos-updates-el7-x86_64
   
   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
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 82253, 17 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

[oVirt Jenkins]

A system test invoked by the "ovirt-master" change queue including change
82253,17 (ovirt-engine) failed. However, this change seems not to be the root
cause for this failure. Change 82615,5 (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 82615,5 (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/82253/17

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/82615/5

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3257/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 82782, 5 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

[oVirt Jenkins]

A system test invoked by the "ovirt-master" change queue including change
82782,5 (ovirt-engine) failed. However, this change seems not to be the root
cause for this failure. Change 82615,5 (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 82615,5 (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/82782/5

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/82615/5

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3253/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: [CQ]: 82785, 5 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

[Yedidyah Bar David]

On Tue, Oct 17, 2017 at 10:38 PM, oVirt Jenkins  wrote:
> A system test invoked by the "ovirt-master" change queue including change
> 82785,5 (ovirt-engine) failed. However, this change seems not to be the root
> cause for this failure. Change 82615,5 (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 82615,5 (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/82785/5
>
> For further details about the change that seems to be the root cause behind 
> the
> testing failures see:
> https://gerrit.ovirt.org/#/c/82615/5
>
> For failed test results see:
> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3248/

Should be fixed temporarily by:

https://gerrit.ovirt.org/82894

Once 4.1.7 is out, this should not be needed. Then, we should merge the
two other patches linked from the same bug. One reverts it, other
requires 4.1.7.
-- 
Didi
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 82785, 5 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

[oVirt Jenkins]

A system test invoked by the "ovirt-master" change queue including change
82785,5 (ovirt-engine) failed. However, this change seems not to be the root
cause for this failure. Change 82615,5 (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 82615,5 (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/82785/5

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/82615/5

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3248/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 82252, 15 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

[oVirt Jenkins]

A system test invoked by the "ovirt-master" change queue including change
82252,15 (ovirt-engine) failed. However, this change seems not to be the root
cause for this failure. Change 82615,5 (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 82615,5 (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/82252/15

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/82615/5

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3243/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 82249, 12 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

[oVirt Jenkins]

A system test invoked by the "ovirt-master" change queue including change
82249,12 (ovirt-engine) failed. However, this change seems not to be the root
cause for this failure. Change 82615,5 (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 82615,5 (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/82249/12

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/82615/5

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3237/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Jenkins build is back to normal : system-sync_mirrors-epel-el6-x86_64 #823

[jenkins]

See 


___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1699) Add a 4.2 CQ flow

[Barak Korren (oVirt JIRA)]

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

Barak Korren reassigned OVIRT-1699:
---

  Assignee: Barak Korren  (was: infra)
Issue Type: New Feature  (was: Task)

> Add a 4.2 CQ flow 
> --
>
> Key: OVIRT-1699
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1699
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>  Components: oVirt CI
>Reporter: eyal edri
>Assignee: Barak Korren
>
> As discussed, we need to start preparing a 4.2 flow for CQ so projects which 
> branched for 4.2 will be able to publish their artifacts and also to start 
> preparing the work for the stable branch of 4.2 due in the coming months.
> Initial work for running OST On 4.2 is done via: 
> https://gerrit.ovirt.org/#/c/81969/ 
> Which is basically a clone of 4.1, with empty 4.2 tested repo for now ( 
> disabled for now ).
> Once we start getting more and more projects into the 4.2 branch, we can also 
> move to run 4.2 tests ( which will fail now because they need code from 
> master )



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100066)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 82514, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

[oVirt Jenkins]

A system test invoked by the "ovirt-master" change queue including change
82514,3 (ovirt-engine) failed. However, this change seems not to be the root
cause for this failure. Change 82615,5 (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 82615,5 (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/82514/3

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/82615/5

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3233/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1710) Merge rights to ovirg-guest-agent

[Barak Korren (oVirt JIRA)]

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

Barak Korren reassigned OVIRT-1710:
---

Assignee: Barak Korren  (was: infra)

> Merge rights to ovirg-guest-agent
> -
>
> Key: OVIRT-1710
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1710
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>  Components: Gerrit/git
>Reporter: Tomáš Golembiovský
>Assignee: Barak Korren
>Priority: High
>
> Hi,
> because Vinzenz Feenstra does not work on oVirt anymore and
> ovirt-guest-agent fell into my lap I would like to ask about merge
> rights to the project on Gerrit. Would that be possible?
> Thanks,
> Tomas
> -- 
> Tomáš Golembiovský 



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100066)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1710) Merge rights to ovirg-guest-agent

[Barak Korren (oVirt JIRA)]

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

Barak Korren updated OVIRT-1710:

Component/s: Gerrit/git
  Epic Link: OVIRT-403
 Issue Type: Task  (was: By-EMAIL)
   Priority: High  (was: Medium)

> Merge rights to ovirg-guest-agent
> -
>
> Key: OVIRT-1710
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1710
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>  Components: Gerrit/git
>Reporter: Tomáš Golembiovský
>Assignee: infra
>Priority: High
>
> Hi,
> because Vinzenz Feenstra does not work on oVirt anymore and
> ovirt-guest-agent fell into my lap I would like to ask about merge
> rights to the project on Gerrit. Would that be possible?
> Thanks,
> Tomas
> -- 
> Tomáš Golembiovský 



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100066)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1710) Merge rights to ovirg-guest-agent

[Barak Korren (oVirt JIRA)]

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

Barak Korren updated OVIRT-1710:

Epic Link: OVIRT-403

> Merge rights to ovirg-guest-agent
> -
>
> Key: OVIRT-1710
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1710
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>  Components: Gerrit/git
>Reporter: Tomáš Golembiovský
>Assignee: infra
>
> Hi,
> because Vinzenz Feenstra does not work on oVirt anymore and
> ovirt-guest-agent fell into my lap I would like to ask about merge
> rights to the project on Gerrit. Would that be possible?
> Thanks,
> Tomas
> -- 
> Tomáš Golembiovský 



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100066)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1710) Merge rights to ovirg-guest-agent

[Barak Korren (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=35158#comment-35158
 ] 

Barak Korren commented on OVIRT-1710:
-

No problem for us to do that from a technical standpoint. But I'm not sure who 
should approve such policy decision. 

The other people in the maintainers group are [~ih...@redhat.com] and 
[~bazu...@redhat.com] which are also not working on ovirt any moe, so who owns 
this ATM?

I think the best approach would be to open a thread on 
[de...@ovirt.org|mailto:de...@ovirt.org], announce you are taking ownership and 
get +1 votes...

> Merge rights to ovirg-guest-agent
> -
>
> Key: OVIRT-1710
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1710
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Tomáš Golembiovský
>Assignee: infra
>
> Hi,
> because Vinzenz Feenstra does not work on oVirt anymore and
> ovirt-guest-agent fell into my lap I would like to ask about merge
> rights to the project on Gerrit. Would that be possible?
> Thanks,
> Tomas
> -- 
> Tomáš Golembiovský 



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100066)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1708) Add a mirror for the FC27 'updates' repo.

[Barak Korren (oVirt JIRA)]

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

Barak Korren reassigned OVIRT-1708:
---

Assignee: Evgheni Dereveanchin  (was: infra)

> Add a mirror for the FC27 'updates' repo.
> -
>
> Key: OVIRT-1708
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1708
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Repositories Mgmt
>Reporter: Barak Korren
>Assignee: Evgheni Dereveanchin
>  Labels: fedora, mirrors
>
> Just like we did for FC26, we recently added a mirror for FC27. And since its 
> not released yet, we can't add an 'updates' mirror.
> This ticket is for adding the FC27 'updates' mirror once FC27 is released.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100066)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1710) Merge rights to ovirg-guest-agent

[oVirt JIRA]

Tomáš Golembiovský created OVIRT-1710:
-

 Summary: Merge rights to ovirg-guest-agent
 Key: OVIRT-1710
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1710
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Tomáš Golembiovský
Assignee: infra


Hi,

because Vinzenz Feenstra does not work on oVirt anymore and
ovirt-guest-agent fell into my lap I would like to ask about merge
rights to the project on Gerrit. Would that be possible?

Thanks,

Tomas

-- 
Tomáš Golembiovský 



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100066)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1709) provision Persistent Storage for OpenShift

[Evgheni Dereveanchin (oVirt JIRA)]

Evgheni Dereveanchin created OVIRT-1709:
---

 Summary: provision Persistent Storage for OpenShift
 Key: OVIRT-1709
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1709
 Project: oVirt - virtualization made easy
  Issue Type: Improvement
Reporter: Evgheni Dereveanchin
Assignee: infra


The OpenShift instance in PHX currently does not have any Persistent Storage 
assigned to it which is needed for things like databases and other important 
data. Opening this ticket to track how many volumes we may need and attach them.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100066)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] ovirt-appliance_ovirt-4.2_build-artifacts-el7-x86_64 - Build # 7 - Failure!

[jenkins]

Project: 
http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.2_build-artifacts-el7-x86_64/
 
Build: 
http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.2_build-artifacts-el7-x86_64/7/
Build Number: 7
Build Status:  Failure
Triggered By: Started by timer

-
Changes Since Last Success:
-
Changes for Build #7
[Sandro Bonazzola] ovirt-guest-agent: dropping fc25

[Sandro Bonazzola] ovirt-wgt: drop legacy jobs

[Sandro Bonazzola] repoman: drop el6 jobs

[Barak Korren] Add Fedora rawhide support

[Sandro Bonazzola] nightly-4.1: move ovirt-wgt to standard ci

[Barak Korren] Capture head commit info from GitHub events

[Barak Korren] Added submission of GitHub changes to CQ

[Barak Korren] Generalized CQ tester pipeline code

[Sandro Bonazzola] jasper-reports: drop job

[Eyal Edri] remove getbadges Jenkins integration

[Yuval Turgeman] automation: view install log in console




-
Failed Tests:
-
No tests ran.___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: upgrade-from-release-suite-master failure reason

[Maor Lipchuk]

Thanks for the info

On Tue, Oct 17, 2017 at 1:52 PM, Daniel Belenky  wrote:

> Hi Maor,
>
> This patch https://gerrit.ovirt.org/#/c/82615/5 to engine introduced a
> bug in the upgrade process,
> so every patch that is based on top of this one will fail upgrade until a
> fix will be merged.
>
> On Tue, Oct 17, 2017 at 12:55 PM, Maor Lipchuk 
> wrote:
>
>> Hi all,
>>
>> I ran several OST on a patchset I'm about to merge.
>> The standard OST tests finished with success (see [1]), although
>> upgrade-from-release-suite-master fail for an odd reason of "Failed to
>> clear zombie commands." (see [2])
>>
>> I don't recall any changes related to upgrade, so I was wondering if
>> maybe I'm missing something with my patchset, or it is a known issue
>> not related to my changes?
>>
>> [1]
>> http://jenkins.ovirt.org/job/ovirt-system-tests_manual/1384/
>> http://jenkins.ovirt.org/job/ovirt-system-tests_manual/1386/
>>
>> [2] http://jenkins.ovirt.org/job/ovirt-system-tests_manual/1385/ :
>> [ ERROR ] Failed to execute stage 'Setup validation': Failed to clear
>> zombie commands. Please access support in attempt to resolve the
>> problem
>>
>> Regards,
>> Maor
>> ___
>> Infra mailing list
>> Infra@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/infra
>>
>
>
>
> --
>
> DANIEL BELENKY
>
> RHV DEVOPS
>
> EMEA VIRTUALIZATION R
> 
>
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 82799, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

[oVirt Jenkins]

A system test invoked by the "ovirt-master" change queue including change
82799,2 (ovirt-engine) failed. However, this change seems not to be the root
cause for this failure. Change 82615,5 (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 82615,5 (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/82799/2

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/82615/5

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3221/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: Infineon firmware security issues

[Michael Scherer]

Le mardi 17 octobre 2017 à 13:33 +0300, Eyal Edri a écrit :
> Thanks,
> 
> So if I have an old YubiKey ( 2.43 ) I shouldn't be affected right?
> only V4
> is ?

That's what the post on yubico.com seems to imply. We do not know what
chipset is used in the key, so I can't give a educated guess. But I
hear people using yubikey neo weren't affected.

Now, only the CCID function is problematic, and only if you did
generate the ssh key on the chip (e.g., followed official doc on  https
://developers.yubico.com/PIV/Guides/SSH_with_PIV_and_PKCS11.html and
used "yubico-piv-tool -s 9a -a generate -o public.pem" )

If you imported the key, then that should be ok.

If you use the yubikey for non smartcard use (e.g. U2F, 2FA for RH VPN
or similar system ), that's ok too.



> On Tue, Oct 17, 2017 at 12:56 PM, Marc Dequènes (Duck)
> 
> wrote:
> 
> > Quack,
> > 
> > So the news (thanks Misc for the alert):
> > 
> > https://www.infineon.com/cms/en/product/promopages/rsa-
> > update/rsa-background
> > 
> > This affects Yubikeys and other hardware:
> >   https://www.yubico.com/support/security-advisories/ysa-2017-01/
> > 
> > There's a nice tool to test if a key is vulnerable:
> >   https://github.com/crocs-muni/roca
> > 
> > I tested keys in the oVirt Puppet repository and none are affected.
> > 
> > You may check your other keys and ensure keys are checked in other
> > projects.
> > 
> > \_o<
> > 
> > 
> > ___
> > Infra mailing list
> > Infra@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> > 
> > 
> 
> 
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
-- 
Michael Scherer
Sysadmin, Community Infrastructure and Platform, OSAS



signature.asc
Description: This is a digitally signed message part
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: upgrade-from-release-suite-master failure reason

[Daniel Belenky]

Hi Maor,

This patch https://gerrit.ovirt.org/#/c/82615/5 to engine introduced a bug
in the upgrade process,
so every patch that is based on top of this one will fail upgrade until a
fix will be merged.

On Tue, Oct 17, 2017 at 12:55 PM, Maor Lipchuk  wrote:

> Hi all,
>
> I ran several OST on a patchset I'm about to merge.
> The standard OST tests finished with success (see [1]), although
> upgrade-from-release-suite-master fail for an odd reason of "Failed to
> clear zombie commands." (see [2])
>
> I don't recall any changes related to upgrade, so I was wondering if
> maybe I'm missing something with my patchset, or it is a known issue
> not related to my changes?
>
> [1]
> http://jenkins.ovirt.org/job/ovirt-system-tests_manual/1384/
> http://jenkins.ovirt.org/job/ovirt-system-tests_manual/1386/
>
> [2] http://jenkins.ovirt.org/job/ovirt-system-tests_manual/1385/ :
> [ ERROR ] Failed to execute stage 'Setup validation': Failed to clear
> zombie commands. Please access support in attempt to resolve the
> problem
>
> Regards,
> Maor
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>



-- 

DANIEL BELENKY

RHV DEVOPS

EMEA VIRTUALIZATION R

___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: Infineon firmware security issues

[Michael Scherer]

Le mardi 17 octobre 2017 à 13:36 +0300, Eyal Edri a écrit :
> On Tue, Oct 17, 2017 at 1:31 PM, Michael Scherer  >
> wrote:
> 
> > Le mardi 17 octobre 2017 à 18:56 +0900, Marc Dequènes (Duck) a
> > écrit :
> > > Quack,
> > > 
> > > So the news (thanks Misc for the alert):
> > > 
> > > https://www.infineon.com/cms/en/product/promopages/rsa-update/rsa
> > > -bac
> > > kground
> > > 
> > > This affects Yubikeys and other hardware:
> > >   https://www.yubico.com/support/security-advisories/ysa-2017-01/
> > > 
> > > There's a nice tool to test if a key is vulnerable:
> > >   https://github.com/crocs-muni/roca
> > > 
> > > I tested keys in the oVirt Puppet repository and none are
> > > affected.
> > > 
> > > You may check your other keys and ensure keys are checked in
> > > other
> > > projects.
> > 
> > Ideally, if someone could verify the key in Gerrit, it would be
> > helpful. I removed mine, but I suspect i am not the only one who
> > tried
> > to follow best practices :)
> > 
> 
> If you run the tool locally on your .ssh/ dir, it should include
> already
> the public key you have on Gerrit no?

Well, I know my key is vulnerable, got notified by Fedora and Github.
But I just do not know where I used it exactly, because I have account
everywhere, and that's likely that I may forget it in some place.

> We'll need to check if its possible to run that tool on Gerrit and if
> the
> keys are even stored on the fs and not inside the Gerrit DB.

If they are in the DB, we can extract it with a sql request ILMHO.

I plan to look at Gluster's gerrit instance once I finish my own
cleanup and key generation, which is a rather tedious task (cause I
also found out that my backup key is not working anymore for a unknown
reason).

-- 
Michael Scherer
Sysadmin, Community Infrastructure and Platform, OSAS



signature.asc
Description: This is a digitally signed message part
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: Infineon firmware security issues

[Eyal Edri]

On Tue, Oct 17, 2017 at 1:31 PM, Michael Scherer 
wrote:

> Le mardi 17 octobre 2017 à 18:56 +0900, Marc Dequènes (Duck) a écrit :
> > Quack,
> >
> > So the news (thanks Misc for the alert):
> >
> > https://www.infineon.com/cms/en/product/promopages/rsa-update/rsa-bac
> > kground
> >
> > This affects Yubikeys and other hardware:
> >   https://www.yubico.com/support/security-advisories/ysa-2017-01/
> >
> > There's a nice tool to test if a key is vulnerable:
> >   https://github.com/crocs-muni/roca
> >
> > I tested keys in the oVirt Puppet repository and none are affected.
> >
> > You may check your other keys and ensure keys are checked in other
> > projects.
>
> Ideally, if someone could verify the key in Gerrit, it would be
> helpful. I removed mine, but I suspect i am not the only one who tried
> to follow best practices :)
>

If you run the tool locally on your .ssh/ dir, it should include already
the public key you have on Gerrit no?
We'll need to check if its possible to run that tool on Gerrit and if the
keys are even stored on the fs and not inside the Gerrit DB.


>
>
> Debian, Github and Fedora did sent alert to people affected, and I am
> in the process of changing my key from the 50 to 60 place where I used
> it and I assume most affected people will be aware somehow, but
> automated removal from vulnerable systems would surely help.
>
> --
> Michael Scherer
> Sysadmin, Community Infrastructure and Platform, OSAS
>
>
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>


-- 

Eyal edri


MANAGER

RHV DevOps

EMEA VIRTUALIZATION R


Red Hat EMEA 
 TRIED. TESTED. TRUSTED. 
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: Infineon firmware security issues

[Eyal Edri]

Thanks,

So if I have an old YubiKey ( 2.43 ) I shouldn't be affected right? only V4
is ?

On Tue, Oct 17, 2017 at 12:56 PM, Marc Dequènes (Duck) 
wrote:

> Quack,
>
> So the news (thanks Misc for the alert):
>
> https://www.infineon.com/cms/en/product/promopages/rsa-
> update/rsa-background
>
> This affects Yubikeys and other hardware:
>   https://www.yubico.com/support/security-advisories/ysa-2017-01/
>
> There's a nice tool to test if a key is vulnerable:
>   https://github.com/crocs-muni/roca
>
> I tested keys in the oVirt Puppet repository and none are affected.
>
> You may check your other keys and ensure keys are checked in other
> projects.
>
> \_o<
>
>
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>


-- 

Eyal edri


MANAGER

RHV DevOps

EMEA VIRTUALIZATION R


Red Hat EMEA 
 TRIED. TESTED. TRUSTED. 
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: Infineon firmware security issues

[Michael Scherer]

Le mardi 17 octobre 2017 à 18:56 +0900, Marc Dequènes (Duck) a écrit :
> Quack,
> 
> So the news (thanks Misc for the alert):
> 
> https://www.infineon.com/cms/en/product/promopages/rsa-update/rsa-bac
> kground
> 
> This affects Yubikeys and other hardware:
>   https://www.yubico.com/support/security-advisories/ysa-2017-01/
> 
> There's a nice tool to test if a key is vulnerable:
>   https://github.com/crocs-muni/roca
> 
> I tested keys in the oVirt Puppet repository and none are affected.
> 
> You may check your other keys and ensure keys are checked in other
> projects.

Ideally, if someone could verify the key in Gerrit, it would be
helpful. I removed mine, but I suspect i am not the only one who tried
to follow best practices :)


Debian, Github and Fedora did sent alert to people affected, and I am
in the process of changing my key from the 50 to 60 place where I used
it and I assume most affected people will be aware somehow, but
automated removal from vulnerable systems would surely help. 

-- 
Michael Scherer
Sysadmin, Community Infrastructure and Platform, OSAS



signature.asc
Description: This is a digitally signed message part
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] standard-enqueue - Build #5763 - FAILURE!

[jenkins]

Build: http://jenkins.ovirt.org/job/standard-enqueue/5763/
Build Name: #5763
Build Description: Gerrit: 82868 - ovirt-engine-api-model (4.2)
Build Status: FAILURE
Gerrit change: https://gerrit.ovirt.org/82868
- title: Document HostService.java
- project: ovirt-engine-api-model
- branch: model_4.2
- author: Juan Hernandez ___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Infineon firmware security issues

[Duck]

Quack,

So the news (thanks Misc for the alert):

https://www.infineon.com/cms/en/product/promopages/rsa-update/rsa-background

This affects Yubikeys and other hardware:
  https://www.yubico.com/support/security-advisories/ysa-2017-01/

There's a nice tool to test if a key is vulnerable:
  https://github.com/crocs-muni/roca

I tested keys in the oVirt Puppet repository and none are affected.

You may check your other keys and ensure keys are checked in other
projects.

\_o<



signature.asc
Description: OpenPGP digital signature
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

upgrade-from-release-suite-master failure reason

[Maor Lipchuk]

Hi all,

I ran several OST on a patchset I'm about to merge.
The standard OST tests finished with success (see [1]), although
upgrade-from-release-suite-master fail for an odd reason of "Failed to
clear zombie commands." (see [2])

I don't recall any changes related to upgrade, so I was wondering if
maybe I'm missing something with my patchset, or it is a known issue
not related to my changes?

[1]
http://jenkins.ovirt.org/job/ovirt-system-tests_manual/1384/
http://jenkins.ovirt.org/job/ovirt-system-tests_manual/1386/

[2] http://jenkins.ovirt.org/job/ovirt-system-tests_manual/1385/ :
[ ERROR ] Failed to execute stage 'Setup validation': Failed to clear
zombie commands. Please access support in attempt to resolve the
problem

Regards,
Maor
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1708) Add a mirror for the FC27 'updates' repo.

[Barak Korren (oVirt JIRA)]

Barak Korren created OVIRT-1708:
---

 Summary: Add a mirror for the FC27 'updates' repo.
 Key: OVIRT-1708
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1708
 Project: oVirt - virtualization made easy
  Issue Type: Improvement
  Components: Repositories Mgmt
Reporter: Barak Korren
Assignee: infra


Just like we did for FC26, we recently added a mirror for FC27. And since its 
not released yet, we can't add an 'updates' mirror.

This ticket is for adding the FC27 'updates' mirror once FC27 is released.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100066)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1708) Add a mirror for the FC27 'updates' repo.

[Barak Korren (oVirt JIRA)]

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

Barak Korren updated OVIRT-1708:

Epic Link: OVIRT-403

> Add a mirror for the FC27 'updates' repo.
> -
>
> Key: OVIRT-1708
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1708
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Repositories Mgmt
>Reporter: Barak Korren
>Assignee: infra
>  Labels: fedora, mirrors
>
> Just like we did for FC26, we recently added a mirror for FC27. And since its 
> not released yet, we can't add an 'updates' mirror.
> This ticket is for adding the FC27 'updates' mirror once FC27 is released.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100066)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1707) The infra docs index page needs a face lift

[Barak Korren (oVirt JIRA)]

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

Barak Korren updated OVIRT-1707:

Epic Link: OVIRT-403

> The infra docs index page needs a face lift
> ---
>
> Key: OVIRT-1707
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1707
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: General
>Reporter: Barak Korren
>Assignee: infra
>Priority: High
>  Labels: documentation
>
> The infra-docs index page is the first page about the oVirt infra team that 
> anyone will see, but it looks bad. Here are a few issues with it:
> # The page title was probably auto-generated by GitHub and looks wrong
> # The page contains no text. There needs to be some short 2-3 line 
> explanation about what is this page and what could be found in it. The sub 
> sections should probably also include 1-2 lines each about which documents 
> can be found in them.
> # Some links have opaque non-descriptive text. For example "Communication" 
> should probably be "Communicating with the oVirt infra team".
> # The documents and sections are listed in semi-random order. Instead, they 
> should be ordered in such a way that the more important public-facing 
> documents are closer to the top
> # The "general" section is just a random collection of things. It should 
> probably be split apart into more specific sections like "Gerrit", 
> "Contribution guidelines" and "Procedures for infra-team members".



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100066)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1707) The infra docs index page needs a face lift

[Barak Korren (oVirt JIRA)]

Barak Korren created OVIRT-1707:
---

 Summary: The infra docs index page needs a face lift
 Key: OVIRT-1707
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1707
 Project: oVirt - virtualization made easy
  Issue Type: Improvement
  Components: General
Reporter: Barak Korren
Assignee: infra
Priority: High


The infra-docs index page is the first page about the oVirt infra team that 
anyone will see, but it looks bad. Here are a few issues with it:
# The page title was probably auto-generated by GitHub and looks wrong
# The page contains no text. There needs to be some short 2-3 line explanation 
about what is this page and what could be found in it. The sub sections should 
probably also include 1-2 lines each about which documents can be found in them.
# Some links have opaque non-descriptive text. For example "Communication" 
should probably be "Communicating with the oVirt infra team".
# The documents and sections are listed in semi-random order. Instead, they 
should be ordered in such a way that the more important public-facing documents 
are closer to the top
# The "general" section is just a random collection of things. It should 
probably be split apart into more specific sections like "Gerrit", 
"Contribution guidelines" and "Procedures for infra-team members".



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100066)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: ovirt-system-tests_manual against specific version

[Daniel Belenky]

On Mon, Oct 16, 2017 at 6:51 PM, Eyal Edri  wrote:

>
>
> On Mon, Oct 16, 2017 at 6:48 PM, Martin Perina  wrote:
>
>>
>>
>> On Mon, Oct 16, 2017 at 5:42 PM, Eyal Edri  wrote:
>>
>>>
>>>
>>> On Mon, Oct 16, 2017 at 6:18 PM, Miroslava Voglova 
>>> wrote:
>>>
 Hi,

 I need to test patch for upgrade from newest 4.1.7.
 Upgrade_from_release gives me ovirt-engine-4.1.6.2.
 Is there some way how to choose particular version?

>>>
>>> If you need to test upgrade from newer engine, you can specify the link
>>> to the newer engine RPMs from build-artifacts job.
>>> It works well for basic suite, though not sure we tested how it affects
>>> upgrade suite.
>>>
>>> If it doesn't work, you can always run it locally and tweak the relevant
>>> repos.
>>>
>>> What are you trying to test? upgrade from 4.1.7 latest to master?
>>>
>>
>> ​Right we need to test upgrade from latest 4.1.z (latest tested) to the
>> master with our patch. But unless I miss something, we can ​specify repo
>> only for target version of the upgrade, but not the source one. It seems
>> that upgrade OST always takes latest released as source for upgrade. Or am
>> I missing something?
>>
>>
> I rerun you job [1], now using latest tested, if that doesn't work, we'll
> probably need to run it locally with some update to the reposync file
>
> [1] http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/
> ovirt-system-tests_manual/1378/console
>

I see that in the test you've attached in your mail used
ovirt-engine-setup-4.2.0 which was built in
http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-on-demand-el7-x86_64/520
.
Please note that using "*latest-tested*" as a fallback repo is risky (your
test might fail because this repo is being changed constantly) and is* not
recommended* at all. It has nothing to do with the RPMs that you want to
fetch from the CUSTOM_REPOS you've added.
Please feel free to ping me via IRC (dbelenky) #rhev-integ or #rhev-dev
with questions regarding the manual suite, I'll be happy to help :)
-- 

DANIEL BELENKY

RHV DEVOPS

EMEA VIRTUALIZATION R

___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #822

[jenkins]

See 


--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
Resetting working tree
 > git reset --hard # timeout=10
 > git clean -fdx # timeout=10
Pruning obsolete local branches
Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git
 > git --version # timeout=10
 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git 
 > +refs/heads/*:refs/remotes/origin/* --prune
 > git rev-parse origin/master^{commit} # timeout=10
Checking out Revision e6b384b087b966ad7895b5c8289a29e5957cac9c (origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f e6b384b087b966ad7895b5c8289a29e5957cac9c
Commit message: "remove getbadges Jenkins integration"
 > git rev-list e6b384b087b966ad7895b5c8289a29e5957cac9c # timeout=10
[system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe 
/tmp/jenkins6320395438582383974.sh
+ jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 
jenkins/data/mirrors-reposync.conf
Checking if mirror needs a resync
Traceback (most recent call last):
  File "/usr/bin/reposync", line 343, in 
main()
  File "/usr/bin/reposync", line 175, in main
my.doRepoSetup()
  File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in 
doRepoSetup
return self._getRepos(thisrepo, True)
  File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in 
_getRepos
self._repos.doSetup(thisrepo)
  File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup
self.retrieveAllMD()
  File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in 
retrieveAllMD
dl = repo._async and repo._commonLoadRepoXML(repo)
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1478, in 
_commonLoadRepoXML
self._revertOldRepoXML()
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1323, in 
_revertOldRepoXML
os.rename(old_data['old_local'], old_data['local'])
OSError: [Errno 2] No such file or directory
Build step 'Execute shell' marked build as failure
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 82586, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

[oVirt Jenkins]

A system test invoked by the "ovirt-master" change queue including change
82586,3 (ovirt-engine) failed. However, this change seems not to be the root
cause for this failure. Change 82615,5 (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 82615,5 (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/82586/3

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/82615/5

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3214/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.1 - Build # 63 - Fixed!

[jenkins]

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.1/ 
Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.1/63/
Build Number: 63
Build Status:  Fixed
Triggered By: Started by timer

-
Changes Since Last Success:
-
Changes for Build #62
[Yaniv Kaul] Allow to skip sync, to work offline

[Eyal Edri] remove getbadges Jenkins integration


Changes for Build #63
[Yaniv Kaul] Allow to skip sync, to work offline




-
Failed Tests:
-
All tests passed___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1706) [gerrit] create cli tool to automate the new project creation

[Shlomo Ben David (oVirt JIRA)]

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

Shlomo Ben David updated OVIRT-1706:

Epic Link: OVIRT-403

> [gerrit] create cli tool to automate the new project creation
> -
>
> Key: OVIRT-1706
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1706
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Shlomo Ben David
>Assignee: infra
>




--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100066)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1706) [gerrit] create cli tool to automate the new project creation

[Shlomo Ben David (oVirt JIRA)]

Shlomo Ben David created OVIRT-1706:
---

 Summary: [gerrit] create cli tool to automate the new project 
creation
 Key: OVIRT-1706
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1706
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: Shlomo Ben David
Assignee: infra






--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100066)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1706) [gerrit] create cli tool to automate the new project creation

[Shlomo Ben David (oVirt JIRA)]

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

Shlomo Ben David reassigned OVIRT-1706:
---

Assignee: Shlomo Ben David  (was: infra)

> [gerrit] create cli tool to automate the new project creation
> -
>
> Key: OVIRT-1706
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1706
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Shlomo Ben David
>Assignee: Shlomo Ben David
>




--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100066)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra