Problem migrating site from a AE 0.3 on drupal 13 to a AE 0.4 on drupal 14 - Migration not allowed - meaning of the codes/colors
| Project: | Hosting |
| Version: | 6.x-0.4-alpha1 |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Hello all.
I tried last night o migrate from Aegir 0.3 on drupal-6.13 to Aegir 0.4 alpha 1 on drupal-6.14.
I struggled a bit with the documentation I'll do a separate post on a few "errors" I encountered.
I then tried to migrate through AEGir my websites, seems to be the purpose of the whole thing :)
On simple "nothing installed" sites It worked fine.
On two other sites it started go get ugly
Basically I get the migration screen and don't understand why no platform qualify.
First question what does the color mean ?
Green : a new higher version is installed on the target platform ? does not prevent migration
red : an older version is installed on the target platform : migration not allowed ?
grey : same components version on both platform : nothing special, migration allowed
is that right ?
Second I have numbers after the version numbers of things, number in parenthesis I don't get ... sometime a (1) on the source and a (2) on the target or a (6202) on source and (6203) on target.... It seems the target number is always on up the source one ...
what does that mean ?
But the problem is In the case of two websites, I had all green and Grey modules and I am unable to migrate.
On the most simple case a storm site with 3 other modules active, I was able to migrate with an "orange light" after deactivating a few modules
But i am still stuck on the most complex case .
Here is a chunk of the table for the most complex case:
Platform | user | update | trigger | taxonomy | system | statistics | search | profile | php | path | node | menu | locale | help | filter | dblog | contact | comment | color | block |
Current | 6.13 | 6.13 (6000) | 6.13 | 6.13 | 6.13 (6051) | 6.13 (1000) | 6.13 | 6.13 | 6.13 | 6.13 | 6.13 | 6.13 | 6.13 (6005) | 6.13 | 6.13 | 6.13 | 6.13 | 6.13 (6003)| 6.13 | 6.13 |
Aegir 0.4 sur Drupal6-14 | 6.14 (1) | 6.14 (6001) | 6.14 (1) | 6.14 (1) | 6.14 (6054) | 6.14 (6001) | 6.14 (1) | 6.14 (1) | 6.14 (1) | 6.14 (1)| 6.14 (1)| 6.14 (1)| 6.14 (6006) | 6.14 (1)| 6.14 (1)| 6.14 (6001)| 6.14 (1)| 6.14 (6004)| 6.14 (1)| 6.14 (1)|(sorry for the table presentation but can't see a way to express it properly with the allowed tags ... maybe activating REST syntax could help ;) )
I am trying to hold my finger from doing a MOVE xxxx/oldsite xxxxx/newSite ..... but it it hard :)
I have seen the issue about early alpha versions of the Aegir 0.4 preventing migration by duplicating modules in internal tables but AFAIK it is not the case here the sql returns only single modules instance in the table mentioned in in the issues.
Any clue how I can investigate the matter further and help the cause ?
Thanks a lot for you time
#1
Hi Annakan,
Your understanding of the 'colors' is accurate.
The issue regarding Duplicate modules in internal tables does not apply in this case: it only affects users who are installing 0.4 alpha1 from scratch.
I'm having trouble reading that table: maybe you want to take a screenshot of the migration comparison table and attach it in this ticket so we can have a look.
Also remember to re-verify all sites before migration. See my blog post which may also assist you.
#2
Sorry I know the table is not easy to read but I did not know how to convey the information(I added | between fields).
I joined an image of a part of the table because I can't see the full table on the screen, it only has a reserved space with a scrollbar.
It shows the "6000/6001" numbers attached to versions at least.
I have only green and grey in the LAST row witch is my target but as you can see the target is still orange/red :(
thanks a lot for your time; Mig5 and all.
#3
Sorry for not getting back to you sooner,
These reflect the hook_update changes on the modules. Some modules are inconsistent and use hook_update_1 or hook_update_2 where they should be using hook_update_6001 and hook_update_6002.
So, nothing to worry about.
I am wondering if the site in question that you're trying to migrate was installed with an install_profile that is not the default profile. That could be one of the reasons why the platform's shown as Red even though no modules are red. Still not sure about this though.