Database Media Storage - Admin Product Edit page does not handle product images correctly in database storage mode

[gwharton]

Preconditions (*)

1. Magento 2.2-develop or 2.3-develop

Steps to reproduce (*)

1. Vanilla install of 2.2-develop or 2.3-develop
2. Change mode to database storage, synchronise and save settings
3. Add new product and assign an image
4. Save the product
5. Verify that the image is present in the filesystem (2.3-develop will fail this test due to [2.3] Database Media Storage - New Product Images fail to be processed correctly #21546. Don't worry, carry on the test as we are going to clear the images anyway in Step 8)
6. Edit the product and view the images section. Verify image displays correctly in the images and videos section. (2.3-develop will fail this test due to [2.3] Database Media Storage - New Product Images fail to be processed correctly #21546. Don't worry, carry on the test as we are going to clear the images anyway in Step 8)
7. Now simulate running on a new node in a cluster by clearing pub/media/catalog
8. Now refresh the product edit page.
9. Verify that the product image is still shown correctly

Expected result (*)

1. When the admin page is refreshed, Magento should realise we are in database storage mode, and see that the image does not exist locally in pub/media/catalog. It should be copied from the database to local storage and then should be displayed on the product edit page.

Actual result (*)

1. Placeholder image is shown with 0 size.

[magento-engcom-team]

Hi @gwharton. 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-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

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

@gwharton do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

[magento-engcom-team]

Hi @engcom-backlog-nazar. 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.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• Next steps are available in case you are a member of Community Maintainers.

• 6. Add label Issue: Confirmed once verification is complete.

• 7. Make sure that automatic system confirms that report has been added to the backlog.

[magento-engcom-team]

✅ Confirmed by @engcom-backlog-nazar
Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-98608, MAGETWO-98609 were created

Issue Available: @engcom-backlog-nazar, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.