Comments (6)
It looks like Chef::Provider::Package::Rubygems
did not contain an AlternateGemEnvironment
class in version 0.8.x of Chef (this was introduced in the 0.9.x releases). So I guess in this current implementation, the 0.8.x versions of Chef wouldn't work with the rvm_gem
LWRP.
To make this clear in the meantime, I'll add this gotcha to the README.
Any idea if RightScale has plans to upgrade their Chef gem version? I'd guess a lot of cookbook code would be breaking for their customers.
from rvm.
Looking into it more, I don't think I'd be able to support the 0.8 release line and 0.9+ line in a sustainable way. Certainly if anyone has ideas or pull requests I'm more than happy to engage. I'd rather not limit anyone's ability to use this project and I know you're most likely constrained in your Chef version but it looks like Opscode even considers this version really old:
Open Source Chef users should upgrade their chef-server(s) and chef-clients to the newest version that provides the functionality and bug fixes they require. Another driver for upgrades would be availability of support resources from Opscode and the community. Release Notes has a listing of all of the current supportable versions of Chef. Versions older than 0.9.0 should be considered obsolete at this point.
(Source: Opscode Wiki: Troubleshooting and Techical FAQ)
If I'm off the mark, please re-open!
from rvm.
They do have Chef 9 now so I just need to move to those images. Great to know this will should work in 9. Your recipe is quite nice.
On Nov 26, 2011, at 10:31 AM, "Fletcher Nichol" [email protected] wrote:
It looks like
Chef::Provider::Package::Rubygems
did not contain anAlternateGemEnvironment
class in version 0.8.x of Chef (this was introduced in the 0.9.x releases). So I guess in this current implementation, the 0.8.x versions of Chef wouldn't work with thervm_gem
LWRP.To make this clear in the meantime, I'll add this gotcha to the README.
Any idea if RightScale has plans to upgrade their Chef gem version? I'd guess a lot of cookbook code would be breaking for their customers.
Reply to this email directly or view it on GitHub:
#50 (comment)
from rvm.
Hmm.... it looks that with chef 9 there are similar problems with the attribute definition. Do I have to assign the attributes differently in chef .9 than as it is done in chef .10?
Here is what I do:
node['rvm']['global_gems'] = [
{ 'name' => 'daemon_controller',
'version' => '0.2.6'
},
{ 'name' => 'fastthread',
'version' => '1.0.7'
},
{ 'name' => 'passenger',
'version' => '3.0.9'
},
{ 'name' => 'rake',
'version' => '0.9.2'
},
{ 'name' => 'rack',
'version' => '1.3.4'
},
]
Here is what the chef converge output is in RS:
00:45:04: Setting the run_list to ["rs_utils::default", "rs_utils::setup_timezone", "rs_utils::setup_server_tags", "rs_utils::setup_hostname", "rs_utils::setup_mail", "rs_utils::setup_ssh", "rs_utils::setup_logging", "rs_utils::setup_monitoring", "rvm::rpx_app_rvm"] from JSON
00:45:04: Starting Chef Run (Version 0.9.14.3)
*ERROR> Chef converge failed
*ERROR> An error occurred during the execution of Chef. The error message was:
undefined method `[]=' for nil:NilClass
The error occurred line 4 of [COOKBOOKS]//cba6517ca09f7e2acb30dbb9524f3684485ab58e/cookbooks/rvm/attributes/rpx_app_rvm.rb in method 'from_file' while executing:
2 # attribute: rpx_app_rvm
3
- node['rvm']['global_gems'] = [
5 { 'name' => 'daemon_controller',
6 'version' => '0.2.6'
*ERROR> Chef process failure
*ERROR> Chef process failed exited with 1
On Nov 26, 2011, at 11:01 AM, Fletcher Nichol wrote:
Looking into it more, I don't think I'd be able to support the 0.8 release line and 0.9+ line in a sustainable way. Certainly if anyone has ideas or pull requests I'm more than happy to engage. I'd rather not limit anyone's ability to use this project and I know you're most likely constrained in your Chef version but it looks like Opscode even considers this version really old:
Open Source Chef users should upgrade their chef-server(s) and chef-clients to the newest version that provides the functionality and bug fixes they require. Another driver for upgrades would be availability of support resources from Opscode and the community. Release Notes has a listing of all of the current supportable versions of Chef. Versions older than 0.9.0 should be considered obsolete at this point.
(Source: Opscode Wiki: Troubleshooting and Techical FAQ)
If I'm off the mark, please re-open!
Reply to this email directly or view it on GitHub:
#50 (comment)
from rvm.
I just realized that you also said .9 was out... misread your email.
Dang.
On Nov 26, 2011, at 11:01 AM, Fletcher Nichol wrote:
Looking into it more, I don't think I'd be able to support the 0.8 release line and 0.9+ line in a sustainable way. Certainly if anyone has ideas or pull requests I'm more than happy to engage. I'd rather not limit anyone's ability to use this project and I know you're most likely constrained in your Chef version but it looks like Opscode even considers this version really old:
Open Source Chef users should upgrade their chef-server(s) and chef-clients to the newest version that provides the functionality and bug fixes they require. Another driver for upgrades would be availability of support resources from Opscode and the community. Release Notes has a listing of all of the current supportable versions of Chef. Versions older than 0.9.0 should be considered obsolete at this point.
(Source: Opscode Wiki: Troubleshooting and Techical FAQ)
If I'm off the mark, please re-open!
Reply to this email directly or view it on GitHub:
#50 (comment)
from rvm.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
from rvm.
Related Issues (20)
- user::install only supports one user HOT 1
- Is this project dead? HOT 7
- Deprecated Features HOT 2
- cannot load such file -- chef/mixin/command HOT 6
- gem_package recipe breaks chef_gem HOT 1
- Chef 12.17.5: could not find filename for attribute .gitkeep in cookbook rvm HOT 1
- How do you use this with chef solo? HOT 1
- Use --no-document instead of --no-rdoc --no-ri HOT 5
- Compatibility with Ubuntu 18.04 HOT 4
- Dangerfile should use failure instead of fail
- Remove .rubocop.yml with Dangerfile
- Update Changelog
- Run latest cookstyle
- Update builds to be parallel
- Could not parse `-/metadata.rb': undefined method `chef_version' HOT 2
- Support Modern Operating systems and have working dokken
- Error: cannot load such file -- rvm HOT 7
- rvm Chef 17 compatibility
- No resource, method, or local variable named `create_rvm_shell_chef_wrapper' for `Chef::Recipe "default"' HOT 2
- Dependency Dashboard
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from rvm.