Bug 1803231

Summary: Vertical Pod Autoscaler (VPA) not available in 4.5
Product: OpenShift Container Platform Reporter: Joel Smith <joelsmith>
Component: NodeAssignee: Joel Smith <joelsmith>
Status: CLOSED ERRATA QA Contact: Weinan Liu <weinliu>
Severity: high Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: aos-bugs, jokerman, mpatel, nagrawal, rphillips, skordas, weinliu
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:15:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
vpa fail none

Description Joel Smith 2020-02-14 18:30:29 UTC 
Description of problem:

The VPA should be installable via OLM in OCP 4.5

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

4.5

How reproducible:

100%

Steps to Reproduce:
1. Go to web console
2. Search for Vertical Pod Autoscaler in list of available operators

Actual results:

Not found

Expected results:

Found

Additional info:

This bug is needed so that https://github.com/openshift/vertical-pod-autoscaler-operator/pull/9 can be merged.
Comment 3 Weinan Liu 2020-05-20 08:55:39 UTC 
Created attachment 1690099 [details]
vpa fail
Comment 4 Weinan Liu 2020-05-20 08:56:16 UTC 
$ oc version
Client Version: 4.4.0-rc.10
Server Version: 4.5.0-0.nightly-2020-05-19-041951
Kubernetes Version: v1.18.2

Not fixed on version above.

Without creating ns for vpa manually, vpa can not get shown on operatorhub
Comment 6 Weinan Liu 2020-05-22 03:14:12 UTC 
No fixed on 
$ oc version
Client Version: 4.4.0-rc.10
Server Version: 4.5.0-0.nightly-2020-05-21-135919
Kubernetes Version: v1.18.2

@Joel,

Did I get it right?

Search for Vertical Pod Autoscaler in list of available operators will work when this fixed, no manual steps for creating ns and cs, as the steps below:

https://github.com/joelsmith/vertical-pod-autoscaler-operator/#temporary-deployment-instructions
Comment 12 Weinan Liu 2020-05-29 07:24:58 UTC 
Not fixed 
$ oc version
Client Version: 4.4.0-rc.10
Server Version: 4.5.0-0.nightly-2020-05-29-005153
Kubernetes Version: v1.18.3+1bc7b9e

@Joel, any flag made it go to ON_QA status by Errata?
Comment 20 Weinan Liu 2020-06-01 06:04:50 UTC 
@Luke,
Still fails on 4.5.0-0.nightly-2020-05-30-025738
Comment 21 Joel Smith 2020-06-01 14:28:03 UTC 
The last fix I made appears not to have been included in the build it triggered. We're still working on the image build process and will hopefully get that sorted out very soon.
Comment 26 Weinan Liu 2020-06-05 06:46:55 UTC 
Failed on 4.5.0-0.nightly-2020-06-04-214605

Hi Joel, 

It's been failed test for four times, is it as expected?
Comment 29 Weinan Liu 2020-06-08 07:11:15 UTC 
Failed test on 4.5.0-0.nightly-2020-06-07-080121
Comment 37 errata-xmlrpc 2020-07-13 17:15:32 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