Date
1 - 4 of 4
Communication to blobs tore failing during bosh deploy
|
Koper, Dies <diesk@...>
Hi Nitin,
toggle quoted message
Show quoted text
I wonder if you could be hitting the following issue: https://www.pivotaltracker.com/n/projects/956238/stories/143700951 This was fixed in https://github.com/cloudfoundry/bosh-cli/releases/tag/v2.0.17. Regards, Dies Koper Cloud Foundry Product Manager - CLI -----Original Message-----
From: nitin padalia [mailto:padalia.nitin(a)gmail.com] Sent: Thursday, July 06, 2017 4:36 AM To: cf-bosh(a)lists.cloudfoundry.org Subject: [cf-bosh] Communication to blobs tore failing during bosh deploy 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 calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. For more information, see REST Authentication and SOAP Authentication for details. Later when I tried to deploy again, it is giving me: Failed to download S3 object, code 1, output: '', error: '2017/07/05 17:36:10 performing operation get: ServiceUnavailable: The server is temporarily unavailable. Please try again later I tried aws cli s3 ls and was able to list folders there using the credentials. What could be causing this? |
|
|
|
nitin padalia
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. |
|
|
|
Tushar Dadlani
Can you share your manifest without the credentials ? Also, did you upload
release yml or release tarball ? On Wed, Jul 5, 2017 at 11:36 AM nitin padalia <padalia.nitin(a)gmail.com> wrote:
|
|
|
|
nitin padalia
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 calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. For more information, see REST Authentication and SOAP Authentication for details. Later when I tried to deploy again, it is giving me: Failed to download S3 object, code 1, output: '', error: '2017/07/05 17:36:10 performing operation get: ServiceUnavailable: The server is temporarily unavailable. Please try again later I tried aws cli s3 ls and was able to list folders there using the credentials. What could be causing this? |
|
|