Here's a peculiar use case that showed how limited the db server support is in aegir. I don't know if this is by design, but it just sounds wrong enough that I file it as a bug report at this point, considering that we have refactored the server nodes...

Here's my situation:

* server A is the aegir server, with a web and db service, that was installed as a single-server instance
* server B is a new remote db server I'm trying to put in place

Here's what I did:

* I create server B (the new DB server) in the frontend, with only a mysql service
* I went in the frontend to disable the db service on server A, which triggered a platform verification on this server

Here's what happened:

* first, I hit #726984: all sites go to aegir and all my sites went down
* second, the generated drushrc.php in the platform didn't have the new DB server settings, it had the old one from server A, even though that service is disabled

What I expected:

* that the new drushrc would use the only db server settings available

Comments

adrian’s picture

adrian commented

This needs to be worked on again. We now store separate config files for each server.

You will still need to edit each site node and point them at the different db server first.
we probably need some validation around this.

anarcat’s picture

anarcat commented

I realize this is very close to #823224: hostmaster-migrate fails from alpha2 to alpha8 on remote db servers, maybe one of those should be marked as dupe?

adrian’s picture

adrian commented
Status: Active » Closed (duplicate)

the other one was fixed.

closing this.