Skip to content

Fixing error when disabling service management and the service does not exist #787

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

Merged
merged 1 commit into from
Dec 15, 2015

Conversation

obi11235
Copy link
Contributor

If you set service_manage => false, because your instance of mysql is not managed by any service management OR in my case I'm only using this puppet module to manage mysql users, puppet generates an error.

Error: /Stage[main]/Mysql::Server::Service/Service[mysqld]: Could not evaluate: Could not find init script or upstart conf file for 'mysql'

@pabelanger
Copy link

+1

Not sure what is wrong with the CI however

@igalic
Copy link
Contributor

igalic commented Dec 15, 2015

centos build has been broken since forever
there's a way to fix it, and we should push that into modulesync
ping @nibalizer @blkperl @bkero

igalic added a commit that referenced this pull request Dec 15, 2015
Fixing error when disabling service management and the service does not exist
@igalic igalic merged commit 45419fd into puppetlabs:master Dec 15, 2015
@roidelapluie
Copy link
Contributor

@igalic please note that this is a breaking change that should trigger more than a minor release version (y.Y.z )

@roidelapluie
Copy link
Contributor

(e.g this should be released in 3.7)

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

Successfully merging this pull request may close these issues.

5 participants