[Issue] Avoid exception when config.xml nodes exist for not-installed payment methods

[m2-assistant]

This issue is automatically created based on existing pull request: #27940: Avoid exception when config.xml nodes exist for not-installed payment methods

---

Preconditions (*)

Magento 2.4-develop
When a payment configuration node exists in XML but there is no <model> defined, getList() will throw an UnexpectedValueException. One use case for creating such a set-up is a module that provides default configuration overrides for payment methods which are not installed on the current website. For example:

<config>
  <default>
    <payment>
      <checkmo>
        <active>0</active>
      </checkmo>
      <not_installed_here>
        <debug>0</debug>
        <environment>production</environment>
      </not_installed_here>
    </payment>
  </default>
</config>

In this case, the payment method not_installed_here does not have a <model> node defined, as the payment method module is not installed on the website.

Steps to reproduce (*)

1. Add supplied XML or similar to a local module's config.xml
2. Browse to checkout with an item in basket
3. Observe (lack of) exception thrown during checkout page load

Expected result (*)

Actual result (*)

Additional information
I have not yet written/changed any unit/functional tests for this change. I suspect some existing tests may fail which I will review at a later date.

[m2-assistant]

Hi @engcom-Delta. 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.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.

[magento-engcom-team]

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

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

[magento-engcom-team]

Hi @m2-assistant[bot]. Thank you for your report.
The issue has been fixed in #27940 by @fredden in 2.4-develop branch
Related commit(s):

• 158582ac38e7749771a5acf3997a6e97ee258e7a
• 2ce21168514a6f03410cedb730bb6ad083891394
• fbd618c1dff9d62276fad8f5b6322f112f9b7937
• 38dbccf14cd629f857f19f53c05828c9d146a348
• c7658e322524daae9fa4c260f7e128782ba59863
• dfcb7b1b583b889c328b68df4ade146643a8e589
• eb80bd8d2840ea805bbd2f971d011164b68d23a5

The fix will be available with the upcoming 2.4.2 release.