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

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

Re: oVirt 4.1 beta2 build planned: branch and string freeze for this build

A friendly reminder about the planned build which will start in one hour and 39 minutes. Please note this will be the second oVirt 4.1 beta compose and will be done taking ovirt-4.1-snapshot in its state at compose time. If you've pending fixes to be published please ping me at least 40 minutes

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4329 - SUCCESS!

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

oVirt infra daily report - unstable production jobs - 174

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/174//artifact/exported-artifacts/upstream_report.html Cheers, Jenkins

oVirt infra daily report - unstable production jobs - 174

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/174//artifact/exported-artifacts/upstream_report.html Cheers, Jenkins

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

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

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

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

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

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

[JIRA] (OVIRT-949) ovirt devel archives end on Dec 8th

danken created OVIRT-949: Summary: ovirt devel archives end on Dec 8th Key: OVIRT-949 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-949 Project: oVirt - virtualization made easy Issue Type:

[JIRA] (OVIRT-950) vdsm_master_check-merged-el7 is failing for days due to "groovy"

danken created OVIRT-950: Summary: vdsm_master_check-merged-el7 is failing for days due to "groovy" Key: OVIRT-950 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-950 Project: oVirt - virtualization made

Re: planned Jenkins restart

Maintenance completed, Jenkins back up and running. As always - if you see any issues please report them on Jira. Regards, Evgheni Dereveanchin - Original Message - From: "Evgheni Dereveanchin" To: "infra" Cc: "devel" Sent:

planned Jenkins restart

Hi everyone, I'll be performing a planned Jenkins restart today. No new builds will be scheduled during this maintenance period. I will announce you once it is finished. Regards, Evgheni Dereveanchin ___ Infra mailing list Infra@ovirt.org

[JIRA] (OVIRT-948) test

