Bug 1853371

Summary:	Official builds of VPA Operator are failing due to too-strict version check in Makefile
Product:	OpenShift Container Platform	Reporter:	OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component:	Node	Assignee:	Joel Smith <joelsmith>
Status:	CLOSED ERRATA	QA Contact:	Weinan Liu <weinliu>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	4.5	CC:	aos-bugs, jokerman
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:44:51 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1853072
Bug Blocks:

Description OpenShift BugZilla Robot 2020-07-02 14:07:32 UTC

+++ This bug was initially created as a clone of Bug #1853072 +++

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 1 Weinan Liu 2020-07-06 06:04:24 UTC

https://github.com/openshift/vertical-pod-autoscaler-operator/pull/31 is merged, it's ready for test now.

Comment 4 errata-xmlrpc 2020-07-13 17:44:51 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