Deployment cache - Unable to install the %module module since it does not exist.

Created on 11 July 2022, over 2 years ago

Updated 20 March 2023, almost 2 years ago

Problem/Motivation

In our deployments we have a release folder setup.
Only after a deployments is successful the new release folder will be symlinked.
Therefor it is possible that during a deployment cache will be triggered on a previous release.

This can cause the \Drupal\Core\Extension\ExtensionList::getList method to think a module does not exist based on cache from another release.

In the past most of the issues occurring from this setup could be solved by setting the "Deployment identifier" correctly.
Unfortunately this is not the case for the ConfigImportSubscriber.
( webroot/core/lib/Drupal/Core/EventSubscriber/ConfigImportSubscriber.php:116 )

Steps to reproduce

Have separate release folders ( one with an new module and one without )
Trigger cache (getList) on release without the concerning module.
Run config import on the other release folder.

Proposed resolution

In \Drupal\Core\Extension\ExtensionList::getListCacheId make use of the "deployment_identifier".

🐛 Bug report

Status

Needs work

Version

9.3

Component

Extension →

Last updated about 20 hours ago

No maintainer

Created by

🇳🇱Netherlands willempje2

Live updates comments and jobs are added and updated live.

Bug Smash Initiative

Needs Review Queue Initiative
Used to track the progress of issues reviewed by the Drupal Needs Review Queue Initiative.

Needs tests
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment almost 2 years ago →
🇺🇸United States smustgrave
This issue is being reviewed by the kind folks in Slack, #needs-review-queue-initiative. We are working to keep the size of Needs Review queue [2700+ issues] to around 400 (1 month or less), following Review a patch or merge request → as a guide.

As a bug this will need a test case please (if valid)
Comment almost 2 years ago →
🇳🇱Netherlands willempje2
It seems someone beat me to the punch.
See: https://www.drupal.org/project/drupal/issues/3312001 →
Although i think my solution might be more elegant.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024