Performing Product Resource save action on frontend area invalidates cache of all products

[adamwaclawczyk]

Preconditions and environment

Magento version containing these three lines: https://github.com/magento/magento2/blame/fab20b001d40ec34560751e1986d93c227714d19/app/code/Magento/Catalog/Model/Product.php#L2408

Steps to reproduce

1. Enable debug logging for monitoring cache invalidation log entries
2. Create a new module
3. Create a frontend area router and Controller e.g. custom/index/index
4. Implement product saving action in Controller
5. Use $product->save() or $productResource->save($product) (check using both to confirm)
6. Start monitoring cache_invalidate entries e.g. with tail -f -n 0 var/log/debug.log | grep "cache_invalidate"

Expected result

Only the related cache tags are invalidated

Actual result

cat_p cache tag is included in logs due to

magento2/lib/internal/Magento/Framework/Model/AbstractModel.php

Line 846 in fab20b0

public function cleanModelCache()

https://github.com/magento/magento2/blame/fab20b001d40ec34560751e1986d93c227714d19/app/code/Magento/Catalog/Model/Product.php#L2408

Additional information

No response

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.
• 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]

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

• 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.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 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]

Hi @engcom-November. 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).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - 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.

[m2-assistant]

Hi @engcom-Hotel. 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).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - 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.

[engcom-Hotel]

Hello @adamwaclawczyk,

Thanks for the report and collaboration!

After going through with the issue description and tried to reproduce it in the latest development branch i.e. 2.4-develop, it seems the behaviour is expected. The cat_p cache tag is invalidated in several scenarios:

• When any product is saved, updated, or deleted
• When product attributes change
• When product prices are updated
• During certain indexing operations related to products

Please let us know if we missed anything in getting the issue.

Thanks