Skip to content
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

CentOS 7 Fail due cookbook ruby_rbenv #18

Open
Pierozi opened this issue Jul 25, 2017 · 4 comments
Open

CentOS 7 Fail due cookbook ruby_rbenv #18

Pierozi opened this issue Jul 25, 2017 · 4 comments
Assignees
Labels
Milestone

Comments

@Pierozi
Copy link
Contributor

Pierozi commented Jul 25, 2017

Yesterday, 24 July 2017, the cookbook ruby_rbenv has been updated to a new major version.
This provoques a BC Break in the manual installation process. You may have this error :

Chef::Exceptions::RecipeNotFound
--------------------------------
could not find recipe system for cookbook ruby_rbenv

  4:    include_recipe 'build-essential'
  5>>   include_recipe 'ruby_rbenv::system'
  6:    include_recipe 'ruby_build'

You can easily bypass it by freezing the version in your metadata.rb file
depends 'ruby_rbenv', '= 1.2.1'

Please let me know if you are impacted by this bug (this will motivate me to update it 😄).
Feel free to submit a PR if you want to make this cookbook compatible with version 2.

Thanks.

@Pierozi Pierozi added the bug label Jul 25, 2017
@Pierozi Pierozi self-assigned this Jul 25, 2017
@jarrettj
Copy link

jarrettj commented Aug 1, 2017

👍

@jarrettj
Copy link

jarrettj commented Aug 4, 2017

Hi,

I've added:

depends 'ruby_rbenv', '= 1.2.1'
depends "aws-codedeploy-agent"

to my metadata.rb but it fails with:

==> chef-legal: Missing Cookbooks:
==> chef-legal: ------------------
==> chef-legal: Could not satisfy version constraints for: ruby_rbenv
==> chef-legal: Expanded Run List:
==> chef-legal: ------------------
==> chef-legal: System Info:
==> chef-legal: ------------
==> chef-legal: chef_version=13.2.20
==> chef-legal: platform=ubuntu
==> chef-legal: platform_version=16.04
==> chef-legal: ruby=ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-linux]
==> chef-legal: program_name=chef-solo worker: ppid=4054;start=13:04:38;
==> chef-legal: executable=/opt/chef/bin/chef-solo

Any help would be much appreciated.

Thanks.

@Pierozi
Copy link
Contributor Author

Pierozi commented Aug 4, 2017

Hi @jarrettj

Maybe you can try to remove the Berksfile.lock and execute berks install again.
If still not working, can you share me your version with next commands:

➜  #~ $ chef -v
Chef Development Kit Version: 1.5.0
chef-client version: 13.2.20
delivery version: master (17c1b0fed9be4c70f69091a6d21a4cbf0df60a23)
berks version: 5.6.4 
kitchen version: 1.16.0
inspec version: 1.31.1

➜  #~ $ berks -v
5.6.4

➜  #~ $ which berks
/usr/bin/berks

➜  #~ $ which gem
/home/pierozi/.rbenv/shims/gem

➜  #~ $ cat Gemfile
# frozen_string_literal: true

source 'https://rubygems.org'

gem 'berkshelf'
gem 'kitchen-docker'
gem 'kitchen-dokken'
gem 'kitchen-ec2'
gem 'kitchen-vagrant'
gem 'serverspec'
gem 'test-kitchen'
gem 'kitchen-inspec'

@Pierozi Pierozi added this to the v1.0.0 milestone Aug 4, 2017
@jarrettj
Copy link

jarrettj commented Aug 5, 2017

Hi,

Thanks for the quick response.

I had a look at the ruby_rbenv folder and the CHANGELOG, and for some reason the cookbook did not update. To solve it I did a 'knife cookbook site install ruby_rbenv 1.2.1'. All working now. Thanks.

Regards.
JJ

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants