I'm using the latest BOA so I hope the version above is correct.
Created a test dev platform and tried to create a test site but I had a Profiler dependencies[] entry in my .info without the corresponding projects[] in my .make.
Failed site install log shows;
Drush bootstrap phase : _drush_bootstrap_drupal_configuration()
DRUPAL_INSTALL_FAILED
Exception Object ( [message:protected] => Required modules: Required modules not found.
...
Drush command terminated abnormally due to an unrecoverable error.
Drush was not able to start (bootstrap) the Drupal database.Tried to delete site, failed delete log shows;
Initialized Drupal 7.14 root directory at /var/aegir/platforms/test-d7-base-3
Could not find a Drupal settings.php file at ./sites/default/settings.php.
clearing error
Adding sites directory to /var/aegir/backups/devtest.mysite.org-20120531.123702.tar.gz
chdir(): No such file or directory (errno 2) backup.provision.inc:85
cannot change directory to /var/aegir/platforms/test-d7-base-3/sites/devtest.mysite.orgChanged .info, reverified platform ok (though this might not have been required?) site enable failed again as sites/default/settings.php could not be found. Realised thats what the error was saying anyway, manually moved default.settings.php to settings.php, site enable goes through fine.
/But/ there's no site folder and using the Go to site link gives a 403 error. Verify site, this fails, but now there is a site folder but with just local.settings.php and settings.php. At this point I'm going to stop for now!
Comments
Comment #1
jon pughThis is an oldie but a goodie.
This has been a problem of aegir since the beginning. If an install fails for any reason, you cannot just delete the site!
I don't have a solution, but this is a major problem and I am commenting here to try and remind myself that it should really really be fixed.
Comment #2
ergonlogicI don't know that the regular site delete task will work without being able to bootstrap the site. If we don't have a site drushrc.php, then we won't even be sure of the proper db to delete.
I suspect we need a new site 'purge' task that will simply do it's best to remove any and all config files/dirs for the site in question. Perhaps it should only become available when a regular site 'delete' task fails. It'd probably be best not to guess at the database name, and instead leave that to whatever solution we come up with for #2107349: obsolete databases housekeeping.
Comment #3
ergonlogicI just posted a broader feature request that covers this issue: [2242687]. I'm closing this issue, so we can follow-up there.