- Infra - oVirt List Archives

[JENKINS] Failed to setup proejct vdsm_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 05 Mar '19

05 Mar '19

Failed to run project_setup.sh for: #3561 vdsm [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0100.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 05 Mar '19

05 Mar '19

Failed to run project_setup.sh for: #3555 vdsm [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0037.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 05 Mar '19

05 Mar '19

Failed to run project_setup.sh for: #3567 vdsm [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0004.workers-phx.ovirt.org.

1 0

[JIRA] (OVIRT-2691) All builds on vm0145.workers-phx.ovirt.org (fc28 phx nested) fail with: Error fetching remote repo 'origin'
by Eyal Edri (oVirt JIRA) 05 Mar '19

05 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2691?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2691: ---------------------------------- you can also just remove the workspace or chown to jenkins user. > All builds on vm0145.workers-phx.ovirt.org (fc28 phx nested) fail with: Error fetching remote repo 'origin' > ----------------------------------------------------------------------------------------------------------- > > Key: OVIRT-2691 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2691 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Nir Soffer > Assignee: Evgheni Dereveanchin > > Looks like all builds on Fedora 28 fail with this error now: > - > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > vm0145.workers-phx.ovirt.org (fc28 phx nested) > - > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > vm0145.workers-phx.ovirt.org (fc28 phx nested) > - > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > vm0145.workers-phx.ovirt.org (fc28 phx nested) > https://jenkins.ovirt.org/job/vdsm_standard-check-patch/buildTimeTrend > For some reason we always get the same slave for the py27 build. > ---- > No credentials specified > Fetching changes from the remote Git repository > Cleaning workspace > ERROR: Error fetching remote repo 'origin' > hudson.plugins.git.GitException: Failed to fetch from > https://gerrit.ovirt.org/vdsm > at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:904) > at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1144) > at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1175) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77) > at > org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > Caused by: hudson.plugins.git.GitException: Command "git clean -fdx" > returned status code 1: > stdout: > stderr: warning: failed to remove > .tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/plugin.cpython-27-PYTEST.pyc: > Permission denied > warning: failed to remove > .tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/compat.cpython-27-PYTEST.pyc: > Permission denied > warning: failed to remove > .tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/engine.cpython-27-PYTEST.pyc: > Permission denied > warning: failed to remove > .tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/embed.cpython-27-PYTEST.pyc: > Permission denied > warning: failed to remove > tests/__pycache__/pywatch_test.cpython-27-PYTEST.pyc: Permission denied > warning: failed to remove > tests/__pycache__/prlimit_test.cpython-27-PYTEST.pyc: Permission denied > warning: failed to remove tests/__pycache__/ssl_test.cpython-27-PYTEST.pyc: > Permission denied > warning: failed to remove > tests/__pycache__/hooking_test.cpython-27-PYTEST.pyc: Permission denied > warning: failed to remove > tests/common/__pycache__/systemd_test.cpython-27-PYTEST.pyc: Permission > denied > warning: failed to remove > tests/common/__pycache__/systemctl_test.cpython-27-PYTEST.pyc: Permission > denied > warning: failed to remove > tests/common/__pycache__/commands_test.cpython-27-PYTEST.pyc: Permission > denied > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2318) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2248) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2244) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1777) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1789) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.clean(CliGitAPIImpl.java:901) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.clean(CliGitAPIImpl.java:912) > at hudson.plugins.git.GitAPI.clean(GitAPI.java:311) > at sun.reflect.GeneratedMethodAccessor225.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:929) > at > hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:903) > at > hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:855) > at hudson.remoting.UserRequest.perform(UserRequest.java:212) > at hudson.remoting.UserRequest.perform(UserRequest.java:54) > at hudson.remoting.Request$2.run(Request.java:369) > at > hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) > ... 4 more > Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to > vm0145.workers-phx.ovirt.org > at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) > at > hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) > at hudson.remoting.Channel.call(Channel.java:955) > at > hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:283) > at com.sun.proxy.$Proxy96.clean(Unknown Source) > at > org.jenkinsci.plugins.gitclient.RemoteGitImpl.clean(RemoteGitImpl.java:463) > at > hudson.plugins.git.extensions.impl.CleanBeforeCheckout.decorateFetchCommand(CleanBeforeCheckout.java:30) > at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:900) > at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1144) > at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1175) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77) > at > org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > ... 4 more > > git rev-parse --is-inside-work-tree # timeout=10 > > git config remote.origin.url https://gerrit.ovirt.org/vdsm # timeout=10 > > git rev-parse --verify HEAD # timeout=10 > Resetting working tree > > git reset --hard # timeout=10 > > git clean -fdx # timeout=10 > Error fetching remote repo 'origin' -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2691) All builds on vm0145.workers-phx.ovirt.org (fc28 phx nested) fail with: Error fetching remote repo 'origin'
by Anton Marchukov (oVirt JIRA) 05 Mar '19

