[devops] 6.1.test_staging_mirror failed because of Jenkins error

Bug #1421335 reported by Dmitry Mescheryakov
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
Critical
Igor Shishkin

Bug Description

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)
...

tags: added: jenkins
Changed in fuel:
assignee: Fuel DevOps (fuel-devops) → Mateusz Matuszkowiak (mmatuszkowiak)
tags: added: staging
Revision history for this message
Mateusz Matuszkowiak (mmatuszkowiak) wrote :

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 ----->

Revision history for this message
Mateusz Matuszkowiak (mmatuszkowiak) wrote :

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

Changed in fuel:
status: New → In Progress
Revision history for this message
Igor Shishkin (teran) wrote :

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

Changed in fuel:
assignee: Mateusz Matuszkowiak (mmatuszkowiak) → Nastya Urlapova (aurlapova)
Revision history for this message
Igor Shishkin (teran) wrote :

Nastya, please comment.

Revision history for this message
Nastya Urlapova (aurlapova) wrote :

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

Changed in fuel:
assignee: Nastya Urlapova (aurlapova) → Fuel DevOps (fuel-devops)
Revision history for this message
Igor Shishkin (teran) wrote :

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.

Changed in fuel:
status: In Progress → Invalid
assignee: Fuel DevOps (fuel-devops) → Igor Shishkin (teran)
Revision history for this message
Mike Scherbakov (mihgen) wrote :

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.

Revision history for this message
Igor Shishkin (teran) wrote :

Ok :)

Changed in fuel:
status: Invalid → Fix Committed
Changed in fuel:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.