-
Notifications
You must be signed in to change notification settings - Fork 682
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
Unexpected failures with kitchen-inspec and inspec 1.0.0 #1187
Comments
@rhass Looks like the cookbook you reference here has gone through some significant changes over the last week; could you please update the replication case details? |
@vjeffrey The issues which I experienced were with the 1.x changes. I found the inspec bug while working on adding the inspec test framework to the cookbook to support the changes I was making. |
thanks; i'll look into it. a couple things: the links posted above that refer to the gemfile throw 404s. the correct link is :https://github.com/chef-cookbooks/rubygems/blob/master/Gemfile#L9 also,
^^^ using .kitchen.local.yml to override the driver and kitchen-vagrant gem in the gemfile got around it. |
Description
I have observed two misbehaviors when using the lastest version of Inspec (1.0.0 and
master
) viakitchen verify
.Failed to complete #verify action: [undefined method
join' for nil:NilClassDid you mean? JSON]` See Stacktrace below.
InSpec and Platform Version
github: 'chef/inspec', ref: '593bdbc282f66cec5fc5e5c8f397ce171d40e055'
Replication Case
1.Replace the version pinning here: https://github.com/chef-cookbooks/rubygems/blob/resource_driven/Gemfile#L9 with
>= 0.15.2
and add a version pin here https://github.com/chef-cookbooks/rubygems/blob/resource_driven/Gemfile#L7 with>= 1.0.0
.2. Run
bundle install
3. Run
bundle exec integration:kitchen:bundle-config-centos-72
orbundle exec integration:kitchen:all
Possible Solutions
The current method of mitigation (not solution) is to use the following pin:
gem "kitchen-inspec", "< 0.15.2", "~> 0.15"
Stacktrace
Please include the stacktrace output or link to a gist of it, if there is one.
The text was updated successfully, but these errors were encountered: