You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
on a 2 instance install in AWS, (db/web) when using
db_host => 'my_remote_db',
create_db => true,
create_db_user => true,
Puppet will fail, as regardless of the $dbhost parameter will still try to connect locally.
Workaround:
Create the DB in the db manifest first using the mysql puppet module
mysql::db {'wordpress':
user => 'wordpress',
password => 'mypass',
host => 'wphost',
ensure => 'present',
require => File['/root/.my.cnf'],
}
You must also then use Vagrant Hostmaster plugin to update hoses file so web and db can communicate.
I never found the RC of why the db_host was ignored, but having read through the code, and the documentation being somewhat 'light' on this subject, i opted to workaround the issue.
The text was updated successfully, but these errors were encountered:
Adding to this, this issue still exists, trying to look into it and I noticed in acceptance/wordpress_spec.rb that there are still some things yet to be setup - is this correct?
i.e. I can see 4x lines saying it 'deploys a wordpress instance with a remote DB'
'deploys a wordpress instance with a pre-existing DB' etc
on a 2 instance install in AWS, (db/web) when using
db_host => 'my_remote_db',
create_db => true,
create_db_user => true,
Puppet will fail, as regardless of the $dbhost parameter will still try to connect locally.
Workaround:
Create the DB in the db manifest first using the mysql puppet module
mysql::db {'wordpress':
user => 'wordpress',
password => 'mypass',
host => 'wphost',
ensure => 'present',
require => File['/root/.my.cnf'],
}
You must also then use Vagrant Hostmaster plugin to update hoses file so web and db can communicate.
I never found the RC of why the db_host was ignored, but having read through the code, and the documentation being somewhat 'light' on this subject, i opted to workaround the issue.
The text was updated successfully, but these errors were encountered: