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

Bug 1757222

Summary: [Docs] Document known issue of imagestreams in openshift namespace are not handled with migrations.
Product: OpenShift Container Platform Reporter: John Matthews <jmatthew>
Component: Migration ToolingAssignee: Avital Pinnick <apinnick>
Status: CLOSED ERRATA QA Contact: Xin jiang <xjiang>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: dymurray, sseago
Target Milestone: ---   
Target Release: 4.2.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: 2019-10-16 06:41:54 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 John Matthews 2019-09-30 21:04:56 UTC 
We want to ensure we have a documentation note that users may hit an issue if they migrate an application that relies on images in the openshift namespace.

Certain images like postgres for example are upgraded throughout OCP releases.  An older application running on OCP 3.7 may reference an older postgres version which is not installed in an OCP 4.2 cluster.

For 4.2.0 we will not be able to help a user with this problem, we want to document this as a known issue.

A user should:
 - Inspect their application to determine if they are using images from the openshift namespace.
 - If they are, check to see if the needed version is present on the destination cluster, if not they will want to recreate the ImageStream with needed version on destination cluster prior to performing the migration
Comment 3 Scott Seago 2019-10-07 17:59:50 UTC 
One comment on the doc wording. I think this section is somewhat vague: "If your applications use images from the openshift namespace, the required versions of the images must be present on the target cluster. If not, you must update the imagestreamtags." I'd suggest something like this instead: "If your applications use images from the openshift namespace, the required versions of the images must be present on the target cluster. If not, you must update the imagestreamtags references to use an available version, making sure that the updated version is compatible with your application."
Comment 4 Avital Pinnick 2019-10-10 06:48:28 UTC 
(In reply to Scott Seago from comment #3)
> One comment on the doc wording. I think this section is somewhat vague: "If
> your applications use images from the openshift namespace, the required
> versions of the images must be present on the target cluster. If not, you
> must update the imagestreamtags." I'd suggest something like this instead:
> "If your applications use images from the openshift namespace, the required
> versions of the images must be present on the target cluster. If not, you
> must update the imagestreamtags references to use an available version,
> making sure that the updated version is compatible with your application."

LGTM. I updated the second sentence: "If not, you must update the imagestreamtags references to use an available version that is compatible with your application."
Comment 6 Xin jiang 2019-10-11 05:26:39 UTC 
Reviewed. LGTM.
Comment 7 errata-xmlrpc 2019-10-16 06:41:54 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-2019:2922