[devops] 6.1.test_staging_mirror failed because of Jenkins error

[Dmitry Mescheryakov]

All the child jobs of the following build
http://jenkins-product.srt.mirantis.net:8080/view/Staging%20Mirrors/job/6.1.test_staging_mirror/101/

completed successfully, but the build itself failed because of the following Jenkins failure:

...
Finished Build : #44 of Job : 6.1.set_stable_mirror with status :SUCCESS
Copied 1 artifact from "6.1.set_stable_mirror" build number 44
FATAL: command execution failed
hudson.remoting.ChannelClosedException: channel is already closed
 at hudson.remoting.Channel.send(Channel.java:524)
 at hudson.remoting.Request.call(Request.java:129)
 at hudson.remoting.Channel.call(Channel.java:722)
...

[Mateusz Matuszkowiak (mmatuszkowiak)]

Today (12 FEB) on master in logs for that particular slave appeared:
<!---- cut ----->
<===[JENKINS REMOTING CAPACITY]===>Slave.jar version: 2.32
This is a Unix slave
Copied maven-agent.jar
Copied maven3-agent.jar
Copied maven3-interceptor.jar
Copied maven-interceptor.jar
Copied maven2.1-interceptor.jar
Copied plexus-classworld.jar
Copied classworlds.jar
Slave successfully connected and online
ERROR: Connection terminated
ha:AAAAWB+LCAAAAAAAAP9b85aBtbiIQSmjNKU4P08vOT+vOD8nVc8DzHWtSE4tKMnMz/PLL0ldFVf2c+b/lb5MDAwVRQxSaBqcITRIIQMEMIIUFgAAckCEiWAAAAA=java.io.IOException: Unexpected termination of the channel
 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50)
Caused by: java.io.EOFException
 at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2570)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1314)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:368)
 at hudson.remoting.Command.readFrom(Command.java:92)
 at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:59)
 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)
<!---- cut ----->

[Mateusz Matuszkowiak (mmatuszkowiak)]

So far it looks like network issues between master and slave node

[Igor Shishkin (teran)]

It looks like it was at the time when we upgraded python-devops by QA folks request.

[Igor Shishkin (teran)]

Nastya, please comment.

[Nastya Urlapova (aurlapova)]

Igor, I don't know at that particular time you were been updating devops. What I have to comment?

[Igor Shishkin (teran)]

It was being updated at that time.
Comment I meant about it was QA's scheduled maintenance.

Anyway reason is announced and it's not a bug so close as Invalid.

[Mike Scherbakov (mihgen)]

I would say it's rather just "Fix Committed" then, instead of Invalid. If it was temporary network failure due to maintenance, then we can say it is actually fixed - we've restored connectivity after maintenance window was over.

[Igor Shishkin (teran)]

Ok :)