Bug 1757918

Summary: [DOCS] CORS configuraiton documentation has changed in 4.2
Product: OpenShift Container Platform Reporter: Jason Montleon <jmontleo>
Component: Migration ToolingAssignee: John Matthews <jmatthew>
Status: CLOSED ERRATA QA Contact: Xin jiang <xjiang>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: apinnick
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 Jason Montleon 2019-10-02 17:54:48 UTC
https://github.com/fusor/mig-operator/pull/106 has some doc updates relevant to the Cluster Application Migration Tool.

- For 4.2 no special configuration should be needed
- For 4.1 deprecated_cors_configuration: true needs to be added to the MigrationController CR.

Comment 1 John Matthews 2019-10-02 18:28:08 UTC
QE, this BZ is mainly to ensure you have a chance to verify downstream docs and CORS configuration documentation matches the new approach for OCP 4.2

Reference to working docs here:

 http://file.tlv.redhat.com/~apinnick/ocp_3_4_migration/migration/migrating-openshift-3-to-4.html#configuring-cross-origin-resource-sharing

Comment 2 Xin jiang 2019-10-09 06:20:00 UTC
Verified.

Comment 3 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