Bug 1294758 - cannot get deployments using oc
Summary: cannot get deployments using oc
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: Deployments
Version: 3.x
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Dan Mace
QA Contact: zhou ying
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-30 07:03 UTC by Wang Haoran
Modified: 2016-12-09 21:53 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-09 21:53:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Wang Haoran 2015-12-30 07:03:30 UTC
Description of problem:
When invoke $oc get deployments, command line return "cannot list extensions.deployments in project"

Version-Release number of selected component (if applicable):
openshift v1.1-630-gb197d32
kubernetes v1.1.0-origin-1107-g4c8e6f4

How reproducible:
always

Steps to Reproduce:
1.Create a project
2.Deploy a pod
3.run command with normal user
 $oc get deployments -n test
4. run command with cluster admin
 $oc get deployments -n test

Actual results:
step 3 will get error: 
cannot list extensions.deployments in project test
step 4 will return nothing.
Expected results:
1. if deployments is not a resource , we should return err like "error: no resource "test" has been defined"
2. cluster admin and project admin user should have the same output
Additional info:

Comment 1 Bogdan Calomfirescu 2016-08-31 10:40:42 UTC
Hello,

Do you have any news about this bug?

Is there a workaround so far?

Kind regards

Comment 2 Dan Mace 2016-08-31 12:49:34 UTC
This bug should probably have been closed as fixed a long time ago. Newer versions of `oc` corrected the issue (in that the commands returns nothing instead of an error, as OpenShift has no "deployment" resource).

Comment 3 Wang Haoran 2016-09-05 07:40:00 UTC
verified with:
openshift v1.3.0-alpha.3+e3e0f53
kubernetes v1.3.0+52492b4
etcd 2.3.0+git


Note You need to log in before you can comment on or make changes to this bug.