Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

config for ci launch_apb_on_bind = false seems to cause issues #858

Closed
maleck13 opened this issue Mar 27, 2018 · 1 comment
Closed

config for ci launch_apb_on_bind = false seems to cause issues #858

maleck13 opened this issue Mar 27, 2018 · 1 comment

Comments

@maleck13
Copy link
Contributor

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:


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.

@maleck13
Copy link
Contributor Author

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?

@maleck13 maleck13 closed this as completed Apr 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant