Bug 2109799

Summary: [oc compatibility] - oc serviceaccounts get-token <sa_name> for 4.10 oc not functioning against 4.11 cluster
Product: OpenShift Container Platform Reporter: RamaKasturi <knarra>
Component: ocAssignee: Arda Guclu <aguclu>
oc sub component: oc QA Contact: zhou ying <yinzhou>
Status: CLOSED DUPLICATE Docs Contact:
Severity: high    
Priority: unspecified CC: jchaloup, mfojtik
Version: 4.11   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-09-06 11:29:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description RamaKasturi 2022-07-22 07:02:44 UTC 
Description of problem:
Given oc is supposed to be +1/-1 version compatible i see that oc get sa <token> for 4.10 against 4.11 cluster gives error

Version-Release number of selected component (if applicable):
4.10


How Reproducible:
Login to 4.11 cluster
Using 4.10 oc client run the command ‘oc serviceaccounts get-token <sa_name> -n openshift-monitoring`

Actual Results:
ec2-user@ip-10-0-8-161 ~ % ./oc serviceaccounts get-token prometheus-k8s -n openshift-monitoring
error: could not find a service account token for service account "prometheus-k8s"

Expected Results:
Given oc is supposed to be +1/-1 version compatible i expect that no error is thrown.

Additional Info:
https://coreos.slack.com/archives/CS05TR7BK/p1658470267599869?thread_ts=1658470242.227799&cid=CS05TR7BK
Comment 2 Arda Guclu 2022-09-06 11:29:45 UTC 

*** This bug has been marked as a duplicate of bug 2108241 ***