You can install and disable it, but every delete task fails with:

The external command could not be executed due to an application error.
Drush command could not be completed.
Output from failed command : Fatal error: Call to undefined function cache_get() in /data/all/001/drupal-7.0-alpha7/includes/module.inc on line 609
An error occurred at function : drush_hosting_task

Tested a few times with Standard install profile and latest Aegir HEAD code.

Comments

Hitby’s picture

Hitby
he/him
commented

Subscribing...

omega8cc’s picture

omega8cc commented

As a side effect: even when you will delete site all files and its node in Aegir and then you will create a site in different platform (!) with the same domain name from scratch, the site will be *disabled* (no way to access it) even if it is not displayed as disabled in the front-end. This is not related to the not updated httpd config file, all files are correct, but the goto link, and even manually entering the URL in the browser sends you to the Site disabled page. Now try to open it in another browser and it works! Cookies issue?

[EDIT] It is not related to the cookies. The browser (Safari 5) remembers this redirect and you need to empty browser cache, since logging out/in doesn't help.

milesw’s picture

milesw commented

Experiencing the same error deleting D7 beta 1 sites.

- D7 beta 1, standard install profile
- Aegir HEAD
- Drush 4.0-dev

omega8cc’s picture

omega8cc commented

Just to confirm, d7-beta1 has the same issue. You can't delete the site, you need to delete its directory, its node in Aegir and then also its config file in vhosts. It is with Aegir alpha14 and latest HEAD with Drush 3.3.

boztek’s picture

boztek commented

I'm assuming this means that site migration is also not possible from one beta1 build to another then?

omega8cc’s picture

omega8cc commented
Title: You can't delete the D7 alpha7 sites. » You can't delete the D7 alpha7 and beta1 sites.

You can clone both alpha7 and beta1, but you can't migrate a7->b1, however it is expected, since there was no upgrade path guaranteed at all for any alpha version, and it is by design.

We should be able to delete any site (even broken) in Aegir, so I believe it needs to be addressed by Aegir somehow.

Changing the subject line to include beta1 as affected.

omega8cc’s picture

omega8cc commented

BTW: this error was reported long time ago for 7.x-dev (and not in the Aegir context), so it will probably break d7 beta upgrade for all again: http://drupal.org/node/221964#comment-763686

omega8cc’s picture

omega8cc commented

I opened an issue also in the 7 core queue: http://drupal.org/node/944022 because I'm not sure if moving existing issue there would be correct - we are not sure if that is d7 bug only or also some Aegir bug, since we should be able to force the delete no matter how broken is the site provisioned in Aegir.

damien tournoud’s picture

damien tournoud commented

Subscribing (coming from the duplicated issue in the core queue).

Anonymous’s picture

Anonymous (not verified) commented

It's buried somewhere in our db logic somewhere, after successfully dropping the db, but before being able to drop the GRANTs for the site's db user.

If you move /var/aegir/.drush/provision/db out of the way before running the Delete task, completely bypassing the db logic, it completes successfully.

Still looking...

Anonymous’s picture

Anonymous (not verified) commented

The issue seems entirely centered on revoking grants.

The relevant section from provision/db/db.drush.inc in destroy_site_database()

    foreach ($this->grant_host_list() as $db_grant_host) {
      drush_log(dt("Revoking privileges of %user@%client from %database", array('%user' => $db_user, '%client' => $db_grant_host, '%database' => $db_name)));
      if (!$this->revoke($db_name, $db_user, $db_grant_host)) {
        drush_log(dt("Failed to revoke user privileges"), 'warning');
      }
    }
Anonymous’s picture

Anonymous (not verified) commented
Status: Active » Fixed

Antoine appears to have accidentally fixed this bug here << can't explain why though.

I'm marking this as fixed as deletes are working in HEAD against drupal 7.0 beta1 sites, tested 3 times. Re-open it if you can't reproduce the fix

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.