November 2017 - Infra - oVirt List Archives

[CQ]: 84618,2 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 26 Nov '17

26 Nov '17

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

1 0

[CQ]: 84568, 2 (ovirt-engine-metrics) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Nov '17

26 Nov '17

A system test invoked by the "ovirt-master" change queue including change 84568,2 (ovirt-engine-metrics) failed. However, this change seems not to be the root cause for this failure. Change 84488,2 (ovirt-engine-metrics) 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 84488,2 (ovirt-engine-metrics) 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/84568/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/84488/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4153/

1 0

[JIRA] (OVIRT-1782) Make sure all VDSM build dependencies for FC27 are met.
by Barak Korren (oVirt JIRA) 26 Nov '17

26 Nov '17

This is a multi-part message in MIME format... ------------=_1511691576-29062-283 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1782?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1782: -------------------------------- Epic Link: OVIRT-400 > Make sure all VDSM build dependencies for FC27 are met. > ------------------------------------------------------- > > Key: OVIRT-1782 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1782 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: vdsm > > There had been attempts recently to make VDSM build on FC27. > Those attempts were met with mixed success as issues kept surfacing. > Fro now all the FC27 jobs for VDSM had been disabled. > This ticket is for racking work of debugging issues to re-enable the jobs -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100073) ------------=_1511691576-29062-283 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1782?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1782:</h3> <pre>Epic Link: OVIRT-400</pre> <blockquote><h3>Make sure all VDSM build dependencies for FC27 are met.</h3> <pre> Key: OVIRT-1782 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1782 Project: oVirt - virtualization made easy Issue Type: New Feature Components: oVirt CI Reporter: Barak Korren Assignee: infra Labels: vdsm</pre> <p>There had been attempts recently to make VDSM build on FC27. Those attempts were met with mixed success as issues kept surfacing. Fro now all the FC27 jobs for VDSM had been disabled. This ticket is for racking work of debugging issues to re-enable the jobs</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100073)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1511691576-29062-283--

1 0

[JIRA] (OVIRT-1782) Make sure all VDSM build dependencies for FC27 are met.
by Barak Korren (oVirt JIRA) 26 Nov '17

26 Nov '17

This is a multi-part message in MIME format... ------------=_1511691577-24833-264 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Barak Korren created OVIRT-1782: ----------------------------------- Summary: Make sure all VDSM build dependencies for FC27 are met. Key: OVIRT-1782 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1782 Project: oVirt - virtualization made easy Issue Type: New Feature Components: oVirt CI Reporter: Barak Korren Assignee: infra There had been attempts recently to make VDSM build on FC27. Those attempts were met with mixed success as issues kept surfacing. Fro now all the FC27 jobs for VDSM had been disabled. This ticket is for racking work of debugging issues to re-enable the jobs -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100073) ------------=_1511691577-24833-264 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Barak Korren created OVIRT-1782:</h3> <pre> Summary: Make sure all VDSM build dependencies for FC27 are met. Key: OVIRT-1782 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1782 Project: oVirt - virtualization made easy Issue Type: New Feature Components: oVirt CI Reporter: Barak Korren Assignee: infra</pre> <p>There had been attempts recently to make VDSM build on FC27.</p> <p>Those attempts were met with mixed success as issues kept surfacing.</p> <p>Fro now all the FC27 jobs for VDSM had been disabled.</p> <p>This ticket is for racking work of debugging issues to re-enable the jobs</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100073)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1511691577-24833-264--

1 0

[JIRA] (OVIRT-1780) Extremely slow build on vm0064.workers-phx.ovirt.org (libvirt phx nested fc26)
by eyal edri (oVirt JIRA) 26 Nov '17

26 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1780?page=com.atlassian.jira.… ] eyal edri reassigned OVIRT-1780: -------------------------------- Assignee: Evgheni Dereveanchin (was: infra) Evgheni, can you have a look? > Extremely slow build on vm0064.workers-phx.ovirt.org (libvirt phx nested fc26) > ------------------------------------------------------------------------------ > > Key: OVIRT-1780 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1780 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: Evgheni Dereveanchin > > *00:00:00.735* Building remotely on vm0064.workers-phx.ovirt.org > <http://jenkins.ovirt.org/computer/vm0064.workers-phx.ovirt.org> > (libvirt phx nested fc26) in workspace > /home/jenkins/workspace/vdsm_master_check-patch-fc27-x86_64 > After 16 minutes, and it is still stuck in: > *00:14:21.914* Start: unpacking root cache > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc27-x86_64/284/console > I left the build running in case you want to debug it. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100073)

