|Summary:||deprovision the serviceinstance, the pod is not deleted when the bundle is deleted from registry|
|Product:||OpenShift Container Platform||Reporter:||Zihan Tang <zitang>|
|Component:||Service Broker||Assignee:||Jesus M. Rodriguez <jesusr>|
|Status:||CLOSED ERRATA||QA Contact:||Zihan Tang <zitang>|
|Version:||3.10.0||CC:||aos-bugs, chezhang, jiazha, jmatthew, zhsun|
|Fixed In Version:||Doc Type:||Bug Fix|
Cause: Broker's reconciliation feature would delete its image references before getting the updated information from the registry. Consequence: there would be a period of time before the records showed up in the broker's data store while other jobs were still running. Fix: the reconciliation feature was redesigned to do an in place update for items that have changed. For items that were removed from the registry, the broker will now delete only those that have not been already provisioned. It will also mark those items for deletion, which filters them out of the UI preventing future provisions of those items. Result: The broker is more robust in its reconciliation feature thereby making the provision and deprovision more resilient to registry changes.
|Last Closed:||2018-10-11 07:20:00 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Zihan Tang 2018-05-14 07:58:41 UTC
Comment 1 John Matthews 2018-05-24 19:22:53 UTC
Realigning to 3.11 as this issue requires a larger amount of work than we are comfortable with at end of 3.10. Likely fix will rework how we handle our reconcile logic.
Comment 2 Zihan Tang 2018-05-28 02:44:22 UTC
I tried this scenario in v3.9 the serviceinstance and pod can both be deleted succeed.
Comment 3 Zihan Tang 2018-08-09 07:29:56 UTC
this scenario is the same with bug 1583495, update the title.
Comment 4 Zihan Tang 2018-08-09 08:09:12 UTC
The related issue https://github.com/openshift/ansible-service-broker/issues/970 is closed and those changes should be in the latest broker release "openshift-enterprise-asb-container-v3.11.0-0.10.0.1" Checking it's fixed asb: 1.3.7 Verify step： 1. provision mariadb-apb 2. edit broker-config registy tag to an invaild tag to simulate asb lose connection to this registry, restart asb pod. 3. check bundles and clusterserviceclass: # oc get bundles -o=custom-columns=NAME:.metadata.name,FQ\ NAME:.spec.fq_name,Delete:.spec.delete NAME FQ NAME Delete 0300d1ae1841c23a9df0a179ad0605fd brew-mariadb-apb true 0e5dbb6592fec99057f94fbb095ec558 brew-mediawiki-apb true 48749329dd289591e11ba737f15fc71b brew-postgresql-apb true bd8dff760b959264f3ab38d42ba5e7a8 brew-mysql-apb true # oc get clusterserviceclass -o=custom-columns=NAME:.metadata.name,EXTERNAL\ NAME:.spec.externalName,REMOVED:.status.removedFromBrokerCatalog NAME EXTERNAL NAME REMOVED 0300d1ae1841c23a9df0a179ad0605fd brew-mariadb-apb false 0e5dbb6592fec99057f94fbb095ec558 brew-mediawiki-apb false 48749329dd289591e11ba737f15fc71b brew-postgresql-apb false bd8dff760b959264f3ab38d42ba5e7a8 brew-mysql-apb false 3. delete serviceinstance , check the pod , pod is deleted.
Comment 6 errata-xmlrpc 2018-10-11 07:20:00 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-2018:2652