Imposible to reorder configurable products with optional custom options

[Axel29]

Preconditions

1. Magento >= 2.4.2 (not tested on older versions)

Steps to reproduce

1. Create a configurable product
2. Add a custom option of type select (drop down) and set it as optional (Uncheck Required field)
3. Order this product without choosing any custom option (as it is optional) from front end
4. Try to reorder from the admin view - Sales - Orders - View Order - Click on Reorder
5. Error message displayed and clicking on Submit Order - Does not work - Issue
   Temporary workaround: Click on Configure button - do not select anything - click OK and submit order - Order is created - No issue

Expected result

1. The reorder page is shown without any error and it is possible to reorder

Actual result

1. An error message is shown at the configurable product: Some of the selected options are not currently available.

Additional information

From what I've debugged, it seems like the issue is caused by the method \Magento\Catalog\Model\Product\Option\Type\Select::getEditableOptionValue.

This one doesn't check if the custom option is required or optional.

Thus, when fetching the value with $_result = $option->getValueById($_value);, which is null, the else statement is reached and then a $this->getListener()->setHasError(true)->setMessage($this->_getWrongConfigurationMessage()); is set.

Finally, this triggers the error in \Magento\Quote\Model\Quote\Item\AbstractItem::checkData because of the if ($this->getProduct()->getHasError()) { ... } condition.

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

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

[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://416f8f8c1f2159c88948540136bf23aa.instances.magento-community.engineering
Admin access: https://416f8f8c1f2159c88948540136bf23aa.instances.magento-community.engineering/admin_7547
Login: e95c7110
Password: d0ab81e22fb8

[engcom-November]

Verified the issue on Magento 2.4-develop branch and the issue is reproducible. Updating the description: steps to reproduce and temporary workaround.

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.magento.com/browse/AC-2998 is successfully created for this GitHub issue.