1 0

[JIRA] (OVIRT-1781) ci failure due to no space on slave?
by Barak Korren (oVirt JIRA) 26 Nov '17

26 Nov '17

This is a multi-part message in MIME format... ------------=_1511682298-27447-558 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1781?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1781: ------------------------------------- [~danken(a)redhat.com] this error has nothing to do with disk space, you can see in the beginning on the log, in the cleanup script that there are 27G available. This is talking about the `workspace` object which is the object that Jenkins uses to communicate with the slave. If the workspace object is lost it typically means that Jenkins lost the connection to the slave, here is the actual relevant exception, where we can see that is indeed a `{{java.io.EOFException}}` (Meaning - an EOF on the slave connection): {code} storage/guarded_test.py::TestContext::test_release_failure PASSED storage/guarded_test.py::TestContext::test_two_vols_different_domains PASSED storage/guarded_test.py::TestContext::test_two_vols_same_image PASSED storage/hsm_test.py::TestVerifyUntrustedVolume::test_compat_not_checked_for_raw FATAL: command execution failed java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2680) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3155) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:864) at java.io.ObjectInputStream.<init>(ObjectInputStream.java:360) at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:35) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:59) Caused: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:73) Caused: hudson.remoting.ChannelClosedException: Remote call on vm0014.workers-phx.ovirt.org failed. The channel is closing down or has closed down at hudson.remoting.Channel.call(Channel.java:898) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:257) at com.sun.proxy.$Proxy80.isAlive(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1138) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1130) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:155) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:109) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:736) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:496) at hudson.model.Run.execute(Run.java:1737) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:421) Build step 'Execute shell' marked build as failure FATAL: remote file operation failed: /home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64@tmp/secretFiles/126de56b-84a8-43d8-8f8d-51ce21780f9c at hudson.remoting.Channel@391e411:vm0014.workers-phx.ovirt.org: hudson.remoting.ChannelClosedException: Remote call on vm0014.workers-phx.ovirt.org failed. The channel is closing down or has closed down java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2680) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3155) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:864) at java.io.ObjectInputStream.<init>(ObjectInputStream.java:360) at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:35) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:59) Caused: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:73) Caused: hudson.remoting.ChannelClosedException: Remote call on vm0014.workers-phx.ovirt.org failed. The channel is closing down or has closed down at hudson.remoting.Channel.call(Channel.java:898) at hudson.FilePath.act(FilePath.java:987) Caused: java.io.IOException: remote file operation failed: /home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64@tmp/secretFiles/126de56b-84a8-43d8-8f8d-51ce21780f9c at hudson.remoting.Channel@391e411:vm0014.workers-phx.ovirt.org at hudson.FilePath.act(FilePath.java:994) at hudson.FilePath.act(FilePath.java:976) at hudson.FilePath.deleteRecursive(FilePath.java:1178) at org.jenkinsci.plugins.credentialsbinding.impl.UnbindableDir$UnbinderImpl.unbind(UnbindableDir.java:84) at org.jenkinsci.plugins.credentialsbinding.impl.SecretBuildWrapper$1.tearDown(SecretBuildWrapper.java:113) at hudson.model.Build$BuildExecution.doRun(Build.java:174) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:496) at hudson.model.Run.execute(Run.java:1737) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:421) {code} Could something with the vdsm tests that ran on the slave cause it to disconnect? > ci failure due to no space on slave? > ------------------------------------ > > Key: OVIRT-1781 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1781 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: oVirt CI > Reporter: danken > Assignee: infra > Priority: High > Labels: vdsm > > Exception when executing the batch command : no workspace from node > hudson.slaves.DumbSlave[vm0014.workers-phx.ovirt.org] which is > computer hudson.slaves.SlaveComputer@695d3d3c and has channel null > http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/19901/conso… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100073) ------------=_1511682298-27447-558 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1781?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren commented on OVIRT-1781:</h3> <p>[~danken(a)redhat.com] this error has nothing to do with disk space, you can see in the beginning on the log, in the cleanup script that there are 27G available.</p> <p>This is talking about the `workspace` object which is the object that Jenkins uses to communicate with the slave.</p> <p>If the workspace object is lost it typically means that Jenkins lost the connection to the slave, here is the actual relevant exception, where we can see that is indeed a `{{java.io.EOFException}}` (Meaning – an EOF on the slave connection):</p> <p>{code} storage/guarded_test.py::TestContext::test_release_failure PASSED storage/guarded_test.py::TestContext::test_two_vols_different_domains PASSED storage/guarded_test.py::TestContext::test_two_vols_same_image PASSED storage/hsm_test.py::TestVerifyUntrustedVolume::test_compat_not_checked_for_raw FATAL: command execution failed java.io.EOFException</p> <pre>at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2680) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3155) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:864) at java.io.ObjectInputStream.<init>(ObjectInputStream.java:360) at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:35) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:59)</pre> <p>Caused: java.io.IOException: Unexpected termination of the channel</p> <pre>at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:73)</pre> <p>Caused: hudson.remoting.ChannelClosedException: Remote call on vm0014.workers-phx.ovirt.org failed. The channel is closing down or has closed down</p> <pre>at hudson.remoting.Channel.call(Channel.java:898) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:257) at com.sun.proxy.$Proxy80.isAlive(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1138) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1130) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:155) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:109) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:736) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:496) at hudson.model.Run.execute(Run.java:1737) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:421)</pre> <p>Build step ‘Execute shell’ marked build as failure FATAL: remote file operation failed: /home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64@tmp/secretFiles/126de56b-84a8-43d8-8f8d-51ce21780f9c at hudson.remoting.Channel@391e411:vm0014.workers-phx.ovirt.org: hudson.remoting.ChannelClosedException: Remote call on vm0014.workers-phx.ovirt.org failed. The channel is closing down or has closed down java.io.EOFException</p> <pre>at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2680) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3155) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:864) at java.io.ObjectInputStream.<init>(ObjectInputStream.java:360) at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:35) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:59)</pre> <p>Caused: java.io.IOException: Unexpected termination of the channel</p> <pre>at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:73)</pre> <p>Caused: hudson.remoting.ChannelClosedException: Remote call on vm0014.workers-phx.ovirt.org failed. The channel is closing down or has closed down</p> <pre>at hudson.remoting.Channel.call(Channel.java:898) at hudson.FilePath.act(FilePath.java:987)</pre> <p>Caused: java.io.IOException: remote file operation failed: /home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64@tmp/secretFiles/126de56b-84a8-43d8-8f8d-51ce21780f9c at hudson.remoting.Channel@391e411:vm0014.workers-phx.ovirt.org</p> <pre>at hudson.FilePath.act(FilePath.java:994) at hudson.FilePath.act(FilePath.java:976) at hudson.FilePath.deleteRecursive(FilePath.java:1178) at org.jenkinsci.plugins.credentialsbinding.impl.UnbindableDir$UnbinderImpl.unbind(UnbindableDir.java:84) at org.jenkinsci.plugins.credentialsbinding.impl.SecretBuildWrapper$1.tearDown(SecretBuildWrapper.java:113) at hudson.model.Build$BuildExecution.doRun(Build.java:174) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:496) at hudson.model.Run.execute(Run.java:1737) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:421)</pre> <p>{code}</p> <p>Could something with the vdsm tests that ran on the slave cause it to disconnect?</p> <blockquote><h3>ci failure due to no space on slave?</h3> <pre> Key: OVIRT-1781 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1781 Project: oVirt - virtualization made easy Issue Type: Outage Components: oVirt CI Reporter: danken Assignee: infra Priority: High Labels: vdsm</pre> <p>Exception when executing the batch command : no workspace from node hudson.slaves.DumbSlave[vm0014.workers-phx.ovirt.org] which is computer hudson.slaves.SlaveComputer@695d3d3c and has channel null <a href="http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/19901/conso…">http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/19901/conso…</a></p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100073)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1511682298-27447-558--

1 0

[JIRA] (OVIRT-1781) ci failure due to no space on slave?
by Barak Korren (oVirt JIRA) 26 Nov '17

26 Nov '17

This is a multi-part message in MIME format... ------------=_1511681861-15549-547 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1781?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1781: -------------------------------- Labels: vdsm (was: ) > ci failure due to no space on slave? > ------------------------------------ > > Key: OVIRT-1781 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1781 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: oVirt CI > Reporter: danken > Assignee: infra > Priority: High > Labels: vdsm > > Exception when executing the batch command : no workspace from node > hudson.slaves.DumbSlave[vm0014.workers-phx.ovirt.org] which is > computer hudson.slaves.SlaveComputer@695d3d3c and has channel null > http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/19901/conso… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100073) ------------=_1511681861-15549-547 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1781?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1781:</h3> <pre>Labels: vdsm (was: )</pre> <blockquote><h3>ci failure due to no space on slave?</h3> <pre> Key: OVIRT-1781 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1781 Project: oVirt - virtualization made easy Issue Type: Outage Components: oVirt CI Reporter: danken Assignee: infra Priority: High Labels: vdsm</pre> <p>Exception when executing the batch command : no workspace from node hudson.slaves.DumbSlave[vm0014.workers-phx.ovirt.org] which is computer hudson.slaves.SlaveComputer@695d3d3c and has channel null <a href="http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/19901/conso…">http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/19901/conso…</a></p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100073)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1511681861-15549-547--

1 0

[JIRA] (OVIRT-1781) ci failure due to no space on slave?
by Barak Korren (oVirt JIRA) 26 Nov '17

26 Nov '17

This is a multi-part message in MIME format... ------------=_1511681852-28246-366 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1781?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1781: -------------------------------- Component/s: oVirt CI Epic Link: OVIRT-403 Issue Type: Outage (was: By-EMAIL) Priority: High (was: Medium) > ci failure due to no space on slave? > ------------------------------------ > > Key: OVIRT-1781 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1781 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: oVirt CI > Reporter: danken > Assignee: infra > Priority: High > > Exception when executing the batch command : no workspace from node > hudson.slaves.DumbSlave[vm0014.workers-phx.ovirt.org] which is > computer hudson.slaves.SlaveComputer@695d3d3c and has channel null > http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/19901/conso… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100073) ------------=_1511681852-28246-366 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1781?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1781:</h3> <pre>Component/s: oVirt CI Epic Link: OVIRT-403 Issue Type: Outage (was: By-EMAIL) Priority: High (was: Medium)</pre> <blockquote><h3>ci failure due to no space on slave?</h3> <pre> Key: OVIRT-1781 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1781 Project: oVirt - virtualization made easy Issue Type: Outage Components: oVirt CI Reporter: danken Assignee: infra Priority: High</pre> <p>Exception when executing the batch command : no workspace from node hudson.slaves.DumbSlave[vm0014.workers-phx.ovirt.org] which is computer hudson.slaves.SlaveComputer@695d3d3c and has channel null <a href="http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/19901/conso…">http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/19901/conso…</a></p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100073)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1511681852-28246-366--

1 0

[JIRA] (OVIRT-1781) ci failure due to no space on slave?
by Barak Korren (oVirt JIRA) 26 Nov '17

26 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1781?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1781: -------------------------------- Epic Link: OVIRT-403 > ci failure due to no space on slave? > ------------------------------------ > > Key: OVIRT-1781 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1781 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: oVirt CI > Reporter: danken > Assignee: infra > > Exception when executing the batch command : no workspace from node > hudson.slaves.DumbSlave[vm0014.workers-phx.ovirt.org] which is > computer hudson.slaves.SlaveComputer@695d3d3c and has channel null > http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/19901/conso… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100073)

1 0

[JIRA] (OVIRT-1781) ci failure due to no space on slave?
by danken (oVirt JIRA) 26 Nov '17

26 Nov '17

This is a multi-part message in MIME format... ------------=_1511679269-25584-136 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit danken created OVIRT-1781: ----------------------------- Summary: ci failure due to no space on slave? Key: OVIRT-1781 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1781 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: danken Assignee: infra Exception when executing the batch command : no workspace from node hudson.slaves.DumbSlave[vm0014.workers-phx.ovirt.org] which is computer hudson.slaves.SlaveComputer@695d3d3c and has channel null http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/19901/conso… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100073) ------------=_1511679269-25584-136 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>danken created OVIRT-1781:</h3> <pre> Summary: ci failure due to no space on slave? Key: OVIRT-1781 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1781 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: danken Assignee: infra</pre> <p>Exception when executing the batch command : no workspace from node hudson.slaves.DumbSlave[vm0014.workers-phx.ovirt.org] which is computer hudson.slaves.SlaveComputer@695d3d3c and has channel null</p> <p><a href="http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/19901/conso…">http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/19901/conso…</a></p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100073)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1511679269-25584-136--

1 0