[Bug 1259148] New: Regression: kubernetes 1.1.0 breaks watching for resources

[Red Hat Bugzilla]

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

            Bug ID: 1259148
           Summary: Regression: kubernetes 1.1.0 breaks watching for
                    resources
           Product: Fedora
           Version: 22
         Component: kubernetes
          Assignee: jchaloup(a)redhat.com
          Reporter: stefw(a)redhat.com
        QA Contact: extras-qa(a)fedoraproject.org
                CC: eparis(a)redhat.com, golang(a)lists.fedoraproject.org,
                    jcajka(a)redhat.com, jchaloup(a)redhat.com,
                    lsm5(a)redhat.com, nhorman(a)redhat.com, vbatts(a)redhat.com



Description of problem:

When cockpit tries to watch resources against kubernetes 1.1.0 it gets the
following complaints:

.> watching kubernetes nodes failed: too old resource version: 0 (13)
>  watching kubernetes pods failed: too old resource version: 0 (1)
>  watching kubernetes endpoints failed: too old resource version: 0 (7)
>  watching kubernetes nodes failed: too old resource version: 0 (13)
>  watching kubernetes pods failed: too old resource version: 0 (1)
>  watching kubernetes endpoints failed: too old resource version: 0 (7)
>  watching kubernetes nodes failed: too old resource version: 0 (13)
>  watching kubernetes pods failed: too old resource version: 0 (1)
>  watching kubernetes endpoints failed: too old resource version: 0 (7)
>  watching kubernetes nodes failed: too old resource version: 0 (13)
>  watching kubernetes pods failed: too old resource version: 0 (1)
>  watching kubernetes endpoints failed: too old resource version: 0 (7)
>  watching kubernetes nodes failed: too old resource version: 0 (13)
>  watching kubernetes pods failed: too old resource version: 0 (1)
>  watching kubernetes endpoints failed: too old resource version: 0 (7)
>  watching kubernetes nodes failed: too old resource version: 0 (13)
>  watching kubernetes pods failed: too old resource version: 0 (1)
>  watching kubernetes endpoints failed: too old resource version: 0 (7)
>  watching kubernetes nodes failed: too old resource version: 0 (13)
>  watching kubernetes pods failed: too old resource version: 0 (1)
>  watching kubernetes endpoints failed: too old resource version: 0 (7)
>  watching kubernetes nodes failed: too old resource version: 0 (13)
>  watching kubernetes pods failed: too old resource version: 0 (1)
>  watching kubernetes endpoints failed: too old resource version: 0 (7)
>  watching kubernetes nodes failed: too old resource version: 0 (13)
>  watching kubernetes pods failed: too old resource version: 0 (1)
>  watching kubernetes endpoints failed: too old resource version: 0 (7)
>  watching kubernetes nodes failed: too old resource version: 0 (13)
>  watching kubernetes pods failed: too old resource version: 0 (1)
>  watching kubernetes endpoints failed: too old resource version: 0 (7)
>  watching kubernetes nodes failed: too old resource version: 0 (13)
>  watching kubernetes pods failed: too old resource version: 0 (1)
>  watching kubernetes endpoints failed: too old resource version: 0 (7)
>  watching kubernetes nodes failed: too old resource version: 0 (13)
>  watching kubernetes pods failed: too old resource version: 0 (1)
>  watching kubernetes endpoints failed: too old resource version: 0 (7) 
E>
watching kubernetes nodes failed: too old resource version: 0 (13)
>  watching kubernetes pods failed: too old resource version: 0 (1)
Version-Release number of selected component (if applicable):

 kubernetes             x86_64 1.1.0-0.14.gitb6f18c7.fc22 updates-testing  33 k
 kubernetes-client      x86_64 1.1.0-0.14.gitb6f18c7.fc22 updates-testing 2.8 M
 kubernetes-master      x86_64 1.1.0-0.14.gitb6f18c7.fc22 updates-testing  13 M
 kubernetes-node        x86_64 1.1.0-0.14.gitb6f18c7.fc22 updates-testing 9.1 M

How reproducible:

Every time.

Steps to Reproduce:
1. Run Cockpit on your node, with cockpit-kubernetes
2. Navigate to cluster tab
3. Look at javascript console output

-- 
You are receiving this mail because:
You are on the CC list for the bug.