Allowed Countries does not work correctly

[zhovnirigor]

Preconditions and environment

1. Magento version 2.4.6-p3
2. Share Customer Accounts (customer/account_share/scope) = Global
3. Allowed countries (general/country/allow) in the default website (for instance, British Website) are set to set X (for instance, United Kingdom only).
4. Allowed countries (general/country/allow) in any other website (for instance, Irish Website) are set to set Y (for instance, Ireland only).
5. Create a customer in the Store View that does not belong not to default website (for instance, create it in any store that belongs to Irish Website).
6. Assign some address to the previously created customer with the country that is allowed not only not in the default website (for instance, with the country Ireland).

Steps to reproduce

First case:

1. Do a PUT request to the /rest/V1/customers/[customer_id], where [customer_id] is the entity_id of the customer created on the 5th step of preconditions.

Another case:

1. In the admin panel, edit the customer created on the 5th step of preconditions.
2. Go to the tab Addresses
3. Click Edit on the address created on the 6th step of preconditions.

Expected result

First case:

PUT request is executed without any errors

Another case:

Country field is present and contains all the available values (so United Kingdom and Ireland, for example).

Actual result

First case:

An error occurred 'Invalid value of "IE" provided for the countryId field.'

Another case:

Country field is not present at all.

Additional information

Fixed in #38182

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 @zhovnirigor. 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.

[zhovnirigor]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @zhovnirigor. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @zhovnirigor, here is your Magento Instance: https://7731cb2cb3d426ed681353fa21ec77a2.instances-prod.magento-community.engineering
Admin access: https://7731cb2cb3d426ed681353fa21ec77a2.instances-prod.magento-community.engineering/admin_4f6e
Login: d99e5885
Password: 2c3aa38da679

[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.