Error when setting indexer 'catalogsearch_fulltext' to 'realtime'

[densen45]

Preconditions and environment

• Magento version 2.4.7
• Elasticsearch 7 or 8 installed (error happens with both, I don't no if the same error occurs with OpenSearch)

Steps to reproduce

• Open a terminal and go to the Magento root directory
• Make sure the 'catalogsearch_fulltext' is in schedule mode ("Update by Schedule"): bin/magento indexer:show-mode and if necessary bin/magento indexer:set-mode schedule catalogsearch_fulltext
• Set the mode to realtime: bin/magento indexer:set-mode realtime catalogsearch_fulltext

Expected result

• The mode is set without errors in the log

Actual result

• The mode is set but the following error is logged in var/log/system.log:

main.CRITICAL: Type Error occurred when creating object: Magento\CatalogSearch\Model\Indexer\Fulltext\Interceptor, Magento\CatalogSearch\Model\Indexer\Fulltext\Interceptor::__construct(): Argument #7 ($data) must be of type arr
ay, null given, called in /path/to/magento/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php on line 121 [] []

Additional information

The error can also be found in the system.log if you change the indexer mode from the adminhtml.

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 @densen45. 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-Delta. 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.

[m2-assistant]

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: 👇

• 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!

---

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

[engcom-Dash]

Hi @densen45

Thanks for reporting and collaboration.

Verified the issue on Magento 2.4.7 instance and the issue is reproducable.

Preconditions and environment
Magento version 2.4.7
Elasticsearch 7 or 8 installed (error happens with both, I don't no if the same error occurs with OpenSearch)
Steps to reproduce

1. Open a terminal and go to the Magento root directory
2. Make sure the 'catalogsearch_fulltext' is in schedule mode ("Update by Schedule"): bin/magento indexer:show-mode and if necessary bin/magento indexer:set-mode schedule catalogsearch_fulltext
3. Set the mode to realtime: bin/magento indexer:set-mode realtime catalogsearch_fulltext

We are seeing the below error in system.log

main.CRITICAL: Type Error occurred when creating object: Magento\CatalogSearch\Model\Indexer\Fulltext\Interceptor, Magento\CatalogSearch\Model\Indexer\Fulltext\Interceptor::__construct(): Argument #7 ($data) must be of type arr
ay, null given, called in /path/to/magento/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php on line 121 [] []

Please refer the attached screenshots