Hide Forgot
Description of problem: When one apiserver group not work well, it should not abort output normal ones under oc api-resources Version-Release number of selected component (if applicable): oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.0.0-0.nightly-2019-01-15-184339 True False 20s Cluster version is 4.0.0-0.nightly-2019-01-15-184339 oc version: oc v4.0.0-0.123.0 How reproducible: Always Steps to Reproduce: 1. $oc scale --replicas=0 deploy/prometheus-adapter -n openshift-monitoring (for reproduce issue) 2. $oc api-resources 3. $oc api-resources --api-group=extensions Actual results: 2-3 error: unable to retrieve the complete list of server APIs: metrics.k8s.io/v1beta1: the server is currently unable to handle the request Expected results: 2-3 should print the supported normal API resources Additional info:
shahan, just remembered there reported 3.11 bug 1656295 . But that has additional `oc adm migrate storage` symptom.
Origin PR: https://github.com/openshift/origin/pull/21816
Origin PR has merged. Moving to ON_QA
[hasha@fedora_pc ~]$ oc scale --replicas=0 deploy/prometheus-adapter -n openshift-monitoring deployment.extensions/prometheus-adapter scaled [hasha@fedora_pc ~]$ oc api-resources NAME SHORTNAMES APIGROUP NAMESPACED KIND <trunked> groups user.openshift.io false Group identities user.openshift.io false Identity useridentitymappings user.openshift.io false UserIdentityMapping users user.openshift.io false User error: unable to retrieve the complete list of server APIs: metrics.k8s.io/v1beta1: the server is currently unable to handle the request, packages.apps.redhat.com/v1alpha1: the server is currently unable to handle the request cluster version: 4.0.0-0.alpha-2019-02-11-201342 Verified this bug
Can this be backported to 3.11? Same problem.
You can easily use oc 4.1 binary for that. I'm not sure that this is that critical to get it backported.
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-2019:0758