Created
March 14, 2013 09:01
-
-
Save ranjib/5159935 to your computer and use it in GitHub Desktop.
berkshelf error
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[berkshefl] $ berks upload | |
Using apache2 (1.6.0) | |
Using java (1.10.0) | |
Using yum (2.1.0) | |
Using s3cmd (0.0.0) at path: 'site-cookbooks/s3cmd' | |
Using as_app (0.0.3) at path: 'site-cookbooks/as_app' | |
Using rabbitmq (0.0.0) at path: 'site-cookbooks/rabbitmq' | |
Using solr (0.0.0) at path: 'site-cookbooks/solr' | |
Using windows (1.8.4) | |
Using chef_handler (1.1.4) | |
Uploading apache2 (1.6.0) to: 'https://10.123.2.10' | |
1 | |
Ridley::SandboxUploader crashed! | |
Ridley::Errors::HTTPForbidden: <?xml version="1.0" encoding="UTF-8"?><Error><Code>SignatureDoesNotMatch</Code><Message>The request signature we calculated does not match the signature you provided. Check your key and signing method.</Message><StringToSignBytes></StringToSignBytes><RequestId>g2gCZAATYm9va3NoZWxmQDEyNy4wLjAuMWgDYgAABVNiAAPT/GIACxsJ</RequestId><HostId></HostId><SignatureProvided>am/s76Rm4jThJK9BNsEGezrV+C0=</SignatureProvided><StringToSign>PUT | |
KrZaMcBq0is= | |
application/x-binary | |
1363251771 | |
/bookshelf/organization-00000000000000000000000000000000/checksum-d27172f615417a58ecb0c6ea9d69a22b</StringToSign><AWSAccessKeyId>8f75676a726cf09818f6ab64cdbd14de80521eaf</AWSAccessKeyId></Error> | |
/home/ranjibd/.rbenv/versions/1.9.3-p327/lib/ruby/gems/1.9.1/gems/ridley-0.8.4/lib/ridley/middleware/chef_response.rb:25:in `on_complete' | |
/home/ranjibd/.rbenv/versions/1.9.3-p327/lib/ruby/gems/1.9.1/gems/faraday-0.8.6/lib/faraday/response.rb:9:in `block in call' | |
/home/ranjibd/.rbenv/versions/1.9.3-p327/lib/ruby/gems/1.9.1/gems/faraday-0.8.6/lib/faraday/response.rb:63:in `on_complete' | |
/home/ranjibd/.rbenv/versions/1.9.3-p327/lib/ruby/gems/1.9.1/gems/faraday-0.8.6/lib/faraday/response.rb:8:in `call' | |
/home/ranjibd/.rbenv/versions/1.9.3-p327/lib/ruby/gems/1.9.1/gems/faraday-0.8.6/lib/faraday/connection.rb:247:in `run_request' | |
/home/ranjibd/.rbenv/versions/1.9.3-p327/lib/ruby/gems/1.9.1/gems/faraday-0.8.6/lib/faraday/connection.rb:112:in `put' | |
/home/ranjibd/.rbenv/versions/1.9.3-p327/lib/ruby/gems/1.9.1/gems/ridley-0.8.4/lib/ridley/sandbox_uploader.rb:133:in `upload' | |
/home/ranjibd/.rbenv/versions/1.9.3-p327/lib/ruby/gems/1.9.1/gems/celluloid-0.12.4/lib/celluloid/calls.rb:23:in `public_send' | |
/home/ranjibd/.rbenv/versions/1.9.3-p327/lib/ruby/gems/1.9.1/gems/celluloid-0.12.4/lib/celluloid/calls.rb:23:in `dispatch' | |
/home/ranjibd/.rbenv/versions/1.9.3-p327/lib/ruby/gems/1.9.1/gems/celluloid-0.12.4/lib/celluloid/actor.rb:327:in `block in handle_message' | |
/home/ranjibd/.rbenv/versions/1.9.3-p327/lib/ruby/gems/1.9.1/gems/celluloid-0.12.4/lib/celluloid/tasks/task_fiber.rb:24:in `block in initialize' | |
Ridley::Errors::HTTPForbidden <?xml version="1.0" encoding="UTF-8"?><Error><Code>SignatureDoesNotMatch</Code><Message>The request signature we calculated does not match the signature you provided. Check your key and signing method.</Message><StringToSignBytes></StringToSignBytes><RequestId>g2gCZAATYm9va3NoZWxmQDEyNy4wLjAuMWgDYgAABVNiAAPT/GIACxsJ</RequestId><HostId></HostId><SignatureProvided>am/s76Rm4jThJK9BNsEGezrV+C0=</SignatureProvided><StringToSign>PUT | |
KrZaMcBq0is= | |
application/x-binary | |
1363251771 | |
/bookshelf/organization-00000000000000000000000000000000/checksum-d27172f615417a58ecb0c6ea9d69a22b</StringToSign><AWSAccessKeyId>8f75676a726cf09818f6ab64cdbd14de80521eaf</AWSAccessKeyId></Error> |
I'm seeing the same error as well today, any insight?
Solved this. It appears to be a bug in Ridley 0.8.4. Explicitly downgrading to 0.8.3 in my gemfile did the trick.
Added an issue to ridley on github here:
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm seeing pretty much the same error - do you have any insight as to the cause?
As far as I can tell, my config.json correctly specifies my key paths - but this is my first time experimenting with Berkshelf, so it could just be a n00b mistake...