When restoring a Drupal site from backup to Aegir, I have been using drush provision-save and provision-deploy commands to create a new site and restore the contents from backup. After upgrading to Aegir 2.1, the process still works but the Drupal site name is getting corrupted. Here would be an example.

Drupal Site Name: ABC Testing Site
Drupal Site URI: testing.abc.com

drush provision-save @testing.abc.com --context_type=site --platform=@drupal7_platform --profile=standard --uri=testing.abc.com --db_server=@server_localhost --client_name=admin

drush @testing.abc.com provision-deploy ~o1/restores/testing.abc.com-20140919.040411.tar.gz

The results are:
- Site is restored
- accessible as testing.abc.com
- Site name is not ABC Testing Site it is the (site uri + each letter of the original site name)

testing.abc.comAtesting.abc.comBtesting.abc.comCtesting.abc.comTtesting.abc.cometesting.abc.comstesting.abc.comttesting.abc.comitesting.abc.comntesting.abc.comgtesting.abc.comStesting.abc.comitesting.abc.comttesting.abc.come

Other information:
Aegir 2.1
Drush 6
BOA 2.3.2
Drupal 7

Comments

larryboy360’s picture

larryboy360 commented

Any help on this one would be greatly appreciated.

helmo’s picture

helmo commented

My guess would be that this fails in: http://cgit.drupalcode.org/provision/tree/platform/drupal/deploy_7.inc?h...

Although I can't reproduce it...
What would be the site_name and URI from the original site, as stored in the backup?

lieb’s picture

lieb commented

This happens to me on every provision-deploy, but never on a migrate or clone. It happens wether the URL changes or not, which is interesting looking at the code from #2 . I've got more of these to do so I will try and insert some debug code and see if I can pinpoint the problem.

sgardapee’s picture

sgardapee commented

We were able to avoid the issue by adding the --old_uri parameter, e.g.
drush @yoursitename provision-deploy --old_uri=yoursitename ~o1/restores/yoursitename-yymmdd.hhmmss.tar.gz

helmo’s picture

helmo commented
Status: Active » Closed (outdated)

The 6.x-2.x branch will go EOL along with Drupal this week. So I'm closing
this issue. If it remains a confirmed issue in 7.x-3.x, feel free to re-open,
or better yet, create a new issue referencing this one.

PS: This has been fixed in another issue.