Bug 2024643 - Bump to latest available 1.22.5 k8s
Summary: Bump to latest available 1.22.5 k8s
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-apiserver
Version: 4.9
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
: 4.9.z
Assignee: Josef Karasek
QA Contact: Zimo Xiao
Olivia Payne
URL:
Whiteboard: LifecycleReset
: 2005076 2050253 (view as bug list)
Depends On: 2044347
Blocks: 2024642 2042501
TreeView+ depends on / blocked
 
Reported: 2021-11-18 15:02 UTC by Thomas Jungblut
Modified: 2022-03-16 11:39 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
This fix contains the following changes coming from updated version of kubernetes up to v1.22.5: Changelog for v1.22.5: https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.22.md#changelog-since-v1225
Clone Of:
Environment:
Last Closed: 2022-03-16 11:38:43 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift kubernetes pull 1103 0 None open Bug 2024643: Rebase v1.22.5 2022-01-04 13:52:02 UTC
Red Hat Product Errata RHBA-2022:0798 0 None None None 2022-03-16 11:39:09 UTC

Description Thomas Jungblut 2021-11-18 15:02:13 UTC
This fix contains the following changes coming from updated version of kubernetes up to v1.22.4:

Changelog for v1.22.4:
https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.22.md#changelog-since-v1223

Comment 1 Michal Fojtik 2021-12-25 05:22:30 UTC
This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Whiteboard if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.

Comment 2 Michal Fojtik 2022-01-04 14:22:35 UTC
The LifecycleStale keyword was removed because the needinfo? flag was reset.
The bug assignee was notified.

Comment 5 Scott Dodson 2022-03-04 15:27:42 UTC
*** Bug 2005076 has been marked as a duplicate of this bug. ***

Comment 7 Zimo Xiao 2022-03-07 08:58:20 UTC
Verification steps:
$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.9.0-0.nightly-2022-03-05-223017   True        False         7m45s   Cluster version is 4.9.0-0.nightly-2022-03-05-223017

Check the kubelet version as below,
$ oc get no
NAME                                         STATUS   ROLES    AGE   VERSION
ip-10-0-149-137.us-east-2.compute.internal   Ready    master   28m   v1.22.5+5c84e52
ip-10-0-159-32.us-east-2.compute.internal    Ready    worker   21m   v1.22.5+5c84e52
ip-10-0-163-50.us-east-2.compute.internal    Ready    worker   22m   v1.22.5+5c84e52
ip-10-0-184-41.us-east-2.compute.internal    Ready    master   25m   v1.22.5+5c84e52
ip-10-0-211-195.us-east-2.compute.internal   Ready    master   26m   v1.22.5+5c84e52

Check the kube-apiserer version as below,
$ oc get co/kube-apiserver -o yaml | grep -A1 '\- name: kube-apiserver'
  - name: kube-apiserver
    version: 1.22.5

Check Kubernetes version as below,
$ oc version
Client Version: 4.10.1
Server Version: 4.9.0-0.nightly-2022-03-05-223017
Kubernetes Version: v1.22.5+5c84e52

See above, Kubernetes is updated to 1.22.5. As for functional tests, have to rely on QE's daily schedule regression tests. During the tests, if there will be issue hit on any component related to the rebase, separate bug should be filed. Move the bug VERIFIED.

Comment 8 Zimo Xiao 2022-03-07 08:58:50 UTC
Verification steps:
$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.9.0-0.nightly-2022-03-05-223017   True        False         7m45s   Cluster version is 4.9.0-0.nightly-2022-03-05-223017

Check the kubelet version as below,
$ oc get no
NAME                                         STATUS   ROLES    AGE   VERSION
ip-10-0-149-137.us-east-2.compute.internal   Ready    master   28m   v1.22.5+5c84e52
ip-10-0-159-32.us-east-2.compute.internal    Ready    worker   21m   v1.22.5+5c84e52
ip-10-0-163-50.us-east-2.compute.internal    Ready    worker   22m   v1.22.5+5c84e52
ip-10-0-184-41.us-east-2.compute.internal    Ready    master   25m   v1.22.5+5c84e52
ip-10-0-211-195.us-east-2.compute.internal   Ready    master   26m   v1.22.5+5c84e52

Check the kube-apiserer version as below,
$ oc get co/kube-apiserver -o yaml | grep -A1 '\- name: kube-apiserver'
  - name: kube-apiserver
    version: 1.22.5

Check Kubernetes version as below,
$ oc version
Client Version: 4.10.1
Server Version: 4.9.0-0.nightly-2022-03-05-223017
Kubernetes Version: v1.22.5+5c84e52

See above, Kubernetes is updated to 1.22.5. As for functional tests, have to rely on QE's daily schedule regression tests. During the tests, if there will be issue hit on any component related to the rebase, separate bug should be filed. Move the bug VERIFIED.

Comment 10 Ryan Phillips 2022-03-11 13:38:02 UTC
*** Bug 2050253 has been marked as a duplicate of this bug. ***

Comment 12 errata-xmlrpc 2022-03-16 11:38:43 UTC
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.9.24 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-2022:0798


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