[ https://ovirt-jira.atlassian.net/browse/OVIRT-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgheni Dereveanchin updated OVIRT-948: --- Resolution: Done Status: Done (was: To Do) test ticket > test > > >

[JIRA] (OVIRT-948) test

Evgheni Dereveanchin created OVIRT-948: -- Summary: test Key: OVIRT-948 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-948 Project: oVirt - virtualization made easy Issue Type:

Build failed in Jenkins: ovirt_3.6_he-system-tests #781

See Changes: [Ond��ej Svoboda] Add multiple interfaces to basic-suite-4.0/master. -- [...truncated 608 lines...] + create_lun 3 + local ID=3 + lvcreate -L20G -n lun3_bdev vg1_storage +

Build failed in Jenkins: ovirt_3.6_he-system-tests #780

See Changes: [Ond��ej Svoboda] Add multiple interfaces to basic-suite-4.0/master. -- [...truncated 608 lines...] + create_lun 3 + local ID=3 + lvcreate -L20G -n lun3_bdev vg1_storage +

[JIRA] (OVIRT-947) [gerrit hooks] Disable change bug status to MODIFIED for 'master' branch

[ https://ovirt-jira.atlassian.net/browse/OVIRT-947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shlomo Ben David reassigned OVIRT-947: -- Assignee: Shlomo Ben David (was: infra) > [gerrit hooks] Disable change bug status

[JIRA] (OVIRT-947) [gerrit hooks] Disable change bug status to MODIFIED for 'master' branch

[ https://ovirt-jira.atlassian.net/browse/OVIRT-947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shlomo Ben David updated OVIRT-947: --- Epic Link: OVIRT-411 > [gerrit hooks] Disable change bug status to MODIFIED for 'master'

[JIRA] (OVIRT-947) [gerrit hooks] Disable change bug status to MODIFIED for 'master' branch

Shlomo Ben David created OVIRT-947: -- Summary: [gerrit hooks] Disable change bug status to MODIFIED for 'master' branch Key: OVIRT-947 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-947 Project:

Build failed in Jenkins: ovirt_3.6_he-system-tests #779

See Changes: [Ond��ej Svoboda] Add multiple interfaces to basic-suite-4.0/master. -- [...truncated 612 lines...] + create_lun 3 + local ID=3 + lvcreate -L20G -n lun3_bdev vg1_storage +

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4323 - SUCCESS!

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

Build failed in Jenkins: ovirt_3.6_he-system-tests #778

See Changes: [Ond��ej Svoboda] Add multiple interfaces to basic-suite-4.0/master. -- Started by user Lev Veyde [EnvInject] - Loading node environment variables. Building remotely on

Build failed in Jenkins: ovirt_3.6_he-system-tests #777

See -- Started by user Lev Veyde [EnvInject] - Loading node environment variables. Building remotely on ovirt-srv22.phx.ovirt.org (fc24 phx integ-tests physical) in workspace

Build failed in Jenkins: ovirt_3.6_he-system-tests #776

See -- [...truncated 1010 lines...] rm: cannot remove

Build failed in Jenkins: ovirt_3.6_he-system-tests #775

See -- [...truncated 434 lines...] warning: failed to remove deployment-he-basic-suite-3.6/default/internal_repo/el7/noarch/vdsm-hook-nestedvt-4.17.36-9.git3f6afd6.el7.centos.noarch.rpm warning:

[JIRA] (OVIRT-946) emails no longer create JIRA tickets

Evgheni Dereveanchin created OVIRT-946: -- Summary: emails no longer create JIRA tickets Key: OVIRT-946 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-946 Project: oVirt - virtualization made

[JIRA] (OVIRT-946) emails no longer create JIRA tickets

[ https://ovirt-jira.atlassian.net/browse/OVIRT-946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgheni Dereveanchin reassigned OVIRT-946: -- Assignee: Evgheni Dereveanchin (was: infra) > emails no longer create JIRA

Build failed in Jenkins: ovirt_3.6_he-system-tests #773

See -- [...truncated 431 lines...] warning: failed to remove deployment-he-basic-suite-3.6/default/internal_repo/el7/noarch/ovirt-node-plugin-hosted-engine-0.3.0-2.ovirt36.el7.centos.noarch.rpm

Build failed in Jenkins: ovirt_3.6_he-system-tests #772

See -- [...truncated 431 lines...] warning: failed to remove deployment-he-basic-suite-3.6/default/internal_repo/el7/noarch/ovirt-node-plugin-hosted-engine-0.3.0-2.ovirt36.el7.centos.noarch.rpm

Build failed in Jenkins: ovirt_3.6_he-system-tests #771

See -- [...truncated 435 lines...] warning: failed to remove deployment-he-basic-suite-3.6/default/internal_repo/el7/noarch/ovirt-node-plugin-hosted-engine-0.3.0-2.ovirt36.el7.centos.noarch.rpm

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

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

Build failed in Jenkins: ovirt_3.6_he-system-tests #769

See Changes: [Ond��ej Svoboda] Add multiple interfaces to basic-suite-4.0/master. -- [...truncated 618 lines...] + local ID=3 + lvcreate -L20G -n lun3_bdev vg1_storage + targetcli

Re: Maintainers can't give +2 on code review in ovirt-engine-4.1 stable branch

It's disabled (to view by others) by default unless we add special permission. Best Regards, Shlomi Ben-David | Software Engineer | Red Hat ISRAEL RHCSA | RHCE IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci) OPEN SOURCE - 1 4 011 && 011 4 1 On Tue, Dec 20, 2016 at 6:24 PM, Tal Nisan

Re: Maintainers can't give +2 on code review in ovirt-engine-4.1 stable branch

It's disabled (to view by others) by default unless we add special permission. Best Regards, Shlomi Ben-David | Software Engineer | Red Hat ISRAEL RHCSA | RHCE IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci) OPEN SOURCE - 1 4 011 && 011 4 1 On Tue, Dec 20, 2016 at 6:24 PM, Tal Nisan

Re: Maintainers can't give +2 on code review in ovirt-engine-4.1 stable branch

If you disabled other people from watching it if they are not reviewers then it's fine to leave it like that then On Tue, Dec 20, 2016 at 6:21 PM, Shlomo Ben David wrote: > About the last thing... > When people push drafts only they can view them, unless they add someone >

Re: Maintainers can't give +2 on code review in ovirt-engine-4.1 stable branch

About the last thing... When people push drafts only they can view them, unless they add someone as reviewers before publishing it as a regular patch. That's why I think it is useless permission, but if you still want i can add it. Best Regards, Shlomi Ben-David | Software Engineer | Red Hat

Build failed in Jenkins: ovirt_3.6_he-system-tests #768

See Changes: [Ond��ej Svoboda] Add multiple interfaces to basic-suite-4.0/master. [Eyal Edri] refactor engine yaml file [Eyal Edri] Add new trigger 'on-comment-added' [Eyal Edri] enabling on-demand builds for various

[JIRA] (OVIRT-935) Unable to build fc25 chroots with mock

[ https://ovirt-jira.atlassian.net/browse/OVIRT-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=24709#comment-24709 ] Anton Marchukov commented on OVIRT-935: --- Another solution as I see would be to check the current status

Re: Maintainers can't give +2 on code review in ovirt-engine-4.1 stable branch

Hi Tal/Eyal, I added CR (-/+)2 permission for the ovirt-engine-master-maintainers group on the stable-branches. Best Regards, Shlomi Ben-David | Software Engineer | Red Hat ISRAEL RHCSA | RHCE IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci) OPEN SOURCE - 1 4 011 && 011 4 1 On Tue,

Re: Maintainers can't give +2 on code review in ovirt-engine-4.1 stable branch

OK, thanks for the clarification. We'll add the missing permission. any other permissions master-branch-maintainers should have on stable branch? On Tue, Dec 20, 2016 at 5:44 PM, Tal Nisan wrote: > That was always the case, master maintainers should have +2 on the stable >

[JIRA] (OVIRT-935) Unable to build fc25 chroots with mock

[ https://ovirt-jira.atlassian.net/browse/OVIRT-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=24708#comment-24708 ] Anton Marchukov commented on OVIRT-935: --- Official information:

Re: Maintainers can't give +2 on code review in ovirt-engine-4.1 stable branch

That was always the case, master maintainers should have +2 on the stable branches without merge rights, this helps me distinguished between: 1. Who is actually a maintainer from the ones acking the patch 2. If a maintainer meant we're good to go or gave his review yet would like another reviewer

Re: Gerrit hooks change 4.1 bugs status to MODIFIED if merged on master

Hi Tal/Eyal, As I see from [1], you are working on the 'master' branch. The check hooks currently bypass the 'master' branch as you can see in the gerrit log below. - Update Tracker::#1364152::OK, status: POST - Check Bug-Url::OK - Check Product::IGNORE, not relevant for branch: master

Re: Maintainers can't give +2 on code review in ovirt-engine-4.1 stable branch

I wasn't aware we were allowing +2 permissions without merge rights on stable branch, If this should be supported then we need to update the permissions, so all master branch maintainers need +2 (w/o merge) to stable branches? On Tue, Dec 20, 2016 at 4:58 PM, Tal Nisan wrote:

[JIRA] (OVIRT-935) Unable to build fc25 chroots with mock

[ https://ovirt-jira.atlassian.net/browse/OVIRT-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=24706#comment-24706 ] Anton Marchukov commented on OVIRT-935: --- I support [~ederevea] in that we should not try to maintain non

[JIRA] (OVIRT-935) Unable to build fc25 chroots with mock

[ https://ovirt-jira.atlassian.net/browse/OVIRT-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=24707#comment-24707 ] eyal edri [Administrator] commented on OVIRT-935: - This comes with a price - if we'll have more

Re: Maintainers can't give +2 on code review in ovirt-engine-4.1 stable branch

Master On Tue, Dec 20, 2016 at 4:53 PM, Eyal Edri wrote: > stable branch maintainers or master branch maintainers? > > On Dec 20, 2016 4:40 PM, "Tal Nisan" wrote: > >> Heard it from a couple of guys, yesterday it appeared to be working fine, >> today it's

Re: Maintainers can't give +2 on code review in ovirt-engine-4.1 stable branch

stable branch maintainers or master branch maintainers? On Dec 20, 2016 4:40 PM, "Tal Nisan" wrote: > Heard it from a couple of guys, yesterday it appeared to be working fine, > today it's not > > > ___ > Infra mailing list >

Maintainers can't give +2 on code review in ovirt-engine-4.1 stable branch

Heard it from a couple of guys, yesterday it appeared to be working fine, today it's not ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

Re: Gerrit hooks change 4.1 bugs status to MODIFIED if merged on master

Adding Shlomi. On Tue, Dec 20, 2016 at 11:56 AM, Tal Nisan wrote: > This should be change to move to MODIFIED only after the bug is merged on > the 4.1 branch. > Here's an example: > https://gerrit.ovirt.org/#/c/68739/ > > Thanks. > > > >

Gerrit hooks change 4.1 bugs status to MODIFIED if merged on master

This should be change to move to MODIFIED only after the bug is merged on the 4.1 branch. Here's an example: https://gerrit.ovirt.org/#/c/68739/ Thanks. ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-945) Add upgrade suites for 4.1

Daniel Belenky created OVIRT-945: Summary: Add upgrade suites for 4.1 Key: OVIRT-945 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-945 Project: oVirt - virtualization made easy Issue

[JIRA] (OVIRT-945) Add upgrade suites for 4.1

[ https://ovirt-jira.atlassian.net/browse/OVIRT-945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Belenky reassigned OVIRT-945: Assignee: (was: infra) > Add upgrade suites for 4.1 > -- > >

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

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