-
Notifications
You must be signed in to change notification settings - Fork 122
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
Removal of Old Gems Fails #121
Comments
If you can please test the changes to the cookbook in an environment with a private rubygems source that is not rubygems.org and without access to ruby gems.org. So far I'm running into long waits and timeouts. |
@MarkGibbons I can't as we don't have one right now. A colleague of mine removed the old gems manually and ran Chef again and it worked OK. It seems there is an issue running uninstall on the old gem as shown here:
I guess Chef can't hit |
sous-chefsGH-121 * Uses node['lvm']'['gemsource'] in the two chef_gem resources that remove gems but hang or fail when rubygems.org is not available. Signed-off-by: Beauregard, Josh <Josh.Beaureg@gmail.com>
adding source for the air gaped environment use case
thanks @tas50 whats the release date on this? |
Just pushed it up |
sweet as thanks! |
Cookbook version
4.0.4
Chef-client version
12.17.44
Platform Details
CentOS 7.2.1511 (Core)
Scenario:
Using any resource from this cookbook fails as the new Gems conflict with the old ones.
Steps to Reproduce:
Expected Result:
Old Gems should be removed, new Gems should be installed & Chef run continues without any changes to the system otherwise.
Actual Result:
Chef run fails. It claims the old Gems are removed but cannot install the new ones as the binaries conflict with the old ones:
The text was updated successfully, but these errors were encountered: