Bug 1915304 - Updating scheduling component builder & base images to be consistent with ART
Summary: Updating scheduling component builder & base images to be consistent with ART
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-scheduler
Version: 4.7
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 4.7.0
Assignee: Jan Chaloupka
QA Contact: RamaKasturi
URL:
Whiteboard:
Depends On:
Blocks: 1916347
TreeView+ depends on / blocked
 
Reported: 2021-01-12 12:19 UTC by Jan Chaloupka
Modified: 2021-02-24 15:52 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-24 15:52:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-capacity pull 45 0 None closed bug 1915304: Updating openshift-enterprise-cluster-capacity builder & base images to be consistent with ART 2021-02-09 13:07:44 UTC
Github openshift cluster-kube-controller-manager-operator pull 495 0 None closed bug 1915304: Updating ose-cluster-kube-controller-manager-operator builder & base images to be consistent with ART 2021-02-09 13:07:44 UTC
Github openshift cluster-kube-descheduler-operator pull 167 0 None closed bug 1915304: Updating ose-cluster-kube-descheduler-operator builder & base images to be consistent with ART 2021-02-09 13:07:44 UTC
Github openshift cluster-kube-scheduler-operator pull 321 0 None closed bug 1915304: Updating ose-cluster-kube-scheduler-operator builder & base images to be consistent with ART 2021-02-09 13:07:43 UTC
Github openshift cluster-openshift-controller-manager-operator pull 194 0 None closed bug 1915304: Updating ose-cluster-openshift-controller-manager-operator builder & base images to be consistent with ART 2021-02-09 13:07:43 UTC
Github openshift descheduler pull 50 0 None closed bug 1915304: Updating atomic-openshift-descheduler builder & base images to be consistent with ART 2021-02-09 13:07:45 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:52:28 UTC

Description Jan Chaloupka 2021-01-12 12:19:57 UTC
Updating atomic-openshift-descheduler builder & base images to be consistent with ART
Reconciling with https://github.com/openshift/ocp-build-data/tree/ce8ceaf63b458a778da06e96138bf50938597aab/images/atomic-openshift-descheduler.yml

Comment 4 RamaKasturi 2021-01-25 12:45:40 UTC
Verified in the payload below and i see that kube-scheduler-operator, kube-contoller-manager-operator, kube-descheduler-operator was updated to be consistent with ART.

[knarra@knarra ~]$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.7.0-0.nightly-2021-01-21-215614   True        False         5h49m   Cluster version is 4.7.0-0.nightly-2021-01-21-215614

For kube-scheduler-operator:
=================================
oc get deployment.apps/openshift-kube-scheduler-operator -o yaml -n openshift-kube-scheduler-operator, can see that OPERATOR_IMAGE_VERSION has the value below and that payload contains the fix.

env:
        - name: IMAGE
          value: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:4b1a9563b100e090d69474ee66a11c827ebe64885de8622417cd85c70fbe761a
        - name: OPERATOR_IMAGE
          value: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:b88c99cd72ce33a904aedbf8c6bf54d1190a4736f3a58ce53cb935c52ead5af2
        - name: OPERATOR_IMAGE_VERSION
          value: 4.7.0-0.nightly-2021-01-21-215614
        - name: OPERAND_IMAGE_VERSION
          value: 1.20.0-beta.2
        - name: POD_NAME
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: metadata.name

For kube-controller-manager-operator:
=====================================
oc get deployment.apps/kube-controller-manager-operator -o yaml -n openshift-kube-controller-manager-operator

        env:
        - name: IMAGE
          value: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:4b1a9563b100e090d69474ee66a11c827ebe64885de8622417cd85c70fbe761a
        - name: OPERATOR_IMAGE
          value: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:a6c481be9499c04958d6193ee105af828ca2dcf2785f787ab3a26629ecf9825e
        - name: CLUSTER_POLICY_CONTROLLER_IMAGE
          value: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:0cfdb7f806ba9d8ab99b930daa405ee7c11df88a82aa5a734d876498fc66bb44
        - name: TOOLS_IMAGE
          value: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:d60adf2022cf25aef75e4a792a7ad3d8c0cd315c43e433270522c6e267a4df52
        - name: OPERATOR_IMAGE_VERSION
          value: 4.7.0-0.nightly-2021-01-21-215614
        - name: OPERAND_IMAGE_VERSION
          value: 1.20.0-beta.2
        - name: POD_NAME
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: metadata.name
        image: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:a6c481be9499c04958d6193ee105af828ca2dcf2785f787ab3a26629ecf9825e
        imagePullPolicy: IfNotPresent
        name: kube-controller-manager-operator

For descheduler operator:
================================
can see that operator was built on 23rd jan, which means it already has the necessary fix.

[knarra@knarra ~]$ oc get csv -n openshift-kube-descheduler-operator
NAME                                                   DISPLAY                     VERSION                 REPLACES   PHASE
clusterkubedescheduleroperator.4.7.0-202101230053.p0   Kube Descheduler Operator   4.7.0-202101230053.p0              Succeeded

Also, running command below could see that OPERATOR_CONDITION_NAME has the value as clusterkubedescheduleroperator.4.7.0-202101230053.p0

For descheduler:
==========================
checked in brew and could see that it was built on Jan23rd & the same image has been included with the operator.

https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=1470860

image: registry.redhat.io/openshift4/ose-descheduler@sha256:a5ddfeaba10f24c233b1b00ff70155f0029806d59013f5522cbbf9bf0c4da841

Based on the above moving the bug to verified state.

P.S: As per dev suggestion left cluster-capacity operator

Comment 5 Jan Chaloupka 2021-01-25 12:54:10 UTC
Another operator found, sorry. Moving back to POST

Comment 7 RamaKasturi 2021-01-27 13:52:15 UTC
Verified all the operators/images which are listed in the bug here and i see that they are updated to be consistent with ART.

ose-cluster-kube-controller-manager-operator-container-v4.7.0-202101261648.p0 -> verified from build.log and i see that the commit is 49bfb16 which is the master HEAD.
ose-cluster-kube-descheduler-operator-container-v4.7.0-202101261648.p0 -> verified from build.log and i see that the commit is 692e760 which is the master HEAD. 
ose-cluster-kube-scheduler-operator-container-v4.7.0-202101261648.p0 -> verified from build.log and i see that the commit is be3e34b which is the master HEAD.
ose-cluster-openshift-controller-manager-operator-container-v4.7.0-202101261648.p0 -> verified from build.log and i see that the commit is 7d311b3 which is the master HEAD
atomic-openshift-descheduler-container-v4.7.0-202101261648.p0 -> verified from build.log and i see that the commit is df87082 which is the master HEAD

Checked in the same way for openshift-enterprise-cluster-capacity-container-v4.7.0-202101261648.p0 -> verified from build.log and i see that the commit is a028e23 which is the master HEAD

Based on the above moving bug to verified state.

Comment 10 errata-xmlrpc 2021-02-24 15:52:05 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement 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-2020:5633


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