Closed edeati closed 5 years ago
Hey There It looks like this is the first issue you've filed against the chef-cookbooks project. I'm here to offer you a bit of extra help to make sure we can quickly get back to you. Make sure you've filled out all the fields in our issue template. Make sure you've provided us with the version of chef-client you're running, your operating system and the version of the cookbook. If you're not using the most up to date version of the cookbook then please make sure to update first. Lots of things change between versions even if you're issue isn't listed in the changelog. Finally please give us a detailed description of the issue you're having. The more we know about what you're trying to do, what actually happens, and how you can reproduce the problem, the better.
If you're looking for more immediate troubleshooting help make sure to check out #general on the Chef Community Slack. There's plenty of folks there willing to lend a helping hand. Thanks for the first issue. We hope we can get back to you soon with a solution.
Please close this bug. It was caused by wrong aws-partitions
dependency set on the release 3.71.0 of aws-sdk-core
so it's an aws-sdk-core issue.
aws-sdk-core 3.72.0
fixes this issue: https://github.com/aws/aws-sdk-ruby/blob/master/gems/aws-sdk-core/CHANGELOG.md
There is still an issue with wrong versions of aws-sdk-core
being used if you have an aws-sdk
dependency in your cookbooks.
Cookbook version
8.0.4
Chef-client version
12.13.37
Platform Details
Amazon Linux 2017.03
Scenario:
Trying to create an EBS volume
Steps to Reproduce:
Create a new instance in OpsWorks and use the following code in your custom cookbooks
Expected Result:
50G volume is created on the OpsWorks instance
Actual Result:
As of today 24/10/2019 and error is thrown in OpsWorks and volume is not created
Earlier in the run logs I see
Using aws-sdk-core 3.52.1
is resolved as dependency but the instance also has 3.71.0 and looks like that's being used during the run of the cookbooks.