-
Notifications
You must be signed in to change notification settings - Fork 67
Binding error: "Service broker error: Could not find an available leader" #130
Comments
We have created an issue in Pivotal Tracker to manage this: https://www.pivotaltracker.com/story/show/172751962 The labels on this github issue will be updated when the story is started. |
Please perform the following instead
CF Dev ships with |
Hi, I get the same error when binding or creating a service key. I've tried on Windows as well as on Linux, but get the same error. Is there a solution for this? |
With PCFDev I only got p.mysql. I did however also tried CFDev which has de p-mysql broker. This works fine, the only problem is it only has 10mb or 20mb plans, which is too small. |
@hfcotino @marcello-dev I think there's some confusion. The plans CF Dev aims to provide you with the same interaction experience that you would get with a full deployment, not the same performance or resource expectations. |
I have deployed a Spring Boot app and mysql on my PCFDEV instance running on Ubuntu.
This is the error I get when I try to bind mysql to the app:
Service broker error: Could not find an available leader from [https://10.144.0.8:8443]
The full list of commands from the start is:
The issue is on the last command which outputs:
The text was updated successfully, but these errors were encountered: