Configurable stock status is not correct when using custom stock (MSI)

[dekiakbar]

Preconditions and environment

• Magento version : 2.4-develop with enterprise edition modules enabled, Magento 2.4.4 (CE), Magento 2.4.4 (EE)
• PHP8.1
• mariadb: 10.4
• elasticsearch: 7.11
• nginx: 1.19

Steps to reproduce

• crate new source in admin > store > sources, i.e : source A
• create new stock in admin > store > stock, i.e : custom stock
• assign source A to Custom stock, and also assign custom stock to main website
• create new configurable product, i.e : test product
  • add simple product to the configurable product in configuration tab
  • assign simple product to source A
  • fill quantity, i.e : 1
• and save new created configurable product. (in this step the configurable product stock = In Stock)
• now change the simple product :
  • Source Item Status : from In Stock to Out Of Stock
  • Qty : from 1 to 0
  • save simple product
• check configurable product (the stock status is still In Stock, it must be Out Of Stock)

Expected result

• The configurable product stock status must be In Stock when the child product Is In Stock and has Qty
• The configurable product stock status must be Out Of Stock when the child product is Out Of Stock
• in short, the configurable product status must be updated when a child's product status is changed.

Actual result

• The configurable product stock status is Instock even if the child product Is Out of stock
• in short, the configurable product status is not updated when the child product is updated.

Additional information

• Screen share: https://www.quicki.com/to/dekiv07t3/ae3b216d-ecbf-42a3-9b15-bfed59660746

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 @dekiakbar. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

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.

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant]

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: 👇

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

[engcom-November]

@magento give me 2.4-develop instance with edition ee

[magento-deployment-service]

Hi @engcom-November. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @engcom-November, here is your Magento Instance: https://4219886f2168b8e4dffee0cceab4b2c1.instances.magento-community.engineering
Admin access: https://4219886f2168b8e4dffee0cceab4b2c1.instances.magento-community.engineering/admin_1c46
Login: 5308e12b
Password: 45c8ee6ccd32

[engcom-November]

Hi @dekiakbar ,
Verified the issue on Magento 2.4-develop with Enterprise version and is reproducible. Hence confirming the issue.
Note: This issue is not reproducible on Magento 2.4-develop instance alone.