Hide Forgot
Problem description: Not able to list any existing resources by running "oc get all" after logging on AEP, can only get these lines without any other thing: $oc get all Unable to list "buildconfigs": the server could not find the requested resource Unable to list "builds": the server could not find the requested resource Version-Release number of selected component (if applicable): oc v3.1.1.905 kubernetes v1.2.0-alpha.7-703-gbc4550d How reproducible: Always Steps to Reproduce: 1.Login to AEP 2.Create a new project with sufficient resources in it: $oc get svc NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR AGE java-mainclass x.x.x.x <none> 8778/TCP app=java-mainclass,deploymentconfig=java-mainclass 4m $ oc get po NAME READY STATUS RESTARTS AGE java-mainclass-1-u62c4 1/1 Running 0 5m java-mainclass-1-y7igr 1/1 Running 0 6m 3.$oc get all Actual Result: Not able to list any existing resources by running "oc get all" after logging on AEP, can only get these lines without any other thing: $oc get all Unable to list "buildconfigs": the server could not find the requested resource Unable to list "builds": the server could not find the requested resource Expected Result: Should be able to list all the existing resources by running "oc get all" after logging on AEP Additional info: Issue did not exist after connected the same oc client with OSE
The 'get' command is supposed to fetch with ContinueOnError, but maybe the "all" alias is being considered just one resource. Looking into it.
See https://github.com/openshift/origin/pull/7661. We've update the determination of what `all` means to correctly choose the list of resources.
Merged into origin.
Verified with devenv-rhel7_3640, it's fixed. Will continue verify this after bug fix merged in AP.
Should be in v3.2.0.1 built today.
It's fixed with latest AEP puddle 2016-03-09.2, together with oc version: oc v3.2.0.1 kubernetes v1.2.0-alpha.7-703-gbc4550d
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/RHSA-2016:1064