Catalog Search index process error during indexation process

[LukaszZabielskiMonogo]

Preconditions and environment

• Magento 2.4.6-p5 Open Source
• PHP 8.2

Steps to reproduce

1. Create Bundle product with simple product option. Simple product option with numeric SKU for example: 10007.
2. Try Reindex - Catalog Search Index via console.

Expected result

Catalog Search index has been rebuilt successfully

Actual result

Catalog Search index process error during indexation process:
Magento\InventorySales\Model\IsProductSalableCondition\IsProductSalableConditionChain::execute(): Argument #1 ($sku) must be of type string, int given, called in /code/vendor/magento/module-inventory-sales/Model/AreProductsSalable.php on line 48

Additional information

Patch to resolve problem.

$isSalable = $this->isProductSalable->execute($sku, $stockId);
$isSalable = $this->isProductSalable->execute((string)$sku, $stockId);

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 @LukaszZabielskiMonogo. 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.
⚠️ 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-Bravo. 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

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

[SerhiiMandrykin]

@magento give me 2.4.7 instance

[magento-deployment-service]

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

[magento-deployment-service]

Hi @SerhiiMandrykin, here is your Magento Instance: https://87b72d2c6d2dac86e5b16fe43ac771ea.instances-prod.magento-community.engineering
Admin access: https://87b72d2c6d2dac86e5b16fe43ac771ea.instances-prod.magento-community.engineering/admin_f54f
Login: 4806e4a1
Password: 6afbcfc3e974

[LukaszZabielskiMonogo]

@SerhiiMandrykin i can't reproduce on Magento 2.4.7 instance. I try to reproduce with option "Update by schedule", everthing is all right. Can you try reproduce via console command: bin/magento indexer:reindex catalogsearch_fulltext

Maybe it's the custom module on my local 2.4.6-p5 instance, or the bug in 2.4.7 has been fixed.

[engcom-Bravo]

Hi @LukaszZabielskiMonogo,

Thanks for your reporting and collaboration.

We have verified the issue in Latest 2.4-develop instance and the issue is not reproducible.Kindly refer the screenshots.

Steps to reproduce

• Create Bundle product with simple product option. Simple product option with numeric SKU for example: 10007.
• Try Reindex - Catalog Search Index via console.

Catalog Search index has been rebuilt successfully

It might be possible the issue has been fixed in Latest branch and please check any third party modules causing the issue.

Thanks.

[LukaszZabielskiMonogo]

Thanks for checking, the issue is not reproducible on Magento 2.4.7. I closed the issue.