Error after installing security patch update 2.4.6-p4

[RobertSokolovSW]

Preconditions and environment

• Magento version 2.4.6 Enterprise Edition

Steps to reproduce

1. Install Magento 2.4.6-p4 using composer command composer require-commerce magento/product-enterprise-edition:2.4.6-p4 -W
2. Run bin/magento setup:db:status or bin/magento setup:upgrade

Expected result

No error is shown

Actual result

In AbstractFactory.php line 264:

Missing required argument $environments of Magento\AdobeIoEventsClient\Model\Config\Env\EnvironmentConfigFactory.

Additional information

Release note

No response

Triage and priority

• [X] 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[bot]]

Hi @RobertSokolovSW. 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. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: 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[bot]]

Hi @engcom-November. 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: :point_down:

• [ ] 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-November]

Hello @RobertSokolovSW,

Thank you for the report and collaboration!

We tried to verify this issue while upgrading from 2.4.6 to 2.4.6-p4, but in our case it's not reproducible.

Please take a look at the screenshot below: We did not get any issue while running bin/magento setup:db:status or bin/magento setup:upgrade.

Please let us know if we are missing anything.

Thank you.

[RobertSokolovSW]

Hello @engcom-November

I am experiencing this error on a clean Magento installation. And this error also breaks the deployment pipeline on our test instance. Which means it is not something related to my machine.

I will provide you with anything you would require for reproducing this issue on your end. Right now, I don't know the reason why you can't reproduce it, but the error came with the security patch update for us.

Thank you.

[engcom-November]

Hello @RobertSokolovSW,

Could you please check if any third party module is causing this issue or is it a core issue, and give us exact steps to reproduce if applicable.

Thank you.

[RobertSokolovSW]

Hello @engcom-November

The issue was caused by cache and was resolved by disabling Magento cache and re-enabling it afterwards.