Add version property to uuidtools chef_gem stanza #15
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.
Add a version property to the uuidtools chef_gem stanza.
In using this cookbook across hundreds of nodes, which are coincidentally NAT'd behind the same public IPv4 address, we started to notice strange network behavior that caused chef-client runs to hang while processing the uuidtools stanza. Each node typically had two https connections stuck in an ESTABLISHED and/or CLOSE_WAIT state with data in recv-q. We quickly surmised that this was symptomatic of chef checking for an updated uuidtools gem, and some kludgey rate limiting over at the gem repo causing our clients to hang indefinitely. If you don't specify a gem version, upon each client run chef will attempt to retrieve the latest version info for that gem. By specifying a suitable gem version we take a step to use the gem repo responsibly.