diff options
author | OpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com> | 2017-10-24 16:47:47 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2017-10-24 16:47:47 -0700 |
commit | 0cccbc04aee808280eb6e5baf0f87494ffee97ce (patch) | |
tree | 94ecdd01b256e9ffd90ff668cd332a1dcee2864e /roles/openshift_builddefaults | |
parent | abb5b1c5b899a121b8d2990b33880c93cd46ac88 (diff) | |
parent | bb5a5bc3e2566a3b1d9b92932c96e59631a4e3cc (diff) | |
download | openshift-0cccbc04aee808280eb6e5baf0f87494ffee97ce.tar.gz openshift-0cccbc04aee808280eb6e5baf0f87494ffee97ce.tar.bz2 openshift-0cccbc04aee808280eb6e5baf0f87494ffee97ce.tar.xz openshift-0cccbc04aee808280eb6e5baf0f87494ffee97ce.zip |
Merge pull request #5806 from staebler/service_catalog_uninstall_issues
Automatic merge from submit-queue.
Fix a few small issues in service catalog uninstall
* Service catalog install was not re-creating the apiserver.crt and apiserver.key files when generating certs. But the ca.crt and ca.key files were being re-created. This was causing non-verifiable certs to be used when service catalog was uninstalled and re-installed. The service catalog installer was changed to delete the apiserver.crt and apiserver.key files so that they are re-created using the new ca.crt and ca.key files.
* The asb auth token secret was not being deleted correctly and causing the uninstaller to fail.
* The asb uninstaller was attempting to delete the broker registration from the service catalog. However, the service catalog is uninstalled first. When the asb uninstaller would fail when attempting to delete the ClusterServiceBroker. The uninstaller was changed to verify that the servicecatalog APIService exists first before attempting to delete the ClusterServiceBroker.
* The service catalog uninstaller was attempting to delete policybindings. The server does not have a resource type name policybinding. I do not know what the intention is there, but I have commented out that part of the uninstaller.
Diffstat (limited to 'roles/openshift_builddefaults')
0 files changed, 0 insertions, 0 deletions