Description of problem:
When trying to approve a csr on 4.6 cluster using oc4.5 client it fails with error "error: no kind "CertificateSigningRequest" is registered for version "certificates.k8s.io/v1" in scheme "k8s.io/kubectl/pkg/scheme/scheme.go:28"
Version-Release number of selected component (if applicable):
[ramakasturinarra@dhcp35-60 ~]$ oc version
Client Version: 4.5.0-202007240519.p0-b66f2d3
Server Version: 4.6.0-0.nightly-2020-07-25-091217
Kubernetes Version: v4.6.0-202007250017.p0-dirty
Steps to Reproduce:
1. Use oc 4.5 client 4.5.0-202007240519.p0-b66f2d3 to approve a csr on 4.6 server
2. oc adm certificate approve <csr-name>
Approving certificate fails with "error: no kind "CertificateSigningRequest" is registered for version "certificates.k8s.io/v1" in scheme "k8s.io/kubectl/pkg/scheme/scheme.go:28"
Approval of certificates should work with out any issues.
Same works fine with "openshift-clients-4.6.0-202007241012.p0.git.3670.b87fe27.el7.x86_64"
[ramakasturinarra@dhcp35-60 ~]$ oc adm certificate approve csr-r4cdq
I run oc get node cmd in 4.5 server, then in .kube/cache/discovery/, it has certificates.k8s.io/v1beta1.
But for 4.6 server, has both certificates.k8s.io/v1beta1 and certificates.k8s.io/v1. oc 4.5 should work for this change, i.e. is a bug
yeah, we need to backport kubernetes fixes that went into 1.18 branch - we are planing a small rebase
Now that I'm back, I'll be handling these.
*** Bug 1861828 has been marked as a duplicate of this bug. ***
*** Bug 1862352 has been marked as a duplicate of this bug. ***
I’m adding UpcomingSprint, because I was occupied by fixing bugs with higher priority/severity, developing new features with higher priority, or developing new features to improve stability at a macro level. I will revisit this bug next sprint.
If not fixed it needs to go to release notes as users expect oc version x.y to be compatible with cluster version x.y+1
(In reply to Aleksandar Kostadinov from comment #8)
> If not fixed it needs to go to release notes as users expect oc version x.y
> to be compatible with cluster version x.y+1
It is planned to be fixed in 4.5
Sounds good, thank you.
This is also failing in the same way with as early as 4.2.35 (that I had available to test with). Are earlier versions going to be fixed?
(In reply to Aleksandar Kostadinov from comment #10)
> Sounds good, thank you.
> This is also failing in the same way with as early as 4.2.35 (that I had
> available to test with). Are earlier versions going to be fixed?
Nope, we guarantee +/- 1 version compatibility, so only 4.5 will be fixed. Also earlier versions are either EOL or in maintenance.
This will be fixed in https://github.com/openshift/oc/pull/551
PR is waiting in the queue.
*** Bug 1879177 has been marked as a duplicate of this bug. ***
The PRs are in the queue already.
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 (OpenShift Container Platform 4.5.15 bug fix update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.