Issue with Image roles in Environment with Multiple Store Views and Unchecked "Use Default" Attribute

[carlosyrm]

Preconditions and environment

• 2.4.4-p4
• Clean environment (just magento)

Steps to reproduce

Starting with a clean Magento installation, follow these steps:

1. Create a new store view.
2. Create a new simple product and add an image to it.
3. Navigate to the frontend and verify that the product is visible in all store views.
4. In the backend, edit the product and change the store view to a particular store view.
5. Modify an attribute, such as the name, specifically for that store view. Click "Save".
6. On the frontend, navigate through all store views and verify that the attribute is different in the selected store view.
7. In the backend, edit the product and select "All Store Views". Upload a new image and click "Save".
8. Check the frontend in all store views to ensure the new image is displayed.
9. Edit the product using the "All Store Views" option and update all roles to the new image. Click "Save".
10. Delete the first image and click "Save".

Expected result

Two expected results:

1. As result of step 9, the image should take the same roles in all store views.
2. As result of step 10, the image should be deleted.

Actual result

Two actual results:

1. Result of Step 9: In the edited store view from steps 4 and 5, the image retains the initial roles and does not reflect the last roles that were set in the "All Store Views" option.
2. Result of Step 10: The backend prevents the deletion of the image because it is still being used in other roles or contexts.

Additional information

It doesn't matter if the same steps are accomplished using the API.

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