Bug 1853072 - Official builds of VPA Operator are failing due to too-strict version check in Makefile
Summary: Official builds of VPA Operator are failing due to too-strict version check i...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: 4.6.0
Assignee: Joel Smith
QA Contact: Weinan Liu
URL:
Whiteboard:
Depends On:
Blocks: 1853371
TreeView+ depends on / blocked
 
Reported: 2020-07-01 21:11 UTC by Joel Smith
Modified: 2020-10-27 16:12 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 16:11:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift vertical-pod-autoscaler-operator pull 30 0 None closed Bug 1853072: Update version check for .p? suffix 2020-10-05 12:30:00 UTC
Red Hat Product Errata RHBA-2020:4196 0 None None None 2020-10-27 16:12:05 UTC

Description Joel Smith 2020-07-01 21:11:12 UTC 
Description of problem:

The VPA Operator build contains a regex to validate the version used for the build. The regex doesn't support versions that contain a .p0 suffix, such as v4.5.0-202007011712.p0-dirty

http://post-office.corp.redhat.com/archives/aos-art-automation/2020-July/msg00045.html

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

v4.5.0-202007011712.p0-dirty

How reproducible:

100%

Steps to Reproduce:
Run a build via art-auto of VPA Operator

Actual results:
Build fails with:
Invalid version v4.5.0-202007011712.p0-dirty, cannot build

Expected results:
Build succeeds
Comment 8 errata-xmlrpc 2020-10-27 16:11:46 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 (OpenShift Container Platform 4.6 GA Images), 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:4196
Note You need to log in before you can comment on or make changes to this bug.