Setting tunable[skip-name-resolve] to true

If tunable[skip-name-resolve] is set to false, hostname resolution
can cause auth issues.

Change-Id: I34b3b530786239c3c42ff1d8a44c536fea82f125
This commit is contained in:
galstrom21 2013-10-17 21:25:27 -05:00
parent cf8e48039b
commit 95b18479e3
2 changed files with 2 additions and 0 deletions

View File

@ -30,6 +30,7 @@ node.override["mysql"]["tunable"]["innodb_thread_concurrency"] = "0"
node.override["mysql"]["tunable"]["innodb_commit_concurrency"] = "0"
node.override["mysql"]["tunable"]["innodb_read_io_threads"] = "4"
node.override["mysql"]["tunable"]["innodb_flush_log_at_trx_commit"] = "2"
node.override["mysql"]["tunable"]["skip-name-resolve"] = true
include_recipe "openstack-ops-database::mysql-client"
include_recipe "mysql::server"

View File

@ -20,6 +20,7 @@ describe "openstack-ops-database::mysql-server" do
expect(@chef_run.node['mysql']['tunable']['innodb_commit_concurrency']).to eql "0"
expect(@chef_run.node['mysql']['tunable']['innodb_read_io_threads']).to eql "4"
expect(@chef_run.node['mysql']['tunable']['innodb_flush_log_at_trx_commit']).to eql "2"
expect(@chef_run.node["mysql"]["tunable"]["skip-name-resolve"]).to eql true
end
it "includes mysql recipes" do