It affects all sites/platforms, not even using CiviCRM.

To reproduce try to create blank/basic D6 site and then try to migrate it to basic D7 platform. It will fail with error:

WD php: PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'd65o1linodeush_0.blocked_ips' doesn't exist: SELECT 1 FROM {blocked_ips} WHERE ip = :ip; Array ( [:ip] => 127.0.0.1 ) in drupal_is_denied() (line 1895 of /data/all/001/drupal-7.14.2-dev/includes/bootstrap.inc).
Drush command terminated abnormally due to an unrecoverable error.
CommentFileSizeAuthor
#1 patch_commit_6904494a3d10.patch2.79 KBomega8cc

Comments

omega8cc’s picture

omega8cc commented
Status: Active » Needs review
StatusFileSize
new patch_commit_6904494a3d10.patch2.79 KB

Attached patch fixes the problem.

bgm’s picture

bgm commented

Thanks for the patch.

Any ideas how we could fix this for sites with CiviCRM?

omega8cc’s picture

omega8cc commented

Not sure what problem related to CiviCRM sites you mean? This patch should not affect any CiviCRM enabled site, it only hides entire function drush_civicrm_post_provision_deploy() from non-CiviCRM sites to avoid breaking their tasks, since Drush happily loads and tries to run all code existing in its directory, no matter if it can be used or not.

bgm’s picture

bgm commented
Status: Needs review » Needs work

For me it fails on a CiviCRM site. As far as I can tell, when drush_civicrm_post_provision_deploy() is called, it tries to bootstrap Drupal, but the Drupal DB has not yet been upgraded, so tables such as "blocked_ips" are not yet created.

bgm’s picture

bgm commented
Status: Needs work » Fixed

I pushed a commit to 6.x-1.x to remove the use of hook_provision_post_deploy(), since it's been causing too many headaches. Tested an upgrade from D6 civi 3.4 to D7 civi 4.2.0.

Also started working on unit testing, based on Steven's scripts: http://drupal.org/project/vagrant_scripts_aegir_civicrm It's a bit time consuming to kickstart though, but it's awsome :)

Status: Fixed » Closed (fixed)

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