Description of problem: sometimes "oc logs" appears to freeze, with new lines only showing after restarting the client program. In some cases the client would also fail with the error message “unexpected stream type ""”. The issue was reported https://github.com/kubernetes/kubernetes/issues/47800. Version-Release number of selected component (if applicable): oc v3.6.0+c4dd4cf kubernetes v1.6.1+5115d708d7 features: Basic-Auth GSSAPI Kerberos SPNEGO docker-1.12.6-55.gitc4618fb.el7.x86_64 How reproducible: ------------ apiVersion: v1 kind: DeploymentConfig metadata: creationTimestamp: null generation: 1 name: btest spec: replicas: 1 selector: deployment-config.name: btest strategy: activeDeadlineSeconds: 21600 resources: {} rollingParams: intervalSeconds: 1 maxSurge: 25% maxUnavailable: 25% timeoutSeconds: 600 updatePeriodSeconds: 1 type: Rolling template: metadata: creationTimestamp: null labels: deployment-config.name: btest spec: containers: - command: - /bin/sh - -c - | gen() { date dd if=/dev/urandom bs=1024 count=2 2>/dev/null | base64 | tr -d '\n' | tr -d '[0-9]' } while sleep .1; do gen; gen >&2; done image: docker.io/busybox:latest imagePullPolicy: Always name: default-container resources: {} terminationMessagePath: /dev/termination-log terminationMessagePolicy: File dnsPolicy: ClusterFirst restartPolicy: Always schedulerName: default-scheduler securityContext: {} terminationGracePeriodSeconds: 30 test: false triggers: - type: ConfigChange --------------- Configuration of docker: /usr/bin/dockerd-current --add-runtime docker-runc=/usr/libexec/docker/docker-runc-current --default-runtime=docker-runc --authorization-plugin=rhel-push-plugin --exec-opt native.cgroupdriver=systemd --userland-proxy-path=/usr/libexec/docker/docker-proxy-current --selinux-enabled -l warn --log-opt max-size=1M --log-opt max-file=3 --storage-driver overlay2 --mtu=1450 --add-registry registry.access.redhat.com Steps to Reproduce: 1. 2. 3. Actual results: Every time this happens the output of "oc logs" stops, as does the output on the web console. Expected results: Following logs Additional info:
This was cherry picked to kube 1.7 here: https://github.com/kubernetes/kubernetes/pull/51871 And brought in as part of the kube 1.7.6 rebase: https://github.com/openshift/origin/pull/16615
I can not reproduce the issue on the environment: openshift v3.7.0-0.184.0 kubernetes v1.7.6+a08f5eeb62 etcd 3.2.8
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:3188