Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

oc get all lost backward compatibility from 3.9 to 3.6 #18473

Closed
tnozicka opened this issue Feb 6, 2018 · 5 comments
Closed

oc get all lost backward compatibility from 3.9 to 3.6 #18473

tnozicka opened this issue Feb 6, 2018 · 5 comments
Assignees
@juanvallejo @deads2k
Labels
component/cli kind/bug Categorizes issue or PR as related to a bug. priority/P1
Milestone
v3.9

Comments

@tnozicka
Copy link
Contributor

tnozicka commented Feb 6, 2018 •
edited
Loading

For some reason oc get all (on 3.9) shows nothing when talking to 3.6 server.
@deads2k @juanvallejo can this be related to something we did when 3.9 stated to show some resources twice?

$ oc get all
No resources found.

$ oc-v3.6.1 get all 
NAME          HOST/PORT      PATH      SERVICES       PORT      TERMINATION     WILDCARD
routes/test   xxxxxxx             non-existing   <all>     edge/Redirect   None

$ oc version
oc v3.9.0-alpha.4+709c3a8-24
kubernetes v1.9.1+a0ce1bc657
features: Basic-Auth GSSAPI Kerberos SPNEGO

Server https://127.0.0.1:8443
openshift v3.6.1+008f2d5
kubernetes v1.6.1+5115d708d7

$ oc get all
No resources found.
@tnozicka tnozicka added kind/bug Categorizes issue or PR as related to a bug. component/cli priority/P1 labels Feb 6, 2018
@tnozicka tnozicka added this to the 3.9.0 milestone Feb 6, 2018
@tnozicka
Copy link
Contributor Author

tnozicka commented Feb 6, 2018

oc get route works so this is likely something about discovery

@deads2k
Copy link
Contributor

deads2k commented Feb 6, 2018

We support n-1 from oc/kubectl. This is beyond the scope. In this case, it's because 3.6 discovery doesn't have categories.

@deads2k deads2k closed this as completed Feb 6, 2018
@tnozicka
Copy link
Contributor Author

tnozicka commented Feb 6, 2018 •
edited
Loading

Ok, tried 3.7 (which is n-1 since 3.8 doesn't count) and it shows the route there (in oc get all), but twice :/

edit: (to clarify I tried 3.9 client to 3.7 server)

@deads2k
Copy link
Contributor

deads2k commented Feb 6, 2018

Ok, tried 3.7 (which is n-1 since 3.8 doesn't count) and it shows the route there (in oc get all), but twice :/

3.7 is bugged. Need picks of #18219 and #18085 into 3.7 I guess.

@juanvallejo

@juanvallejo
Copy link
Contributor

@deads2k on it

This was referenced Feb 6, 2018
Merged
Merged
openshift-merge-robot added a commit that referenced this issue Feb 9, 2018
@openshift-merge-robot
Merge pull request #18478 from juanvallejo/backport-origin-pr-18219-l…
1ce3eee 
…imit-all

Automatic merge from submit-queue.

Backport origin pr 18219 limit all

Picks kubernetes/kubernetes#49624
Picks #18219

Depends on #18476

Addresses #18473 (comment)

cc @deads2k
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@juanvallejo juanvallejo

@deads2k deads2k

Labels
component/cli kind/bug Categorizes issue or PR as related to a bug. priority/P1
Projects
None yet
Milestone
v3.9
Development

No branches or pull requests
3 participants
@juanvallejo @deads2k @tnozicka