Skip to content
This repository has been archived by the owner on Jul 28, 2020. It is now read-only.

Binding error: "Service broker error: Could not find an available leader" #130

Closed
marcello-dev opened this issue May 9, 2020 · 6 comments

Comments

@marcello-dev
Copy link

marcello-dev commented May 9, 2020

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:

cf dev start -f pcfdev-v1.2.0-linux.tgz
cf login -a https://api.dev.cfdev.sh --skip-ssl-validation
cf push
cf dev deploy-service mysql
cf create-service p.mysql db-small  mysql-instance
cf bind-service demo-customer mysql-instance

The issue is on the last command which outputs:

Your CF API version (2.125.0) is no longer supported. Upgrade to a newer version of the API (minimum version 2.128.0). Please refer to https://github.com/cloudfoundry/cli/wiki/Versioning-Policy#cf-cli-minimum-supported-version
Binding service mysql-instance to app demo-customer in org cfdev-org / space cfdev-space as admin...
Service broker error: Could not find an available leader from [https://10.144.0.8:8443]
FAILED

@cf-gitbot
Copy link

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.

@marcello-dev marcello-dev changed the title Error binding mysql to application Binding error: Service broker error: Could not find an available leader May 9, 2020
@marcello-dev marcello-dev changed the title Binding error: Service broker error: Could not find an available leader Binding error: "Service broker error: Could not find an available leader" May 9, 2020
@aemengo
Copy link
Contributor

aemengo commented May 14, 2020

Please perform the following instead

cf create-service p-mysql 10mb mysql-instance 

CF Dev ships with p-mysql not p.mysql. Thus the workflow that you've posted above is not supported.

@hfcotino
Copy link

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?

@marcello-dev
Copy link
Author

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?

Have you tried the solution suggested by @aemengo ? I haven't tried it yet.

@hfcotino
Copy link

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?

Have you tried the solution suggested by @aemengo ? I haven't tried it yet.

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.

@aemengo
Copy link
Contributor

aemengo commented May 27, 2020

@hfcotino @marcello-dev I think there's some confusion. The plans 10mb and 20mb are effectively just labels to match what a real cf-mysql deployment would give you. However, unlike a real deployment, services are allocated all free space in the VM. And this goes for most of the services.

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants