Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

create db on seperate instance #74

Open
msadmn opened this issue Jul 15, 2015 · 1 comment
Open

create db on seperate instance #74

msadmn opened this issue Jul 15, 2015 · 1 comment

Comments

@msadmn
Copy link

msadmn commented Jul 15, 2015

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.

@vladivanovic
Copy link

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

Any timeline on a fix?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants