Configurable shows simple products which are no longer assigned to the website

[amenk]

Preconditions (*)

1. Magento 2.4-develop testinstance

Steps to reproduce (*)

1. Create additional website, store, storeview "other" in backend
2. Create Configurable with Options, assign to both websites

3. Set Quantity and in stock for each option in backend
4. Check that all 3 options are there in the frontend as expected

5. Disable option 1 in the "main website"

6. Flush caches

Expected result (*)

1. The option 1 should disappear in the Frontend

Actual result (*)

1. Option 1 is still there

Remarks

I do not know how to reindex the test instance, so I am not sure if it is a indexer problem

Additional information

I do not know how to reindex the test instance, so I am not sure if it is a indexer problem

Tested on local env. Was done full reindex and flush cache = option 1 still available on website 1

[m2-assistant]

Hi @amenk. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

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

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Add a comment to Assigning an issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[amenk]

@magento give me 2.4-develop instance

[magento-engcom-team]

Hi @amenk. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[magento-engcom-team]

Hi @amenk, here is your Magento instance.
Admin access: https://i-28291-2-4-develop.instances.magento-community.engineering/admin_0154
Login: b7a346f6 Password: e82c798245de
Instance will be terminated in up to 3 hours.

[amenk]

Successfully reproduced on 2.4-develop instance. See above for steps and screenshots.

[m2-assistant]

Hi @krishprakash. 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.

[krishprakash]

Hi @amenk.
It works fine here after re-indexing
You can re-index from System -> Tools -> Index Management -> Update on save all
Refer below screenshot:

So closing this issue

[amenk]

@krishprakash I think there is a misunderstanding. You seem to get a 404 for the configurable. But I un-assigned only one simple and expect the option to disappear. It's not about un-assigning the full configurable.

Please retest and reopen.

[amenk]

Was this solved? in which commits?

[sdzhepa]

Hello @amenk

Sorry for any inconvenience.
The issue was closed by bot too early by mistake...

As I can see this issue was fixed by Magento team and delivered with internal PR
Related commits can be found using search based on internal ticket key MC-34444
https://github.com/magento/magento2/search?q=MC-34444&type=commits