Update chef & ohai pins and set log level #1173
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We've been unexpectedly using a new version of chef-client and ohai for a while since it was being pulled in via the
bundle install
in the knife-ec-backup software definition. This pins us to that version (and another change as been submitted to knife-ec-backup to add a Gemfile.lock to help avoid unexpected drift).This is rather ugly. We need to sort out ruby dependency management across these projects.
Finally, we've explicitly set
log_level :fatal
in our config to avoid spurious INFO level messages that we are now getting.