Cannot update database because 'module is too old'

I have solve issue using below command:

drush eval "\Drupal::service('update.post_update_registry')->registerInvokedUpdates(['taxonomy_post_update_clear_views_argument_validator_plugins_cache', 'user_post_update_update_roles', 'views_post_update_sort_identifier', 'views_post_update_provide_revision_table_relationship', 'views_post_update_image_lazy_load']);"

Drupal core has an undocumented upgrade path requirements where you have to step through specific older versions of Core and run your database updates to proceed to newer versions of Drupal. A fix here could be to document which Core versions you need to install to get all the required database updates.

There's no such thing? The only requirement is that you are on one of the last two minor versions of D8 and D9 respectively before you update to the next major version. And it is not possible to even try to update from older versions as you will get requirement errors.

The problems reported here are one-off issues due scenarios that nobody has managed to reliably reproduce, could be patches that people were using for example, failed updates, contrib modules interfering. By the time this error happens the actual issue that caused it was likely months or years ago, making it obviously challenging to reproduce.

I have upgraded Drupal from 9.5.10 to 10.0.11 and I have multiple site setup. I got this issue in one of the site.

I got the error while upgrading from D9 to D9. I was able to recover my database by reverting this commit and running the updates.

https://github.com/drupal/drupal/commit/4c453683e4bdfb6af53f0d169ddb87ae...

I am not sure how I had missed DB updates. If I had to guess there was a error at some point that caused updb to fail and I hadn't noticed it.

34 💬 Cannot update database because 'module is too old' Postponed: needs info Worked for me.

I've been slowly dragging this upgrade from 8.9 to 10.2, solving things along the way. The error I was getting was "drupal 10 Cannot update database because [modules] are too old"

I plugged all the "post_update" messages into the eval and it was finally successful.

Thanks Pragna →

I could solve my problem with #36 solution:

drush eval "\Drupal::service('update.post_update_registry')->registerInvokedUpdates(['pasted here all error messages', 'separated by comma']);"

quietone → closed merge request !3862

Drupal core has undocumented upgrade path requirements where you have to step through specific older versions of Core and run your database updates to proceed to newer versions of Drupal.

The upgrade path is documented in release notes and in the Drupal wiki.

Looking at the Drupal 9.0.0 release notes → there is a section Important update information which states the versions of Drupal 8 you can update from. The same is true for the Drupal 10.0.0 release notes → there is a section Updating from Drupal 8.

In the Drupal wiki there are How to upgrade from Drupal 8 to Drupal 9 → and How to upgrade from Drupal 9 to Drupal 10 → both of which state which version of Drupal a site must be on before starting a major version upgrade.

I have updated the issue summary with the problem, workarounds and documentation.

Give #19, #36 and steps to reproduce this starting from an install of Drupal core have not been supplied. I am closing this as was done 2 years in #21.

Thanks, #34 worked for me as well.