Skip to content

Rhel centos support #35

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

Closed
wants to merge 7 commits into from

Conversation

justintime
Copy link

There's a few issues with running this module on RHEL/CentOS, this branch attempts to fix them.

The biggest problem is the location of the mysql socket location, but another is that RHEL/CentOS uses /etc/my.cnf instead of /etc/mysql/my.cnf.

ever hit the default.

Moving the variables to just after the case statement will set
them, removing the default part of the case will cause this class
to fail on unsupported distros.
a $config_file variable to allow per-distro config file destinations.
@justintime
Copy link
Author

@ghoneycutt - good idea, committed and pushed 92290b3.

}
}
$python_package_name = 'python-mysqldb'
$ruby_package_name = 'ruby-mysql'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This doesn't make sense to me. The package name is different for ubuntu and centos

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, they sure are :)

I don't use the python libs on CentOS, so that's why I didn't catch that. Since I'm on CentOS, and that's what the variable was set to, I didn't see that.

Commit c21c393 should fix this.

@ryanycoleman
Copy link

+1. Thanks for working on this!

@justintime
Copy link
Author

Bug filed at: http://projects.puppetlabs.com/issues/11916

@ccaum
Copy link
Contributor

ccaum commented Jan 13, 2012

@justintime Do you have any experience with rspec-puppet? The only thing left I'd love to see here is a spec test to ensure the my.cnf file has the proper title depending on the OS. This will protect against regressions. Take a look at the spec tests provided in my use_gem_for_provider branch. I only have a few tests so far, but I'm trying to always add tests for manifest changes.

@justintime
Copy link
Author

@ccaum I've heard of it, but not used it. I'm very good with Perl, but
very new to Ruby, so a lot of the TDD stuff still eludes me. I got some
time to tinker with it today, but I seem to be having some environment
issues. I'd love for you to "teach me to fish" if you have the time,
otherwise I'll keep hacking on it.

On Thu, Jan 12, 2012 at 11:14 PM, Carl Caum <
[email protected]

wrote:

@justintime Do you have any experience with rspec-puppet? The only thing
left I'd love to see here is a spec test to ensure the my.cnf file has the
proper title depending on the OS. This will protect against regressions.


Reply to this email directly or view it on GitHub:
#35 (comment)

@ccaum
Copy link
Contributor

ccaum commented Jan 14, 2012

@justintime No worries. If you're willing to work on it then cool. If not, I don't mind doing it. It'll just take me a few weeks before I can touch it. A lot on my schedule at the moment. Feel free to browse around the tests inside the /spec/classes directory in my branch. It's pretty clear how to write tests for manifests.

@bodepd
Copy link
Contributor

bodepd commented Mar 15, 2012

@justintime Hi, I actually merged a pull request from Nan that I believe contains all of the commits mentioned here.

#41

I am closing this pull request with the assumption that everything in it has already been resolved. If you could verify that, I would be appreciative.

@bodepd bodepd closed this Mar 15, 2012
@justintime
Copy link
Author

Hi Dan -- unfortunately I can't really test because my fork has diverged
too much from the original now to roll back. However, I haven't made any
changes to the code that was in those commits, and I'm running in
production with CentOS, so those commits should indeed be production ready.

Justin

On Thu, Mar 15, 2012 at 11:51 AM, Dan Bode <
[email protected]

wrote:

@justintime Hi, I actually merged a pull request from Nan that I believe
contains all of the commits mentioned here.

#41

I am closing this pull request with the assumption that everything in it
has already been resolved. If you could verify that, I would be
appreciative.


Reply to this email directly or view it on GitHub:
#35 (comment)

pmcmaw pushed a commit to pmcmaw/puppetlabs-mysql that referenced this pull request Mar 3, 2021
(MODULES-6881) - Removing duplicaton in .sync.yml
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants