Bug 1889915 - registry.redhat.io/openshift4/ose-operator-registry:v4.5.0 appears to track latest 4.5.z
Summary: registry.redhat.io/openshift4/ose-operator-registry:v4.5.0 appears to track l...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Release
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Luke Meyer
QA Contact: Wei Sun
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-20 22:07 UTC by Ben Luddy
Modified: 2020-10-21 12:40 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-21 12:40:33 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Ben Luddy 2020-10-20 22:07:39 UTC 
registry.redhat.io/openshift4/ose-operator-registry:v4.5.0 and registry.redhat.io/openshift4/ose-operator-registry:v4.5 both point to the same image digest. I expected v4.5 to track the latest 4.5.z and v4.5.0 to be fixed, with one fixed tag per z-stream.

This appears to also be true of v4.4/v4.4.0. Earlier minor version tags match my expectation.
Comment 1 Luke Meyer 2020-10-21 12:40:33 UTC 
The component versions don't increment in 4.4+ like they did in previous releases (when they did, they weren't reliably accurate, which is why we stopped doing it). Just the release (made up of a timestamp) increases. If you want to pin to a component in a particular release, you have to include the release in the tag e.g. 4.5.1 was registry.redhat.io/openshift4/ose-operator-registry:v4.5.0-202007012112.p0
Note You need to log in before you can comment on or make changes to this bug.