health_check.php fails if any database cache engine configured

[ilnytskyi]

Preconditions (*)

1. Configure any cache to database in env.php
   2.3-develop

    'cache' => [
        'frontend' => [
            '{some_frontend_cache}' => [
                'backend' => 'database',
                'backend_options' => [],
                'id_prefix' => 'U_'
            ]
        ],
        'type' => [
            '{any_cache_type_here}' => [
                'frontend' => '{some_frontend_cache}'
            ]
        ]
    ]

Steps to reproduce (*)

1. configure any cache type to database

Expected result (*)

1. health_check.php works

Actual result (*)

1. health_check.php fails since can't find database class in

$backend = new $cacheBackendClass($cacheConfig[ConfigOptionsListConstants::CONFIG_PATH_BACKEND_OPTIONS]);

2. health_check.php fails since can't create instance of \Magento\Framework\Cache\Backend\Database and throws expeditions from here
   \Magento\Framework\Cache\Backend\Database::__construct

'Option "adapter" should be declared and extend \Magento\Framework\DB\Adapter\AdapterInterface!'
Option "data_table" or "data_table_callback" should be declared!
Option "tags_table" or "tags_table_callback" should be declared!
'DB Adapter should be declared and extend \Magento\Framework\DB\Adapter\AdapterInterface'

however the cache works just uses default connection

[m2-assistant]

Hi @ilnytskyi. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@ilnytskyi do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant]

Hi @engcom-Echo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[magento-engcom-team]

✅ Confirmed by @engcom-Echo
Thank you for verifying the issue. Based on the provided information internal tickets MC-29016 were created

Issue Available: @engcom-Echo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[m2-assistant]

Hi @andrewbess. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 2. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[andrewbess]

#cdkharkiv19nov

[magento-engcom-team]

Hi @ilnytskyi. Thank you for your report.
The issue has been fixed in #25722 by @andrewbess in 2.4-develop branch
Related commit(s):

• 5c121e20f909d666079654c6aa7ff325cc094278
• 3905038c09ee3c5f7a9dac63f5f28070c1197434
• e59ee3a1aafc648d7c297660e986bafbaee0b54f
• 6633cc22aa266a0399a60d6a7b94f8d8841004be

The fix will be available with the upcoming 2.4.0 release.