[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5574 - FAILURE!

[jenkins]

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5574/,
Build Number: 5574,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5573 - FAILURE!

[jenkins]

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5573/,
Build Number: 5573,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5572 - FAILURE!

[jenkins]

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5572/,
Build Number: 5572,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5571 - FAILURE!

[jenkins]

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5571/,
Build Number: 5571,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

oVirt infra daily report - unstable production jobs - 244

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

Cheers,
Jenkins

 
 
 
 RHEVM CI Jenkins Daily Report - 27/02/2017
 
00 Unstable Critical
 
   
   ovirt_4.0_image-ng-system-tests
   
   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_4.1_hc-system-tests
   
   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_4.1_image-ng-system-tests
   
   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_master_hc-system-tests
   
   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_master_image-ng-system-tests
   
   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.

   
   
   
   repos_4.1_check-closure_el7_merged
   
   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.

   
   
   
   repos_4.1_check-closure_fc24_merged
   
   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.

   
   
   
   repos_master_check-closure_el7_merged
   
   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.

   
   
   
   repos_master_check-closure_fc24_merged
   
   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.

   
   
   
   test-repo_ovirt_experimental_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.

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

[JIRA] (OVIRT-1202) Need write access to http://resources.ovirt.org/repos/docs/

[eyal edri [Administrator] (oVirt JIRA)]

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

eyal edri [Administrator] commented on OVIRT-1202:
--

resources is a yum repository without external access, its a production system 
that is being used by all the CI system and holds official releases, its not a 
documentation placeholder.

Currently the oVirt documentation is scattered around GitHub pages ( like 
ovirt-sdk ) and on ovirt.org
Infra team maintains read the doc page to hold all the infra docs [1], you 
might consider doing the same for your project.
if its presentation/videos, then oVirt has its own youtube channel to hold such 
things.

If any of the above doesn't fit the need, then we need to think on an alternate 
solution, maybe to increase size on GitHub.
[~duck][~bprof...@redhat.com] - What sort of documentation solution is provided 
as part of the community cage? is there an option to extend the GitHub space 
limitation?

[1] infra-docs.readthedocs.org

> Need write access to http://resources.ovirt.org/repos/docs/
> ---
>
> Key: OVIRT-1202
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1202
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Marcin Mirecki
>Assignee: infra
>
> Can you please grant me write access on: 
> http://resources.ovirt.org/repos/docs/
> There is a need to host some docs (like presentations) on ovirt site. Ovirt 
> site itself is not a good place for this due to github space limitations. The 
> idea is to host the actual docs here, and link them on ovirt-site.



--
This message was sent by Atlassian JIRA
(v1000.784.2#100032)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5570 - FAILURE!

[jenkins]

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5570/,
Build Number: 5570,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5569 - FAILURE!

[jenkins]

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5569/,
Build Number: 5569,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5568 - FAILURE!

[jenkins]

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5568/,
Build Number: 5568,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5567 - FAILURE!

[jenkins]

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5567/,
Build Number: 5567,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5566 - FAILURE!

[jenkins]

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5566/,
Build Number: 5566,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5565 - FAILURE!

[jenkins]

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5565/,
Build Number: 5565,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-682) Improve CI logging

[Barak Korren (oVirt JIRA)]

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

Barak Korren commented on OVIRT-682:


One more thing we can do if we implement extended reporting to Gerrit as I 
suggested above, is let the CI system issue warnings, like for example if the 
job used external repos instead of mirrors.

> Improve CI logging
> --
>
> Key: OVIRT-682
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-682
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Jenkins
>Reporter: eyal edri [Administrator]
>Assignee: infra
>  Labels: standard-ci
>
> On Fri, Aug 12, 2016 at 8:08 PM, Nir Soffer  wrote:
> > Hi all,
> >
> > Lately vdsm builds are failing in the install packages stage with
> > this unhelpful error:
> >
> > 13:59:42 INFO: installing package(s): autoconf automake gdb ...
> > 13:59:53 ERROR: Command failed. See logs for output.
> >
> > I downloaded the logs.tgz file from
> > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-
> > x86_64/1154/artifact/exported-artifacts/logs.tgz
> >
> > And indeed in /./vdsm/logs/mocker-fedora-24-x86_64.fc24.install_packages/
> > root.log
> > I found found this error:
> >
> > DEBUG util.py:421:  Error: Package:
> > python-ioprocess-0.17.0-1.201608111609.gitbd272f2.fc24.noarch
> > (ovirt-snapshot)
> > DEBUG util.py:421: Requires: ioprocess =
> > 0.17.0-1.201608111609.gitbd272f2.fc24
> > DEBUG util.py:421: Available:
> > ioprocess-0.15.1-1.fc24.x86_64 (fedora)
> > DEBUG util.py:421: ioprocess = 0.15.1-1.fc24
> > DEBUG util.py:421: Available:
> > ioprocess-0.16.1-1.fc24.x86_64 (updates)
> > DEBUG util.py:421: ioprocess = 0.16.1-1.fc24
> > DEBUG util.py:421: Available:
> > ioprocess-0.17.0-1.201607121058.gitbd272f2.fc24.x86_64
> > (ovirt-snapshot)
> > DEBUG util.py:421: ioprocess =
> > 0.17.0-1.201607121058.gitbd272f2.fc24
> > DEBUG util.py:421: Available:
> > ioprocess-0.17.0-1.20160829.gitbd272f2.fc24.x86_64
> > (ovirt-snapshot)
> > DEBUG util.py:421: ioprocess =
> > 0.17.0-1.20160829.gitbd272f2.fc24
> >
> > So we have 2 issues here:
> >
> > 1. We need *all* errors in the console
> > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-
> > x86_64/1154/console
> Not sure its possible or easy to do, these errors usually come from mock
> and are not relevant to the code running on the console.
> I've cc'd infra-support and updated topic to track it and check our options.
> Going foward, we might want to install a log collector like logstash and
> then searching errors there should be much easier.
> >
> >
> > 2. Someone need to fix the ovirt-snapshot repository - it should have
> > the missing ioprocess
> > package.
> > Maybe the project xml is not correct?
> >
> > Nir
> >
> -- 
> Eyal Edri
> Associate Manager
> RHV DevOps
> EMEA ENG Virtualization R
> Red Hat Israel
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)



