I was tempted to just say that Drupal 7.50 itself is a bug. Anyway, the same issue (#2762701: Aegir 6.x-2.x to 7.x-3.x broken by Drupal 7.50) we just overcame in upgrades to the hostmaster site are starting to creep up in other site migrations/clones:
The following module has moved within the file system: devel. In order to fix this, clear caches or put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging()
Note that this is triggered during the Drush bootstrap upon beginning deployment of the backup, and before update.php is run.
Comments
Comment #2
ergonlogicAdding some related issues... The code in this comment, which appears to have been added as a patch in #1694792: Allow provision-deploy to move a site to a platform with different module paths, calling registry-rebuild, looks like a promising start.
Comment #3
colanAs suggested in the other ticket, how about sticking a drush registry-rebuild somewhere in the process? In theory, that command should fix this problem.
Comment #4
ergonlogicThe patch from #1694792: Allow provision-deploy to move a site to a platform with different module paths does indeed work to allow migrations/clones to work despite the warning. In fact, it still reports it, but as a warning, rather than an error, and thus allows the task to complete. I'll follow up there.
Comment #5
realityloopclosing due to referenced issue covering whats required here