Bug 1889915
Summary: | registry.redhat.io/openshift4/ose-operator-registry:v4.5.0 appears to track latest 4.5.z | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Ben Luddy <bluddy> |
Component: | Release | Assignee: | Luke Meyer <lmeyer> |
Status: | CLOSED NOTABUG | QA Contact: | Wei Sun <wsun> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.5 | CC: | aos-bugs, jokerman, shurley |
Target Milestone: | --- | ||
Target Release: | --- | ||
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-10-21 12:40:33 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: |
Description
Ben Luddy
2020-10-20 22:07:39 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 |