05 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2691?page=com.atlassian.jira.… ] Anton Marchukov commented on OVIRT-2691: ---------------------------------------- [~ederevea] I guess we can just reprovision the slave when convenient. The reason is found and the slave is disabled. Not urgent. > All builds on vm0145.workers-phx.ovirt.org (fc28 phx nested) fail with: Error fetching remote repo 'origin' > ----------------------------------------------------------------------------------------------------------- > > Key: OVIRT-2691 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2691 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Nir Soffer > Assignee: Evgheni Dereveanchin > > Looks like all builds on Fedora 28 fail with this error now: > - > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > vm0145.workers-phx.ovirt.org (fc28 phx nested) > - > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > vm0145.workers-phx.ovirt.org (fc28 phx nested) > - > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > vm0145.workers-phx.ovirt.org (fc28 phx nested) > https://jenkins.ovirt.org/job/vdsm_standard-check-patch/buildTimeTrend > For some reason we always get the same slave for the py27 build. > ---- > No credentials specified > Fetching changes from the remote Git repository > Cleaning workspace > ERROR: Error fetching remote repo 'origin' > hudson.plugins.git.GitException: Failed to fetch from > https://gerrit.ovirt.org/vdsm > at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:904) > at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1144) > at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1175) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77) > at > org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > Caused by: hudson.plugins.git.GitException: Command "git clean -fdx" > returned status code 1: > stdout: > stderr: warning: failed to remove > .tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/plugin.cpython-27-PYTEST.pyc: > Permission denied > warning: failed to remove > .tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/compat.cpython-27-PYTEST.pyc: > Permission denied > warning: failed to remove > .tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/engine.cpython-27-PYTEST.pyc: > Permission denied > warning: failed to remove > .tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/embed.cpython-27-PYTEST.pyc: > Permission denied > warning: failed to remove > tests/__pycache__/pywatch_test.cpython-27-PYTEST.pyc: Permission denied > warning: failed to remove > tests/__pycache__/prlimit_test.cpython-27-PYTEST.pyc: Permission denied > warning: failed to remove tests/__pycache__/ssl_test.cpython-27-PYTEST.pyc: > Permission denied > warning: failed to remove > tests/__pycache__/hooking_test.cpython-27-PYTEST.pyc: Permission denied > warning: failed to remove > tests/common/__pycache__/systemd_test.cpython-27-PYTEST.pyc: Permission > denied > warning: failed to remove > tests/common/__pycache__/systemctl_test.cpython-27-PYTEST.pyc: Permission > denied > warning: failed to remove > tests/common/__pycache__/commands_test.cpython-27-PYTEST.pyc: Permission > denied > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2318) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2248) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2244) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1777) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1789) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.clean(CliGitAPIImpl.java:901) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.clean(CliGitAPIImpl.java:912) > at hudson.plugins.git.GitAPI.clean(GitAPI.java:311) > at sun.reflect.GeneratedMethodAccessor225.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:929) > at > hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:903) > at > hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:855) > at hudson.remoting.UserRequest.perform(UserRequest.java:212) > at hudson.remoting.UserRequest.perform(UserRequest.java:54) > at hudson.remoting.Request$2.run(Request.java:369) > at > hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) > ... 4 more > Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to > vm0145.workers-phx.ovirt.org > at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) > at > hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) > at hudson.remoting.Channel.call(Channel.java:955) > at > hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:283) > at com.sun.proxy.$Proxy96.clean(Unknown Source) > at > org.jenkinsci.plugins.gitclient.RemoteGitImpl.clean(RemoteGitImpl.java:463) > at > hudson.plugins.git.extensions.impl.CleanBeforeCheckout.decorateFetchCommand(CleanBeforeCheckout.java:30) > at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:900) > at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1144) > at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1175) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77) > at > org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > ... 4 more > > git rev-parse --is-inside-work-tree # timeout=10 > > git config remote.origin.url https://gerrit.ovirt.org/vdsm # timeout=10 > > git rev-parse --verify HEAD # timeout=10 > Resetting working tree > > git reset --hard # timeout=10 > > git clean -fdx # timeout=10 > Error fetching remote repo 'origin' -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2691) All builds on vm0145.workers-phx.ovirt.org (fc28 phx nested) fail with: Error fetching remote repo 'origin'
by Anton Marchukov (oVirt JIRA) 05 Mar '19

05 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2691?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2691: -------------------------------------- Assignee: Evgheni Dereveanchin (was: Liora Milbaum) > All builds on vm0145.workers-phx.ovirt.org (fc28 phx nested) fail with: Error fetching remote repo 'origin' > ----------------------------------------------------------------------------------------------------------- > > Key: OVIRT-2691 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2691 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Nir Soffer > Assignee: Evgheni Dereveanchin > > Looks like all builds on Fedora 28 fail with this error now: > - > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > vm0145.workers-phx.ovirt.org (fc28 phx nested) > - > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > vm0145.workers-phx.ovirt.org (fc28 phx nested) > - > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > vm0145.workers-phx.ovirt.org (fc28 phx nested) > https://jenkins.ovirt.org/job/vdsm_standard-check-patch/buildTimeTrend > For some reason we always get the same slave for the py27 build. > ---- > No credentials specified > Fetching changes from the remote Git repository > Cleaning workspace > ERROR: Error fetching remote repo 'origin' > hudson.plugins.git.GitException: Failed to fetch from > https://gerrit.ovirt.org/vdsm > at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:904) > at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1144) > at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1175) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77) > at > org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > Caused by: hudson.plugins.git.GitException: Command "git clean -fdx" > returned status code 1: > stdout: > stderr: warning: failed to remove > .tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/plugin.cpython-27-PYTEST.pyc: > Permission denied > warning: failed to remove > .tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/compat.cpython-27-PYTEST.pyc: > Permission denied > warning: failed to remove > .tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/engine.cpython-27-PYTEST.pyc: > Permission denied > warning: failed to remove > .tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/embed.cpython-27-PYTEST.pyc: > Permission denied > warning: failed to remove > tests/__pycache__/pywatch_test.cpython-27-PYTEST.pyc: Permission denied > warning: failed to remove > tests/__pycache__/prlimit_test.cpython-27-PYTEST.pyc: Permission denied > warning: failed to remove tests/__pycache__/ssl_test.cpython-27-PYTEST.pyc: > Permission denied > warning: failed to remove > tests/__pycache__/hooking_test.cpython-27-PYTEST.pyc: Permission denied > warning: failed to remove > tests/common/__pycache__/systemd_test.cpython-27-PYTEST.pyc: Permission > denied > warning: failed to remove > tests/common/__pycache__/systemctl_test.cpython-27-PYTEST.pyc: Permission > denied > warning: failed to remove > tests/common/__pycache__/commands_test.cpython-27-PYTEST.pyc: Permission > denied > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2318) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2248) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2244) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1777) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1789) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.clean(CliGitAPIImpl.java:901) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.clean(CliGitAPIImpl.java:912) > at hudson.plugins.git.GitAPI.clean(GitAPI.java:311) > at sun.reflect.GeneratedMethodAccessor225.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:929) > at > hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:903) > at > hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:855) > at hudson.remoting.UserRequest.perform(UserRequest.java:212) > at hudson.remoting.UserRequest.perform(UserRequest.java:54) > at hudson.remoting.Request$2.run(Request.java:369) > at > hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) > ... 4 more > Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to > vm0145.workers-phx.ovirt.org > at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) > at > hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) > at hudson.remoting.Channel.call(Channel.java:955) > at > hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:283) > at com.sun.proxy.$Proxy96.clean(Unknown Source) > at > org.jenkinsci.plugins.gitclient.RemoteGitImpl.clean(RemoteGitImpl.java:463) > at > hudson.plugins.git.extensions.impl.CleanBeforeCheckout.decorateFetchCommand(CleanBeforeCheckout.java:30) > at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:900) > at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1144) > at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1175) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77) > at > org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > ... 4 more > > git rev-parse --is-inside-work-tree # timeout=10 > > git config remote.origin.url https://gerrit.ovirt.org/vdsm # timeout=10 > > git rev-parse --verify HEAD # timeout=10 > Resetting working tree > > git reset --hard # timeout=10 > > git clean -fdx # timeout=10 > Error fetching remote repo 'origin' -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

new user.
by Nir Levy 05 Mar '19

05 Mar '19

I am a new gerrit commiter I have send a patch to jenkins whitelist repo. please merge Regards, Nir.

3 3

[JIRA] (OVIRT-2685) Email not found on mailing list
by Anton Marchukov (oVirt JIRA) 05 Mar '19

05 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2685?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2685: -------------------------------------- Assignee: Marc Dequènes (Duck) (was: infra) > Email not found on mailing list > ------------------------------- > > Key: OVIRT-2685 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2685 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Bitbucket > Assignee: Marc Dequènes (Duck) > > Hi, > I'm trying to do a password reset on mailling list, it says email is not > found. I'm receiving mailing list daily on > al(a)cyberversion.com > -- > Robin -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2688) OST manual: enable engine 4.3
by Anton Marchukov (oVirt JIRA) 05 Mar '19

05 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2688?page=com.atlassian.jira.… ] Anton Marchukov updated OVIRT-2688: ----------------------------------- Issue Type: Task (was: By-EMAIL) > OST manual: enable engine 4.3 > ----------------------------- > > Key: OVIRT-2688 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2688 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Nir Soffer > Assignee: Galit Rosenthal > Attachments: Screenshot from 2019-02-27 21-52-28.png > > > When starting manual OST job, we can select engine version. > The available options are: > - master > - 42 > Since we have now 4.3 branch, we should be able to select 4.3 engine. > See attached screenshot. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2688) OST manual: enable engine 4.3
by Anton Marchukov (oVirt JIRA) 05 Mar '19

05 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2688?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2688: -------------------------------------- Assignee: Galit Rosenthal (was: infra) > OST manual: enable engine 4.3 > ----------------------------- > > Key: OVIRT-2688 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2688 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: Galit Rosenthal > Attachments: Screenshot from 2019-02-27 21-52-28.png > > > When starting manual OST job, we can select engine version. > The available options are: > - master > - 42 > Since we have now 4.3 branch, we should be able to select 4.3 engine. > See attached screenshot. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2688) OST manual: enable engine 4.3
by Anton Marchukov (oVirt JIRA) 05 Mar '19

05 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2688?page=com.atlassian.jira.… ] Anton Marchukov commented on OVIRT-2688: ---------------------------------------- [~grosenth(a)redhat.com] please enable this once you are confident that 4.3 manual job is working > OST manual: enable engine 4.3 > ----------------------------- > > Key: OVIRT-2688 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2688 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > Attachments: Screenshot from 2019-02-27 21-52-28.png > > > When starting manual OST job, we can select engine version. > The available options are: > - master > - 42 > Since we have now 4.3 branch, we should be able to select 4.3 engine. > See attached screenshot. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2691) All builds on vm0145.workers-phx.ovirt.org (fc28 phx nested) fail with: Error fetching remote repo 'origin'
by Anton Marchukov (oVirt JIRA) 05 Mar '19

