Bug 2058291 - CI builds should have correct version of Kube without needing to push tags everytime
Summary: CI builds should have correct version of Kube without needing to push tags ev...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-apiserver
Version: 4.11
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.11.0
Assignee: Abu Kashem
QA Contact: jmekkatt
URL:
Whiteboard:
Depends On: 2049603
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-24 16:19 UTC by ravig
Modified: 2022-08-10 10:51 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2049603
Environment:
Last Closed: 2022-08-10 10:51:15 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 10:51:34 UTC

Description ravig 2022-02-24 16:19:58 UTC 
+++ This bug was initially created as a clone of Bug #2049603 +++

Description of problem:
4.10 CI releases still report Kubernetes Version: v1.22.1-4609+60f5a1c6c03d74-dirty
instead of the expected 1.23

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


How reproducible:


Steps to Reproduce:
1. ask cluster bot for a ci cluster (not nightly)
2. oc version

Actual results:
Cluster version
Client Version: 4.9.15
Server Version: 4.10.0-0.ci.test-2022-01-19-160615-ci-op-03yxzv53-latest
Kubernetes Version: v1.22.1-4609+60f5a1c6c03d74-dirty

Expected results:
something more like what's in the nightly:
# oc version
Client Version: 4.10.0-0.nightly-2022-01-18-044014
Server Version: 4.10.0-0.nightly-2022-01-18-044014
Kubernetes Version: v1.23.0+60f5a1c


Additional info:
slack thread
https://coreos.slack.com/archives/C01CQA76KMX/p1642615280354600

--- Additional comment from ravig on 2022-02-23 18:53:26 UTC ---

A workaround to push the tags is in place for now. We are continuing on debugging where the changes need to be made in the release tooling.

https://github.com/openshift/kubernetes/pull/1193/

The goal of this bug is to make sure CI builds should have correct version of Kube without needing to push tags everytime,
Comment 1 Maciej Szulik 2022-03-04 16:03:51 UTC 
This was done in https://github.com/openshift/kubernetes/pull/1193/
Comment 3 jmekkatt 2022-03-18 07:05:59 UTC 
Created a OCP 4.11 cluster from latest CI build.

$ oc get clusterversion
NAME      VERSION                         AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.11.0-0.ci-2022-03-18-004112   True        False         16m     Cluster version is 4.11.0-0.ci-2022-03-18-004112

$ oc version
Client Version: 4.9.6
Server Version: 4.11.0-0.ci-2022-03-18-004112
Kubernetes Version: v1.23.3-2019+02aefbfd4f05e3-dirty

The kubernetes version updated with 1.23.3 as expected . Hence moved the ticket to verified.
Comment 6 errata-xmlrpc 2022-08-10 10:51:15 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 (Important: OpenShift Container Platform 4.11.0 bug fix and security 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/RHSA-2022:5069
Note You need to log in before you can comment on or make changes to this bug.