- Infra - oVirt List Archives

[JIRA] (OVIRT-1502) gerrit does not print check_merged output
by Barak Korren (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1502?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1502: -------------------------------- Labels: gerrit (was: ) > gerrit does not print check_merged output > ----------------------------------------- > > Key: OVIRT-1502 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1502 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: ybronhei > Assignee: infra > Labels: gerrit > > Hello, > Recently vdsm gerrit job check-merged doesn't send report after its done - > check all recent jobs - they were done but the gerrit url doesn't show the > output nor send email about failures. > Thanks in advance > Yaniv Bronhaim. > -- > Yaniv Bronhaim. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-713) Clean reposync directory after n times of sync failure
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-713?page=com.atlassian.jira.p… ] eedri commented on OVIRT-713: ----------------------------- [~gbenhaim@redhat.com][~ngoldin@redhat.com] was there any progress on this? if we still suffer from reposync errors, might worth prioritizing. > Clean reposync directory after n times of sync failure > ------------------------------------------------------ > > Key: OVIRT-713 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-713 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Gal Ben Haim > Assignee: infra > > Sometimes reposync fail to sync rpms that already been synced. > To resolve this issue, lago removes those rpms, and runs reposync again. > This resolution doesn't always work, and then we need to clean all the rpms that were synced. > We want lago to clear the cached rpms after n times of sync failure, and then try to sync again. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1502) gerrit does not print check_merged output
by Barak Korren (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1502?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1502: -------------------------------- Component/s: oVirt CI > gerrit does not print check_merged output > ----------------------------------------- > > Key: OVIRT-1502 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1502 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: ybronhei > Assignee: infra > > Hello, > Recently vdsm gerrit job check-merged doesn't send report after its done - > check all recent jobs - they were done but the gerrit url doesn't show the > output nor send email about failures. > Thanks in advance > Yaniv Bronhaim. > -- > Yaniv Bronhaim. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1502) gerrit does not print check_merged output
by Barak Korren (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1502?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1502: -------------------------------- Issue Type: Bug (was: By-EMAIL) > gerrit does not print check_merged output > ----------------------------------------- > > Key: OVIRT-1502 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1502 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: ybronhei > Assignee: infra > > Hello, > Recently vdsm gerrit job check-merged doesn't send report after its done - > check all recent jobs - they were done but the gerrit url doesn't show the > output nor send email about failures. > Thanks in advance > Yaniv Bronhaim. > -- > Yaniv Bronhaim. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1502) gerrit does not print check_merged output
by Barak Korren (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1502?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1502: ------------------------------------- [~eedri] no this is completely unrelated to that ticket. In this case we see that the build success/failure comment by jenkins is not added at all, as if the Gerrit plugin "forgot" to return results. See these patches for example: * https://gerrit.ovirt.org/#/c/78890/ * https://gerrit.ovirt.org/#/c/78189/ Here are links to the full set of post-merge jobs for [78189|https://gerrit.ovirt.org/78189] # http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/2091/ # http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-fc25-x86_64/1098/ # http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-el7-x86_64/2686/ # http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-el7-ppc64le/2100/ # http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental/3053/ # http://jenkins.ovirt.org/job/standard-enqueue/2232/ I don't see any obvious issues with the jobs ATM. For engine things seem to work ok: https://gerrit.ovirt.org/#/c/78901/ > gerrit does not print check_merged output > ----------------------------------------- > > Key: OVIRT-1502 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1502 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: ybronhei > Assignee: infra > > Hello, > Recently vdsm gerrit job check-merged doesn't send report after its done - > check all recent jobs - they were done but the gerrit url doesn't show the > output nor send email about failures. > Thanks in advance > Yaniv Bronhaim. > -- > Yaniv Bronhaim. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-686) Find a better way to show unstable status in CI
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-686?page=com.atlassian.jira.p… ] eedri updated OVIRT-686: ------------------------ Priority: Low (was: Medium) > Find a better way to show unstable status in CI > ----------------------------------------------- > > Key: OVIRT-686 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-686 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eedri > Assignee: infra > Priority: Low > > Today we have the main view on jenkins.ovirt.org showing the unstable list of jobs, > While its effective in showing the current stable jobs, its not optimal in showing trends, history or dashboard view of the jenkins itself. > We need to find a jenkins plugin or a dashboard to show the current status of Jenkins in a more efficient and informative way. > There are numerous dashboards and view plugins, just need to find the right one for oVirt. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-638) Tune Gerrit
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-638?page=com.atlassian.jira.p… ] eedri updated OVIRT-638: ------------------------ Priority: Low (was: Medium) > Tune Gerrit > ----------- > > Key: OVIRT-638 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-638 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Barak Korren > Assignee: infra > Priority: Low > > We should probably tune Gerrit to take proper advantage of the bigger server we now have. > This could be useful: > http://ctf-dev-environment-vagrant.s3.amazonaws.com/Gerrit-Performance-Tuni… > Few notable details: > # Most RAM on the new server is currently taken by the FS cache instead of the Gerrit Java processes. > # It seems that the Gerrit can do Git garbage collection on its own, and do so more efficiently then doing so with the Git command line. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1173) Please use git shallow clone as jobs default
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1173?page=com.atlassian.jira.… ] eedri updated OVIRT-1173: ------------------------- Priority: Low (was: Medium) > Please use git shallow clone as jobs default > -------------------------------------------- > > Key: OVIRT-1173 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1173 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: rgolan(a)redhat.com > Assignee: infra > Priority: Low > Labels: standard-ci > > Most if not all the git clone of the jobs don't need history at all. > For ovirt-engine I see it downloading *11Mb* using --depth 1 vs. *157Mb* > for regular clone. > R -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-978) Move ovirt-engine & vdsm projects from git:// to http:// to reduce load from git service
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-978?page=com.atlassian.jira.p… ] eedri commented on OVIRT-978: ----------------------------- havn't seen failures due to it for quite some time, keeping it as low priority in case we hit it again. > Move ovirt-engine & vdsm projects from git:// to http:// to reduce load from git service > ---------------------------------------------------------------------------------------- > > Key: OVIRT-978 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-978 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: danken > Assignee: infra > Priority: Low > > Occasionally, e.g. > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/6870/conso… > I see these failures > 07:29:50 Manually triggered by user ishaby(a)redhat.com for Gerrit: > https://gerrit.ovirt.org/68804 > 07:29:50 [EnvInject] - Loading node environment variables. > 07:29:50 Building remotely on fc24-vm15.phx.ovirt.org (fc24 phx > local_disk nested) in workspace > /home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64 > 07:29:50 > git rev-parse --is-inside-work-tree # timeout=10 > 07:29:50 Fetching changes from the remote Git repository > 07:29:50 > git config remote.origin.url > git://gerrit.ovirt.org/vdsm.git # timeout=10 > 07:29:50 Cleaning workspace > 07:29:50 > git rev-parse --verify HEAD # timeout=10 > 07:29:50 Resetting working tree > 07:29:50 > git reset --hard # timeout=10 > 07:29:51 > git clean -fdx # timeout=10 > 07:29:51 Pruning obsolete local branches > 07:29:51 Fetching upstream changes from git://gerrit.ovirt.org/vdsm.git > 07:29:51 > git --version # timeout=10 > 07:29:51 > git -c core.askpass=true fetch --tags --progress > git://gerrit.ovirt.org/vdsm.git refs/changes/04/68804/3 --prune > 07:29:51 ERROR: Error fetching remote repo 'origin' > 07:29:51 hudson.plugins.git.GitException: Failed to fetch from > git://gerrit.ovirt.org/vdsm.git -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-978) Move ovirt-engine & vdsm projects from git:// to http:// to reduce load from git service
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-978?page=com.atlassian.jira.p… ] eedri updated OVIRT-978: ------------------------ Priority: Low (was: Medium) > Move ovirt-engine & vdsm projects from git:// to http:// to reduce load from git service > ---------------------------------------------------------------------------------------- > > Key: OVIRT-978 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-978 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: danken > Assignee: infra > Priority: Low > > Occasionally, e.g. > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/6870/conso… > I see these failures > 07:29:50 Manually triggered by user ishaby(a)redhat.com for Gerrit: > https://gerrit.ovirt.org/68804 > 07:29:50 [EnvInject] - Loading node environment variables. > 07:29:50 Building remotely on fc24-vm15.phx.ovirt.org (fc24 phx > local_disk nested) in workspace > /home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64 > 07:29:50 > git rev-parse --is-inside-work-tree # timeout=10 > 07:29:50 Fetching changes from the remote Git repository > 07:29:50 > git config remote.origin.url > git://gerrit.ovirt.org/vdsm.git # timeout=10 > 07:29:50 Cleaning workspace > 07:29:50 > git rev-parse --verify HEAD # timeout=10 > 07:29:50 Resetting working tree > 07:29:50 > git reset --hard # timeout=10 > 07:29:51 > git clean -fdx # timeout=10 > 07:29:51 Pruning obsolete local branches > 07:29:51 Fetching upstream changes from git://gerrit.ovirt.org/vdsm.git > 07:29:51 > git --version # timeout=10 > 07:29:51 > git -c core.askpass=true fetch --tags --progress > git://gerrit.ovirt.org/vdsm.git refs/changes/04/68804/3 --prune > 07:29:51 ERROR: Error fetching remote repo 'origin' > 07:29:51 hudson.plugins.git.GitException: Failed to fetch from > git://gerrit.ovirt.org/vdsm.git -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1500) CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit
by Barak Korren (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1500?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1500: ------------------------------------- [~eedri] Its the gerrit plugin, but it simple runs a gerrit command on ssh. You can try it yourself, send a command to update the vote for a patchset that is not the most recent one, Gerrit will add a comment that says you updated the vote but not update it in practice because it only keeps votes for the most recent patcheset. What we have here is a race condition - A new patchset was added before jenkins managed to add its vote, and because the new patchset was a trivial rebase no new jenkins job was invoked. A hook to copy the votes will not help here because they were not registered by Gerrit in the 1st place. The only solution I can think of ATM is to make Jenkins run jobs on trivial rebase too. > CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit > ------------------------------------------------------------------- > > Key: OVIRT-1500 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1500 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Gerrit/git, oVirt CI > Reporter: Allon Mureinik > Assignee: infra > > In my recent engine patch https://gerrit.ovirt.org/#/c/78911 the CI passed, but was not marked as so in gerrit. > Looking through gerrit's history, here's what I *think* is going on: > 08:41 - patchset #1 is submitted > 08:41 - CI (check-patch) starts for both EL7 and fc25 > _At this point I noticed a typo in the commit method. I fixed it and posted patchset #2_ > 08:42 - patchset #2 is submitted > _CI was never triggered for patchset #2. Is this because the only difference between it and patchset #1 is the commit message?_ > 09:15 - CI for patchset #1 completes, and marks *patchset #1* with CI=+1. This is not inherited to patchset #2 for some reason. > Expected behavior: > If CI for patchset #1 passed and the only difference is the commit message (not the parent commit and not the content), I'd expect the CI score to be inherited. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1502) gerrit does not print check_merged output
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1502?page=com.atlassian.jira.… ] eedri commented on OVIRT-1502: ------------------------------ I'm not sure it was sending emails, this might be duplicate: https://ovirt-jira.atlassian.net/browse/OVIRT-833 > gerrit does not print check_merged output > ----------------------------------------- > > Key: OVIRT-1502 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1502 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: ybronhei > Assignee: infra > > Hello, > Recently vdsm gerrit job check-merged doesn't send report after its done - > check all recent jobs - they were done but the gerrit url doesn't show the > output nor send email about failures. > Thanks in advance > Yaniv Bronhaim. > -- > Yaniv Bronhaim. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1500) CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1500?page=com.atlassian.jira.… ] eedri commented on OVIRT-1500: ------------------------------ [~bkorren(a)redhat.com][~ederevea] do we know who manages the flag scores on Gerrit? Is it configured on Gerrit Trigger side or on Gerrit conf itself? Is it configurable at all? I vaguely remember a hook that was maintaining the scores on trivial rebase. > CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit > ------------------------------------------------------------------- > > Key: OVIRT-1500 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1500 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Gerrit/git, oVirt CI > Reporter: Allon Mureinik > Assignee: infra > > In my recent engine patch https://gerrit.ovirt.org/#/c/78911 the CI passed, but was not marked as so in gerrit. > Looking through gerrit's history, here's what I *think* is going on: > 08:41 - patchset #1 is submitted > 08:41 - CI (check-patch) starts for both EL7 and fc25 > _At this point I noticed a typo in the commit method. I fixed it and posted patchset #2_ > 08:42 - patchset #2 is submitted > _CI was never triggered for patchset #2. Is this because the only difference between it and patchset #1 is the commit message?_ > 09:15 - CI for patchset #1 completes, and marks *patchset #1* with CI=+1. This is not inherited to patchset #2 for some reason. > Expected behavior: > If CI for patchset #1 passed and the only difference is the commit message (not the parent commit and not the content), I'd expect the CI score to be inherited. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1502) gerrit does not print check_merged output
by ybronhei (oVirt JIRA) 03 Jul '17

