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
Applications provisioned by APB's can still be managed.
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.
The doc LGTM, verified.
Commit pushed to master at https://github.com/openshift/openshift-docs
Merge pull request #9878 from adellape/apbknownissue
Bug 1586108: Add 3.10 APB known issue