agents were pointing to old blobstore, updating it fixed the isseue. However I believe bosh upload release/stemcell --fix should've fix it.

UPDATE----- ________________________________ When I ran the bosh-blobstore-s3 command from director for the same objectId, I was able to download the object.

Hi, I've switched my bosh director blobstore from one s3 endpoint to another s3 endpoint. However now when I doing deploy of a cf-relase is says : stderr: '2017/07/07 13:31:28 performing operation

Hi Nitin, I wonder if you could be hitting the following issue: https://www.pivotaltracker.com/n/projects/956238/stories/143700951 This was fixed in

Thanks! For reply Tushar. Later I realized that the working blobstore was of CF, when I tried BOSH blobstore from aws CLI, it also failed, and problem is with my blobstore.

Can you share your manifest without the credentials ? Also, did you upload release yml or release tarball ? wrote:

Hi, I am trying to upgrade my cf to v251, when I ran bosh deploy, it gave error during build pack upload to blobstore after compilation: caused by: SignatureDoesNotMatch: The request signature we

Thanks!

Hi Nitin, For the bosh director itself, you can't download its own manifest. You need save it in something like git. As Brandon pointed out, you need to have a copy of your bosh-state.json from your

there is `bosh envs` command to list what environments were aliased ( http://bosh.io/docs/cli-v2.html#env-mgmt). wrote:

You are exactly right not using the –e did the trick and has gotten me to the next issue – thanks for your help. What command should I use to find out what I should be using for the –e

After running `export BOSH_ENVIRONMENT=$(bbl director-address)` there is no need to specify -e on subsequent commands. My guess is that whatever `bbl director-address` returns is different from what

I’m new to bosh, and trying to get an AWS Cloud Foundry set up going. I’m trying to get step 2 working from the “cf-deployment” docs here:

I haven't seen any documentation on the actual upgrade process. What I have always done is just update the bosh manifest with the newest information and done a re-deploy like you would if you were

Hi, How can I upgrade my bosh director to a new version, can you point me some documentation if any? Also is there any way to download bosh director manifest, like we can download deployment

Hi, I want to upgrade my bosh directory, is there any documentation for that? Also I can dowload deployment manifests of deployments managed by bosh director, similarly if I want to download bosh

Hi Alex, Thank you very much for your quick response! Let me explain things in detail. My attempt to is to implement a sample service broker and see how services work on CloudFoundry (CF). The end

BOSH, prior to v258, reported a stemcell-style version number. If you remove the first and last piece of the version and prefix it with "stable-", you can generally cross-reference it with the git

I have read online docs for bosh and followed steps to install bosh and director. Once succeed with these steps I deployed zookeeper as per online example. It seems it created 5 instances. But where

Hi Imesh, The tile is designed to be installed on PCF OpsManager [1] not BOSH directly. This gives enterprises a quick and easy way to deploy your software without having to know about BOSH. If you