Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1794466

Summary:	OpenShift 4.2 release tag format changed in 4.2.14
Product:	OpenShift Container Platform	Reporter:	Matthew Robson <mrobson>
Component:	Documentation	Assignee:	Kathryn Alexander <kalexand>
Status:	CLOSED EOL	QA Contact:	Xiaoli Tian <xtian>
Severity:	high	Docs Contact:	Latha S <lmurthy>
Priority:	high
Version:	4.4	CC:	asadawar, dapark, kalexand, lmurthy, pkhaire, wking
Target Milestone:	---
Target Release:	4.4.0
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-09-08 20:26:40 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 Matthew Robson 2020-01-23 16:20:22 UTC

Document URL: 

Starting with 4.2.14, the release tag for OCP changed from 4.2.13 to 4.2.14-x86_64

For use cases like mirroring images in restricted network installs, this leads to customer concussion are it looks like the new release do not exist.

https://docs.openshift.com/container-platform/4.2/installing/install_config/installing-restricted-networks-preparations.html#installation-mirror-repository_installing-restricted-networks-preparations

oc adm release info quay.io/openshift-release-dev/ocp-release:4.2.13 -o json | jq -r '.digest' | awk -F: '{print $2}'
782b41750f3284f3c8ee2c1f8cb896896da074e362cf8a472846356d1617752d

oc adm release info quay.io/openshift-release-dev/ocp-release:4.2.16 -o json | jq -r '.digest' | awk -F: '{print $2}'
error: image does not exist

oc adm release info quay.io/openshift-release-dev/ocp-release:4.2.16-x86_64 -o json | jq -r '.digest' | awk -F: '{print $2}'
e5a6e348721c38a78d9299284fbb5c60fb340135a86b674b038500bf190ad514

Section Number and Name: 

Mirroring the OpenShift Container Platform image repository

Suggestions for improvement: 

We should link customers to the actual release stream tags and tell them to use the appropriate tag.

Ex: https://openshift-release.svc.ci.openshift.org/releasestream/4-stable/release/4.2.16

Additional information:

Comment 2 Kathryn Alexander 2020-01-24 16:05:34 UTC

Trevor opened a PR here: https://github.com/openshift/openshift-docs/pull/19266

Comment 4 W. Trevor King 2020-05-01 02:41:50 UTC

PR is blocked on someone figuring out [1].  Which I'll get to eventually if nobody else does, but so far it has not been near the top of my queue.

[1]: https://github.com/openshift/openshift-docs/pull/19266#discussion_r375878575

Comment 9 Kathryn Alexander 2022-09-08 20:26:40 UTC

The PR for this issue has been closed due to inactivity, 4.2 is EOL, and no additional information for newer versions has appeared. If additional information is available or additional work is still required, please open a Jira issue in this project: https://issues.redhat.com/projects/OCPBUGS