Bug 1853371 - 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.5.0
Assignee: Joel Smith
QA Contact: Weinan Liu
URL:
Whiteboard:
Depends On: 1853072
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-02 14:07 UTC by OpenShift BugZilla Robot
Modified: 2020-07-13 17:45 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:44:51 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 31 0 None closed [release-4.5] Bug 1853371: Update version check for .p? suffix 2020-09-29 09:03:15 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:45:10 UTC

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


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