Cache frontend 'default' is not recognized. As well as defaultcache is not configured

[technicalrajni]

Preconditions and environment

• Magento version 2.4.6
• fresh installation with php 8.1
• InvalidArgumentException: Cache frontend 'default' is not recognized. As well as defaultcache is not configured in /var/www/html/magentotest/project-community-edition/vendor/magento/framework/App/Cache/Frontend/Pool.php:157
  Stack trace:
  #0 /var/www/html/magentotest/project-community-edition/vendor/magento/framework/App/Cache/Type/FrontendPool.php(87): Magento\Framework\App\Cache\Frontend\Pool->get()
  Can you commit to repository a folder dev/tests/static ? #1 /var/www/html/magentotest/project-community-edition/vendor/magento/framework/App/Cache/Type/Config.php(49): Magento\Framework\App\Cache\Type\FrontendPool->get()
  BUG FIX - Uncaught exception when accessing admin with none existent use... #2 /var/www/html/magentotest/project-community-edition/vendor/magento/framework/Cache/Frontend/Decorator/Bare.php(65): Magento\Framework\App\Cache\Type\Config->_getFrontend()
  __DIR__ Typo fixed #3 /var/www/html/magentotest/project-community-edition/vendor/magento/framework/Interception/PluginList/PluginList.php(227): Magento\Framework\Cache\Frontend\Decorator\Bare->load()
  Enable Magento_Profiler by SetEnv #4 /var/www/html/magentotest/project-community-edition/vendor/magento/framework/Interception/PluginList/PluginList.php(190): Magento\Framework\Interception\PluginList\PluginList->_loadScopedData()
  Enable automated CRUD setup for Adminhtml Grids #5 /var/www/html/magentotest/project-community-edition/generated/code/Magento/Framework/App/State/Interceptor.php(22): Magento\Framework\Interception\PluginList\PluginList->getNext()
  Why use private for message ? #6 /var/www/html/magentotest/project-community-edition/vendor/magento/module-developer/Model/Logger/Handler/Debug.php(71): Magento\Framework\App\State\Interceptor->getMode()
  Ability to provide configuration for different environments in app/etc/local.xml #7 /var/www/html/magentotest/project-community-edition/vendor/magento/module-developer/Model/Logger/Handler/Debug.php(56): Magento\Developer\Model\Logger\Handler\Debug->isLoggingEnabled()
  Clear separation for Controller and controllers required with Full Controller path #8 /var/www/html/magentotest/project-community-edition/vendor/monolog/monolog/src/Monolog/Handler/AbstractProcessingHandler.php(31): Magento\Developer\Model\Logger\Handler\Debug->isHandling()
  Added: dispatchEvent to deleteAction(). Only existed in massDeleteAction(). #9 /var/www/html/magentotest/project-community-edition/vendor/monolog/monolog/src/Monolog/Logger.php(344): Monolog\Handler\AbstractProcessingHandler->handle()
  Merged JS/CSS improvements #10 /var/www/html/magentotest/project-community-edition/vendor/magento/framework/Logger/Monolog.php(48): Monolog\Logger->addRecord()
  Design suggestion for cross browser compitablity #11 /var/www/html/magentotest/project-community-edition/vendor/monolog/monolog/src/Monolog/Logger.php(712): Magento\Framework\Logger\Monolog->addRecord()
  core/template block should use a helper or a model #12 /var/www/html/magentotest/project-community-edition/vendor/magento/framework/Logger/LoggerProxy.php(126): Monolog\Logger->error()
  Performance Testing #13 /var/www/html/magentotest/project-community-edition/vendor/magento/framework/App/Bootstrap.php(269): Magento\Framework\Logger\LoggerProxy->error()
  Adding dispatch of an event before and after applyAllUpdates() #14 /var/www/html/magentotest/project-community-edition/pub/index.php(29): Magento\Framework\App\Bootstrap->run()
  Decrease dependencies from Mage class #15 {main}

Steps to reproduce

Install Latest magento 2 version via composer with php 8.1
After try to access the website this issue comes

Expected result

Expected it should show me the magento 2 default website

Actual result

Expected it should show me the magento 2 default website

Additional information

No response

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @rajni98. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-Bravo. 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).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.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.

[engcom-Bravo]

Hi @rajni98,

Thank you for reporting and collaboration.

Verified the issue while installing 2.4.6 magento instance we are not able to reproduce the issue. Kindly refer the screenshots.

We are able to access the default website.

Kindly let us know if you are still facing any issue.

Thanks.

[engcom-Bravo]

Hi @rajni98,

We have noticed that this issue has not been updated for a period of 14 Days.
Hence we assume that this issue is fixed now, so we are closing it. Please raise a fresh ticket or reopen this ticket if you need more assistance on this.

Thanks.