Database Media Storage - Transaction emails logo not used when pub/media cleared

[gwharton]

Preconditions (*)

1. 2.2-develop or 2.3-develop

Steps to reproduce (*)

1. Setup Magento
2. Change media storage mode to database
3. Synchronize
4. Save Settings
5. Set store General Contact email address to valid email
6. Set email logo (Content->Configuration->Edit->Transactional Emails)
7. Clear Cache
8. Verify email logo exists in database <- This will fail here due to Database Media Storage - Design Config fails to save transactional email logo correctly #21672
9. Verify email logo exists in pub/media
10. On Frontend, subscribe to newsletter
11. Verify newsletter email contains logo
12. Clear pub/media, simulating a new cluster node being used
13. On Frontend, subscribe to newsletter (need to use new email address, or delete 1st address in backend first)
14. Verify newsletter email contains logo

Expected result (*)

1. Transactional email should use the configured email logo image

Actual result (*)

1. Transactional email uses LUMA default logo

[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

[gwharton]

Note : Until #21672 is fixed this issue is not able to be reproduced. The symptom is the same to the end user, but bug #21672 steps in and breaks things as you are uploading the image to the design config. Once #21672 has been addressed, this issue can be successfully reproduced and progressed.

[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-98659, MAGETWO-98660 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.