05 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2691?page=com.atlassian.jira.… ] Anton Marchukov updated OVIRT-2691: ----------------------------------- Issue Type: Task (was: By-EMAIL) > All builds on vm0145.workers-phx.ovirt.org (fc28 phx nested) fail with: Error fetching remote repo 'origin' > ----------------------------------------------------------------------------------------------------------- > > Key: OVIRT-2691 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2691 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Nir Soffer > Assignee: Liora Milbaum > > Looks like all builds on Fedora 28 fail with this error now: > - > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > vm0145.workers-phx.ovirt.org (fc28 phx nested) > - > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > vm0145.workers-phx.ovirt.org (fc28 phx nested) > - > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > vm0145.workers-phx.ovirt.org (fc28 phx nested) > https://jenkins.ovirt.org/job/vdsm_standard-check-patch/buildTimeTrend > For some reason we always get the same slave for the py27 build. > ---- > No credentials specified > Fetching changes from the remote Git repository > Cleaning workspace > ERROR: Error fetching remote repo 'origin' > hudson.plugins.git.GitException: Failed to fetch from > https://gerrit.ovirt.org/vdsm > at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:904) > at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1144) > at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1175) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77) > at > org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > Caused by: hudson.plugins.git.GitException: Command "git clean -fdx" > returned status code 1: > stdout: > stderr: warning: failed to remove > .tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/plugin.cpython-27-PYTEST.pyc: > Permission denied > warning: failed to remove > .tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/compat.cpython-27-PYTEST.pyc: > Permission denied > warning: failed to remove > .tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/engine.cpython-27-PYTEST.pyc: > Permission denied > warning: failed to remove > .tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/embed.cpython-27-PYTEST.pyc: > Permission denied > warning: failed to remove > tests/__pycache__/pywatch_test.cpython-27-PYTEST.pyc: Permission denied > warning: failed to remove > tests/__pycache__/prlimit_test.cpython-27-PYTEST.pyc: Permission denied > warning: failed to remove tests/__pycache__/ssl_test.cpython-27-PYTEST.pyc: > Permission denied > warning: failed to remove > tests/__pycache__/hooking_test.cpython-27-PYTEST.pyc: Permission denied > warning: failed to remove > tests/common/__pycache__/systemd_test.cpython-27-PYTEST.pyc: Permission > denied > warning: failed to remove > tests/common/__pycache__/systemctl_test.cpython-27-PYTEST.pyc: Permission > denied > warning: failed to remove > tests/common/__pycache__/commands_test.cpython-27-PYTEST.pyc: Permission > denied > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2318) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2248) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2244) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1777) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1789) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.clean(CliGitAPIImpl.java:901) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.clean(CliGitAPIImpl.java:912) > at hudson.plugins.git.GitAPI.clean(GitAPI.java:311) > at sun.reflect.GeneratedMethodAccessor225.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:929) > at > hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:903) > at > hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:855) > at hudson.remoting.UserRequest.perform(UserRequest.java:212) > at hudson.remoting.UserRequest.perform(UserRequest.java:54) > at hudson.remoting.Request$2.run(Request.java:369) > at > hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) > ... 4 more > Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to > vm0145.workers-phx.ovirt.org > at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) > at > hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) > at hudson.remoting.Channel.call(Channel.java:955) > at > hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:283) > at com.sun.proxy.$Proxy96.clean(Unknown Source) > at > org.jenkinsci.plugins.gitclient.RemoteGitImpl.clean(RemoteGitImpl.java:463) > at > hudson.plugins.git.extensions.impl.CleanBeforeCheckout.decorateFetchCommand(CleanBeforeCheckout.java:30) > at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:900) > at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1144) > at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1175) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77) > at > org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > ... 4 more > > git rev-parse --is-inside-work-tree # timeout=10 > > git config remote.origin.url https://gerrit.ovirt.org/vdsm # timeout=10 > > git rev-parse --verify HEAD # timeout=10 > Resetting working tree > > git reset --hard # timeout=10 > > git clean -fdx # timeout=10 > Error fetching remote repo 'origin' -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2690) v2v_conversion_host jenkins job bugged
by Anton Marchukov (oVirt JIRA) 05 Mar '19

05 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2690?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2690: -------------------------------------- Assignee: Barak Korren (was: infra) > v2v_conversion_host jenkins job bugged > -------------------------------------- > > Key: OVIRT-2690 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2690 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Barak Korren > > Hi, > just noticed today we have a jenkins job: > https://jenkins.ovirt.org/job/oVirt_v2v-conversion-host_standard-on-ghpush/… > which generates packages named like: > v2v-conversion-host-1.11.0-0.oVirt_v2v_conversion_host_standard_on.githpush_13.20190301133957.fc27.src.rpm > v2v-conversion-host-1.11.0.tar.gz > v2v-conversion-host-ansible-1.11.0-0.oVirt_v2v_conversion_host_standard_on.githpush_13.20190301133957.fc27.noarch.rpm > v2v-conversion-host-debugsource-1.11.0-0.oVirt_v2v_conversion_host_standard_on.githpush_13.20190301133957.fc27.x86_64.rpm > v2v-conversion-host-provider-1.11.0-0.oVirt_v2v_conversion_host_standard_on.githpush_13.20190301133957.fc27.x86_64.rpm > v2v-conversion-host-provider-debuginfo-1.11.0-0.oVirt_v2v_conversion_host_standard_on.githpush_13.20190301133957.fc27.x86_64.rpm > v2v-conversion-host-wrapper-1.11.0-0.oVirt_v2v_conversion_host_standard_on.githpush_13.20190301133957.fc27.noarch.rpm > which are breaking NVR naming conventions for RPMs and are probably the > result of a bug within jenkins job. > Please fix the job as soon as possible and clean up > - https://resources.ovirt.org/repos/ovirt/tested/master > - https://resources.ovirt.org/repos/ovirt/tested/4.2 > - https://resources.ovirt.org/pub/ovirt-4.2-snapshot > - https://resources.ovirt.org/pub/ovirt-master-snapshot > Thanks, > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2691) All builds on vm0145.workers-phx.ovirt.org (fc28 phx nested) fail with: Error fetching remote repo 'origin'
by Anton Marchukov (oVirt JIRA) 05 Mar '19

