-
-
Notifications
You must be signed in to change notification settings - Fork 553
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As a user of chef-solo
I would like to leverage the ebs_volume
resource
#360
Comments
Hey There 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. |
Hey thanks for reporting this but the limitation, after reading the code and this comment: https://github.com/chef-cookbooks/aws/blob/v8.0.3/resources/ebs_volume.rb#L39-L42 I am not sure we can support |
chef-solo
I would like to leverage the ebs_volume
resource
Cookbook version
7.5.0
Platform Details
ubuntu 16.04 on an ec2 node
Scenario:
attempting to attach an ebs volume
Steps to Reproduce:
attempt to attach an ebs volume with chef-solo on an ec2 instance
Expected Result:
volume attaches no errors in chef run
Actual Result:
volume attaches, then chef run terminates with
"I cannot read /etc/chef/client.pem, which you told me to use to sign requests!"
stack trace indicates:
cookbooks/aws/resources/ebs_volume.rb:95:in
block (2 levels) in class_from_file' cookbooks/aws/resources/ebs_volume.rb:89:in
block in class_from_file'looking in ebs_volume.rb line 95:
95 node.save # ~FC075
since there is no node.save in chef solo, and we exclusivly use chef solo, there is no client.pem configured and the chef run fails. Adding a guard fixes this, e.g:
node.save unless Chef::Config[:solo]
The text was updated successfully, but these errors were encountered: