v2 Services API: A service instance for the selected plan cannot be created in this organization

[Hector Castro]

Hi,

Apologies in advance if this is an obvious issue for those more familiar with deploying Cloud Foundry.

I'm working on a v2 Service Broker for Riak [0] and have run into the following CF error when I attempt to create an instance of the service:

```

$ cf create-service

1: riak , via

2: user-provided , via

What kind?> 1

Name?> riak-5fce8

1: bitcask: A bucket using the Bitcask backend.

2: leveldb: A bucket using the LevelDB backend.

Which plan?> 1

Creating service riak-5fce8... FAILED

CFoundry::APIError: 60010: A service instance for the selected plan cannot be created in this organization. The plan is visible because another organization you belong to has access to it.

```

It may be important to note that I'm not seeing a PUT request against the service broker before or after this error message. This leads me to believe that something is missing from my catalog or I need to open up access to this service from my organization somehow.

I've been working against the specifications in the v2 Service API Google Doc [1] and on the docs.cloudfoundry.com site [2].

--

Hector

[0] https://github.com/hectcastro/cf-riak-service-broker

[1] https://docs.google.com/document/d/1qXnEI0pfTs_nUq4w4iMr3RHknLYgFDTYvOe76hugg28/edit#

[2] http://docs.cloudfoundry.com/docs/running/architecture/services/writing-service-v2.html

[jde...@gopivotal.com]

I ran into the same thing and was advised as follows:

v2 service plans are created private by default. You need to make the plan public, or make it available to your org.
flip the bit in ccdb table service_plans or use cf curl:
cf curl POST /v2/service_plans/:guid -b '{"public":"true"}'
With the go cli, we don't make plans visible unless you can create them.

--Jens

[Hector Castro]

Just in case anyone else hits this issue, I was able to make the service plan public with `cf curl` using the following command:

$ cf curl PUT /v2/service_plans/:guid -b '{"public":true}'

Subtle notes:

- HTTP verb is PUT instead of POST

- Value for `public` is true instead of the string "true"

Thanks, Jens.

--

Hector

[James Bayer]

thanks for confirming what worked for you hector. we should get some instructions into the docs.

we currently have this page for v1: http://docs.cloudfoundry.com/docs/running/architecture/services/writing-service.html

i'll talk to david/shannon about incorporating this into the v2 doc: https://docs.google.com/a/gopivotal.com/document/d/1qXnEI0pfTs_nUq4w4iMr3RHknLYgFDTYvOe76hugg28/edit#heading=h.1ov8gjl5iza6

which will migrate to the docs when the Service Broker API v2  is completely finalized.

To unsubscribe from this group and stop receiving emails from it, send an email to vcap-dev+u...@cloudfoundry.org.

--

Thank you,

James Bayer

[Dr Nic Williams]

Thanks Hector for following up. Definitely going to help someone (read: me) one day soon.

Nic

[Shannon Coen]

I've been meaning to add a doc page for management of service ACLs. I'll prioritize that story. 

This will get easier when we get to the CLI stories for managing ACLs; you won't have to run curls to manage public/private and service_plan_visibilities. The pain I feel managing these controls every day with curl is a good forcing function. 

[azwi...@gopivotal.com]

When I attempt this work around I get an auth token error.  I'm not sure if this is complaining about auth to the service broker or the auth to CF.  Any guidance?

cf curl PUT /v2/service_plans/:3101b971-1044-4816-a7ac-9ded2e028079 -b '{"public":true}'

{

  "code": 1000,

  "description": "Invalid Auth Token",

  "error_code": "CF-InvalidAuthToken",

  "types": [

    "InvalidAuthToken",

    "Error"

  ],

[Shannon Coen]

This just means you need to log in again. IIRC, cf curl doesn't use a refresh token so if your access token has expired you need to log in to get another. Basically, when using cf curl you have to log in every 10m or so. When using other cf commands, you wouldn't have this problem.

Shannon Coen

Product Manager, Cloud Foundry

Pivotal, Inc.

mobile: 415.640.0272

skype: shannoncoen

[Shannon Coen]

Hello,

I've just added a bit of documentation for how to add your broker to cloud controller and make plans public. We've got a CLI command coming for controlling publicity, and better docs for catalog lifecycle management. In the meantime, hope this helps.

http://docs.cloudfoundry.com/docs/running/architecture/services/writing-service.html#create-broker

Best,

Shannon 

[Dr Nic Williams]

Thanks Shannon!

[张婕]

/v2/service_plans/:guid，how can I get the guid？

在 2013年11月16日星期六UTC+8上午7时24分27秒，Adam Zwickey写道：

[Wiz]

😄 I looked at it in ccdb

--------------------------------------------

May the Force be with you！

陈星宇 Wiz

--
You received this message because you are subscribed to the Google Groups "Cloud Foundry Developers" group.
To view this discussion on the web visit https://groups.google.com/a/cloudfoundry.org/d/msgid/vcap-dev/7d01fc94-678a-401b-9be0-26c8e5295286%40cloudfoundry.org.

[Shannon Coen]

'cf curl /v2/service_plans' will give you all plans and their guids. 

--
You received this message because you are subscribed to a topic in the Google Groups "Cloud Foundry Developers" group.