Skip to content

As a user of chef-solo I would like to leverage the ebs_volume resource #360

@sigmatechnica

Description

@sigmatechnica

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]

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions