August 2016 - Infra - oVirt List Archives

[JIRA] (OVIRT-675) ci-tools repo does not support RHEL7
by Evgheni Dereveanchin (oVirt JIRA) 15 Aug '16

15 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-675?page=com.atlassian.jira.p… ] Evgheni Dereveanchin updated OVIRT-675: --------------------------------------- Resolution: Fixed Status: Done (was: To Do) closing since the error is gone with the new symlink > ci-tools repo does not support RHEL7 > ------------------------------------ > > Key: OVIRT-675 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-675 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Repositories Mgmt > Reporter: Evgheni Dereveanchin > Assignee: infra > > The ci-tools repo does not work with RHEL7. > Our puppet manifests set it up the following way: > baseurl=http://resources.ovirt.org/repos/ci-tools/EL/$releasever > On RHEL7 this results in: > http://resources.ovirt.org/repos/ci-tools/EL/7Server/ > which does not exist. > Can we create a symlink 7Server -> 7 to make it work? It looks like a similar config ins in place for RHEL6. > The current ci-tools puppet manifest is here: > https://gerrit.ovirt.org/gitweb?p=infra-puppet.git;a=blob;f=site/ovirt_base… -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

1 0

Gerrit/ManualTrigger permission
by Ravi Nori 15 Aug '16

15 Aug '16

Hi, I need dev permissions for "rnori" to be able to trigger manually. "rnori is missing the Gerrit/ManualTrigger permission" Thanks, Ravi

2 6

oVirt infra daily report - unstable production jobs - 46
by jenkins＠jenkins.phx.ovirt.org 15 Aug '16

15 Aug '16

------=_Part_142_2045070902.1471215604345 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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/46//artifact/exported-ar… Cheers, Jenkins ------=_Part_142_2045070902.1471215604345 Content-Type: application/octet-stream; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 14/08/2016 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Jobs (Production)</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/lago_master_check-merged-trigger/">lago_master_check-merged-trigger</a> </td><td> 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 <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-engine_4.0_upgrade-from-4.0_el7_merged/">ovirt-engine_4.0_upgrade-from-4.0_el7_merged</a> </td><td> 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 <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.0_el7_merge…">ovirt-engine_master_upgrade-from-4.0_el7_merged</a> </td><td> 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 <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6…">ovirt-node-ng_master_build-artifacts-el7-x86_64</a> </td><td> 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 <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x8…">ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x86_64</a> </td><td> 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 <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0-pre_build-artifacts-el…">ovirt-node-ng_ovirt-4.0-pre_build-artifacts-el7-x86_64</a> </td><td> 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 <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0-snapshot_build-artifac…">ovirt-node-ng_ovirt-4.0-snapshot_build-artifacts-el7-x86_64</a> </td><td> 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 <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0-snapshot_build-artifac…">ovirt-node-ng_ovirt-4.0-snapshot_build-artifacts-fc22-x86_64</a> </td><td> 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 <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0_build-artifacts-el7-x8…">ovirt-node-ng_ovirt-4.0_build-artifacts-el7-x86_64</a> </td><td> 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 <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/">ovirt_4.0_he-system-tests</a> </td><td> 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 <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/">ovirt_4.0_system-tests</a> </td><td> 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 <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/vdsm_4.0_check-merged-fc23-x86_64/">vdsm_4.0_check-merged-fc23-x86_64</a> </td><td> 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 <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-el7-ppc64le/">vdsm_master_build-artifacts-el7-ppc64le</a> </td><td> 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 <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-el7-x86_64/">vdsm_master_build-artifacts-el7-x86_64</a> </td><td> 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 <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/vdsm_master_check-merged-fc24-x86_64/">vdsm_master_check-merged-fc24-x86_64</a> </td><td> 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 <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_142_2045070902.1471215604345--

1 0

[JIRA] (OVIRT-416) [standard-ci] build-artifacts should reuse the artifacts built on check-merged if any
by eyal edri [Administrator] (oVirt JIRA) 14 Aug '16

14 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-416?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-416: ------------------------------------------------- OK, looking at the code it seems check-merged is running a draft build: # create the rpms rpmbuild \ -D "_rpmdir $PWD/output" \ -D "_topmdir $PWD/rpmbuild" \ -D "release_suffix ${SUFFIX}" \ -D "ovirt_build_ut $BUILD_UT" \ -D "ovirt_build_extra_flags $EXTRA_BUILD_FLAGS" \ -D "ovirt_build_draft 1" \ --rebuild output/*.src.rpm while build artifacts is running full blown matrix: # create the rpms rpmbuild \ -D "_rpmdir $PWD/output" \ -D "_topmdir $PWD/rpmbuild" \ -D "release_suffix ${SUFFIX}" \ -D "ovirt_build_ut $BUILD_UT" \ -D "ovirt_build_extra_flags $EXTRA_BUILD_FLAGS" \ --rebuild output/*.src.rpm and currently running 27(!) permutations. So the question is, can we reduce this to 1-2 permutations? if this is just going to nightly / hourly repo then we don't need all these permutations and we'll enjoy a much faster verification on the experimental flow which collects artifacts from build-artifacts jobs. We are now adding the 'build official manual' option to standard CI, so we can keep the 27 permutations there for official builds. I believe this will reduce dramatically the CI flow runtime and will give us much faster feedback on failures. Also, it will simplify the move to running experimental flow per patch as the full run-time will be significantly lower. > [standard-ci] build-artifacts should reuse the artifacts built on check-merged if any > ------------------------------------------------------------------------------------- > > Key: OVIRT-416 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-416 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: David Caro Estevez > Assignee: infra > > Right now most projects just rebuild twice the artifacts, what for some means a big waste of resources, if we could just reuse what was built previously there would be no rebuilding. > Something to take into account is that the distributions that check-merged and build-artifacts run for might not match, so you can be running check-merged only on fc23 but building artifacts for fc23, fc22 an el7 (as an example), maybe we should not allow different distros on each stage?| -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

1 0

[JIRA] (OVIRT-562) find a way not to fail CI jobs if git clone fails
by eyal edri [Administrator] (oVirt JIRA) 14 Aug '16

14 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-562?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-562: -------------------------------------------- Priority: Low (was: Medium) lowering priority since we don't hit this issue anymore upgrade gerrit upgrade. > find a way not to fail CI jobs if git clone fails > ------------------------------------------------- > > Key: OVIRT-562 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-562 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Low > > We need to find away to tell gerrit trigger plugin not to put -1 if git clone fails (obviously an infra issue) -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

1 0

[JIRA] (OVIRT-685) Add Ubunto slaves to CI
by eyal edri [Administrator] (oVirt JIRA) 14 Aug '16

14 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-685?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-685: -------------------------------------------- Epic Link: OVIRT-400 > Add Ubunto slaves to CI > ----------------------- > > Key: OVIRT-685 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-685 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > > We are looking into building Lago on Ubunto, so we'll need some slaves to do it. > not sure yet about puppet classes, we might need to do some changes to support it. -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

1 0

[JIRA] (OVIRT-685) Add Ubunto slaves to CI
by eyal edri [Administrator] (oVirt JIRA) 14 Aug '16

14 Aug '16

eyal edri [Administrator] created OVIRT-685: ----------------------------------------------- Summary: Add Ubunto slaves to CI Key: OVIRT-685 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-685 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri [Administrator] Assignee: infra We are looking into building Lago on Ubunto, so we'll need some slaves to do it. not sure yet about puppet classes, we might need to do some changes to support it. -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

1 0

[JIRA] (OVIRT-678) vdsm check-merge jobs doesn't work for el7
by eyal edri [Administrator] (oVirt JIRA) 14 Aug '16

14 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-678?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-678: ------------------------------------------------- I understand you want to remove the el7 job for master, the question is why? If we want to fix it, I suggest to keep it or at least disable it, otherwise we'll just forget about it. if its only check-merged then it doesn't give -1 on patches and its not blocking patches. also, if there is something the infra team can do to help with fixing el7 please let us know > vdsm check-merge jobs doesn't work for el7 > ------------------------------------------ > > Key: OVIRT-678 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-678 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > On Wed, Aug 10, 2016 at 3:41 PM, Irit Goihman <igoihman(a)redhat.com> wrote: > > Hi, > > jobs vdsm_master_build-artifacts-el7-ppc64le and vdsm_master_check-merged-el7-x86_64 > > keep failing. They were created recently and should be removed. > > > The ppc64le should be fixed, not removed. > We want ppc64le builds now that we have ppc64le slaves. > The check-merged for el7 is your call, fine for me if you want to remove. > Just weird since el7 is our main target. > > > > Thanks > > > > -- > > Irit Goihman > > Software Engineer > > Red Hat Israel Ltd. > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

1 0

[JIRA] (OVIRT-678) vdsm check-merge jobs doesn't work for el7
by eyal edri [Administrator] (oVirt JIRA) 14 Aug '16

14 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-678?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-678: -------------------------------------------- Summary: vdsm check-merge jobs doesn't work for el7 (was: Re: please remove the following jenkins jobs) > vdsm check-merge jobs doesn't work for el7 > ------------------------------------------ > > Key: OVIRT-678 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-678 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > On Wed, Aug 10, 2016 at 3:41 PM, Irit Goihman <igoihman(a)redhat.com> wrote: > > Hi, > > jobs vdsm_master_build-artifacts-el7-ppc64le and vdsm_master_check-merged-el7-x86_64 > > keep failing. They were created recently and should be removed. > > > The ppc64le should be fixed, not removed. > We want ppc64le builds now that we have ppc64le slaves. > The check-merged for el7 is your call, fine for me if you want to remove. > Just weird since el7 is our main target. > > > > Thanks > > > > -- > > Irit Goihman > > Software Engineer > > Red Hat Israel Ltd. > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

1 0

[JIRA] (OVIRT-684) dev permissions
by eyal edri [Administrator] (oVirt JIRA) 14 Aug '16

14 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-684?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-684: -------------------------------------------- Resolution: Fixed Status: Done (was: Blocked) please open if you still require more permissions > dev permissions > --------------- > > Key: OVIRT-684 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-684 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Liron Aravot > Assignee: infra > > Hi, > I need dev permissions for "laravot" to be able to trigger manually. > "laravot is missing the Gerrit/ManualTrigger permission" > thanks. -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

1 0