Yeah, just as it is possible to create users in UAA, it is also possible to delete them there, thus orphaning the user accounts in the Cloud Controller. The orphaned users won't cause any problems in

If you can't get the list to accept the attachment, you can give it to Dies and he should be able to get it to us. Joseph OSS Release Integration Team wrote:

The users reported by CloudController.total_users are the users the Cloud Controller has in its database. This is normally the same set of users that exist in UAA. However, there is nothing that preve

It's not something we've ever seen before. In theory, the warden container needs the git binary, which I think it gets from the cflinuxfs2 stack; and internet access to wherever the git repo lives. If

Looking at the logs, we can see it finishing downloading the app package. The next step should be to download and run the buildpack. Since you mention there is no output after this, I'm guessing it do

Couple of updates here for clarity. No databases are stored on NFS in any default installation. NFS is only used to store blobstore data. If you are using the postgres job from cf-release, since it is

That's not an error we normally get. It's not clear if the staging_info.yml error is the source of the problem or an artifact of it. Having more logs would allow us to speculate more. Joseph & Dan OSS

Hmm, do you know what version of bosh-lite you are using? And could you also provide us with the output of `bosh status`? Joseph & Dan OSS Release Integration Team

I think that the DEA will reap any warden containers it finds every 30 seconds. The containers in a grace period are containers it is still keeping track of. We're not sure about the error you're gett

The DEA will receive a request to stop instance. The DEA calls into warden telling it to stop the container. Warden will send a TERM signal once a second for 10 seconds, at which point it will send a

Hi Kyle, I'm not sure what mean by "running it locally". Can you explain in more detail how you've deployed your CF installation? Zak + Dan

Hey Kyle, Can we take a look at your deployment manifest (with all the secrets redacted)? Zak + Dan, CF OSS Integration team

MRI Ruby is not able to execute threads in parallel. There is a "Global Interpreter Lock" that prevents Ruby code in multiple threads from executing at the same time. Threads can still do IO operation

A token should be valid for any number of requests until the expiration time is reached. In your code example, is the "result" passed to your second call to "getApps" the result from the login attempt

Hi Lakshman, We are wondering why you would like to add routes to the gorouter? Unfortunately there is not any way to add these untill the routing api becomes part of the official release. The NATS wo

Unfortunately those properties don't actually do what they say. A story has been added to the CAPI backlog to clean those up, and possibly change them: https://www.pivotaltracker.com/story/show/102523

Are you able to deploy the jar yourself using "cf push" if you build the jar yourself? Are you having trouble pushing the jar, or having trouble figuring out how to do that same thing in travis? Josep

Hi, We think this message was dropped and so we are posting it again. How long of a timeout are you seeing? The gorouter and ha_proxy have a default timeout of 15 minutes. If you are using an ELB or s

Hi R M, We think that this message may have been lost so we are resending it. Are you able to deploy other applications? This error seems to stem from mounted disk problems. Could you see if the disks

Hi Owais, We think this message may have been lost so we are sending it again. We compiled one back in December, I can't think of anything that would have changed since then. https://docs.google.com/d