Bug 1832150 - No v4.5 descheduler CSV bundles and Images
Summary: No v4.5 descheduler CSV bundles and Images
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-scheduler
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: 4.5.0
Assignee: Jan Chaloupka
QA Contact: RamaKasturi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-06 08:15 UTC by RamaKasturi
Modified: 2020-07-13 17:35 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:35:22 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:35:43 UTC

Description RamaKasturi 2020-05-06 08:15:11 UTC
This bug was initially created as a copy of Bug #1817592

I am copying this bug because: 

Problem is same for descheduler as well.

Description of problem:
No 4.5 upstream and downstream descheduler images.
so that is blocking QE testing and Bug fix.

QE had workaround to verified the bugs using internal image.  We expected the images can be built ASAP.

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

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Mike Dame 2020-05-13 15:27:34 UTC
Moving this to our team since we own the image, Jan's on it already. 

It looks like our operator image building was disabled in https://github.com/openshift/ocp-build-data/blame/openshift-4.5/images/ose-cluster-kube-descheduler-operator.yml#L1

Descheduler operand images appear to be building, was just the operator that got disabled.

Comment 2 Jan Chaloupka 2020-05-15 13:51:33 UTC
Building descheduler-operator image has been re-enabled.

Comment 3 Jan Chaloupka 2020-05-15 14:06:29 UTC
Also, with https://github.com/openshift/descheduler/pull/30 merged, new descheduler 4.5 image will be built.

Rama, please give it some time before all the images get built. If not on Monday, let's poke ART team to see what is missing.

Comment 6 RamaKasturi 2020-05-18 12:38:54 UTC
Could successfully install descheduler operator for 4.5, so moving the bug to verified state.

[ramakasturinarra@dhcp35-60 ocp_files]$ oc get csv
NAME                                                DISPLAY                     VERSION              REPLACES   PHASE
clusterkubedescheduleroperator.4.5.0-202005161517   Kube Descheduler Operator   4.5.0-202005161517              Succeeded
[ramakasturinarra@dhcp35-60 ocp_files]$ oc get sub
NAME                                PACKAGE                             SOURCE            CHANNEL
cluster-kube-descheduler-operator   cluster-kube-descheduler-operator   qe-app-registry   4.5

Images:
==========
quay.io/openshift-qe-optional-operators/ose-descheduler@sha256:bfc47632721cff57e97a9c19482d70475a91b91a4ac51c3b6bed79310e34a1ad
quay.io/openshift-qe-optional-operators/ose-cluster-kube-descheduler-operator@sha256:135298904521961ea1a2abafb890e62c3d9d0387dfb6ae9294cac194f1ab1676


But since both 4.4 & 4.5 had the same name i had to disable redhat-operators by editing the operatorhub and adding the following spec to install 4.5 descheduler operator from UI.

spec:
  disableAllDefaultSources: false
  sources:
  - disabled: true
    name: redhat-operators
  - disabled: false
    name: certified-operators

Comment 7 RamaKasturi 2020-05-18 13:08:06 UTC
Verified the bug in the payload below:
========================================
[ramakasturinarra@dhcp35-60 ocp_files]$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.5.0-0.nightly-2020-05-17-235851   True        False         108m    Cluster version is 4.5.0-0.nightly-2020-05-17-235851

Comment 8 errata-xmlrpc 2020-07-13 17:35:22 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, 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:2409


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