You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
Note
This is currently happening on my PR not sure if it is a wider issue #828
What happened:
Running the CI job it fails waiting for postgres to be deprovisoned. This looks to fail because are still bindings present:
172.17.0.5 - - [27/Mar/2018:08:29:22 +0000] "DELETE /ansible-service-broker/v2/service_instances/a8b175f5-37c5-4fd9-abd4-4fff930c1eb2?accepts_incomplete=true&plan_id=7f4a5e35e4af2beb70076e72fab0b7ff&service_id=1dda1477cace09730bd8ed7a6505607e HTTP/1.1" 400 3
--
[2018-03-27T08:29:23.43Z] [DEBUG] - Found bindings with ids: map[83291992-0ded-469a-ad94-c974aba7ad55:true]
I believe the issue here is the setting launch_apb_on_bind as this is false nothing is removing the binding reference.
My question: Is launch_apb_on_bind why do we want this to be false, is it a real scenario if so should we just remove the binding reference when this is set.
The text was updated successfully, but these errors were encountered:
Looking more into this I think I know what the problem is and it is in my code change. But wondering what the usecase for launch_apb_on_bind=false would be?
Bug:
Note
This is currently happening on my PR not sure if it is a wider issue
#828
What happened:
Running the CI job it fails waiting for postgres to be deprovisoned. This looks to fail because are still bindings present:
I believe the issue here is the setting
launch_apb_on_bindas this is false nothing is removing the binding reference.My question: Is
launch_apb_on_bindwhy do we want this to be false, is it a real scenario if so should we just remove the binding reference when this is set.The text was updated successfully, but these errors were encountered: