apologies, i can get a bit long-winded in my questions…
should I follow the fix for COOK-517, or the fix for COOK-727?
on RHEL/CentOS6, the current mysql cookbook installs the mysql server
package (which creates the mysql user and mysql group)
then it tries to create some folders and templates using the mysql
user and mysql group
since ruby caches the group names, this fails, as the group doesn’t yet exist.
This is documented in COOK-1676, and has been occurring for a long
time, just didn’t get a chance to write it up before, but now someone
I see two ways to fix this, neither have I completely tested, but both
theoretically will work.
In COOK-517, Seth Chisamore fixed the same bug in the users cookbook
by adding the following code:
ruby_block “reset group list” do
then adding a notifies line to whatever block creates the group.
I just finished completing a mirror fix for the mysql cookbook here:
In COOK-727, Joshua Timberman made a fix for the postgresql cookbook
for the same issue,
but instead of resetting the group list, he manually created the user
and group for postgresql "like the package will"
I could follow Joshua’s way of doing it, but I worry… what happens
if the mysql upstream package changes? Then it doesn’t create it
"like the package will". Then I’ll be screwed in the middle of the
night when i am rebuilding a failed server.