Red Hat Bugzilla – Bug 1515878
Short names discovery broken on v3.7.9 server
Last modified: 2018-01-23 12:58:09 EST
Description of problem: 'oc logs sts/mysts' fails with the error below instead of listing the statefulsets or "No resource found": oc logs -c prom-proxy sts/prometheus --loglevel=6 F1120 11:12:06.569506 76005 helpers.go:120] the server doesn't have a resource type "sts" 'oc logs statefulsets/mysts' works correctly. Version-Release number of selected component (if applicable): It works correctly on ca-central-1, but not on free-stg. So this probably regressed between 178 OSE and RC OSE. How reproducible: Not always, meaning this could be related to caching.
Adding Clayton which could add more info.
Could you help trying to reproduce this one? Clayton noticed it first but I was yet unable to reproduce. 'oc' used is always the latest version.
Adding some more folks since it's not yet clear if this is client-side or related to discovery and the shortNames field.
I built openshift/origin:release-3.7 and hit discovery. Got back ```json { "name": "statefulsets", "singularName": "", "namespaced": true, "kind": "StatefulSet", "verbs": [ "create", "delete", "deletecollection", "get", "list", "patch", "update", "watch" ], "shortNames": [ "sts" ], "categories": [ "all" ] } ``` It looks correct to me.
https://github.com/openshift/origin/issues/17411 master against 3.7 server, svc not in all
David, do you see it for services? I built openshift/origin:release-3.7 and see shortNames and categories for statefulsets, but not for services for example. Likely others.
BTW the same issue happens with `kubectl` master against openshift/origin:release-3.7 server.
There was a bug for services. I fixed it in kube, might have been 3.8 though.
(In reply to Fabiano Franz from comment #2) > Could you help trying to reproduce this one? Clayton noticed it first but I > was yet unable to reproduce. 'oc' used is always the latest version. Tried 3.7.9 oc against free-stg (3.7.9), I didn't reproduce it. But I found possible cause: try oc version several times, server version is unstable, seems some masters on free-stg were not restarted after upgrade[1]: $ oc version oc v3.7.9 ... Server https://api.free-stg.openshift.com:443 openshift v3.6.173.0.49 kubernetes v1.6.1+5115d708d7 $ oc version oc v3.7.9 ... Server https://api.free-stg.openshift.com:443 openshift v3.7.9 kubernetes v1.7.6+a08f5eeb62 Fabiano, it is possible cause, because I checked 3.7 oc against 3.6 OCP can reproduce 'the server doesn't have a resource type "sts"' [1] Adding Abhishek, default Assignee of Website, in CC' list for confirming to help check and restart them, thanks
> There was a bug for services. I fixed it in kube, might have been 3.8 though. David, picking the fix for services into 3.7 in https://github.com/openshift/ose/pull/931.
Will be in the next 3.7.
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/RHBA-2018:0113