Description of problem: Meet error 'cannot get path "/swagger-2.0.0.pb-v1"' when run v3.9 `oc explain` resource against old server (e.g. v3.7). Other oc command does not replicate this. It is not met when using oc v3.9 against openshift v3.9, or v3.7 against v3.7 Version-Release number of selected component (if applicable): oc v3.9.0-0.24.0 against openshift v3.7.26 How reproducible: Always Steps to Reproduce: 1. Use oc v3.9 login v3.7 server 2. Run v3.9 `oc explain pod` Error from server (Forbidden): User "xxia" cannot get path "/swagger-2.0.0.pb-v1": User "xxia" cannot "get" on "/swagger-2.0.0.pb-v1" Actual results: 2. More log info: $ oc explain pod --loglevel 6 I0126 16:24:35.047529 1714 round_trippers.go:436] GET https://MASTER:8443/swagger-2.0.0.pb-v1 403 Forbidden in 1013 milliseconds I0126 16:24:35.048949 1714 helpers.go:201] server response object: [{ "metadata": {}, "status": "Failure", "message": "User \"xxia\" cannot get path \"/swagger-2.0.0.pb-v1\": User \"xxia\" cannot \"get\" on \"/swagger-2.0.0.pb-v1\"", "reason": "Forbidden", "details": { "causes": [ { "reason": "UnexpectedServerResponse", "message": "User \"xxia\" cannot get path \"/swagger-2.0.0.pb-v1\": User \"xxia\" cannot \"get\" on \"/swagger-2.0.0.pb-v1\"" } ] }, "code": 403 }] F0126 16:24:35.052265 1714 helpers.go:119] Error from server (Forbidden): User "xxia" cannot get path "/swagger-2.0.0.pb-v1": User "xxia" cannot "get" on "/swagger-2.0.0.pb-v1" Expected results: 2. Command should work Additional info:
Pick into 3.7 branch: https://github.com/openshift/origin/pull/18309
Waiting for 3.7 new puddle that will include the PR
New 3.7 version v3.7.28 is built. Tested with oc 3.9 against v3.7.28 server, the bug is fixed, so moving it to VERIFIED: $ oc version oc v3.9.0-0.38.0 kubernetes v1.9.1+a0ce1bc657 features: Basic-Auth GSSAPI Kerberos SPNEGO Server https://$MASTER:8443 openshift v3.7.28 kubernetes v1.7.6+a08f5eeb62 $ oc explain po DESCRIPTION: Pod is a collection of containers that can run on a host. This resource is created by clients and scheduled onto hosts. FIELDS: ...
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:0636