Description of problem: The kube-scheduler/kube-controller-manager operator still show use 1.19.2, but when check the operand pod logs could see the rebase has update with kubernetes version v1.21 Version-Release number of selected component (if applicable): [root@localhost ~]# oc version Client Version: 4.8.0-0.nightly-2021-04-08-200632 Server Version: 4.8.0-0.nightly-2021-04-08-214526 Kubernetes Version: v1.21.0-rc.0+6d27558 How reproducible: always Steps to Reproduce: 1) Check the kubernetes version from kube-scheduler operator by command: `oc describe po/openshift-kube-scheduler-operator-6cbd6bb5d4-t66db` 2) Check the operand pods for kube-scheduler by command : `oc logs -f po/openshift-kube-scheduler-ip-10-0-130-205.us-east-2.compute.internal` Actual results: 1) Show wrong version with kubernetes 1.19.2 for payload: [root@localhost ~]# oc describe po/openshift-kube-scheduler-operator-6cbd6bb5d4-t66db Name: openshift-kube-scheduler-operator-6cbd6bb5d4-t66db Namespace: openshift-kube-scheduler-operator … OPERATOR_IMAGE_VERSION: 4.8.0-0.nightly-2021-04-08-214526 OPERAND_IMAGE_VERSION: 1.19.2 POD_NAME: openshift-kube-scheduler-operator-6cbd6bb5d4-t66db (v1:metadata.name) 2) The operand pod show has rebase with kubernetes version to v1.21: [root@localhost ~]# oc logs -f po/openshift-kube-scheduler-ip-10-0-130-205.us-east-2.compute.internal Using deprecated annotation `kubectl.kubernetes.io/default-logs-container` in pod/openshift-kube-scheduler-ip-10-0-130-205.us-east-2.compute.internal. Please use `kubectl.kubernetes.io/default-container` instead ... I0409 04:23:40.185990 1 server.go:147] Starting Kubernetes Scheduler version v1.21.0-rc.0+6d27558 Expected results: 1) Should correct update with kubernetes version to v1.21 from kube-scheduler operator Additional info: Same issue for the kube-controller-manager operator
Jan check, what and where we're missing, if this is something that should be happening during k8s bump make sure to add that step in https://github.com/openshift/kubernetes/blob/master/REBASE.openshift.md
Checking 4.7.7: ``` $ oc describe pods openshift-kube-scheduler-operator-78cd65cbc-vgq85 | egrep "OPERATOR_IMAGE_VERSION|OPERAND_IMAGE_VERSION" OPERATOR_IMAGE_VERSION: 4.7.7 OPERAND_IMAGE_VERSION: 1.20.0-beta.2 ``` so in production the version gets properly injected. Checking 4.8.0-0.nightly-2021-04-18-203506: ``` $ oc describe pods openshift-kube-scheduler-operator-845c88cb4f-gfppl | egrep "OPERATOR_IMAGE_VERSION|OPERAND_IMAGE_VERSION" OPERATOR_IMAGE_VERSION: 4.8.0-0.nightly-2021-04-18-203506 OPERAND_IMAGE_VERSION: 1.21.0-rc.0 ``` ``` $ oc describe pods kube-controller-manager-operator-77465d46d9-z9q2x | egrep "OPERATOR_IMAGE_VERSION|OPERAND_IMAGE_VERSION" OPERATOR_IMAGE_VERSION: 4.8.0-0.nightly-2021-04-18-203506 OPERAND_IMAGE_VERSION: 1.21.0-rc.0 ```
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 (Moderate: OpenShift Container Platform 4.8.2 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-2021:2438