05 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2691?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2691: -------------------------------------- Assignee: Liora Milbaum (was: infra) > All builds on vm0145.workers-phx.ovirt.org (fc28 phx nested) fail with: Error fetching remote repo 'origin' > ----------------------------------------------------------------------------------------------------------- > > Key: OVIRT-2691 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2691 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: Liora Milbaum > > Looks like all builds on Fedora 28 fail with this error now: > - > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > vm0145.workers-phx.ovirt.org (fc28 phx nested) > - > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > vm0145.workers-phx.ovirt.org (fc28 phx nested) > - > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > vm0145.workers-phx.ovirt.org (fc28 phx nested) > https://jenkins.ovirt.org/job/vdsm_standard-check-patch/buildTimeTrend > For some reason we always get the same slave for the py27 build. > ---- > No credentials specified > Fetching changes from the remote Git repository > Cleaning workspace > ERROR: Error fetching remote repo 'origin' > hudson.plugins.git.GitException: Failed to fetch from > https://gerrit.ovirt.org/vdsm > at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:904) > at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1144) > at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1175) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77) > at > org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > Caused by: hudson.plugins.git.GitException: Command "git clean -fdx" > returned status code 1: > stdout: > stderr: warning: failed to remove > .tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/plugin.cpython-27-PYTEST.pyc: > Permission denied > warning: failed to remove > .tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/compat.cpython-27-PYTEST.pyc: > Permission denied > warning: failed to remove > .tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/engine.cpython-27-PYTEST.pyc: > Permission denied > warning: failed to remove > .tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/embed.cpython-27-PYTEST.pyc: > Permission denied > warning: failed to remove > tests/__pycache__/pywatch_test.cpython-27-PYTEST.pyc: Permission denied > warning: failed to remove > tests/__pycache__/prlimit_test.cpython-27-PYTEST.pyc: Permission denied > warning: failed to remove tests/__pycache__/ssl_test.cpython-27-PYTEST.pyc: > Permission denied > warning: failed to remove > tests/__pycache__/hooking_test.cpython-27-PYTEST.pyc: Permission denied > warning: failed to remove > tests/common/__pycache__/systemd_test.cpython-27-PYTEST.pyc: Permission > denied > warning: failed to remove > tests/common/__pycache__/systemctl_test.cpython-27-PYTEST.pyc: Permission > denied > warning: failed to remove > tests/common/__pycache__/commands_test.cpython-27-PYTEST.pyc: Permission > denied > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2318) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2248) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2244) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1777) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1789) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.clean(CliGitAPIImpl.java:901) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.clean(CliGitAPIImpl.java:912) > at hudson.plugins.git.GitAPI.clean(GitAPI.java:311) > at sun.reflect.GeneratedMethodAccessor225.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:929) > at > hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:903) > at > hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:855) > at hudson.remoting.UserRequest.perform(UserRequest.java:212) > at hudson.remoting.UserRequest.perform(UserRequest.java:54) > at hudson.remoting.Request$2.run(Request.java:369) > at > hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) > ... 4 more > Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to > vm0145.workers-phx.ovirt.org > at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) > at > hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) > at hudson.remoting.Channel.call(Channel.java:955) > at > hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:283) > at com.sun.proxy.$Proxy96.clean(Unknown Source) > at > org.jenkinsci.plugins.gitclient.RemoteGitImpl.clean(RemoteGitImpl.java:463) > at > hudson.plugins.git.extensions.impl.CleanBeforeCheckout.decorateFetchCommand(CleanBeforeCheckout.java:30) > at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:900) > at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1144) > at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1175) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77) > at > org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > ... 4 more > > git rev-parse --is-inside-work-tree # timeout=10 > > git config remote.origin.url https://gerrit.ovirt.org/vdsm # timeout=10 > > git rev-parse --verify HEAD # timeout=10 > Resetting working tree > > git reset --hard # timeout=10 > > git clean -fdx # timeout=10 > Error fetching remote repo 'origin' -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2691) All builds on vm0145.workers-phx.ovirt.org (fc28 phx nested) fail with: Error fetching remote repo 'origin'
by Anton Marchukov (oVirt JIRA) 05 Mar '19

05 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2691?page=com.atlassian.jira.… ] Anton Marchukov commented on OVIRT-2691: ---------------------------------------- Disabling slaves in jenkins does not prevent finding the solution, but prevents further failures in case it is specific to single slave. Assigning to [~lmilbaum(a)redhat.com] current infra owner. > All builds on vm0145.workers-phx.ovirt.org (fc28 phx nested) fail with: Error fetching remote repo 'origin' > ----------------------------------------------------------------------------------------------------------- > > Key: OVIRT-2691 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2691 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Looks like all builds on Fedora 28 fail with this error now: > - > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > vm0145.workers-phx.ovirt.org (fc28 phx nested) > - > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > vm0145.workers-phx.ovirt.org (fc28 phx nested) > - > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > vm0145.workers-phx.ovirt.org (fc28 phx nested) > https://jenkins.ovirt.org/job/vdsm_standard-check-patch/buildTimeTrend > For some reason we always get the same slave for the py27 build. > ---- > No credentials specified > Fetching changes from the remote Git repository > Cleaning workspace > ERROR: Error fetching remote repo 'origin' > hudson.plugins.git.GitException: Failed to fetch from > https://gerrit.ovirt.org/vdsm > at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:904) > at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1144) > at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1175) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77) > at > org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > Caused by: hudson.plugins.git.GitException: Command "git clean -fdx" > returned status code 1: > stdout: > stderr: warning: failed to remove > .tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/plugin.cpython-27-PYTEST.pyc: > Permission denied > warning: failed to remove > .tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/compat.cpython-27-PYTEST.pyc: > Permission denied > warning: failed to remove > .tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/engine.cpython-27-PYTEST.pyc: > Permission denied > warning: failed to remove > .tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/embed.cpython-27-PYTEST.pyc: > Permission denied > warning: failed to remove > tests/__pycache__/pywatch_test.cpython-27-PYTEST.pyc: Permission denied > warning: failed to remove > tests/__pycache__/prlimit_test.cpython-27-PYTEST.pyc: Permission denied > warning: failed to remove tests/__pycache__/ssl_test.cpython-27-PYTEST.pyc: > Permission denied > warning: failed to remove > tests/__pycache__/hooking_test.cpython-27-PYTEST.pyc: Permission denied > warning: failed to remove > tests/common/__pycache__/systemd_test.cpython-27-PYTEST.pyc: Permission > denied > warning: failed to remove > tests/common/__pycache__/systemctl_test.cpython-27-PYTEST.pyc: Permission > denied > warning: failed to remove > tests/common/__pycache__/commands_test.cpython-27-PYTEST.pyc: Permission > denied > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2318) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2248) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2244) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1777) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1789) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.clean(CliGitAPIImpl.java:901) > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.clean(CliGitAPIImpl.java:912) > at hudson.plugins.git.GitAPI.clean(GitAPI.java:311) > at sun.reflect.GeneratedMethodAccessor225.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:929) > at > hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:903) > at > hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:855) > at hudson.remoting.UserRequest.perform(UserRequest.java:212) > at hudson.remoting.UserRequest.perform(UserRequest.java:54) > at hudson.remoting.Request$2.run(Request.java:369) > at > hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) > ... 4 more > Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to > vm0145.workers-phx.ovirt.org > at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) > at > hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) > at hudson.remoting.Channel.call(Channel.java:955) > at > hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:283) > at com.sun.proxy.$Proxy96.clean(Unknown Source) > at > org.jenkinsci.plugins.gitclient.RemoteGitImpl.clean(RemoteGitImpl.java:463) > at > hudson.plugins.git.extensions.impl.CleanBeforeCheckout.decorateFetchCommand(CleanBeforeCheckout.java:30) > at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:900) > at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1144) > at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1175) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90) > at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77) > at > org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > ... 4 more > > git rev-parse --is-inside-work-tree # timeout=10 > > git config remote.origin.url https://gerrit.ovirt.org/vdsm # timeout=10 > > git rev-parse --verify HEAD # timeout=10 > Resetting working tree > > git reset --hard # timeout=10 > > git clean -fdx # timeout=10 > Error fetching remote repo 'origin' -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[CQ]: 98234, 1 (ovirt-node-ng-image) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Mar '19

