ACP2E-4448: L2 cache, local cache, stale cache, and Redis became unsynchronized…

Categories

Cache

Components

magento/framework

Origin

adobe-commerce-support

Since QPT

1.1.78

Issue

L2 cache, local cache, stale cache, and Redis became unsynchronized when Redis was unavailable. Configuration changes made during Redis outages were not reflected after Redis recovered, causing stale values to persist.

Steps to reproduce

1. Configure the L2 cache using the RemoteSynchronizedCache backend with Redis as the remote backend and file cache as the local backend. 1. Navigate to Configuration > General > Contact > Email Options > Send Emails To. 1. Update the Send Emails To value to _100@example.com_. 1. Refresh the page multiple times to confirm that the value is cached. 1. Stop the Redis service to simulate a service interruption. 1. Update Send Emails To value to _200@example.com_. 1. Start the Redis service. 1. Refresh the configuration page.

Adobe's page lists 2.4.8 - 2.4.8-p4 as compatible; the versions below are resolved from the current QPT constraints and are the ones the tool will offer.

Adobe scheduled the permanent fix for 2.4.9.

Install

Install the Quality Patches Tool with composer require magento/quality-patches, apply the prerequisites listed for all files applicable to your distribution and version first, then run vendor/bin/magento-patches apply ACP2E-4448. On Cloud, add ACP2E-4448 under stage.build.QUALITY_PATCHES in .magento.env.yaml.

For cweagans/composer-patches, choose a compatible version below and download the bundle. Copy its ACP2E-4448/ folder into patches/composer/, merge composer.patches.json into composer.json, then run composer install. Bundle prerequisites the same way and list them first. Paths are relative to each package root, using the default -p1 level. Prefer local files when configuring composer-patches; a remote URL can change.

Patch files and compatible versions

Sources

• Adobe documentation for ACP2E-4448
• JSON API: /api/v1/patches/ACP2E-4448