[chef] Re: MySQL Cookbook Ignores Root Password Setting On First Converge

[DV < >]

I suggest you replace the following in recipes/server.rb:

root_account = ChefVault::Item.load("mysql_accounts", "root")
node.set['mysql']['server_root_password'] = root_account['password']

With the following in attributes/default.rb:

root_account = ChefVault::Item.load("mysql_accounts", "root")
default['mysql']['server_root_password'] = root_account['password']

It's very likely that your node.set call happens after mysql cookbook tries to determine root password, which is why you're not seeing the behavior you want.

On Sat, Jun 21, 2014 at 2:51 AM, Stuart Ellis < " target="_blank"> > wrote:

Hello all,

I’m currently building a Chef setup and have hit a consistent issue with the MySQL cookbook. Given the popularity of this cookbook, I’m happy to believe that I’m just doing something wrong.

The problem is it’s ignoring the passwords in my wrapper cookbook the first time that the cookbook is applied, and instead, uses the default values. The second time that the cookbook runs it does try to apply the correct passwords, but fails, because the MySQL installation requires the root password that was set on the first run.

The test nodes are fresh Ubuntu 14.04 LTS VMs - I’m building and destroying the nodes each time to ensure that they are clean. I’ve tried using the block format for configuring the MySQL resource, and with hard-coded values instead of Chef Vault, but get the same behaviour in both cases. There’s no open issue in JIRA or GitHub to suggest that this is a known issue.

My wrapper cookbook is here:

https://bitbucket.org/stuartellis/se-mysql

Thanks in advance,

Stuart

---
Stuart Ellis
">

--
Best regards, Dmitriy V.