MDVA-39605: The Redis cache TTL (expiration date) has a wrong value

Categories

Catalog/Product

Components

magento/module-configurable-product

Origin

adobe-commerce-support

Since QPT

1.1.13

Issue

The Redis cache TTL (expiration date) has a wrong value.

Steps to reproduce

In order to test the fix, flush cache and open a configurable product on the storefront. Then open a terminal (console) and follow the steps below: 1. Run the command: redis-cli. 1. Run KEYS "*PRICE" (there should be only one key in the result, for example, zc:ti:e54_PRICE). Copy the key. 1. Run SMEMBERS followed by the key from the previous step (for example, SMEMBERS zc:ti:e54_PRICE). Copy any key from the result (for example, e54_4E67B390D5C28FC7C3D9BB0D37AB3F7B5E576421). 1. Run KEYS "*<key>" with the key name from the previous step to get the full key name (for example, KEYS "*e54_4E67B390D5C28FC7C3D9BB0D37AB3F7B5E576421"). There should be only one key in the result (for example, zc:k:e54_4E67B390D5C28FC7C3D9BB0D37AB3F7B5E576421). As you may notice, the full key name is simply the key name with prefix "zc:k:". Now copy the full key name. 1. Run HGETALL followed by the full key name from Step 4 to check the value. The value should contain serialized data of associated products of a related configurable product. 1. Run TTL followed by the full key name from Step 4 to check whether the key has an expiration. The result should be different from -1 and -2 and should be approximately 2592000 (30 days). Although the expiration set in the code is one year, the Redis library used in Adobe Commerce has a hard max expiration limit of 2592000s.

Adobe's page lists 2.3.4 - 2.4.4 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.5.

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 MDVA-39605. On Cloud, add MDVA-39605 under stage.build.QUALITY_PATCHES in .magento.env.yaml.

For cweagans/composer-patches, choose a compatible version below and download the bundle. Copy its MDVA-39605/ 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 MDVA-39605
• JSON API: /api/v1/patches/MDVA-39605