Updating to 8.x-2.0-beta21 causes config import to fail

Created on 27 February 2025, 11 days ago

Problem/Motivation

After updating to 8.x-2.0-beta21 trying to import config changes results in errors:

 [error]  Drupal\Core\Config\ConfigException: Errors occurred during import in Drush\Commands\config\ConfigImportCommands->doImport() (line 276 of /opt/drupal/vendor/drush/drush/src/Commands/config/ConfigImportCommands.php).

In ConfigImportCommands.php line 290:

  The import failed due to the following reasons:
  Unexpected error during import with operation delete for ldap_servers.server.dc4: You have requested a non-existent service "Drupal\entity_usage\PreSaveUrlRecorder".
  Unexpected error during import with operation update for core.entity_view_mode.media_gallery.full_gallery: You have requested a non-existent service "Drupal\entity_usage\PreSaveUrlRecorder".
  Unexpected error during import with operation update for core.entity_view_display.node.embedded_content.teaser: You have requested a non-existent service "Drupal\entity_usage\PreSaveUrlRecorder".
  Unexpected error during import with operation update for core.entity_view_display.node.embedded_content.default: You have requested a non-existent service "Drupal\entity_usage\PreSaveUrlRecorder".
  Unexpected error during import with operation update for views.view.media_galleries: You have requested a non-existent service "Drupal\entity_usage\PreSaveUrlRecorder".
  Unexpected error during import with operation update for ldap_servers.server.dc11: You have requested a non-existent service "Drupal\entity_usage\PreSaveUrlRecorder".


In ConfigImportCommands.php line 276:

  Errors occurred during import


This appears to be related to https://www.drupal.org/project/entity_usage/issues/3509039 πŸ› Updating to 8.x-2.0-beta20 from 8.x-2.0-beta19 causes WSD Active because it is the same error message.

Steps to reproduce

  1. update entity_usage to 8.x-2.0-beta21
  2. using drush attempt to import config
πŸ› Bug report
Status

Active

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States kwfinken Lansing, MI

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @kwfinken
  • πŸ‡ΊπŸ‡ΈUnited States kwfinken Lansing, MI

    For those facing a similar issuer, getting the container running again and clearing cache fixed the issue. It appears that in the update the cache was somehow not cleared. Unsure if there are other issues or not.

  • πŸ‡¬πŸ‡§United Kingdom alexpott πŸ‡ͺπŸ‡ΊπŸŒ

    Did you run config import before ensuring there are no database updates? After you update any code you need to ensure that database updates are run before doing anything like a config import.

Production build 0.71.5 2024