Regression: kubectl logs --follow is broken

[stefwalter]

This command is broken on git master:

kubectl logs --follow <pod>

It just hangs forever rather than producing any output. It used to work in kubernetes 1.0

[stefwalter]

Reproduce like so:

$ wget -O test.json 'https://bugzilla.redhat.com/attachment.cgi?id=1072268'
$ kubectl create -f test.json
$ kubectl get pods # get name and wait until running
$ kubectl logs --follow mock-ffctj
^C

The above just hangs. It should instead produce output:

$ kubectl logs --follow mock-tpo3j
HelloMessage.
HelloMessage.
HelloMessage.
HelloMessage.
HelloMessage.
HelloMessage.
HelloMessage.
HelloMessage.
...

docker logs --follow on the same machine works:

[root@falcon kubernetes]# docker logs --follow 248896a80890
HelloMessage.
HelloMessage.
HelloMessage.
HelloMessage.
HelloMessage.
...

[stefwalter]

@eparis @ingvagabund @liggitt CC

[roberthbailey]

@jlowdermilk CC as well

[roberthbailey]

It sounds like we don't have any regression tests for this feature; we should add one as we fix it.

[stefwalter]

The Cockpit integration tests caught this bug. So yes, testing upstream would be great.

[mikedanese]

@kubernetes/kubectl

[smarterclayton]

Do we know what the problem is?

[liggitt]

Did #13864 not resolve it?

[feiskyer]

#13864 has fixed kubectl logs --follow broken problem.

[liggitt]

@stefwalter closing as fixed in master