Product with any custom option causes an error when deleting product images

[ksenia-zlotin]

Preconditions and environment

• Magento 2.4.4

Steps to reproduce

1. create any product with any custom option and save.
2. add a product image with any role or no roles at all and save.
3. delete the product image and save

Expected result

Product is saved, image is deleted and no error or warning messages are shown

Actual result

Product is saved, image is deleted but an error/warning message is shown, stating: "The image cannot be removed as it has been assigned to the other image role"

Additional information

This seems to solely happen to products with custom options.

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.
• [X] 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[bot]]

Hi @ksenia-zlotin. 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.

  :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

:clock10: You can find the schedule on the Magento Community Calendar page.

:telephone_receiver: 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.

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

[m2-assistant[bot]]

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

• [ ] 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-Bravo]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

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

[magento-deployment-service[bot]]

Hi @engcom-Bravo, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[engcom-Bravo]

Hi @ksenia-zlotin,

Thank you for reporting and collaboration.

Verified the issue on Magento 2.4-develop instance and the issue is not reproducible.Kindly refer the screenshots.

Steps to reproduce

1.create any product with any custom option and save. 2.add a product image with any role or no roles at all and save. 3.delete the product image and save.

Could you please try with these steps.

Go to Stores > Attributes > Product
Change Scope to "Global" for the following attributes:

• image
• small_image
• swatch_image
• thumbnail

Kindly recheck the behavior on Magento 2.4-develop instance and elaborate steps to reproduce if the issue is still reproducible.

Thanks.

[ksenia-zlotin]

@engcom-Bravo It does not look like you actually added a custom option based on the screenshots provided. For me - it also works when no custom option is added. Please retest with a custom option added, as seen in this attached screenshot:

[engcom-Bravo]

Hi @ksenia-zlotin,

Thanks for your Update.

Verified the issue on Magento 2.4-develop instance and the issue is reproducible.Kindly refer the screenshots.

Steps to reproduce

1.create any product with any custom option and save. 2.add a product image with any role or no roles at all and save. 3.delete the product image and save.

Product is saved successfully and image also deleted.but warning message is shown.

Product without custom options we are not getting any warning message.

Hence confirming this issue.

Thanks.

[github-jira-sync-bot]

:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-7384 is successfully created for this GitHub issue.

[m2-assistant[bot]]

:white_check_mark: Confirmed by @engcom-Bravo. Thank you for verifying the issue.
Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[adamphh]

@magento I am working on this

[adamphh]

@magento run all tests

[CGLOB]

Internal team is working on it.

[chittima]

Here is the commit id : https://github.com/magento/magento2/commit/423cd2a2466167e929efa1cfbf8eb4821489a714

[hostep]

Commit mentioned above seems to be too broad, it contains many other tickets as well. I think the following commits are the correct ones: https://github.com/magento/magento2/search?q=ACP2E-1479&type=commits, but no clean merge commit unfortunately :(

[INPVLSA]

Still actual on 2.4.6-p3

Commit mentioned above seems to be too broad, it contains many other tickets as well. I think the following commits are the correct ones: https://github.com/magento/magento2/search?q=ACP2E-1479&type=commits, but no clean merge commit unfortunately :(

Unfortunately, there are only error messages snoozing on product saving here:

• https://github.com/magento/magento2/commit/58d133817c3df821d2ec5ecfbe7d9178ec1ecdd8
• https://github.com/magento/magento2/commit/ae0678ea17b5ce2511ee7fd9c1ff7746ffdd0285

As a result - no message "The image cannot be removed as it has been assigned to the other image role" after saving the product, but the image still exists for the product