Root credentials #123
Merged
Root credentials #123
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is necessary when running puppet as root using sudo because mysql will still look in the user's home directory in that case unless told otherwise.
pmcmaw
pushed a commit
to pmcmaw/puppetlabs-mysql
that referenced
this pull request
Mar 3, 2021
(PDK-1501) Allow Appveyor CI config to be templated
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
From #92:
The mysql root password is stored in
.my.cnfin root's home directory. However, themysqlandmysqladmincommands use the value of the HOME environment variable rather than libc user ent data to determine the location of.my.cnf. This causes the puppet module'smysqlandmysqladmininvocations to fail when HOME and the current user's home directory are not the same, e.g. if the puppet process was started usingsudo.I had created a pull request earlier and then got talked out of it. My initial discovery was that 'sudo puppet agent -t' failed but the running puppet daemon was able to apply the catalog. Someone suggested
sudo -i puppet agent -twhich works. I have since discovered that even restarting the agent daemon with sudo (sudo /etc/init.d/puppet restart) causes the a mismatch. This is much more insidious because the running daemon will fail on every run.