Magento2: php bin/magento catalog:image:resize error if image is missing

[ioweb-gr]

Preconditions (*)

1. Magento 2.3.1

Steps to reproduce (*)

1. Delete manually a product image from pub/media/catalog folder
2. Execute catalog:image:resize

Expected result (*)

1. The system creates the resized images for all products that the images exist and lists the errors.

Actual result (*)

1. The execution halts immediately at the first missing image.

This doesn't affect on the fly generation of images when browsing the products but it's good to be able to execute and test.

[m2-assistant[bot]]

Hi @ioweb-gr. 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.

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

• [ ] yes
• [ ] no

[m2-assistant[bot]]

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

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

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

[nikunjskd20]

Hi, I am facing the same issue in Magento Commerce ver. 2.3.1

[m2-assistant[bot]]

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

[ioweb-gr]

I forgot to mention this can also happen after migrating from magento 1 because the data migration tool does not take into account a few things regarding media galleries like cleaning up catalog_entity_varchar table and magento 2 cannot handle product images where the path is not like /x/x/filename.ext but just /filename.ext. the latter can happen in older versions of m1 using csv import so this can be a problem for a lot of users who migrated

[gwharton]

How about database media storage mode, when it is valid for pub/media to be completely wiped. Make sure any solution works in this mode too.

[m2-assistant[bot]]

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

---

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

[amitvishvakarma]

imagine2019

[magento-engcom-team]

:white_check_mark: Confirmed by @sdzhepa
Thank you for verifying the issue. Based on the provided information internal tickets MC-17217, MC-17218 were created

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

[magento-engcom-team]

Hi @ioweb-gr, @k4emic, @tdgroot, @gulshanchitransh.

Thank you for your report and collaboration!

The issue was fixed by Magento team. The fix was delivered into magento/magento2:2.3-develop branch(es).
Related commit(s):

• 6a694a9bab15ab20531ffb2f70a744127611a1e3
• 6e350d1a703199ded6d872367a5668f57c9f92cb
• 3a818b218434eb8dd4961a0a8b8b20013c593c14
• 9a44da1e9b910d8c1c06f4af9e02b8db91e9ea7a

The fix will be available with the upcoming 2.3.3 release.

[gwharton]

Hmmm, those commits don't appear in 2.3-develop and they also conflict with changes that were merged into 2.3-develop in PR #23598 11 days ago. @ihor-sviziev can you take a quick look at this to make sure this is right. which commits will take precedence, the above commits, or those in #23598. 2.3-develop currently reflects the changes in #23598.

Update : OK, forget this comment. Perhaps things just hadnt updated when I viewed them. 2.3-develop now reflects both commits, with conflicts resolved.

[ihor-sviziev]

Hi,
Sorry, right now on vacation, could check it in a weak

On Fri, Jul 26, 2019 at 18:31 gwharton [e-mail] wrote:

Hmmm, those commits don't appear in 2.3-develop and they also conflict
with changes that were merged into 2.3-develop in PR #23598
https://github.com/magento/magento2/pull/23598 11 days ago.
@ihor-sviziev https://github.com/ihor-sviziev can you take a quick look
at this to make sure this is right. which commits will take precedence, the
above commits, or those in #23598
https://github.com/magento/magento2/pull/23598. 2.3-develop currently
reflects the changes in #23598
https://github.com/magento/magento2/pull/23598.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/magento/magento2/issues/22808?email_source=notifications&email_token=AAOJOUICAL5RLV5TYONSZSDQBMKEBA5CNFSM4HL2COO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD246ALY#issuecomment-515498031,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOJOUII24QICBJ27X6TTCLQBMKEBANCNFSM4HL2COOQ
.

[gwharton]

@ihor-sviziev . Don't worry. a check of 2.3-develop around 10 minutes later showed it had been merged and conflicts resolved so we're all good. Well, apart from the fact that the conflicts weren't resolved correctly and the bug that #23598 fixed is now broken again, but thats another issue, for another PR, for another day. :)