mysql gem not available within chef run on centos after running mysql::client recipe on node

Details

  • Type: Sub-task Sub-task
  • Status: Closed Closed
  • Priority: Unknown Unknown
  • Resolution: Fixed
  • Component/s: mysql
  • Labels:
    None

Description

The MySQL gem required for resource/provider operations is not installed to the node via the current mysql::client recipe. A case around platform instructs centos nodes to install the 'ruby-mysql' package instead of running the gem_package 'mysql' resource.

The ruby-mysql package makes the assumption that your system ruby is installed by yum packages. It would be great if we could generalize this recipe instead to just be safe and install the mysql gem.

[Wed, 01 Feb 2012 21:13:41 +0100] INFO: Processing mysql_database[merlin_production] action create (merlin::database_server line 25)
[Wed, 01 Feb 2012 21:13:41 +0100] ERROR: Running exception handlers
[Wed, 01 Feb 2012 21:13:41 +0100] ERROR: Exception handlers complete
[Wed, 01 Feb 2012 21:13:41 +0100] FATAL: Stacktrace dumped to /tmp/vagrant-chef-1/chef-stacktrace.out
[Wed, 01 Feb 2012 21:13:41 +0100] FATAL: LoadError: no such file to load – mysql

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Jamie Winsor added a comment -

https://github.com/opscode/cookbooks/pull/326

Show
Jamie Winsor added a comment - https://github.com/opscode/cookbooks/pull/326
Hide
Permalink
jtimberman added a comment -

We had some discussion around the proper approach to use here, and the general intention is that the ruby bindings should be available to Chef in the most sane way possible. This particular recipe is part of what prompted this ticket:

That said, we don't know who is using or relying on the mysql recipe as it stands now, so we're reluctant to change this particular behavior, since the current installation instructions indicate a Ruby installation that will result in things working "as expected". We will switch the recipe to use chef_gem once Chef 0.10.10 is released, however.

Based on that, I'm going to leave this in resolved status for now so we can revisit it when Chef 0.10.10 is out and chef_gem is available.

Thanks!

Show
jtimberman added a comment - We had some discussion around the proper approach to use here, and the general intention is that the ruby bindings should be available to Chef in the most sane way possible. This particular recipe is part of what prompted this ticket: CHEF-2879 That said, we don't know who is using or relying on the mysql recipe as it stands now, so we're reluctant to change this particular behavior, since the current installation instructions indicate a Ruby installation that will result in things working "as expected". We will switch the recipe to use chef_gem once Chef 0.10.10 is released, however. Based on that, I'm going to leave this in resolved status for now so we can revisit it when Chef 0.10.10 is out and chef_gem is available. Thanks!
Hide
Permalink
jtimberman added a comment -

Based on the above, and comment on the triage email in the mailing list, I'm reopening this, as its not 100% what the resolution might be following principle of least surprise.

Show
jtimberman added a comment - Based on the above, and comment on the triage email in the mailing list, I'm reopening this, as its not 100% what the resolution might be following principle of least surprise.
Hide
Permalink
Jamie Winsor added a comment -

This pull request has been moved to the opscode-cookbooks/mysql repo

https://github.com/opscode-cookbooks/mysql/pull/1

Show
Jamie Winsor added a comment - This pull request has been moved to the opscode-cookbooks/mysql repo https://github.com/opscode-cookbooks/mysql/pull/1
Hide
Permalink
Jamie Winsor added a comment -

this pull request has been updated with the chef_gem resource/provider to install mysql gem that way

Show
Jamie Winsor added a comment - this pull request has been updated with the chef_gem resource/provider to install mysql gem that way
Hide
Permalink
Matt Ray added a comment -

COOK-1384 is a similar issue and fix, but both tickets probably need COOK-1296 resolved

Show
Matt Ray added a comment - COOK-1384 is a similar issue and fix, but both tickets probably need COOK-1296 resolved
Hide
Permalink
Jesse Howarth added a comment -

The following pull request addresses this ticket: https://github.com/opscode-cookbooks/mysql/pull/28

Show
Jesse Howarth added a comment - The following pull request addresses this ticket: https://github.com/opscode-cookbooks/mysql/pull/28
Hide
Permalink
jtimberman added a comment -

Pull request #28 is merged. Thanks Jesse, Jamie!

https://github.com/opscode-cookbooks/mysql/commit/9c0a347111337e423b26376aefd9399970ce0f77

Show
jtimberman added a comment - Pull request #28 is merged. Thanks Jesse, Jamie! https://github.com/opscode-cookbooks/mysql/commit/9c0a347111337e423b26376aefd9399970ce0f77
Hide
Permalink
jtimberman added a comment -

This is released in version 1.3.0 of the mysql cookbook.

Show
jtimberman added a comment - This is released in version 1.3.0 of the mysql cookbook.
Hide
Permalink
Abel Lopez added a comment -

Got this same LoadError: no such file to load – mysql using 1.3.0 mysql cookbook on Ubuntu 12.04

Show
Abel Lopez added a comment - Got this same LoadError: no such file to load – mysql using 1.3.0 mysql cookbook on Ubuntu 12.04
Hide
Permalink
jtimberman added a comment -

Abel, did you use the mysql::ruby recipe?

Show
jtimberman added a comment - Abel, did you use the mysql::ruby recipe?

People

  • Assignee:
    jtimberman
    Reporter:
    Jamie Winsor
Vote (2)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: