[Fail] [k8s.io] Pods [It] should support remote command execution over websockets [Suite:openshift/conformance/parallel] [Suite:k8s]

[gabemontero]

See https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin_extended_conformance_install/7855/consoleFull#-169259343956c60d7be4b02b88ae8c268b

The failed test highlighted that Feb 22 20:21:07.165: Got message from server that didn't start with channel 1 (STDOUT): [2]

The pod for the test was in fact running.

I saw no errors in the node log for the pod prior to the namespace getting tore down.

[gabemontero]

@openshift/sig-kube-origin

[gabemontero]

@sjenning fyi

[sosiouxme]

subject looks similar to #18721 but not sure failure is the same.

I saw this too in https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/18709/test_pull_request_origin_extended_conformance_install/7879/

[deads2k]

Is this flaking or just straight out failing?

[deads2k]

No successful runs in the last 18 hours. Bumping to p0.

[deads2k]

The commit suggested by https://deck-ci.svc.ci.openshift.org/?job=test_branch_origin_extended_conformance_install doesn't make any sense. It must be a side-effect of something else.

@Kargakis @stevekuznetsov @derekwaynecarr there was a docker something in our ami, right?

[runcom]

This has been broken by the upgrade to docker 1.13 (very very likely). First build with 1.13 broken:

https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin_extended_conformance_install/7843/consoleFull#51637152658b6e51eb7608a5981914356

Previous build with 1.12 success: https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/18625/test_pull_request_origin_extended_conformance_install/7842/