We have a website which is at Drupal Core version 8.9.18. We are upgrading it to drupal 9.2.5. Our database has been updated with the 8.9.18 codebase deployed. There are no old updates that need to be run.
When we upgrade to Drupal 9, we get the following message on the first updb...
> [notice] Update started: lightning_update_8007
> [notice] Update completed: lightning_update_8007
> [notice] Update started: lightning_update_8008
> [notice] Update completed: lightning_update_8008
> [notice] Update started: user_update_9301
> [notice] Update completed: user_update_9301
> [notice] Update started: block_post_update_replace_node_type_condition
> [notice] Update completed: block_post_update_replace_node_type_condition
> [notice] Update started: file_post_update_add_txt_if_allows_insecure_extensions
> [notice] Update completed: file_post_update_add_txt_if_allows_insecure_extensions
> [notice] Update started: node_post_update_rebuild_node_revision_routes
> [notice] Update completed: node_post_update_rebuild_node_revision_routes
> [notice] Update started: panelizer_post_update_enable_layout_builder_dependencies
> [error] Table 'inline_block_usage' already exists.
> [error] Update failed: panelizer_post_update_enable_layout_builder_dependencies
[error] Update aborted by: panelizer_post_update_enable_layout_builder_dependencies
[error] Finished performing updates.
Then I run it again and...
[warning] Schema information for module layout_builder was missing from the database. You should manually review the module updates and your database to check if any updates have been skipped up to, and including, layout_builder_update_8602().
[error] The installed version of the /Layout Builder/ module is too old to update.
Update to a version prior to 9.0.0 first (missing updates:
layout_builder_post_update_rebuild_plugin_dependencies,
layout_builder_post_update_add_extra_fields,
layout_builder_post_update_section_storage_context_definitions,
layout_builder_post_update_overrides_view_mode_annotation,
layout_builder_post_update_cancel_link_to_discard_changes_form,
layout_builder_post_update_remove_layout_is_rebuilding,
layout_builder_post_update_routing_entity_form,
layout_builder_post_update_discover_blank_layout_plugin,
layout_builder_post_update_routing_defaults,
layout_builder_post_update_discover_new_contextual_links,
layout_builder_post_update_fix_tempstore_keys,
layout_builder_post_update_section_third_party_settings_schema,
layout_builder_post_update_layout_builder_dependency_change,
layout_builder_post_update_update_permissions,
layout_builder_post_update_make_layout_untranslatable).
but it actually performs a bunch of the updates despite the errors.
> [notice] Update started: layout_builder_post_update_override_entity_form_controller
> [notice] Update completed: layout_builder_post_update_override_entity_form_controller
> [notice] Update started: layout_builder_post_update_section_storage_context_mapping
> [notice] Update completed: layout_builder_post_update_section_storage_context_mapping
> [notice] Update started: panelizer_post_update_enable_layout_builder_dependencies
> [notice] Update completed: panelizer_post_update_enable_layout_builder_dependencies
> [notice] Update started: serialization_post_update_delete_settings
> [notice] Update completed: serialization_post_update_delete_settings
> [notice] Update started: system_post_update_claro_dropbutton_variants
> [notice] Update completed: system_post_update_claro_dropbutton_variants
> [notice] Update started: system_post_update_delete_authorize_settings
> [notice] Update completed: system_post_update_delete_authorize_settings
> [notice] Update started: system_post_update_delete_rss_settings
> [notice] Update completed: system_post_update_delete_rss_settings
> [notice] Update started: system_post_update_entity_revision_metadata_bc_cleanup
> [notice] Update completed: system_post_update_entity_revision_metadata_bc_cleanup
> [notice] Update started: system_post_update_remove_key_value_expire_all_index
> [notice] Update completed: system_post_update_remove_key_value_expire_all_index
> [notice] Update started: system_post_update_schema_version_int
> [notice] Update completed: system_post_update_schema_version_int
> [notice] Update started: system_post_update_service_advisory_settings
> [notice] Update completed: system_post_update_service_advisory_settings
> [notice] Update started: system_post_update_uninstall_classy
> [notice] Update completed: system_post_update_uninstall_classy
> [notice] Update started: system_post_update_uninstall_entity_reference_module
> [notice] Update completed: system_post_update_uninstall_entity_reference_module
> [notice] Update started: system_post_update_uninstall_simpletest
> [notice] Update completed: system_post_update_uninstall_simpletest
> [notice] Update started: system_post_update_uninstall_stable
> [notice] Update completed: system_post_update_uninstall_stable
> [notice] Update started: taxonomy_post_update_clear_views_argument_validator_plugins_cache
> [notice] Update completed: taxonomy_post_update_clear_views_argument_validator_plugins_cache
> [notice] Update started: user_post_update_update_roles
> [notice] The role Anonymous user has had the following non-existent permission(s) removed: view bootstrap site alerts.
> [notice] The role Authenticated user has had the following non-existent permission(s) removed: view bootstrap site alerts.
> [notice] The role Media manager has had the following non-existent permission(s) removed: administer media bundles.
> [notice] The role Site Admin has had the following non-existent permission(s) removed: use text format uber_admin.
> [notice] The roles Anonymous user, Authenticated user, Media manager, Site Admin have had non-existent permissions removed. Check the logs for details.
> [notice] Update completed: user_post_update_update_roles
> [notice] Update started: views_post_update_configuration_entity_relationships
> [notice] Update completed: views_post_update_configuration_entity_relationships
> [notice] Update started: views_post_update_remove_sorting_global_text_field
> [notice] Update completed: views_post_update_remove_sorting_global_text_field
> [notice] Update started: views_post_update_rename_default_display_setting
> [notice] Update completed: views_post_update_rename_default_display_setting
> [notice] Update started: views_post_update_sort_identifier
> [notice] Update completed: views_post_update_sort_identifier
> [notice] Update started: views_post_update_title_translations
> [notice] Update completed: views_post_update_title_translations
[success] Finished performing updates.
So then I perform updb a third time and get the following...
[error] The installed version of the /Layout Builder/ module is too old to update.
Update to a version prior to 9.0.0 first (missing updates:
layout_builder_post_update_rebuild_plugin_dependencies,
layout_builder_post_update_add_extra_fields,
layout_builder_post_update_section_storage_context_definitions,
layout_builder_post_update_overrides_view_mode_annotation,
layout_builder_post_update_cancel_link_to_discard_changes_form,
layout_builder_post_update_remove_layout_is_rebuilding,
layout_builder_post_update_routing_entity_form,
layout_builder_post_update_discover_blank_layout_plugin,
layout_builder_post_update_routing_defaults,
layout_builder_post_update_discover_new_contextual_links,
layout_builder_post_update_fix_tempstore_keys,
layout_builder_post_update_section_third_party_settings_schema,
layout_builder_post_update_layout_builder_dependency_change,
layout_builder_post_update_update_permissions,
layout_builder_post_update_make_layout_untranslatable).I have no idea what this error means. There do seem to be a few old issues and posts bopping around the internet without a real resolution to them.
Since none of our other sites have had this problem and this site is running Lightning, my instinct is to blame Lightning.
But then again, my instinct is ALWAYS to blame Lightning, so there's that.
I think this is related to #3206215 but I don't know what to do about it.
Active
5.0
Documentation
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This can happen when module install crashes and \Drupal\Core\Update\UpdateRegistry::onConfigSave can not do its job.
See
#3206215-11: "The installed version of the