April 2017 - Infra - oVirt List Archives

[JIRA] (OVIRT-1296) review Rebase Always submit strategy on Gerrit
by Evgheni Dereveanchin (oVirt JIRA) 04 Apr '17

04 Apr '17

Evgheni Dereveanchin created OVIRT-1296: ------------------------------------------- Summary: review Rebase Always submit strategy on Gerrit Key: OVIRT-1296 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1296 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Evgheni Dereveanchin Assignee: infra Priority: Lowest A new submit strategy was included in recent builds of Gerrit: Rebase Always. [Docs|https://gerrit-review.googlesource.com/Documentation/project-configura…] {quote}Basically, the same as Rebase If Necessary, but it creates a new patchset even if fast forward is possible AND like Cherry Pick it ensures footers such as Change-Id, Reviewed-On, and others are present in resulting commit that is merged. Thus, Rebase Always can be considered similar to Cherry Pick, but with the important distinction that Rebase Always does not ignore dependencies.{quote} It is only available in [2.14|https://gerrit.googlesource.com/gerrit/+/stable-2.14/gerrit-server/src…] while we are still at 2.12 and [2.13|https://gerrit.googlesource.com/gerrit/+/stable-2.13/gerrit-server/src…] is the current stable branch. -- This message was sent by Atlassian JIRA (v1000.870.5#100039)

1 0

[JIRA] (OVIRT-1250) Github PR builder plugin generates too many messages
by eyal edri [Administrator] (oVirt JIRA) 04 Apr '17

04 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1250?page=com.atlassian.jira.… ] eyal edri [Administrator] reassigned OVIRT-1250: ------------------------------------------------ Assignee: Daniel Belenky (was: infra) > Github PR builder plugin generates too many messages > ---------------------------------------------------- > > Key: OVIRT-1250 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1250 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Pavel Zhukov > Assignee: Daniel Belenky > > Seems like GH PR builder plugin posts one message like: > Can one of the admins verify this patch? > Per job which should be triggered. For example if we have el7/fc25/fc24/master jobs to be triggered by Pull Request it means message will appear 4 times in the GH UI which is useless and annoying. -- This message was sent by Atlassian JIRA (v1000.870.5#100039)

1 0

[JIRA] (OVIRT-1250) Github PR builder plugin generates too many messages
by Michal Skrivanek (oVirt JIRA) 04 Apr '17

04 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1250?page=com.atlassian.jira.… ] Michal Skrivanek commented on OVIRT-1250: ----------------------------------------- any progress? example of a message every 2 hours: https://github.com/oVirt/ovirt-web-ui/pull/113 > Github PR builder plugin generates too many messages > ---------------------------------------------------- > > Key: OVIRT-1250 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1250 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Pavel Zhukov > Assignee: infra > > Seems like GH PR builder plugin posts one message like: > Can one of the admins verify this patch? > Per job which should be triggered. For example if we have el7/fc25/fc24/master jobs to be triggered by Pull Request it means message will appear 4 times in the GH UI which is useless and annoying. -- This message was sent by Atlassian JIRA (v1000.870.5#100039)

1 0

[JIRA] (OVIRT-1295) Add job to auto-rebase patches that are ready to be merged
by Barak Korren (oVirt JIRA) 04 Apr '17