03 Jul '17

ybronhei created OVIRT-1502: ------------------------------- Summary: gerrit does not print check_merged output Key: OVIRT-1502 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1502 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: ybronhei Assignee: infra Hello, Recently vdsm gerrit job check-merged doesn't send report after its done - check all recent jobs - they were done but the gerrit url doesn't show the output nor send email about failures. Thanks in advance Yaniv Bronhaim. -- Yaniv Bronhaim. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1501) Jenkins slave is stuck on virsh cleanup
by Daniel Belenky (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1501?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-1501: ---------------------------------- Summary: Jenkins slave is stuck on virsh cleanup (was: Jenkins slave is stuck on libvirt cleanup) > Jenkins slave is stuck on virsh cleanup > --------------------------------------- > > Key: OVIRT-1501 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1501 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Daniel Belenky > Assignee: infra > > Jenkins slave was stuck on virsh cleanup. > The following job: [Link|http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-…] timed out after 6 hours. > The next job that tried to run on the same slave [link|http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-…] couldn't destroy the domain. > I couldn't manually destroy the domain either, and I've ended up rebooting the VM. > The slave that was rebooted: vm0015.workers-phx.ovirt.org. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1501) Jenkins slave is stuck on libvirt cleanup
by Daniel Belenky (oVirt JIRA) 03 Jul '17

03 Jul '17

Daniel Belenky created OVIRT-1501: ------------------------------------- Summary: Jenkins slave is stuck on libvirt cleanup Key: OVIRT-1501 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1501 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Daniel Belenky Assignee: infra Jenkins slave was stuck on virsh cleanup. The following job: [Link|http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-…] timed out after 6 hours. The next job that tried to run on the same slave [link|http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-…] couldn't destroy the domain. I couldn't manually destroy the domain either, and I've ended up rebooting the VM. The slave that was rebooted: vm0015.workers-phx.ovirt.org. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[oVirt Jenkins] standard-enqueue - Build #2224 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 03 Jul '17

03 Jul '17

------=_Part_122_48570426.1499075611183 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/standard-enqueue/2224/ Build Name: 2224 ovirt-engine (master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/78902 - title: core: remove unused fields in update cluster - project: ovirt-engine - branch: master - author: Arik Hadas <ahadas(a)redhat.com> ------=_Part_122_48570426.1499075611183--

1 0

[oVirt Jenkins] deploy-to-ovirt_experimental - Build #3038 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 03 Jul '17

03 Jul '17

------=_Part_120_1793821833.1499073008613 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental/3038/ Build Name: 3038 ovirt-engine-api-metamodel (master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/75083 - title: Live Documentation - Auto validation - project: ovirt-engine-api-metamodel - branch: master - author: Ori Liel <oliel(a)redhat.com> ------=_Part_120_1793821833.1499073008613--

1 0

[oVirt Jenkins] deploy-to-ovirt_experimental - Build #3036 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 03 Jul '17

03 Jul '17

------=_Part_118_1305787878.1499072396254 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental/3036/ Build Name: 3036 ovirt-engine-api-metamodel (master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/77793 - title: Generate doGet, doList methods - project: ovirt-engine-api-metamodel - branch: master - author: Ori Liel <oliel(a)redhat.com> ------=_Part_118_1305787878.1499072396254--

1 0

[JIRA] (OVIRT-1500) CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit
by Allon Mureinik (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1500?page=com.atlassian.jira.… ] Allon Mureinik edited comment on OVIRT-1500 at 7/3/17 11:52 AM: ---------------------------------------------------------------- {quote} So i'm not sure which inheritance are you reffering to, CI shouldn't run on patchset #2 since it was just commit msg update and returned +1 on the 1st patchset, no? {quote} Eyal - the behavior of just marking patchset #1 with CI=+1 is correct. I want this value *copied* to patchset #2, so it's visible from gerrit's dashboard. Otherwise, I need to see there's no CI score on the dashboard, go into this patch, read through the history to understand why it was never triggered on patchset #2 and mark CI=+1 myself (or manually trigger) in order to merge. Nothing here is technically "wrong", but it's a poor UX for gerrit users, and we should strive to improve it if possible. was (Author: mureinik): > So i'm not sure which inheritance are you reffering to, CI shouldn't run on patchset #2 since it was just commit msg update and returned +1 on the 1st patchset, no? Eyal - the behavior of just marking patchset #1 with CI=+1 is correct. I want this value **copied** to patchset #2, so it's visible from gerrit's dashboard. Otherwise, I need to see there's no CI score on the dashboard, go into this patch, read through the history to understand why it was never triggered on patchset #2 and mark CI=+1 myself (or manually trigger) in order to merge. Nothing here is technically "wrong", but it's a poor UX for gerrit users, and we should strive to improve it if possible. > CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit > ------------------------------------------------------------------- > > Key: OVIRT-1500 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1500 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Gerrit/git, oVirt CI > Reporter: Allon Mureinik > Assignee: infra > > In my recent engine patch https://gerrit.ovirt.org/#/c/78911 the CI passed, but was not marked as so in gerrit. > Looking through gerrit's history, here's what I *think* is going on: > 08:41 - patchset #1 is submitted > 08:41 - CI (check-patch) starts for both EL7 and fc25 > _At this point I noticed a typo in the commit method. I fixed it and posted patchset #2_ > 08:42 - patchset #2 is submitted > _CI was never triggered for patchset #2. Is this because the only difference between it and patchset #1 is the commit message?_ > 09:15 - CI for patchset #1 completes, and marks *patchset #1* with CI=+1. This is not inherited to patchset #2 for some reason. > Expected behavior: > If CI for patchset #1 passed and the only difference is the commit message (not the parent commit and not the content), I'd expect the CI score to be inherited. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1500) CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit
by Allon Mureinik (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1500?page=com.atlassian.jira.… ] Allon Mureinik commented on OVIRT-1500: --------------------------------------- > So i'm not sure which inheritance are you reffering to, CI shouldn't run on patchset #2 since it was just commit msg update and returned +1 on the 1st patchset, no? Eyal - the behavior of just marking patchset #1 with CI=+1 is correct. I want this value **copied** to patchset #2, so it's visible from gerrit's dashboard. Otherwise, I need to see there's no CI score on the dashboard, go into this patch, read through the history to understand why it was never triggered on patchset #2 and mark CI=+1 myself (or manually trigger) in order to merge. Nothing here is technically "wrong", but it's a poor UX for gerrit users, and we should strive to improve it if possible. > CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit > ------------------------------------------------------------------- > > Key: OVIRT-1500 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1500 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Gerrit/git, oVirt CI > Reporter: Allon Mureinik > Assignee: infra > > In my recent engine patch https://gerrit.ovirt.org/#/c/78911 the CI passed, but was not marked as so in gerrit. > Looking through gerrit's history, here's what I *think* is going on: > 08:41 - patchset #1 is submitted > 08:41 - CI (check-patch) starts for both EL7 and fc25 > _At this point I noticed a typo in the commit method. I fixed it and posted patchset #2_ > 08:42 - patchset #2 is submitted > _CI was never triggered for patchset #2. Is this because the only difference between it and patchset #1 is the commit message?_ > 09:15 - CI for patchset #1 completes, and marks *patchset #1* with CI=+1. This is not inherited to patchset #2 for some reason. > Expected behavior: > If CI for patchset #1 passed and the only difference is the commit message (not the parent commit and not the content), I'd expect the CI score to be inherited. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1468) Use CI mirrors for the slaves
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1468?page=com.atlassian.jira.… ] eedri commented on OVIRT-1468: ------------------------------ Let's discuss on the next CI meeting. > Use CI mirrors for the slaves > ----------------------------- > > Key: OVIRT-1468 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1468 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt Infra > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: jenkins, mirrors, slaves > > Since we've seen that issues like OVIRT-1467 can very quickly break our entire infrastructure, it may be advisable to use out mirrors to isolate the slave VMs from the upstream repos as well, and not just the testing environments. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1468) Use CI mirrors for the slaves
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1468?page=com.atlassian.jira.… ] eedri updated OVIRT-1468: ------------------------- Priority: High (was: Medium) > Use CI mirrors for the slaves > ----------------------------- > > Key: OVIRT-1468 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1468 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt Infra > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: jenkins, mirrors, slaves > > Since we've seen that issues like OVIRT-1467 can very quickly break our entire infrastructure, it may be advisable to use out mirrors to isolate the slave VMs from the upstream repos as well, and not just the testing environments. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1500) CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1500?page=com.atlassian.jira.… ] eedri commented on OVIRT-1500: ------------------------------ bq. CI was never triggered for patchset #2. Is this because the only difference between it and patchset #1 is the commit message? The current configuration skips any change that doesn't include 'code change': "Exclude changes without code change from triggering build If set, this will ignore any patchset which Gerrit considers without any code changes from triggering this build. These patches did not contain any differences in code from the previous patchset and did not change the parent commit. " So i'm not sure which inheritance are you reffering to, CI shouldn't run on patchset #2 since it was just commit msg update and returned +1 on the 1st patchset, no? > CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit > ------------------------------------------------------------------- > > Key: OVIRT-1500 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1500 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Gerrit/git, oVirt CI > Reporter: Allon Mureinik > Assignee: infra > > In my recent engine patch https://gerrit.ovirt.org/#/c/78911 the CI passed, but was not marked as so in gerrit. > Looking through gerrit's history, here's what I *think* is going on: > 08:41 - patchset #1 is submitted > 08:41 - CI (check-patch) starts for both EL7 and fc25 > _At this point I noticed a typo in the commit method. I fixed it and posted patchset #2_ > 08:42 - patchset #2 is submitted > _CI was never triggered for patchset #2. Is this because the only difference between it and patchset #1 is the commit message?_ > 09:15 - CI for patchset #1 completes, and marks *patchset #1* with CI=+1. This is not inherited to patchset #2 for some reason. > Expected behavior: > If CI for patchset #1 passed and the only difference is the commit message (not the parent commit and not the content), I'd expect the CI score to be inherited. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1468) Use CI mirrors for the slaves
by Barak Korren (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1468?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1468: ------------------------------------- Another case of job that has failed because of lack of this: http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-x86_64… We need to move forward. > Use CI mirrors for the slaves > ----------------------------- > > Key: OVIRT-1468 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1468 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt Infra > Reporter: Barak Korren > Assignee: infra > Labels: jenkins, mirrors, slaves > > Since we've seen that issues like OVIRT-1467 can very quickly break our entire infrastructure, it may be advisable to use out mirrors to isolate the slave VMs from the upstream repos as well, and not just the testing environments. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1500) CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit
by Gil Shinar (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1500?page=com.atlassian.jira.… ] Gil Shinar commented on OVIRT-1500: ----------------------------------- Saw it before. If the results of a certain patchset comes after the user has sent a new patchset, the CI will not get +1. All jobs should be retriggered for it to get the +1 > CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit > ------------------------------------------------------------------- > > Key: OVIRT-1500 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1500 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Gerrit/git, oVirt CI > Reporter: Allon Mureinik > Assignee: infra > > In my recent engine patch https://gerrit.ovirt.org/#/c/78911 the CI passed, but was not marked as so in gerrit. > Looking through gerrit's history, here's what I *think* is going on: > 08:41 - patchset #1 is submitted > 08:41 - CI (check-patch) starts for both EL7 and fc25 > _At this point I noticed a typo in the commit method. I fixed it and posted patchset #2_ > 08:42 - patchset #2 is submitted > _CI was never triggered for patchset #2. Is this because the only difference between it and patchset #1 is the commit message?_ > 09:15 - CI for patchset #1 completes, and marks *patchset #1* with CI=+1. This is not inherited to patchset #2 for some reason. > Expected behavior: > If CI for patchset #1 passed and the only difference is the commit message (not the parent commit and not the content), I'd expect the CI score to be inherited. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1500) CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit
by Allon Mureinik (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1500?page=com.atlassian.jira.… ] Allon Mureinik updated OVIRT-1500: ---------------------------------- Description: In my recent engine patch https://gerrit.ovirt.org/#/c/78911 the CI passed, but was not marked as so in gerrit. Looking through gerrit's history, here's what I *think* is going on: 08:41 - patchset #1 is submitted 08:41 - CI (check-patch) starts for both EL7 and fc25 _At this point I noticed a typo in the commit method. I fixed it and posted patchset #2_ 08:42 - patchset #2 is submitted _CI was never triggered for patchset #2. Is this because the only difference between it and patchset #1 is the commit message?_ 09:15 - CI for patchset #1 completes, and marks *patchset #1* with CI=+1. This is not inherited to patchset #2 for some reason. Expected behavior: If CI for patchset #1 passed and the only difference is the commit message (not the parent commit and not the content), I'd expect the CI score to be inherited. was: In my recent engine patch https://gerrit.ovirt.org/#/c/78911 the CI passed, but was not marked as so in gerrit. Looking through gerrit's history, here's what I *think* is going on: 08:41 - patchset #1 is submitted 08:41 - CI (check-patch) starts for both EL7 and fc25 * At this point I noticed a typo in the commit method. I fixed it and posted patchset #2 * 08:42 - patchset #2 is submitted * CI was never triggered for patchset #2. Is this because the only difference between it and patchset #1 is the commit message ? * 09:15 - CI for patchset #1 completes, and marks *patchset #1* with CI=+1. This is not inherited to patchset #2 for some reason. Expected behavior: If CI for patchset #1 passed and the only difference is the commit message (not the parent commit and not the content), I'd expect the CI score to be inherited. > CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit > ------------------------------------------------------------------- > > Key: OVIRT-1500 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1500 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Gerrit/git, oVirt CI > Reporter: Allon Mureinik > Assignee: infra > > In my recent engine patch https://gerrit.ovirt.org/#/c/78911 the CI passed, but was not marked as so in gerrit. > Looking through gerrit's history, here's what I *think* is going on: > 08:41 - patchset #1 is submitted > 08:41 - CI (check-patch) starts for both EL7 and fc25 > _At this point I noticed a typo in the commit method. I fixed it and posted patchset #2_ > 08:42 - patchset #2 is submitted > _CI was never triggered for patchset #2. Is this because the only difference between it and patchset #1 is the commit message?_ > 09:15 - CI for patchset #1 completes, and marks *patchset #1* with CI=+1. This is not inherited to patchset #2 for some reason. > Expected behavior: > If CI for patchset #1 passed and the only difference is the commit message (not the parent commit and not the content), I'd expect the CI score to be inherited. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1500) CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit
by Allon Mureinik (oVirt JIRA) 03 Jul '17

03 Jul '17

Allon Mureinik created OVIRT-1500: ------------------------------------- Summary: CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit Key: OVIRT-1500 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1500 Project: oVirt - virtualization made easy Issue Type: Bug Components: Gerrit/git, oVirt CI Reporter: Allon Mureinik Assignee: infra In my recent engine patch https://gerrit.ovirt.org/#/c/78911 the CI passed, but was not marked as so in gerrit. Looking through gerrit's history, here's what I *think* is going on: 08:41 - patchset #1 is submitted 08:41 - CI (check-patch) starts for both EL7 and fc25 * At this point I noticed a typo in the commit method. I fixed it and posted patchset #2 * 08:42 - patchset #2 is submitted * CI was never triggered for patchset #2. Is this because the only difference between it and patchset #1 is the commit message ? * 09:15 - CI for patchset #1 completes, and marks *patchset #1* with CI=+1. This is not inherited to patchset #2 for some reason. Expected behavior: If CI for patchset #1 passed and the only difference is the commit message (not the parent commit and not the content), I'd expect the CI score to be inherited. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1500) CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit
by Allon Mureinik (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1500?page=com.atlassian.jira.… ] Allon Mureinik updated OVIRT-1500: ---------------------------------- Epic Link: OVIRT-400 > CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit > ------------------------------------------------------------------- > > Key: OVIRT-1500 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1500 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Gerrit/git, oVirt CI > Reporter: Allon Mureinik > Assignee: infra > > In my recent engine patch https://gerrit.ovirt.org/#/c/78911 the CI passed, but was not marked as so in gerrit. > Looking through gerrit's history, here's what I *think* is going on: > 08:41 - patchset #1 is submitted > 08:41 - CI (check-patch) starts for both EL7 and fc25 > * At this point I noticed a typo in the commit method. I fixed it and posted patchset #2 * > 08:42 - patchset #2 is submitted > * CI was never triggered for patchset #2. Is this because the only difference between it and patchset #1 is the commit message ? * > 09:15 - CI for patchset #1 completes, and marks *patchset #1* with CI=+1. This is not inherited to patchset #2 for some reason. > Expected behavior: > If CI for patchset #1 passed and the only difference is the commit message (not the parent commit and not the content), I'd expect the CI score to be inherited. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[oVirt Jenkins] ovirt-node-ng_master_build-artifacts-el7-x86_64 - Build # 460 - Failure!
by jenkins＠jenkins.phx.ovirt.org 03 Jul '17

03 Jul '17

------=_Part_67_1073209132.1498881854179 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… Build Number: 460 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #460 ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_67_1073209132.1498881854179--

1 3

Change 78909,1 (ovirt-engine) failed system tests
by oVirt Jenkins 03 Jul '17

03 Jul '17

Change 78909,1 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/78909/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1027/

1 0

[JIRA] (OVIRT-1097) review ovirt snapshot static repos and remove not needed RPMs
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1097?page=com.atlassian.jira.… ] eedri reassigned OVIRT-1097: ---------------------------- Assignee: eedri (was: infra) > review ovirt snapshot static repos and remove not needed RPMs > ------------------------------------------------------------- > > Key: OVIRT-1097 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1097 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eedri > Assignee: eedri > Priority: High > > We should aim to drop the static repos, any RPMs oVirt needs should come from one of the following sources: > 1. Built in standard CI via build artifacts job > 2. If its external, then we need to use the origin repo and not copy it to be on oVirt. > We can start from master and move to stable versions when its verified. > existing RPMS on master static: (showing el7 as most OS should be similar ) > . > ├── noarch > │ ├── ebay-cors-filter-1.0.1-3.el7.noarch.rpm > │ ├── ebay-cors-filter-javadoc-1.0.1-3.el7.noarch.rpm > │ ├── nsis-simple-service-plugin-1.30-1.noarch.rpm > │ ├── openvswitch-selinux-policy-2.6.90-1.el7.centos.noarch.rpm > │ ├── openvswitch-test-2.6.90-1.el7.centos.noarch.rpm > │ ├── ovirt-engine-wildfly-overlay-10.0.0-1.el7.noarch.rpm > │ ├── python-openvswitch-2.6.90-1.el7.centos.noarch.rpm > │ ├── rubygem-fluent-plugin-rewrite-tag-filter-1.5.5-1.el7.centos.noarch.rpm > │ └── rubygem-fluent-plugin-rewrite-tag-filter-doc-1.5.5-1.el7.centos.noarch.rpm > ├── ppc64 > │ ├── python-cpopen-1.3-4.el7.ppc64.rpm > │ └── python-cpopen-debuginfo-1.3-4.el7.ppc64.rpm > ├── ppc64le > ├── repodata > │ ├── 008d859bb942a115e9b0077bd65c84f49e5a01eca2209ad393c27a036237783f-filelists.xml.gz > │ ├── 14a142882a77ec4120c34a7d88dd69bdcf9463915c34d0f139fe6a9f01a78ca5-filelists.sqlite.bz2 > │ ├── 3299fdf213c4ee0e8bea41142691d1ab861496291a2302dfa32a7247eb43660c-primary.xml.gz > │ ├── 648a0a77bce1ba70babe4c8f5ac90b8f4b89103f8fa429903d572022066367be-primary.sqlite.bz2 > │ ├── 715d2c608d40b1982b5a02c1c98bc6fca827e46d260849afc8eec6ad928caa6f-other.xml.gz > │ ├── f54bf13a0e486128a9bc41a975e4ecf597b553c47a7cdb70c169ce8c042c3b94-other.sqlite.bz2 > │ └── repomd.xml > ├── SRPMS > │ ├── ebay-cors-filter-1.0.1-3.el7.src.rpm > │ ├── nsis-simple-service-plugin-1.30-1.src.rpm > │ ├── openvswitch-2.6.90-1.el7.centos.src.rpm > │ ├── ovirt-engine-wildfly-10.1.0-1.el7.src.rpm > │ ├── ovirt-engine-wildfly-overlay-10.0.0-1.el7.src.rpm > │ ├── ovirt-web-ui-0.1.0-4.el7.centos.src.rpm > │ ├── ovirt-web-ui-0.1.1-2.el7.centos.src.rpm > │ ├── repodata > │ │ ├── 1f13684ed34daa19755884e49132dcee7b60eafd38b52a51f945a92e63459e65-filelists.xml.gz > │ │ ├── 3f20e34cc666f1df8667288b5cdf3eb449fed6ab8b032e1a0d9be0fc78d53b56-primary.sqlite.bz2 > │ │ ├── 7e260234efc35f032a0d22f976d17758b28555566d742c04911a4758c3552db1-primary.xml.gz > │ │ ├── 87cdc086330908e1dc39ca53c50eb9b6ba3627b2b562e0d278a0e899fd925167-other.xml.gz > │ │ ├── e2cb0de1abd9d51f783862d7d498ead766a96261dd942230f0182afee7195bdb-other.sqlite.bz2 > │ │ ├── ed15cb166756bbf49aecd3f8e65ca0da96ca860d64e4fc80a141280a9114e5ee-filelists.sqlite.bz2 > │ │ └── repomd.xml > │ ├── rubygem-fluent-plugin-rewrite-tag-filter-1.5.5-1.el7.centos.src.rpm > │ └── vhostmd-0.5-11.el7.src.rpm > └── x86_64 > ├── openvswitch-2.6.90-1.el7.centos.x86_64.rpm > ├── openvswitch-debuginfo-2.6.90-1.el7.centos.x86_64.rpm > ├── openvswitch-devel-2.6.90-1.el7.centos.x86_64.rpm > ├── openvswitch-ovn-central-2.6.90-1.el7.centos.x86_64.rpm > ├── openvswitch-ovn-common-2.6.90-1.el7.centos.x86_64.rpm > ├── openvswitch-ovn-docker-2.6.90-1.el7.centos.x86_64.rpm > ├── openvswitch-ovn-host-2.6.90-1.el7.centos.x86_64.rpm > ├── openvswitch-ovn-vtep-2.6.90-1.el7.centos.x86_64.rpm > ├── ovirt-engine-wildfly-10.1.0-1.el7.x86_64.rpm > ├── ovirt-web-ui-0.1.0-4.el7.centos.x86_64.rpm > ├── ovirt-web-ui-0.1.1-2.el7.centos.x86_64.rpm > ├── vhostmd-0.5-11.el7.x86_64.rpm > ├── vhostmd-debuginfo-0.5-11.el7.x86_64.rpm > ├── vm-dump-metrics-0.5-11.el7.x86_64.rpm > └── vm-dump-metrics-devel-0.5-11.el7.x86_64.rpm -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1097) review ovirt snapshot static repos and remove not needed RPMs
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1097?page=com.atlassian.jira.… ] eedri updated OVIRT-1097: ------------------------- Priority: High (was: Medium) > review ovirt snapshot static repos and remove not needed RPMs > ------------------------------------------------------------- > > Key: OVIRT-1097 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1097 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eedri > Assignee: infra > Priority: High > > We should aim to drop the static repos, any RPMs oVirt needs should come from one of the following sources: > 1. Built in standard CI via build artifacts job > 2. If its external, then we need to use the origin repo and not copy it to be on oVirt. > We can start from master and move to stable versions when its verified. > existing RPMS on master static: (showing el7 as most OS should be similar ) > . > ├── noarch > │ ├── ebay-cors-filter-1.0.1-3.el7.noarch.rpm > │ ├── ebay-cors-filter-javadoc-1.0.1-3.el7.noarch.rpm > │ ├── nsis-simple-service-plugin-1.30-1.noarch.rpm > │ ├── openvswitch-selinux-policy-2.6.90-1.el7.centos.noarch.rpm > │ ├── openvswitch-test-2.6.90-1.el7.centos.noarch.rpm > │ ├── ovirt-engine-wildfly-overlay-10.0.0-1.el7.noarch.rpm > │ ├── python-openvswitch-2.6.90-1.el7.centos.noarch.rpm > │ ├── rubygem-fluent-plugin-rewrite-tag-filter-1.5.5-1.el7.centos.noarch.rpm > │ └── rubygem-fluent-plugin-rewrite-tag-filter-doc-1.5.5-1.el7.centos.noarch.rpm > ├── ppc64 > │ ├── python-cpopen-1.3-4.el7.ppc64.rpm > │ └── python-cpopen-debuginfo-1.3-4.el7.ppc64.rpm > ├── ppc64le > ├── repodata > │ ├── 008d859bb942a115e9b0077bd65c84f49e5a01eca2209ad393c27a036237783f-filelists.xml.gz > │ ├── 14a142882a77ec4120c34a7d88dd69bdcf9463915c34d0f139fe6a9f01a78ca5-filelists.sqlite.bz2 > │ ├── 3299fdf213c4ee0e8bea41142691d1ab861496291a2302dfa32a7247eb43660c-primary.xml.gz > │ ├── 648a0a77bce1ba70babe4c8f5ac90b8f4b89103f8fa429903d572022066367be-primary.sqlite.bz2 > │ ├── 715d2c608d40b1982b5a02c1c98bc6fca827e46d260849afc8eec6ad928caa6f-other.xml.gz > │ ├── f54bf13a0e486128a9bc41a975e4ecf597b553c47a7cdb70c169ce8c042c3b94-other.sqlite.bz2 > │ └── repomd.xml > ├── SRPMS > │ ├── ebay-cors-filter-1.0.1-3.el7.src.rpm > │ ├── nsis-simple-service-plugin-1.30-1.src.rpm > │ ├── openvswitch-2.6.90-1.el7.centos.src.rpm > │ ├── ovirt-engine-wildfly-10.1.0-1.el7.src.rpm > │ ├── ovirt-engine-wildfly-overlay-10.0.0-1.el7.src.rpm > │ ├── ovirt-web-ui-0.1.0-4.el7.centos.src.rpm > │ ├── ovirt-web-ui-0.1.1-2.el7.centos.src.rpm > │ ├── repodata > │ │ ├── 1f13684ed34daa19755884e49132dcee7b60eafd38b52a51f945a92e63459e65-filelists.xml.gz > │ │ ├── 3f20e34cc666f1df8667288b5cdf3eb449fed6ab8b032e1a0d9be0fc78d53b56-primary.sqlite.bz2 > │ │ ├── 7e260234efc35f032a0d22f976d17758b28555566d742c04911a4758c3552db1-primary.xml.gz > │ │ ├── 87cdc086330908e1dc39ca53c50eb9b6ba3627b2b562e0d278a0e899fd925167-other.xml.gz > │ │ ├── e2cb0de1abd9d51f783862d7d498ead766a96261dd942230f0182afee7195bdb-other.sqlite.bz2 > │ │ ├── ed15cb166756bbf49aecd3f8e65ca0da96ca860d64e4fc80a141280a9114e5ee-filelists.sqlite.bz2 > │ │ └── repomd.xml > │ ├── rubygem-fluent-plugin-rewrite-tag-filter-1.5.5-1.el7.centos.src.rpm > │ └── vhostmd-0.5-11.el7.src.rpm > └── x86_64 > ├── openvswitch-2.6.90-1.el7.centos.x86_64.rpm > ├── openvswitch-debuginfo-2.6.90-1.el7.centos.x86_64.rpm > ├── openvswitch-devel-2.6.90-1.el7.centos.x86_64.rpm > ├── openvswitch-ovn-central-2.6.90-1.el7.centos.x86_64.rpm > ├── openvswitch-ovn-common-2.6.90-1.el7.centos.x86_64.rpm > ├── openvswitch-ovn-docker-2.6.90-1.el7.centos.x86_64.rpm > ├── openvswitch-ovn-host-2.6.90-1.el7.centos.x86_64.rpm > ├── openvswitch-ovn-vtep-2.6.90-1.el7.centos.x86_64.rpm > ├── ovirt-engine-wildfly-10.1.0-1.el7.x86_64.rpm > ├── ovirt-web-ui-0.1.0-4.el7.centos.x86_64.rpm > ├── ovirt-web-ui-0.1.1-2.el7.centos.x86_64.rpm > ├── vhostmd-0.5-11.el7.x86_64.rpm > ├── vhostmd-debuginfo-0.5-11.el7.x86_64.rpm > ├── vm-dump-metrics-0.5-11.el7.x86_64.rpm > └── vm-dump-metrics-devel-0.5-11.el7.x86_64.rpm -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1156) Fwd: build-artifacts-on-demand marks CI +1
by Barak Korren (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1156?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1156: ----------------------------------- Assignee: Barak Korren (was: infra) > Fwd: build-artifacts-on-demand marks CI +1 > ------------------------------------------ > > Key: OVIRT-1156 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1156 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Barak Korren > Assignee: Barak Korren > Labels: standard-ci > > Forwarding to Jira. > ---------- Forwarded message ---------- > From: Yedidyah Bar David <didi(a)redhat.com> > Date: 16 February 2017 at 15:02 > Subject: build-artifacts-on-demand marks CI +1 > To: infra <infra(a)ovirt.org> > Hi all, > I have a change [1] that currently fails some jenkins jobs, so it gets > -1 from it. After pushing patchset 4 (a mere rebase actually), I ran > build-artifacts-on-demand ("ci please build"), and it passed, and set > CI +1. Then I rebased again and again got -1 as expected. > IMO build-artifacts-on-demand should not set CI +1, it might be > misleading for the maintainer to think that all is good when in fact > CI failed. > [1] https://gerrit.ovirt.org/71590 > -- > Didi > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > -- > Barak Korren > bkorren(a)redhat.com > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1156) Fwd: build-artifacts-on-demand marks CI +1
by Barak Korren (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1156?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1156: ------------------------------------- Created [a patch|https://gerrit.ovirt.org/78921] to fix this. [~danken(a)redhat.com] since you are the last person to report this, can you help +v the patch? I've applied it to the 'vdsm_master_build-artifacts-on-demand-*' jobs. > Fwd: build-artifacts-on-demand marks CI +1 > ------------------------------------------ > > Key: OVIRT-1156 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1156 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > Forwarding to Jira. > ---------- Forwarded message ---------- > From: Yedidyah Bar David <didi(a)redhat.com> > Date: 16 February 2017 at 15:02 > Subject: build-artifacts-on-demand marks CI +1 > To: infra <infra(a)ovirt.org> > Hi all, > I have a change [1] that currently fails some jenkins jobs, so it gets > -1 from it. After pushing patchset 4 (a mere rebase actually), I ran > build-artifacts-on-demand ("ci please build"), and it passed, and set > CI +1. Then I rebased again and again got -1 as expected. > IMO build-artifacts-on-demand should not set CI +1, it might be > misleading for the maintainer to think that all is good when in fact > CI failed. > [1] https://gerrit.ovirt.org/71590 > -- > Didi > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > -- > Barak Korren > bkorren(a)redhat.com > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

Change 77768,30 (vdsm) failed system tests
by oVirt Jenkins 03 Jul '17

03 Jul '17

A system test invoked by the "ovirt-master" change queue including change 77768,30 (vdsm) failed. However, this change seems not to be to root cause for failure. Change 78630,13 (vdsm) that this change depends on or is based on, was detected to cause testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 78630,13 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/77768/30 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/78630/13 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1025/

1 0

[JIRA] (OVIRT-1499) false CI+1 on https://gerrit.ovirt.org/#/c/78910/1
by Barak Korren (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1499?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1499: -------------------------------- Resolution: Duplicate Status: Done (was: To Do) This is a duplicate of OVIRT-1156 > false CI+1 on https://gerrit.ovirt.org/#/c/78910/1 > -------------------------------------------------- > > Key: OVIRT-1499 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1499 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: danken > Assignee: infra > > I've posted https://gerrit.ovirt.org/#/c/78910/1 that included a > python style problem, and immediately asked for "ci please build". > http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/14766/ > justly gave me -1, but the later > http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-on-demand-el7-x86_… > flipped it to +1. > This is wrong, and could have caused breakage of vdsm master. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1156) Fwd: build-artifacts-on-demand marks CI +1
by Barak Korren (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1156?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1156: -------------------------------- Labels: standard-ci (was: sy) > Fwd: build-artifacts-on-demand marks CI +1 > ------------------------------------------ > > Key: OVIRT-1156 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1156 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > Forwarding to Jira. > ---------- Forwarded message ---------- > From: Yedidyah Bar David <didi(a)redhat.com> > Date: 16 February 2017 at 15:02 > Subject: build-artifacts-on-demand marks CI +1 > To: infra <infra(a)ovirt.org> > Hi all, > I have a change [1] that currently fails some jenkins jobs, so it gets > -1 from it. After pushing patchset 4 (a mere rebase actually), I ran > build-artifacts-on-demand ("ci please build"), and it passed, and set > CI +1. Then I rebased again and again got -1 as expected. > IMO build-artifacts-on-demand should not set CI +1, it might be > misleading for the maintainer to think that all is good when in fact > CI failed. > [1] https://gerrit.ovirt.org/71590 > -- > Didi > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > -- > Barak Korren > bkorren(a)redhat.com > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1156) Fwd: build-artifacts-on-demand marks CI +1
by Barak Korren (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1156?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1156: -------------------------------- Labels: sy (was: ) > Fwd: build-artifacts-on-demand marks CI +1 > ------------------------------------------ > > Key: OVIRT-1156 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1156 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: sy > > Forwarding to Jira. > ---------- Forwarded message ---------- > From: Yedidyah Bar David <didi(a)redhat.com> > Date: 16 February 2017 at 15:02 > Subject: build-artifacts-on-demand marks CI +1 > To: infra <infra(a)ovirt.org> > Hi all, > I have a change [1] that currently fails some jenkins jobs, so it gets > -1 from it. After pushing patchset 4 (a mere rebase actually), I ran > build-artifacts-on-demand ("ci please build"), and it passed, and set > CI +1. Then I rebased again and again got -1 as expected. > IMO build-artifacts-on-demand should not set CI +1, it might be > misleading for the maintainer to think that all is good when in fact > CI failed. > [1] https://gerrit.ovirt.org/71590 > -- > Didi > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > -- > Barak Korren > bkorren(a)redhat.com > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1156) Fwd: build-artifacts-on-demand marks CI +1
by Barak Korren (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1156?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1156: -------------------------------- Component/s: oVirt CI > Fwd: build-artifacts-on-demand marks CI +1 > ------------------------------------------ > > Key: OVIRT-1156 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1156 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > > Forwarding to Jira. > ---------- Forwarded message ---------- > From: Yedidyah Bar David <didi(a)redhat.com> > Date: 16 February 2017 at 15:02 > Subject: build-artifacts-on-demand marks CI +1 > To: infra <infra(a)ovirt.org> > Hi all, > I have a change [1] that currently fails some jenkins jobs, so it gets > -1 from it. After pushing patchset 4 (a mere rebase actually), I ran > build-artifacts-on-demand ("ci please build"), and it passed, and set > CI +1. Then I rebased again and again got -1 as expected. > IMO build-artifacts-on-demand should not set CI +1, it might be > misleading for the maintainer to think that all is good when in fact > CI failed. > [1] https://gerrit.ovirt.org/71590 > -- > Didi > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > -- > Barak Korren > bkorren(a)redhat.com > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1499) false CI+1 on https://gerrit.ovirt.org/#/c/78910/1
by danken (oVirt JIRA) 03 Jul '17

03 Jul '17

danken created OVIRT-1499: ----------------------------- Summary: false CI+1 on https://gerrit.ovirt.org/#/c/78910/1 Key: OVIRT-1499 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1499 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: danken Assignee: infra I've posted https://gerrit.ovirt.org/#/c/78910/1 that included a python style problem, and immediately asked for "ci please build". http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/14766/ justly gave me -1, but the later http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-on-demand-el7-x86_… flipped it to +1. This is wrong, and could have caused breakage of vdsm master. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[oVirt Jenkins] ovirt-node-ng_ovirt-4.1-snapshot_build-artifacts-el7-x86_64 - Build # 176 - Failure!
by jenkins＠jenkins.phx.ovirt.org 03 Jul '17

03 Jul '17

------=_Part_63_456482479.1498881608713 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-snapshot_build-artifac… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-snapshot_build-artifac… Build Number: 176 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #176 ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_63_456482479.1498881608713--

1 3

Change 78630,13 (vdsm) failed system tests
by oVirt Jenkins 02 Jul '17

02 Jul '17

Change 78630,13 (vdsm) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/78630/13 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1023/

1 0

oVirt infra daily report - unstable production jobs - 371
by jenkins＠jenkins.phx.ovirt.org 02 Jul '17

02 Jul '17

------=_Part_106_284037677.1499036402068 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/371//artifact/exported-a… Cheers, Jenkins ------=_Part_106_284037677.1499036402068 Content-Type: text/html; charset=us-ascii; 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 - 02/07/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_he-system-tests/">ovirt_master_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/test-repo_ovirt_experimental_master/">test-repo_ovirt_experimental_master</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_106_284037677.1499036402068--

1 0

[JIRA] (OVIRT-1498) Gate lago versions with change-queue
by Barak Korren (oVirt JIRA) 02 Jul '17

02 Jul '17

Barak Korren created OVIRT-1498: ----------------------------------- Summary: Gate lago versions with change-queue Key: OVIRT-1498 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1498 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra Priority: High Lago should be considered an upstream dependency, like CentOS and libvirt. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1498) Gate lago versions with change-queue
by Barak Korren (oVirt JIRA) 02 Jul '17

02 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1498?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1498: -------------------------------- Epic Link: OVIRT-400 > Gate lago versions with change-queue > ------------------------------------ > > Key: OVIRT-1498 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1498 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: change-queue, gating, lago, ost > > Lago should be considered an upstream dependency, like CentOS and libvirt. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #7428 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 02 Jul '17

02 Jul '17

------=_Part_97_757660688.1498990003291 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/7428/, Build Number: 7428, Build Status: FAILURE ------=_Part_97_757660688.1498990003291--

1 1

Change 78622,8 (ovirt-engine) failed system tests
by oVirt Jenkins 02 Jul '17

02 Jul '17

Change 78622,8 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/78622/8 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1017/

1 0

Jenkins build became unstable: ovirt_4.1_publish-rpms_nightly #232
by jenkins＠jenkins.phx.ovirt.org 02 Jul '17

02 Jul '17

See <http://jenkins.ovirt.org/job/ovirt_4.1_publish-rpms_nightly/232/display/red…>

1 2

New Gerrit 2.13 UI updates
by Eyal Edri 02 Jul '17

02 Jul '17

FYI, Following last night Gerrit upgrade to 2.13.8 ( Thanks Evgheni! ), there are some nice updates worth mentioning: (I really like the new 'blame' option on the diff screen... :) User Interface - The UI can now be loaded in an iFrame by enabling gerrit.canLoadInIFrame <https://gerrit-documentation.storage.googleapis.com/Documentation/2.13/conf…> in the site configuration. <https://www.gerritcodereview.com/releases/2.13.md#Change-Screen>Change Screen - Issue 106 <https://bugs.chromium.org/p/gerrit/issues/detail?id=106>: Allow to select merge commit's parent for diff base in change screen. - Issue 3035 <https://bugs.chromium.org/p/gerrit/issues/detail?id=3035>: Allow to remove specific votes from a change, while leaving the reviewer on the change. - Issue 3487 <https://bugs.chromium.org/p/gerrit/issues/detail?id=3487>: Use ‘Ctrl-Alt-e’ instead of ‘e’ to open edit mode. <https://www.gerritcodereview.com/releases/2.13.md#Diff-Screens>Diff Screens - Add all syntax highlighting available in CodeMirror. - Improve search experience in diff screen. Ctrl-F, Ctrl-G and Shift-Ctrl-G now bind to the search dialog box provided by CodeMirror's search add-on. Enter and Shift-Enter navigate among the search results from the CodeMirror search, just like they do in a normal browser search. Esc now clears the search result. If the user sets Render to Slow in the diff preferences and the file is less than 4000 lines (huge), then Ctrl-F, Ctrl-G and Shift-Ctrl-G fall back to the browser search. - Issue 2968 <https://bugs.chromium.org/p/gerrit/issues/detail?id=2968>: Allow to go back to change list by keyboard shortcut from diff screens. - Blame annotations. By enabling change.allowBlame <https://gerrit-documentation.storage.googleapis.com/Documentation/2.13/conf…>, blame annotations can be shown in the side-by-side diff screen gutter. Clicking the annotation opens the relevant change. <https://www.gerritcodereview.com/releases/2.13.md#User-Preferences>User Preferences - Issue 989 <https://bugs.chromium.org/p/gerrit/issues/detail?id=989>: New option to control email notifications. Users can now choose between ‘Enabled’, ‘Disabled’ and ‘CC Me on Comments I Write’. - New option to control adding ‘Signed-off-by’ footer in commit message of new changes created online. - New option to control auto-indent width in inline editor. - Issue 890 <https://bugs.chromium.org/p/gerrit/issues/detail?id=890>: New diff option to control whether to skip unchanged files when navigating to the previous or the next file. <https://www.gerritcodereview.com/releases/2.13.md#New-Features-Changes> Full changelog: https://www.gerritcodereview.com/releases/2.13.md -- Eyal edri ASSOCIATE MANAGER RHV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

2 1