If for some reason you change your platform so that modules move from sites/all/modules/* to sites/all/modules/contrib/* (a common practice) and you migrate a site between platforms, it's going to fail as Drupal is going to look for the modules in sites/all/modules during updatedb.
I suspect this is just a matter of flushing the module cache before running the updatedb...
Comments
Comment #1
yrocq commentedError example :
Comment #2
anarcat commentedi have added a quick fix to flush the caches before the updatedb...
Comment #3
anarcat commentedWe can't flush caches before drupal is bootstrapped. So I reverted the patch in e93c2e5.
Comment #4
anarcat commentedWhile this is a pain, there are workarounds and I do not know of a quick solution and I don't want to block the 1.0 release.
Comment #5
Robin Millette commentedsubbing
Comment #6
pearcec commentedI wonder if this is related to an issue I am having with clone a site when the platform moved the modules from profiles to sites/all
#1265630: Blocks disabled (disappear) after site clone.
Thoughts?
Comment #7
helmo commentedA similar issue with some progress is filed under: #1694792: Allow provision-deploy to move a site to a platform with different module paths