Bug 1364948

Description of problem:
Created two pipeline apps,one slave uses maven image, one slave uses nodejs image.

After jenkins server run more than 24 hours,the synchronization doesn't work well.

1.The build numbers are not consistent.
maven slave pipeline app shows bc have built 11 times in openshift client, but there is 13 build in jenkins webconsole.
nodejs slave pipleline app shows bc have built 10 times in openshift client, but there is 12 builds in jenkins webcosnole.
Some builds are triggered from client, some from jenkins webconsole.

See the attachment.

2.The first new triggered build keep new status in both apps, no matter this build is complete/failed/cancelled in jenkins webconsole.

3.New triggered builds become to complete/failed/cancelled directly from new status(except the first new build), no running staus in openshift client.

New created pipeline apps work well.

Version-Release number of selected component (if applicable):
ci.dev.../openshift/jenkins-slave-nodejs-rhel7 965eb5e5766a
ci.dev.../openshift/jenkins-slave-maven-rhel7  7c6bbfb9656e
ci.dev.../openshift/jenkins-1-rhel7 bd3ab5d39d48

openshift v3.3.0.16
kubernetes v1.3.0+507d3a7

How reproducible:
always

Steps to Reproduce:
1.Created two pipeline apps,one slave uses maven image, one slave uses nodejs image.
2.Trigger some builds from openshift client and jenkins wenconsole
3.Leave jenkins server run more than 24 hours
4.Trigger some builds from openshift client and jenkins webconsole again
5.Check builds from openshift client and jenkins webconsole.

Actual results:
Builds can't sync well after jenkins server run long time.

Expected results:
Builds should sync well after jenkins server run long time.

Additional info:
There are errors in jenkins server pod log

INFO: onCompleted job/sample-pipeline/1/
Aug 08, 2016 4:18:03 AM jenkins.slaves.JnlpSlaveAgentProtocol$Handler$1 onClosed
WARNING: Computer.threadPoolForRemoting [#19] for afb6aa4b5300 terminated
java.io.EOFException
	at org.jenkinsci.remoting.nio.NioChannelHub$3.run(NioChannelHub.java:614)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112)
	at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
	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:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)

Aug 08, 2016 4:18:04 AM io.fabric8.jenkins.openshiftsync.BuildSyncRunListener upsertBuild
INFO: Patching build in namespace xiuwang91 with name: sample-pipeline-1 phase: Failed
Aug 08, 2016 4:18:04 AM io.fabric8.jenkins.openshiftsync.BuildSyncRunListener onFinalized
INFO: onFinalized job/sample-pipeline/1/