



I do not know how to reindex the test instance, so I am not sure if it is a indexer problem
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
Hi @amenk. Thank you for your report.
To help us process this issue please make sure that you provided the following information:
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
@magento give me 2.4-develop instance
Hi @amenk. Thank you for your request. I'm working on Magento 2.4-develop instance for you
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.
Successfully reproduced on 2.4-develop instance. See above for steps and screenshots.
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: :point_down:
Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.[x] 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.
[x] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
[x] 4. Verify that the issue is reproducible on 2.4-develop branchDetails
- 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_!
[x] 5. Add label Issue: Confirmed once verification is complete.
[x] 6. Make sure that automatic system confirms that report has been added to the backlog.
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
@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.
:white_check_mark: Confirmed by @krishprakash
Thank you for verifying the issue. Based on the provided information internal tickets MC-34444 were created
Issue Available: @krishprakash, _You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself._
I will work on this issue.
Was this solved? in which commits?
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