- π¬π§United Kingdom welly
I've found that this issue seems to occur when I use drush to run a migration - drush migrate:import users_migration, which has a required dependency on users_roles_migration, results in this error:
Migration users_migration did not meet the requirements. Missing migrations users_roles_migration. requirements: users_roles_migration.
However, if I run the migration through the Migrate Tools UI it executes correctly and runs the required dependencies first. I've got $settings['cache']['default'] = 'cache.backend.null'; commented out.
- π©π°Denmark ressa Copenhagen
I got the "Migration did not meet requirements" error while importing translated nodes. In my case it had nothing to do with caching, but I am sharing the cause and solution here anyway, in case anyone else searches and finds this issue, like I just did.
It turned out there was a duplicate id, which caused a required migration (
locations
) to not complete:$ drush migrate:status ------------------- -------- ------- ------------- ------------- Migration ID Status Total Imported Unprocessed ------------------- -------- ------- ------------- ------------- locations Idle 796 795 (99.9%) 1 locations_en Idle 0 796 (0%) 796
I got the requirement error when I tried to run with
--all --execute-dependencies
or partial test migrations withlocations_en
:
drush migrate:import locations_en --limit=5 --migrate-debug
After fixing the duplicate id, the
locations
migration completed to 100%, and I could run partiallocations_en
test migrations, or full.