Magento2: Product CSV import error report file missing

[mischabraam]

Preconditions (*)

1. Magento 2.3.5-p1
   2.

Steps to reproduce (*)

1. Import a product CSV which will generate errors like a not existing path to an image.
2.

Expected result (*)

1. An error_report.csv file with the errors generated in the import.
   2.

Actual result (*)

1. No file..... the file is generated, but will be removed after the application ends.
   2.

The following causes this problem, see my comment in the destructor.
https://github.com/magento/magento2/commit/bc06501851838ca9a07a3fc437b778c46366b4e9?diff=split#r39524421

Additional information

• detailed steps during confirmation on 2.4-develop https://github.com/magento/magento2/issues/28420#issuecomment-635893447
  

  - https://github.com/magento/magento2/issues/28420#issuecomment-635900690

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• [x] 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._
• [ ] 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 @mischabraam. 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 give me 2.4-develop instance - upcoming 2.4.x release

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

Please, add a comment to assign the issue: @magento I am working on this

---

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

[m2-assistant[bot]]

Hi @swathishs. 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.

[swathishs]

@magento give me 2.4-develop instance

[magento-engcom-team]

Hi @swathishs. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[magento-engcom-team]

Hi @swathishs, here is your Magento instance.
Admin access: https://i-28420-2-4-develop.instances.magento-community.engineering/admin_70b5
Login: 014ba51e Password: ccb37a638d04
Instance will be terminated in up to 3 hours.

[swathishs]

@mischabraam: The issue is reproducible in Magento 2.4-develop instance

Please find the attachment below:

1.Check the data

1. After import
   
2. Click on error file
   
   Viedo -
   

[mischabraam]

Yes, I saw the commit I mentioned is also in de 2.4-develop branch.

[magento-engcom-team]

:white_check_mark: Confirmed by @swathishs
Thank you for verifying the issue. Based on the provided information internal tickets MC-34741 were created

Issue Available: @swathishs, _You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself._

[mischabraam]

Don't know if this helps or not, but see screenshot above.

[m2-assistant[bot]]

Hi @engcom-Charlie. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• 
  
  1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components 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_!
• 1. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

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

[magento-engcom-team]

Hi @mischabraam. Thank you for your report.
The issue has been fixed in magento/magento2#28460 by @engcom-Charlie in 2.4-develop branch
Related commit(s):

• d4d8ef48391fdff05c9fce5d1cf013dff40d724d
• 597d65f0721e3de11d2e3f2c2a39e6490f90eb8b

The fix will be available with the upcoming 2.4.1 release.

[aheadcreative]

Same issue - NOT fixed in 2.3.5-p1

[alejandrocastanon]

Same issue - NOT fixed in 2.3.5-p1

[aheadcreative]

Same issue - NOT fixed in 2.3.5-p1

[Lukas713]

Same issue - NOT fixed in 2.3.5-p2

[RonakParmar]

I have same issue in 2.3.5-p1. Is there any patch available ?

[camachogfelipe]

I have same issue in 2.3.5-p2

[jpkileaf]

is it solved?

[Jeevachezhiyan]

Is it resolved? Facing same issue in 2.3.5-p1.

I tried this fix in 2.3. But, not working.

https://github.com/magento/magento2/commit/bd208cc3173697470729a53761872a45e6ad645a

[magento-seis10]

Facing same issue in 2.3.5-p2