Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Right now it's possible to create a zombie site that's only deletable by hacking database...
Steps to reproduce...
. Create a couple remote sites and add them to a cluster.
. Create a platform on the cluster.
. Accidentally create a site on the platform using localhost as the database server ;)
Expected: it doesn't let you
Actual: site is created and fails to install... Worse yet... It can't be deleted or installed without changing the database entry manually.
FYI I never tried this on a non cluster...
Comments
Comment #2
captainack CreditAttribution: captainack commentedComment #3
Jon PughMarking this as major.
It happens a lot.
I want to come up with an issue tag to try and catalog these kinds of issues.
Comment #4
Jon PughComment #5
helmo CreditAttribution: helmo at Initfour websolutions for Aegir Cooperative commentedI think we have aegirWTF for that :)
The problem could be summarized as "Create a site on a server that does not have access to the specified database server. Fail!"
Forcing the db to be on the same host as the webserver is not always an option, as there are many architectures possible.
But detecting localhost as invalid option for a remote site could be a first step. Something in the hosting_site_validate() or hosting_site_form() functions?