Bug 1860789
| Summary: | [oc compatibility] - Cannot approve csr using oc 4.5 client on 4.6 server | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | RamaKasturi <knarra> |
| Component: | oc | Assignee: | Maciej Szulik <maszulik> |
| Status: | CLOSED ERRATA | QA Contact: | RamaKasturi <knarra> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.5 | CC: | akostadi, aos-bugs, fbrychta, jokerman, maszulik, mfojtik, rvanderp, sdodson, tnozicka, tsze, walters, wjiang, wking, yanyang |
| Target Milestone: | --- | Keywords: | Regression |
| Target Release: | 4.5.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause:
A new API version for CSR was introduced in OCP 4.6.
Consequence:
As a consequence older versions were not able to approve or deny certificates during upgrade.
Fix:
Tolerate different versions of CSRs in older versions of oc.
Result:
It is possible to deny or approve certificates with oc 4.5 against OCP server 4.6.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-10-19 14:54:24 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: | |||
| Bug Depends On: | 1874056 | ||
| Bug Blocks: | |||
|
Description
RamaKasturi
2020-07-27 07:05:52 UTC
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. https://access.redhat.com/errata/RHBA-2020:4228 |