05 Mar '19

A system test invoked by the "ovirt-4.3" change queue including change 98234,1 (ovirt-node-ng-image) failed. However, this change seems not to be the root cause for this failure. Change 97519,2 (ovirt-node-ng-image) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 97519,2 (ovirt-node-ng-image) 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/98234/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97519/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/123/

2 1

[ OST Failure Report ] [ oVirt Master (v2v-conversion-host) ] [ 05-03-2019 ] [ 002_bootstrap.get_host_hooks]
by Dafna Ron 05 Mar '19

05 Mar '19

Hi, We have a failure reported on basic suite and CQ has identified the below patch as root cause: https://github.com/oVirt/v2v-conversion-host/commit/ad74db5a93b7cff1f5309fc… logs can be found here: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13229/artifa… can you please take a look? error: 2019-03-04 11:04:19,704-05 ERROR [org.ovirt.engine.core.bll.GetVdsHooksByIdQuery] (default task-1) [2830423d-12b2-41f6-b4a0-ad616bfcdfca] Query 'GetVdsHooksByIdQuery' failed: null 2019-03-04 11:04:19,759-05 DEBUG [org.ovirt.vdsm.jsonrpc.client.reactors.stomp.impl.Message] (SSL Stomp Reactor) [320e116b] MESSAGE content-length:198 destination:jms.topic.vdsm_responses content-type:application/json subscription:0c285ec7-2518-4489-9d30-d949db933118 {"jsonrpc": "2.0", "id": "55a3412e-25bf-4926-b49b-652a612bb4c8", "result": [{"status": 0, "id": "0f0aef42-0538-4b6c-8fac-3aa51e3a1e30"}, {"status": 0, "id": "f6d1e432-7b85-4383-9db7-55ca471870d2"}]}^@ 2019-03-04 11:04:19,764-05 DEBUG [org.ovirt.vdsm.jsonrpc.client.internal.ResponseWorker] (ResponseWorker) [] Message received: {"jsonrpc": "2.0", "id": "55a3412e-25bf-4926-b49b-652a612bb4c8", "result": [{"status ": 0, "id": "0f0aef42-0538-4b6c-8fac-3aa51e3a1e30"}, {"status": 0, "id": "f6d1e432-7b85-4383-9db7-55ca471870d2"}]} 2019-03-04 11:04:19,764-05 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-14) [1cebc213] FINISH, ConnectStorageServerVDSCommand, return: {0f0aef42-0538-4b6c-8fac-3aa51e3a1e30=0, f6d1e432-7b85-4383-9db7-55ca471870d2=0}, log id: 7b6e4cab 2019-03-04 11:04:19,764-05 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (EE-ManagedThreadFactory-engineScheduled-Thread-14) [1cebc213] method: runVdsCommand, params: [ConnectStorag eServer, StorageServerConnectionManagementVDSParameters:{hostId='19ceb20c-0c1b-4f72-a082-4a70055244b0', storagePoolId='7fa468f8-267e-466e-9038-89ef5bcc365f', storageType='ISCSI', connectionList='[StorageServerCo nnections:{id='0f0aef42-0538-4b6c-8fac-3aa51e3a1e30', connection='192.168.200.4', iqn='iqn.2014-07.org.ovirt:storage', vfsType='null', mountOptions='null', nfsVersion='null', nfsRetrans='null', nfsTimeo='null', iface='null', netIfaceName='null'}, StorageServerConnections:{id='f6d1e432-7b85-4383-9db7-55ca471870d2', connection='192.168.201.4', iqn='iqn.2014-07.org.ovirt:storage', vfsType='null', mountOptions='null', nfsV ersion='null', nfsRetrans='null', nfsTimeo='null', iface='null', netIfaceName='null'}]', sendNetworkEventOnFailure='true'}], timeElapsed: 2805ms 2019-03-04 11:04:19,771-05 INFO [org.ovirt.engine.core.bll.storage.pool.ConnectHostToStoragePoolServersCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-14) [1cebc213] Host 'lago-basic-suite-master-host- 1' storage connection was succeeded 2019-03-04 11:04:19,704-05 ERROR [org.ovirt.engine.core.bll.GetVdsHooksByIdQuery] (default task-1) [2830423d-12b2-41f6-b4a0-ad616bfcdfca] Exception: java.lang.NullPointerException at org.ovirt.engine.core.utils.vdshooks.VdsHooksParser.parseHooks(VdsHooksParser.java:146) [utils.jar:] at org.ovirt.engine.core.bll.GetVdsHooksByIdQuery.executeQueryCommand(GetVdsHooksByIdQuery.java:36) [bll.jar:] at org.ovirt.engine.core.bll.QueriesCommandBase.executeCommand(QueriesCommandBase.java:106) [bll.jar:] at org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:31) [dal.jar:] at org.ovirt.engine.core.bll.executor.DefaultBackendQueryExecutor.execute(DefaultBackendQueryExecutor.java:14) [bll.jar:] at org.ovirt.engine.core.bll.Backend.runQueryImpl(Backend.java:520) [bll.jar:] at org.ovirt.engine.core.bll.Backend.runQuery(Backend.java:489) [bll.jar:] at sun.reflect.GeneratedMethodAccessor65.invoke(Unknown Source) [:1.8.0_191] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_191] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_191] at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) at org.jboss.as.weld.ejb.DelegatingInterceptorInvocationContext.proceed(DelegatingInterceptorInvocationContext.java:92) [wildfly-weld-ejb-15.0.1.Final.jar:15.0.1.Final] at org.jboss.weld.interceptor.proxy.WeldInvocationContextImpl.interceptorChainCompleted(WeldInvocationContextImpl.java:107) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.interceptor.proxy.WeldInvocationContextImpl.proceed(WeldInvocationContextImpl.java:126) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.ovirt.engine.core.common.di.interceptor.LoggingInterceptor.apply(LoggingInterceptor.java:12) [common.jar:] at sun.reflect.GeneratedMethodAccessor61.invoke(Unknown Source) [:1.8.0_191] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_191] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_191] at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:73) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.interceptor.proxy.WeldInvocationContextImpl.invokeNext(WeldInvocationContextImpl.java:92) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.interceptor.proxy.WeldInvocationContextImpl.proceed(WeldInvocationContextImpl.java:124) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.bean.InterceptorImpl.intercept(InterceptorImpl.java:105) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.as.weld.ejb.DelegatingInterceptorInvocationContext.proceed(DelegatingInterceptorInvocationContext.java:82) [wildfly-weld-ejb-15.0.1.Final.jar:15.0.1.Final] Thanks, Dafna

