Bug 1586108

Summary: [Docs] After an upgrade from 3.9 to 3.10 applications provisioned with APB's cannot be managed
Product: OpenShift Container Platform Reporter: Jason Montleon <jmontleo>
Component: DocumentationAssignee: Alex Dellapenta <adellape>
Status: CLOSED CURRENTRELEASE QA Contact: Zihan Tang <zitang>
Severity: unspecified Docs Contact: Vikram Goyal <vigoyal>
Priority: unspecified    
Version: 3.10.0CC: aos-bugs, chezhang, jiazha, jmatthew, jokerman, mmccomas, xtian, zhsun, zitang
Target Milestone: ---   
Target Release: 3.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
Cause: During 3.10 work we added the ability for multiple instances of an APB to be invoked in same namespace, this required we rely on a GUID for each instance. Instances deployed by a 3.9 version of APB lack the GUID, 3.10 APBs require it. Consequence: With the lack of GUID a 3.10 APB is not able to manage a 3.9 deployed service, so upgrades run into issues if an application deployed with 3.9 is then deprovisioned from 3.10 APB there is an error. Workaround (if any): 2 choices exist: 1. Delete the namespace of the application and recreate after the 3.10 upgrade. This will use 3.10 version of APB and function as expected. 2. Modify the config of the Broker to stick with 3.9 version of APBs. This has the downside of after upgrade while Broker will be using 3.10 code, APBs will be using older 3.9 versions. This is not recommended. Result:
 Story Points: ---
Clone Of: Environment:
Last Closed: 2018-08-09 20:25:36 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 2018-06-05 14:03:27 UTC 
Description of problem:
After upgrading from v3.9 to v3.10 applications provisioned using a version 3.9 APB cannot be managed by a v3.10 APB

Expected results:
Applications provisioned by APB's can still be managed.

Additional info:
We need to document a couple of alternatives when this situation is encountered.

The first is that the user can delete the namespace in order to clean up the resources created by the old APB and then recreate their applications using the v3.10 APB's.

Alternatively they can:
1. Change the label on the broker-config configmap in the ansible-service-broker namespace to v3.9
2. Restart the asb pod in the ansible-service-broker namespace
3. Run 'apb bootstrap', which should bootstrap the broker, and relist the catalog. 

If this is done it will be possible to continue managing applications with the v3.9 APB's.

In the future we will work on developing the means to create applications with updated APB's while maintaining the ability to manage applications created with old APB's.
Comment 3 Alex Dellapenta 2018-06-06 17:53:05 UTC 
Docs PR:

https://github.com/openshift/openshift-docs/pull/9878

Preview:

http://file.rdu.redhat.com/~adellape/060618/apbknownissue/release_notes/ocp_3_10_release_notes.html#ocp-310-known-issues
Comment 4 Zihan Tang 2018-06-07 02:28:27 UTC 
The doc LGTM, verified.
Comment 5 openshift-github-bot 2018-06-07 14:40:49 UTC 
Commit pushed to master at https://github.com/openshift/openshift-docs

https://github.com/openshift/openshift-docs/commit/c910d42883a177c8334c1d23b10aa235777cdd77
Merge pull request #9878 from adellape/apbknownissue

Bug 1586108: Add 3.10 APB known issue
Comment 6 Alex Dellapenta 2018-08-09 20:25:36 UTC 
https://access.redhat.com/documentation/en-us/openshift_container_platform/3.10/html/release_notes/release-notes-ocp-3-10-release-notes#ocp-310-known-issues