Description of problem: When using command `oc get storagelcass storageclass_name` will got error message like Error from server (Forbidden): User "chaoyang" cannot get storage.k8s.io.storageclasses at the cluster scope Version-Release number of selected component (if applicable): dev-preview-int openshift v3.6.65 kubernetes v1.6.1+5115d708d7 How reproducible: Always Steps to Reproduce: 1.Using `oc get storageclass` $ oc get storageclass NAME TYPE ebs (default) kubernetes.io/aws-ebs 2.Using cli command `oc get storageclass ebs` oc get storageclass ebs Error from server (Forbidden): User "chaoyang" cannot get storage.k8s.io.storageclasses at the cluster scope Actual results: Got error message like Error from server (Forbidden): User "chaoyang" cannot get storage.k8s.io.storageclasses at the cluster scope Expected results: Should display the storageclass name and type info Master Log: Node Log (of failed PODs): PV Dump: PVC Dump: StorageClass Dump (if StorageClass used by PV/PVC): Additional info:
Yes, the original intent was to be able to let users list storageclass names without seeing details, but as stated above, that can not be accomplished with the API, so at this point, not sure it makes sense to restrict "get"
OK, I agree it makes sense to let users "get" storage classes, I will open a PR and we can discuss it further there if needed. I think there are some implications of this on the UI side as well, if we all agree there's no harm in letting users see storage class details, so that will have to be considered/tracked somewhere.
PR opened against origin master https://github.com/openshift/origin/pull/14209
OpenShift Online Preview has been decommissioned, go to https://manage.openshift.com/ for using OpenShift Online starter cluster
It is passed on oc v3.6.135 kubernetes v1.6.1+5115d70 oc get storageclass gp2 NAME TYPE gp2 (default) kubernetes.io/aws-ebs
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-2017:3188