[Bug 1261459] New: Regression: kubectl logs --follow is now broken

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1261459

Bug ID: 1261459
           Summary: Regression: kubectl logs --follow is now broken
           Product: Fedora
           Version: 22
         Component: kubernetes
          Assignee: [e-mail]
          Reporter: [e-mail]
        QA Contact: [e-mail]
                CC: [e-mail], [e-mail],
                    [e-mail], [e-mail],
                    [e-mail], [e-mail], [e-mail]

Description of problem:

kubectl logs --follow hash now regressed.

Version-Release number of selected component (if applicable):

kubernetes-1.1.0-0.5.gite44c8e6.fc22.x86_64

How reproducible:

Every time.

Steps to Reproduce:
1. kubectl create -f <attachment>
2. kubectl get pods
3. kubectl logs --follow <pod>

Actual results:

Hangs.

Expected results:

Show the log output.

Additional info:

docker logs on the same container works.

[Bug 1261459] Regression: kubectl logs --follow is now broken

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1261459

--- Comment #1 from Stef Walter  ---
Created attachment 1071695
  --> https://bugzilla.redhat.com/attachment.cgi?id=1071695&action=edit
Test case

[Bug 1261459] Regression: kubectl logs --follow is now broken

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1261459

--- Comment #2 from Stef Walter  ---
This build works: http://koji.fedoraproject.org/koji/buildinfo?buildID=670280

[Bug 1261459] Regression: kubectl logs --follow is now broken

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1261459

Stef Walter  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
         Attachment|0                           |1
        #1071695 is|                            |
           obsolete|                            |

--- Comment #3 from Stef Walter  ---
Created attachment 1072268
  --> https://bugzilla.redhat.com/attachment.cgi?id=1072268&action=edit
Test case

Updated to simpler test case file.

[Bug 1261459] Regression: kubectl logs --follow is now broken

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1261459

--- Comment #4 from Stef Walter  ---
Tested against kubernetes git master. Fails there too. Filed issue:
https://github.com/kubernetes/kubernetes/issues/13811

[Bug 1261459] Regression: kubectl logs --follow is now broken

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1261459

--- Comment #5 from Stef Walter  ---
This build fixes the issue:

# rpm -q kubernetes
kubernetes-1.1.0-0.16.git388061f.fc22.x86_64

Jan, if you have narrowed it down, could you report upstream where the breakage
was? https://github.com/kubernetes/kubernetes/issues/13811

[Bug 1261459] Regression: kubectl logs --follow is now broken

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1261459

--- Comment #6 from Jan Chaloupka  ---
Actually, kubernetes-1.1.0-0.16.git388061f is kubernetes-1.0.6. Did not want to
introduce Epoch and mess with the spec file. Once 1.1.0 is stable, version will
continue.

[Bug 1261459] Regression: kubectl logs --follow is now broken

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1261459

--- Comment #7 from Jan Chaloupka  ---
$ kubectl version
will return the correct version. In AH or cockpit, rpm -q kubernetes is not
used so often I suppose. So it will not matter. All blame for this hack on me.

[Bug 1261459] Regression: kubectl logs --follow is now broken

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1261459

--- Comment #8 from Scott Dodson  ---
Seems the fix is here https://github.com/kubernetes/kubernetes/pull/13864

[Bug 1261459] Regression: kubectl logs --follow is now broken

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1261459

Stef Walter  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #9 from Stef Walter  ---
This is still the case on Fedora 22.

[Bug 1261459] Regression: kubectl logs --follow is now broken

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1261459

--- Comment #10 from Stef Walter  ---
$ rpm -q kubernetes-client
kubernetes-client-1.1.0-0.5.gite44c8e6.fc22.x86_64
$ rpm -q kubernetes
kubernetes-1.1.0-0.5.gite44c8e6.fc22.x86_64

$ 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-vp4k6
^C

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

sudo docker logs --follow on the same machine works, as does 'kubectl logs
mock-vp4k6' without --follow.

[Bug 1261459] Regression: kubectl logs --follow is now broken

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1261459

--- Comment #11 from Fedora Update System  ---
kubernetes-1.1.0-0.17.git388061f.fc22 has been submitted as an update to Fedora
22. https://bodhi.fedoraproject.org/updates/FEDORA-2016-b8c9642851

[Bug 1261459] Regression: kubectl logs --follow is now broken

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1261459

Fedora Update System  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |MODIFIED

[Bug 1261459] Regression: kubectl logs --follow is now broken

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1261459

Fedora Update System  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|MODIFIED                    |ON_QA

--- Comment #12 from Fedora Update System  ---
kubernetes-1.1.0-0.17.git388061f.fc22 has been pushed to the Fedora 22 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2016-b8c9642851

[Bug 1261459] Regression: kubectl logs --follow is now broken

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1261459

--- Comment #13 from Fedora Update System  ---
kubernetes-1.1.0-0.17.git388061f.fc22 has been pushed to the Fedora 22 stable
repository. If problems still persist, please make note of it in this bug
report.

[Bug 1261459] Regression: kubectl logs --follow is now broken

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1261459

Fedora Update System  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ON_QA                       |CLOSED
   Fixed In Version|                            |kubernetes-1.1.0-0.17.git38
                   |                            |8061f.fc22
         Resolution|---                         |ERRATA
        Last Closed|                            |2016-04-20 11:17:42