2 3

[CQ]: 98156, 1 (ovirt-node-ng-image) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Mar '19

05 Mar '19

A system test invoked by the "ovirt-4.3" change queue including change 98156,1 (ovirt-node-ng-image) failed. However, this change seems not to be the root cause for this failure. Change 97519,2 (ovirt-node-ng-image) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 97519,2 (ovirt-node-ng-image) 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/98156/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97519/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/118/

2 1

[JIRA] (OVIRT-2566) make network suite blocking
by Dafna Ron (oVirt JIRA) 05 Mar '19

05 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2566?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2566: ---------------------------------- its basic and upgrade suites that run. the basic suite covers multiple projects and should continue running. I think that we should not add any specific components suites for 3 reasons: 1. Basic suites tests basic tests on all components, testing your specific area would not give the coverage we would like as sometimes the code change would effect multiple components and we are likely to miss serious regressions. 2. if we start adding more and more suites to CQ we would end up testing like QE and we are not providing those sort of tests 3. if we add the network suite we will have to add storage, virt, sla atc and we do not have resources to run every suite on every change. I think that the basic and upgrade suite provide the coverage we need for CQ and other suites are running in check-patch. If you believe that the basic suite is not stable or lacking, please contribute to stabilizing and adding to it. > make network suite blocking > --------------------------- > > Key: OVIRT-2566 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2566 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: danken > Assignee: infra > Priority: High > > The network suite is executing nightly for almost a year. It has a caring team that tends to it, and it does not have false positives. > Currently, it currently fails for a week on the 4.2 branch, but it is due to a production code bug. > https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… > I would like to see this suite escalated to the importance of the basic suite, making it a gating condition for marking a collection of packages as "tested". > [~gbenhaim(a)redhat.com] what should be done to make this happen? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[CQ]: ad74db5 (v2v-conversion-host) failed "ovirt-master" system tests
by oVirt Jenkins 05 Mar '19

05 Mar '19

Change ad74db5 (v2v-conversion-host) 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://github.com/oVirt/v2v-conversion-host/commit/ad74db5a93b7cff1f5309fc… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13229/

2 1

[CQ]: b2ac05e (v2v-conversion-host) failed "ovirt-master" system tests
by oVirt Jenkins 05 Mar '19

05 Mar '19

Change b2ac05e (v2v-conversion-host) 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://github.com/oVirt/v2v-conversion-host/commit/b2ac05e131384e50835f870… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13234/

2 1

[JIRA] (OVIRT-2566) make network suite blocking
by danken (oVirt JIRA) 05 Mar '19

05 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2566?page=com.atlassian.jira.… ] danken commented on OVIRT-2566: ------------------------------- Nir, in change-queue context, "gating" has a clear meaning: if you do not pass the suite, your package does not get to "tested". There is no meaning to "gate only vdsm-network". Currently, only basic-suite-* is gating. this means that someone can post an engine patch which breaks the network suite inadvertently. That's what I would like to prevent. You are right that this can be costly. We need to measure what is the time and resources to enable this gate, vs. our gain. Currently we do not know the price. The network suite is currently shorter in tests and more stable the then the basic suite. > make network suite blocking > --------------------------- > > Key: OVIRT-2566 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2566 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: danken > Assignee: infra > Priority: High > > The network suite is executing nightly for almost a year. It has a caring team that tends to it, and it does not have false positives. > Currently, it currently fails for a week on the 4.2 branch, but it is due to a production code bug. > https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… > I would like to see this suite escalated to the importance of the basic suite, making it a gating condition for marking a collection of packages as "tested". > [~gbenhaim(a)redhat.com] what should be done to make this happen? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

oVirt infra daily report - unstable production jobs - 754
by jenkins＠jenkins.phx.ovirt.org 05 Mar '19

05 Mar '19

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/754//artifact/exported-a… Cheers, Jenkins

1 0

[JIRA] (OVIRT-2566) make network suite blocking
by Nir Soffer (oVirt JIRA) 04 Mar '19

04 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2566?page=com.atlassian.jira.… ] Nir Soffer commented on OVIRT-2566: ----------------------------------- On Mon, Nov 5, 2018 at 8:59 AM danken (oVirt JIRA) < I'm ok with this only if it will gate *only* vdsm-network package, and it will run in parallel, so it does not slow down OST run. For basic suite, we have too many random failures, so I don't think it is useful, and we should make it optional. Nir > make network suite blocking > --------------------------- > > Key: OVIRT-2566 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2566 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: danken > Assignee: infra > Priority: High > > The network suite is executing nightly for almost a year. It has a caring team that tends to it, and it does not have false positives. > Currently, it currently fails for a week on the 4.2 branch, but it is due to a production code bug. > https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… > I would like to see this suite escalated to the importance of the basic suite, making it a gating condition for marking a collection of packages as "tested". > [~gbenhaim(a)redhat.com] what should be done to make this happen? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2566) make network suite blocking
by danken (oVirt JIRA) 04 Mar '19

