Hi Adrian, Thanks so much, I'll give it a try Ricky Yunata Please consider the environment before printing this email

I also found this: root(a)fe34f4b9-37f1-4c6e-ba86-17f667ef4fa9:/var/vcap/sys/log# cat ./blobstore/internal_error.log 2016/04/02 02:26:00 [error] 404#0: *1953 access forbidden by rule, client: <bosh

Hi, I just deployed CF 233 using bosh-lite-v233.yml. After deployment, I tried create-buildpack and it failed: cf create-buildpack noop-buildpack ./buildpack_noop-buildpack_v01.zip 1 Creating

We have recently added a property 'routing_api.enabled' which indicates if the routing-api is also deployed. Gorouter has a property 'router.enable_routing_api' which would determine if gorouter

JT, Thanks for responding. This is a test runtime and small. I checked all orgs and spaces. No routes matching the app. Found the route information and the result: { "total_results": 0,

Tom, Are you sure the route isn't bound to another application in another org/space? When you do `cf routes` it only show routes for the current space. You can hit specific API endpoints though to

Hi Ricky, We deconstructed the certs you provided in your manifest and think that you may have missed a step when you generated your peer ssl cert. Your peer cert is missing the DNS wildcard entry

Hi Dies, Nick, I can confirm that a swift blobstore works with domains different than 'default'. Here is our configuration on an OpenStack Liberty fog_connection: &fog_connection provider:

cf 230, diego 0.1450.0, etcd 27, garden-linux 0.330.0 Default to diego true. Developer deployed a java application. Deleted the application: cf delete <app> No errors. The app still responds. The

Excellent. Thanks for your investigation on this. -Rich

Hi Nick, Can you try with a domain other than “default”? We initially found that with the BOSH CPI, Keystone V3 worked for the “default” domain, but not for any other domain. Note that the

Great, thanks Filip! Guillaume.

Hi all, The blobs in the S3 bucket appear to be back up and running. If you believe something is still missing please let us know and we will file a support ticket with AWS on your

Hi all, Several releases, including cf-release and diego-release, use an AWS account belonging to the Cloud Foundry Foundation to store final release blobs. This account was accidentally closed,

If the question can be paraphrased as "when colocating multiple job (templates) on a single VM, will they start in parallel or instead in some sort of order?" then the jobs will generally come online

yes, they are always returned. introducing an option sounds like a good idea for the systems that wish to turn it off, thanks for the

Thanks Filip for your answer. Wouldn't it make sense to progressively change this behavior, possibly controlled by a configuration option to give clients time to handle this incompatible

For option 2 would it not be simpler to have a single property such as cc.blacklisted_system_domain_routes that contains the desired list and have the CC deny route requests for those routes? I don't

The access token used to double down as an identity token before OpenID Connect was standardized, now that we have implemented id_token, we don't really need it. but removing it would cause an

Hi, I wonder the rationale for apparenty uaa-specific [0] user-related fields in the access token (username, email [1]) while they are now returned in a standard maneer in the openidconnect id