sample data installing wrong path /var/www/magento2/pub/media/downloadable/files/links/l/u/

skygunner commented 1 year ago

Preconditions and environment

2.4.6

Steps to reproduce

Install fresh Magento instance
Install sample data Using DevDocs

Expected result

It is looking for file /var/www/magento2/pub/media/downloadable/files/links/l/u/lumabackground-_model_against_fence_4sec.mp4

Actual result

while the actual file has been put into the wrong location which is

/var/www/magento2/pub/media/downloadable/downloadable/files/links/l/u/lumabackground-_model_against_fence_4sec.mp4

Additional information

[2023-04-13T04:20:03.546989+00:00] main.ERROR: Sample Data error: Warning: file_get_contents(/var/www/magento2/pub/media/downloadable/files/links/l/u/lumabackground-_model_against_fence_4sec.mp4): Failed to open stream: No such file or directory in /var/www/magento2/vendor/magento/module-downloadable-sample-data/Model/Product/Converter.php on line 132 [] []

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] commented 1 year ago

Hi @skygunner. Thank you for your report. To speed up processing of this issue, 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.

m2-assistant[bot] commented 1 year ago

Hi @engcom-Dash. 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).
1. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
1. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
1. 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!

Join Magento Community Engineering Slack and ask your questions in #github channel.

SPbryan007 commented 1 year ago

@magento give me 2.4.6 instance

magento-deployment-service[bot] commented 1 year ago

Hi @SPbryan007. Thank you for your request. I'm working on Magento instance for you.

magento-deployment-service[bot] commented 1 year ago

Hi @SPbryan007, here is your Magento Instance: https://08365ba70fd542fa8fd771e6d28add86.instances-prod.magento-community.engineering Admin access: https://08365ba70fd542fa8fd771e6d28add86.instances-prod.magento-community.engineering/admin_2ef9 Login: ce449f3b Password: a2ebfcce252d

engcom-Dash commented 1 year ago

Hi @skygunner ,

Verified the issue in 2.4.6 and 2.4-develop instance.The issue is reproducible in 2.4.6 and the issue is not reproducible 2.4-develop instance.

Preconditions:

Magento version 2.4.6 and 2.4-develop PHP version 8.1

Kindly refer the below screenshots: In 2.4-develop Instance:

in 2.4.6 -Magento instance

Issue can be reproducible in 2.4.6 magento instance,Sample data installed in wrong path,Hence we are confirming the issue.

Regards,

github-jira-sync-bot commented 1 year ago

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

m2-assistant[bot] commented 1 year ago

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

magento / magento2