A bug with health_check.php

[wexo-team]

Preconditions (*)

1. Magento 2.2.8
2. Varnish set up with a health_check.php script for the backend

Steps to reproduce (*)

1. Flush or disable the cache on the installation.
2. Visit health_check.php script. It should respond with 500 since the shutdown handler gets called and get_last_error in it returns a deprecation warning from the mcrypt functions.

Expected result (*)

1. health_check.php should not return 500 when an mcrypt deprecation warning(or any other warning suppressed with @ in front) is triggered on the page.

Actual result (*)

1. health_check.php returns 500

[m2-assistant]

Hi @wexo-team. 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-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

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

@wexo-team do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

[magento-engcom-team]

Hi @wexo-team. Thank you for your report.
The issue has been fixed in #22200 by @wexo-team in 2.3-develop branch
Related commit(s):

• 9675984b0487996de1521e2ba70d35ad7f77a788

The fix will be available with the upcoming 2.3.2 release.