04 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1295?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1295: ------------------------------------- [~ykaul] To run OST, you need to automatically come up with a proper merging order, and then emulate the sequence of merges. Then you need to also build the artifacts, and only then you can start considering running OST. And you need to do all this for engine, vdsm, and probably other projects as well. And when OST fails, you also want to narrow down the failure to the specific patch that caused it. This is what we call "gating" or "patch-queueing" our currently ongoing "package gating" or "change queue" work (OVIRT-1077) is a necessary predecessor to that. > Add job to auto-rebase patches that are ready to be merged > ----------------------------------------------------------- > > Key: OVIRT-1295 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1295 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri [Administrator] > Assignee: infra > > We want to help stable branch maintainers to minimize the time needed for merging approved changes ( i.e CR +2 and VERIFY +1 ) and also to reduce the chance of merge conflicts. > A suggestion was made to create a job which will detect patches ready to be merged with the flags CR +2 and V +1 set and will auto rebase them, so when a maintainer is ready to submit a patch, hopefully the patch won't need a rebase and can be merged without further waiting for rebase or CI. > This approach might introduce challenges when working on patches that are dependent on other patches and a specific logic might be required to handle special cases. > [~tnisan(a)redhat.com][~ykaul][~dfediuck] I hope this conveys the need and requirement, please comment or add thoughts if I missed anything. > Initially we'll try enabling it for ovirt-engine on 4.1 branch. -- This message was sent by Atlassian JIRA (v1000.870.5#100039)

1 0

[JIRA] (OVIRT-1295) Add job to auto-rebase patches that are ready to be merged
by Yaniv Kaul (oVirt JIRA) 04 Apr '17

04 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1295?page=com.atlassian.jira.… ] Yaniv Kaul commented on OVIRT-1295: ----------------------------------- I think we need to see how many of those we have - and how many have CR+1 and V+1 and can go through the same process as well - on lower priority (say, on 3AM in the morning). What about running o-s-t on the first batch? > Add job to auto-rebase patches that are ready to be merged > ----------------------------------------------------------- > > Key: OVIRT-1295 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1295 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri [Administrator] > Assignee: infra > > We want to help stable branch maintainers to minimize the time needed for merging approved changes ( i.e CR +2 and VERIFY +1 ) and also to reduce the chance of merge conflicts. > A suggestion was made to create a job which will detect patches ready to be merged with the flags CR +2 and V +1 set and will auto rebase them, so when a maintainer is ready to submit a patch, hopefully the patch won't need a rebase and can be merged without further waiting for rebase or CI. > This approach might introduce challenges when working on patches that are dependent on other patches and a specific logic might be required to handle special cases. > [~tnisan(a)redhat.com][~ykaul][~dfediuck] I hope this conveys the need and requirement, please comment or add thoughts if I missed anything. > Initially we'll try enabling it for ovirt-engine on 4.1 branch. -- This message was sent by Atlassian JIRA (v1000.870.5#100039)

1 0

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #215
by jenkins＠jenkins.phx.ovirt.org 04 Apr '17

04 Apr '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/215/displa…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/ws/> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision bdca0b5702e3f2058805edcff168947ee95b1996 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f bdca0b5702e3f2058805edcff168947ee95b1996 > git rev-list bdca0b5702e3f2058805edcff168947ee95b1996 # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/hudson7434573794514853450.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 687, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 727, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 96, in retrieveAllMD downloading = repo._commonRetrieveDataMD_list(mdtypes) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1590, in _commonRetrieveDataMD_list os.rename(local, local + '.old.tmp') OSError: [Errno 2] No such file or directory Build step 'Execute shell' marked build as failure

1 1

[JIRA] (OVIRT-1295) Add job to auto-rebase patches that are ready to be merged
by eyal edri [Administrator] (oVirt JIRA) 04 Apr '17

04 Apr '17

eyal edri [Administrator] created OVIRT-1295: ------------------------------------------------ Summary: Add job to auto-rebase patches that are ready to be merged Key: OVIRT-1295 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1295 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: eyal edri [Administrator] Assignee: infra We want to help stable branch maintainers to minimize the time needed for merging approved changes ( i.e CR +2 and VERIFY +1 ) and also to reduce the chance of merge conflicts. A suggestion was made to create a job which will detect patches ready to be merged with the flags CR +2 and V +1 set and will auto rebase them, so when a maintainer is ready to submit a patch, hopefully the patch won't need a rebase and can be merged without further waiting for rebase or CI. This approach might introduce challenges when working on patches that are dependent on other patches and a specific logic might be required to handle special cases. [~tnisan(a)redhat.com][~ykaul][~dfediuck] I hope this conveys the need and requirement, please comment or add thoughts if I missed anything. Initially we'll try enabling it for ovirt-engine on 4.1 branch. -- This message was sent by Atlassian JIRA (v1000.870.5#100039)

1 0

[JIRA] (OVIRT-1295) Add job to auto-rebase patches that are ready to be merged
by eyal edri [Administrator] (oVirt JIRA) 04 Apr '17

04 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1295?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1295: --------------------------------------------- Epic Link: OVIRT-403 > Add job to auto-rebase patches that are ready to be merged > ----------------------------------------------------------- > > Key: OVIRT-1295 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1295 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri [Administrator] > Assignee: infra > > We want to help stable branch maintainers to minimize the time needed for merging approved changes ( i.e CR +2 and VERIFY +1 ) and also to reduce the chance of merge conflicts. > A suggestion was made to create a job which will detect patches ready to be merged with the flags CR +2 and V +1 set and will auto rebase them, so when a maintainer is ready to submit a patch, hopefully the patch won't need a rebase and can be merged without further waiting for rebase or CI. > This approach might introduce challenges when working on patches that are dependent on other patches and a specific logic might be required to handle special cases. > [~tnisan(a)redhat.com][~ykaul][~dfediuck] I hope this conveys the need and requirement, please comment or add thoughts if I missed anything. > Initially we'll try enabling it for ovirt-engine on 4.1 branch. -- This message was sent by Atlassian JIRA (v1000.870.5#100039)

1 0

Build failed in Jenkins: system-sync_mirrors-fedora-base-fc25-x86_64 #141
by jenkins＠jenkins.phx.ovirt.org 04 Apr '17

04 Apr '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-base-fc25-x86_64/14…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-base-fc25-x86_64/ws/> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune ERROR: Error fetching remote repo 'origin' hudson.plugins.git.GitException: Failed to fetch from http://gerrit.ovirt.org/jenkins.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:799) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1055) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1086) at hudson.scm.SCM.checkout(SCM.java:495) at hudson.model.AbstractProject.checkout(AbstractProject.java:1278) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1728) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404) Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune" returned status code 128: stdout: stderr: fatal: unable to access 'http://gerrit.ovirt.org/jenkins.git/': The requested URL returned error: 503 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1784) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1513) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:64) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:315) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145) at hudson.remoting.UserRequest.perform(UserRequest.java:153) at hudson.remoting.UserRequest.perform(UserRequest.java:50) at hudson.remoting.Request$2.run(Request.java:336) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) at ......remote call to mirrors.phx.ovirt.org(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1537) at hudson.remoting.UserResponse.retrieve(UserRequest.java:253) at hudson.remoting.Channel.call(Channel.java:822) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145) at sun.reflect.GeneratedMethodAccessor473.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131) at com.sun.proxy.$Proxy72.execute(Unknown Source) at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:797) ... 11 more ERROR: null

1 1

planned Gerrit maintenance
by Evgheni Dereveanchin 03 Apr '17

03 Apr '17

Hi everyone, I will be performing updates on gerrit.ovirt.org during the next hour. Within this period the UI and repositories may be unavailable. I will follow up as soon as maintenance activities are over. -- Regards, Evgheni Dereveanchin

1 1