--
This message was sent by Atlassian JIRA
(v1000.784.2#100032)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5564 - FAILURE!

[jenkins]

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5564/,
Build Number: 5564,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1202) Need write access to http://resources.ovirt.org/repos/docs/

[Marcin Mirecki (oVirt JIRA)]

Marcin Mirecki created OVIRT-1202:
-

 Summary: Need write access to 
http://resources.ovirt.org/repos/docs/
 Key: OVIRT-1202
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1202
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: Marcin Mirecki
Assignee: infra


Can you please grant me write access on: http://resources.ovirt.org/repos/docs/

There is a need to host some docs (like presentations) on ovirt site. Ovirt 
site itself is not a good place for this due to github space limitations. The 
idea is to host the actual docs here, and link them on ovirt-site.





--
This message was sent by Atlassian JIRA
(v1000.784.2#100032)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5563 - FAILURE!

[jenkins]

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5563/,
Build Number: 5563,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OST-5) export and import vm

[eyal edri [Administrator] (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OST-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=27895#comment-27895
 ] 

eyal edri [Administrator] commented on OST-5:
-

duplicate, tracked in Lago GitHub issues.

> export and import vm
> 
>
> Key: OST-5
> URL: https://ovirt-jira.atlassian.net/browse/OST-5
> Project: oVirt system tests
>  Issue Type: Bug
>Reporter: Gal Ben Haim
>Assignee: infra
>
> check in the history of ost for the disabled test



--
This message was sent by Atlassian JIRA
(v1000.784.2#100032)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OST-5) export and import vm

[eyal edri [Administrator] (oVirt JIRA)]

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

eyal edri [Administrator] updated OST-5:

Status: Done  (was: To Do)
Resolution: Done

> export and import vm
> 
>
> Key: OST-5
> URL: https://ovirt-jira.atlassian.net/browse/OST-5
> Project: oVirt system tests
>  Issue Type: Bug
>Reporter: Gal Ben Haim
>Assignee: infra
>
> check in the history of ost for the disabled test



--
This message was sent by Atlassian JIRA
(v1000.784.2#100032)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1073) Drop nightly publishers in oVirt CI

[eyal edri [Administrator] (oVirt JIRA)]

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

eyal edri [Administrator] commented on OVIRT-1073:
--

We won't drop the nightly publishers.
Instead we'll just stop publishing RPMs from it and it will only be used to 
sync tested RPMs each night to the snapshot repos, that way we'll have static 
nightly updated oVirt repos.

The code to support it for master is already merged and part of the master 
publisher.

We need to remove all the YAML code from the publisher job gradually until all 
is left is the code that sync the test repo.

fyi [~sbonazo...@redhat.com]

> Drop nightly publishers in oVirt CI
> ---
>
> Key: OVIRT-1073
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1073
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>Reporter: eyal edri [Administrator]
>Assignee: infra
>
> We saw how destructive using the current publishers can be during 4.1 cycle, 
> Problems we encountered:
> 1. It hides missing RPMs from experimental flows 
> 2. It hides projects that needs to branch or using previous version released
> 3. It creates confusion of which RPMs are really tested in OST and give 
> different results than experimental instead of having a single source of RPMs 
> for oVirt.
> We should aim to drop it for 4.2 and use only experimental deployment.
> However, since we have errors on deploy to experimental flow, we can't 
> progress with this until they will be solved.



--
This message was sent by Atlassian JIRA
(v1000.784.2#100032)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1073) Drop nightly publishers in oVirt CI

[eyal edri [Administrator] (oVirt JIRA)]

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

eyal edri [Administrator] updated OVIRT-1073:
-
Status: In Progress  (was: Blocked)

> Drop nightly publishers in oVirt CI
> ---
>
> Key: OVIRT-1073
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1073
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>Reporter: eyal edri [Administrator]
>Assignee: infra
>
> We saw how destructive using the current publishers can be during 4.1 cycle, 
> Problems we encountered:
> 1. It hides missing RPMs from experimental flows 
> 2. It hides projects that needs to branch or using previous version released
> 3. It creates confusion of which RPMs are really tested in OST and give 
> different results than experimental instead of having a single source of RPMs 
> for oVirt.
> We should aim to drop it for 4.2 and use only experimental deployment.
> However, since we have errors on deploy to experimental flow, we can't 
> progress with this until they will be solved.



--
This message was sent by Atlassian JIRA
(v1000.784.2#100032)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1199) Re: Please add me to the CI white list

[eyal edri [Administrator] (oVirt JIRA)]

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

eyal edri [Administrator] updated OVIRT-1199:
-
Resolution: Fixed
Status: Done  (was: To Do)

> Re: Please add me to the CI white list
> --
>
> Key: OVIRT-1199
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1199
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: eyal edri [Administrator]
>Assignee: infra
>
> adding infra support to open a ticket.
> On Tue, Feb 21, 2017 at 5:58 PM, Milan Zamazal  wrote:
> > Hi, please put me to the CI white list on gerrit.ovirt.org so that
> > Jenkins runs for my patches.
> >
> > Thanks,
> > Milan
> > ___
> > Infra mailing list
> > Infra@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> >
> >
> -- 
> Eyal Edri
> Associate Manager
> RHV DevOps
> EMEA ENG Virtualization R
> Red Hat Israel
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)



--
This message was sent by Atlassian JIRA
(v1000.784.2#100032)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: Ovirt Jenkins Account

[Pavel Zhukov]

Adding infra-support to open a ticket

On Mon, Feb 27 2017, Phillip Bailey wrote:

> Hi,
>
> I need a Jenkins account so that I can retrigger CI builds when necessary.
> I'm not sure whether an account has been created for me previously. I was
> going to attempt resetting my password to see if an account exists, but I
> couldn't find a "reset password" link anywhere.
>
> Could you please tell me if I have an account and what the process is for
> having one created if I don't?
>
> Thank you!
>
> -Phillip Bailey
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra


-- 
Pavel Zhukov
Software Engineer
RHV DevOps
IRC: landgraf
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1198) Job times out on: 'Removing the used loop devices' on the initial clean up stage

[Nadav Goldin (oVirt JIRA)]

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

Nadav Goldin edited comment on OVIRT-1198 at 2/27/17 4:42 PM:
--

another job which timed out(not loop device this time)
http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_64/193/console



was (Author: ngol...@redhat.com):
another one: 
http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_64/193/console

> Job times out on: 'Removing the used loop devices' on the initial clean up 
> stage
> 
>
> Key: OVIRT-1198
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1198
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nadav Goldin
>Assignee: infra
>
> 15:44:38 Making sure there are no device mappings...
> 15:44:38 Removing the used loop devices...
> 21:44:37 Build timed out (after 360 minutes). Marking the build as failed.
> 21:44:37 Build was aborted
> (Notice the 6 hours between).
> http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc25-x86_64/710/console
> I think I saw another one earlier this week, also on fc25.



--
This message was sent by Atlassian JIRA
(v1000.784.2#100032)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Ovirt Jenkins Account

[Phillip Bailey]

Hi,

I need a Jenkins account so that I can retrigger CI builds when necessary.
I'm not sure whether an account has been created for me previously. I was
going to attempt resetting my password to see if an account exists, but I
couldn't find a "reset password" link anywhere.

Could you please tell me if I have an account and what the process is for
having one created if I don't?

Thank you!

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

[JIRA] (OVIRT-1201) Build oVirt 4.1.1 RC1

[sbonazzo (oVirt JIRA)]

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

sbonazzo reassigned OVIRT-1201:
---

Assignee: sbonazzo  (was: infra)

> Build oVirt 4.1.1 RC1
> -
>
> Key: OVIRT-1201
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1201
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>  Components: Repositories Mgmt
>Reporter: sbonazzo
>Assignee: sbonazzo
>Priority: Highest
>




--
This message was sent by Atlassian JIRA
(v1000.784.2#100032)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1201) Build oVirt 4.1.1 RC1

[sbonazzo (oVirt JIRA)]

sbonazzo created OVIRT-1201:
---

 Summary: Build oVirt 4.1.1 RC1
 Key: OVIRT-1201
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1201
 Project: oVirt - virtualization made easy
  Issue Type: Task
  Components: Repositories Mgmt
Reporter: sbonazzo
Assignee: infra
Priority: Highest






--
This message was sent by Atlassian JIRA
(v1000.784.2#100032)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1201) Build oVirt 4.1.1 RC1

[sbonazzo (oVirt JIRA)]

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

sbonazzo updated OVIRT-1201:

Epic Link: OVIRT-411

> Build oVirt 4.1.1 RC1
> -
>
> Key: OVIRT-1201
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1201
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>  Components: Repositories Mgmt
>Reporter: sbonazzo
>Assignee: infra
>Priority: Highest
>




--
This message was sent by Atlassian JIRA
(v1000.784.2#100032)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1129) Upgrade gerrit.ovirt.org to latest 2.12.z

[Evgheni Dereveanchin (oVirt JIRA)]

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

Evgheni Dereveanchin reassigned OVIRT-1129:
---

Assignee: Evgheni Dereveanchin  (was: infra)

> Upgrade gerrit.ovirt.org to latest 2.12.z
> -
>
> Key: OVIRT-1129
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1129
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Martin Perina
>Assignee: Evgheni Dereveanchin
>
> Hi,
> could you please upgrade gerrit to latest 2.12.z? Or at least 2.12.3 which 
> fixed small but very annoying behaviour of Control+C in Firefox:
> https://bugs.chromium.org/p/gerrit/issues/detail?id=2647
> Thanks
> Martin



--
This message was sent by Atlassian JIRA
(v1000.784.2#100032)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1200) upgrade Gerrit core tp 2.13

[Evgheni Dereveanchin (oVirt JIRA)]

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

Evgheni Dereveanchin reassigned OVIRT-1200:
---

Assignee: Evgheni Dereveanchin  (was: infra)

> upgrade Gerrit core tp 2.13
> ---
>
> Key: OVIRT-1200
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1200
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Evgheni Dereveanchin
>Assignee: Evgheni Dereveanchin
>
> The current release of Gerrit is 2.13 and we have 2.12 installed. Some 
> plugins require this core version so we should upgrade.



--
This message was sent by Atlassian JIRA
(v1000.784.2#100032)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1200) upgrade Gerrit core tp 2.13

[Evgheni Dereveanchin (oVirt JIRA)]

Evgheni Dereveanchin created OVIRT-1200:
---

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


The current release of Gerrit is 2.13 and we have 2.12 installed. Some plugins 
require this core version so we should upgrade.



--
This message was sent by Atlassian JIRA
(v1000.784.2#100032)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1009) Re: When trigged manually the check-merged job

[ybronhei (oVirt JIRA)]

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

ybronhei commented on OVIRT-1009:
-

once I trigger manually using jenkins check_merged vdsm job, the job starts
as expected, but the link to that job does not appear in the gerrit patch
page. In the past we used to to have new comment in the patch page about
manual triggering

On Sun, Feb 26, 2017 at 4:00 PM, eyal edri [Administrator] (oVirt JIRA) <




-- 
*Yaniv Bronhaim.*


> Re: When trigged manually the check-merged job
> --
>
> Key: OVIRT-1009
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1009
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: eyal edri [Administrator]
>Assignee: infra
>
> Adding infra-support to open a ticket on it.
> But it will help if you'll provide example of what you are expecting to see
> so we'll check its possible.
> On Mon, Jan 9, 2017 at 11:32 AM, Yaniv Bronheim  wrote:
> > When trigged manually the check-merged job for specific patch we don't see
> > the link in the patch History - see in https://gerrit.ovirt.org/#/
> > c/69802/3
> >
> > it used to be different .. can we get the link back?
> >
> > Thanks.
> >
> > --
> > *Yaniv Bronhaim.*
> >
> -- 
> Eyal Edri
> Associate Manager
> RHV DevOps
> EMEA ENG Virtualization R
> Red Hat Israel
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)



--
This message was sent by Atlassian JIRA
(v1000.784.2#100032)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #787 - SUCCESS!

[jenkins]

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/787/,
Build Number: 787,
Build Status: SUCCESS___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1193) add on request 'ci help' command via Gerrit

[Martin Sivak (oVirt JIRA)]

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

Martin Sivak commented on OVIRT-1193:
-

Eyal, it was my request inspired by Kubernetes. One message per changeset 
(first comment) is hardly obtrusive and it can provide customized links for the 
patchset (real links with proper IDs instead of just a generic help message).

Please realize that we want to have as low barrier of entry as possible, so 
everything has to be immediately obvious from the first message (either a 
direct link or copy/paste command). There are also people who do not really use 
the UI too much (we get all the comments using email too) so UI improvement 
does not solve it for those cases.

But feel free to do a survey.

> add on request 'ci help' command via Gerrit
> ---
>
> Key: OVIRT-1193
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1193
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>  Components: Gerrit/git
>Reporter: Barak Korren
>Assignee: infra
>
> On 23 February 2017 at 15:10, Martin Sivak  wrote:
> > Hi,
> >
> > do you think it would make sense to send a copy-and-paste ready
> > message with help to every new gerrit change?
> >
> > It could provide all the system test (lago) links, mention the Rerun
> > hooks syntax and so on. Just so we do not have to search for it all
> > the time?
> This is doable, but I think experienced users may find this annoying
> it ifs too long.
> I'm thinking it may be better to have such a message just suggesting
> to type something like '@ci help' to get the full help.
> It may even be possible to make it clickable with some trickery rather
> then just copy-and-paster ready (I will need to check if its possible
> to inject links into Gerrit comments).
> Apart from that, Roy offered to write a Gerrit plugin that will add
> buttons with the various CI commands.
> Adding infra-support to get a Jira ticket opened.
> -- 
> Barak Korren
> bkor...@redhat.com
> RHCE, RHCi, RHV-DevOps Team
> https://ifireball.wordpress.com/



--
This message was sent by Atlassian JIRA
(v1000.784.2#100032)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #786 - FAILURE!

[jenkins]

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/786/,
Build Number: 786,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1199) Re: Please add me to the CI white list

[eyal edri [Administrator] (oVirt JIRA)]

eyal edri [Administrator] created OVIRT-1199:


 Summary: Re: Please add me to the CI white list
 Key: OVIRT-1199
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1199
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: eyal edri [Administrator]
Assignee: infra


adding infra support to open a ticket.

On Tue, Feb 21, 2017 at 5:58 PM, Milan Zamazal  wrote:

> Hi, please put me to the CI white list on gerrit.ovirt.org so that
> Jenkins runs for my patches.
>
> Thanks,
> Milan
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>
>


-- 
Eyal Edri
Associate Manager
RHV DevOps
EMEA ENG Virtualization R
Red Hat Israel

phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)



--
This message was sent by Atlassian JIRA
(v1000.784.2#100032)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: Please add me to the CI white list

[Eyal Edri]

adding infra support to open a ticket.

On Tue, Feb 21, 2017 at 5:58 PM, Milan Zamazal  wrote:

> Hi, please put me to the CI white list on gerrit.ovirt.org so that
> Jenkins runs for my patches.
>
> Thanks,
> Milan
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>
>


-- 
Eyal Edri
Associate Manager
RHV DevOps
EMEA ENG Virtualization R
Red Hat Israel

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

[JIRA] (OVIRT-1110) rpms served from new jenkins repos sometimes timeout with "xyz bytes remaining to read"

[Evgheni Dereveanchin (oVirt JIRA)]

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

Evgheni Dereveanchin reassigned OVIRT-1110:
---

Assignee: Evgheni Dereveanchin  (was: infra)

> rpms served from new jenkins repos sometimes timeout with "xyz bytes 
> remaining to read"
> ---
>
> Key: OVIRT-1110
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1110
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Greg Sheremeta
>Assignee: Evgheni Dereveanchin
>
> I'm running mock_runner locally.
> ../jenkins/mock_configs/mock_runner.sh --mock-confs-dir
> ../jenkins/mock_configs el7:epel-7-x86_64 --patch-only
> I've seen this error about 5 times when using the new jenkins-based mini
> repos:
> 
> Total download size: 162 M
> Installed size: 515 M
> http://jenkins.ovirt.org/job/ovirt-engine-nodejs_master_build-artifacts-el7-x86_64/lastSuccessfulBuild/artifact/exported-artifacts/x86_64/ovirt-engine-nodejs-6.9.4-2.el7.centos.x86_64.rpm:
> [Errno 14] curl#18 - "transfer closed with 2444831 bytes remaining to read"
> Trying other mirror.
> When I try once more, I always get this error:
> Installed size: 515 M
> No Presto metadata available for ovirt-engine-nodejs_master
> http://jenkins.ovirt.org/job/ovirt-engine-nodejs_master_build-artifacts-el7-x86_64/lastSuccessfulBuild/artifact/exported-artifacts/x86_64/ovirt-engine-nodejs-6.9.4-2.el7.centos.x86_64.rpm:
> [Errno -1] Package does not match intended download. Suggestion: run yum
> --enablerepo=ovirt-engine-nodejs_master clean metadata and try again
> Trying other mirror.
> And the final third time works.
> Any ideas?
> -- 
> Greg Sheremeta, MBA
> Red Hat, Inc.
> Sr. Software Engineer
> gsher...@redhat.com



--
This message was sent by Atlassian JIRA
(v1000.784.2#100032)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra