7.0 staging fails because of network issue

Bug #1484065 reported by Ivan Berezovskiy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
Critical
Andrey Nikitin

Bug Description

Staging jobs have failed because of network issues:

Build step 'MultiJob Phase' marked build as failure
Looks like the node went offline during the build. Check the slave log for the details.
details

FATAL: channel is already closed
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)
 at hudson.Launcher$RemoteLauncher.kill(Launcher.java:887)
 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:609)
 at com.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.run(MultiJobBuild.java:134)
 at hudson.model.Run.execute(Run.java:1593)
 at com.tikal.jenkins.plugins.multijob.MultiJobBuild.run(MultiJobBuild.java:73)
 at hudson.model.ResourceController.execute(ResourceController.java:88)
 at hudson.model.Executor.run(Executor.java:247)
Caused by: java.net.SocketException: Socket closed

http://jenkins-product.srt.mirantis.net:8080/view/7.0/job/7.0.test_staging_mirror/163/

Tags: devops
Changed in fuel:
importance: Undecided → Critical
Revision history for this message
Aleksandra Fedorova (bookwar) wrote :

Outage of network hardware in Saratov. Resolved by IT department.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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