04 Mar '19

danken created OVIRT-2566: ----------------------------- Summary: make network suite blocking Key: OVIRT-2566 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2566 Project: oVirt - virtualization made easy Issue Type: Improvement Components: OST Reporter: danken Assignee: infra Priority: High The network suite is executing nightly for almost a year. It has a caring team that tends to it, and it does not have false positives. Currently, it currently fails for a week on the 4.2 branch, but it is due to a production code bug. https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… I would like to see this suite escalated to the importance of the basic suite, making it a gating condition for marking a collection of packages as "tested". [~gbenhaim(a)redhat.com] what should be done to make this happen? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

2 1

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 04 Mar '19

04 Mar '19

Failed to run project_setup.sh for: #1478 containerized-data-importer [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-gg1mn.

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 04 Mar '19

04 Mar '19

Failed to run project_setup.sh for: #1477 containerized-data-importer [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-423j5.

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 04 Mar '19

04 Mar '19

Failed to run project_setup.sh for: #1477 containerized-data-importer [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-qv1hn.

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 04 Mar '19

04 Mar '19

Failed to run project_setup.sh for: #1476 containerized-data-importer [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-7bdfh.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 04 Mar '19

04 Mar '19

Failed to run project_setup.sh for: #3686 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-hvhdq.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 04 Mar '19

04 Mar '19

Failed to run project_setup.sh for: #3686 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-807wk.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 04 Mar '19

04 Mar '19

Failed to run project_setup.sh for: #3686 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-wn4gp.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 04 Mar '19

04 Mar '19

Failed to run project_setup.sh for: #3686 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-91gr2.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 04 Mar '19

04 Mar '19

Failed to run project_setup.sh for: #3685 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-l6h9v.

1 0

[JIRA] (OVIRT-2693) [request] jenkins dev permission
by Anton Marchukov (oVirt JIRA) 04 Mar '19

04 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2693?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2693: -------------------------------------- Assignee: Anton Marchukov (was: infra) > [request] jenkins dev permission > -------------------------------- > > Key: OVIRT-2693 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2693 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Ahmad Khiet > Assignee: Anton Marchukov > > Hi, > can I get a developer permission on jenkins for ovirt? > Thanks, > Ahmad Khiet -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 04 Mar '19

04 Mar '19

Failed to run project_setup.sh for: #3685 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-r68hd.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 04 Mar '19

04 Mar '19

Failed to run project_setup.sh for: #3685 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-zl71v.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 04 Mar '19

04 Mar '19

Failed to run project_setup.sh for: #3685 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-lg8w6.

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 04 Mar '19

04 Mar '19

Failed to run project_setup.sh for: #1475 containerized-data-importer [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-cm1pz.

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 04 Mar '19

04 Mar '19

Failed to run project_setup.sh for: #1474 containerized-data-importer [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-hfp3l.

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 04 Mar '19

04 Mar '19

Failed to run project_setup.sh for: #1473 containerized-data-importer [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-b31jr.

1 0

[JIRA] (OVIRT-2566) make network suite blocking
by Eyal Edri (oVirt JIRA) 04 Mar '19

04 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2566?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2566: ---------------------------------- We still need to allocate bare metal to run it on each CQ run, and I'm not sure we have available resources for it, pretty sure we don't have since KubeVirt took half of the hosts. On Mon, Mar 4, 2019 at 2:09 PM danken (oVirt JIRA) < -- Eyal edri MANAGER RHV/CNV 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) > make network suite blocking > --------------------------- > > Key: OVIRT-2566 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2566 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: danken > Assignee: infra > Priority: High > > The network suite is executing nightly for almost a year. It has a caring team that tends to it, and it does not have false positives. > Currently, it currently fails for a week on the 4.2 branch, but it is due to a production code bug. > https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… > I would like to see this suite escalated to the importance of the basic suite, making it a gating condition for marking a collection of packages as "tested". > [~gbenhaim(a)redhat.com] what should be done to make this happen? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2566) make network suite blocking
by danken (oVirt JIRA) 04 Mar '19

04 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2566?page=com.atlassian.jira.… ] danken commented on OVIRT-2566: ------------------------------- Is there news here? Would you try adding it? A benefit for sequential execution, is that you don't need to waste resources on the network suite if the basic suite has finished successfully. > make network suite blocking > --------------------------- > > Key: OVIRT-2566 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2566 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: danken > Assignee: infra > Priority: High > > The network suite is executing nightly for almost a year. It has a caring team that tends to it, and it does not have false positives. > Currently, it currently fails for a week on the 4.2 branch, but it is due to a production code bug. > https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… > I would like to see this suite escalated to the importance of the basic suite, making it a gating condition for marking a collection of packages as "tested". > [~gbenhaim(a)redhat.com] what should be done to make this happen? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

2 1

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 04 Mar '19

04 Mar '19

Failed to run project_setup.sh for: #3684 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-c2m45.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 04 Mar '19

04 Mar '19

Failed to run project_setup.sh for: #3684 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-7zxnk.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 04 Mar '19

04 Mar '19

Failed to run project_setup.sh for: #3684 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-0cq3b.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 04 Mar '19

04 Mar '19

Failed to run project_setup.sh for: #3684 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-90n54.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 04 Mar '19

04 Mar '19

Failed to run project_setup.sh for: #3683 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-62gsk.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 04 Mar '19

04 Mar '19

Failed to run project_setup.sh for: #3683 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-9fvmp.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 04 Mar '19

04 Mar '19

Failed to run project_setup.sh for: #3683 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-4rfdb.

1 0