Search query throwing error in all case.

[deepaksnair]

Preconditions (*)

1. Magento 2.4 Develop

Steps to reproduce (*)

1. Search anything (greater than 3 letter), throws exception.

Expected result (*)

1. Should search and show the results.

Actual result (*)

1. Throwing exception and creating log

I have checked this on local fresh environment also on magento 2.4 developer instance provided by magento.

Solution

The issue must be solved by adding full reindex execution at the very end of the Magento installation process.

[m2-assistant]

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

@deepaksnair do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

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

[deepaksnair]

@magento give me 2.4-develop instance

[magento-engcom-team]

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

[magento-engcom-team]

Hi @deepaksnair, here is your Magento instance.
Admin access: https://i-26520-2-4-develop.instances.magento-community.engineering/admin_eaeb
Login: 00352191 Password: 9645a8e7a959
Instance will be terminated in up to 3 hours.

[m2-assistant]

Hi @shikhamis11. 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).

  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.

[magento-engcom-team]

✅ Confirmed by @shikhamis11
Thank you for verifying the issue. Based on the provided information internal tickets MC-30767 were created

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

[ajithkumar-maragathavel]

@magento give me 2.4-develop instance

[magento-engcom-team]

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

[magento-engcom-team]

Hi @ajithkumar-maragathavel, here is your Magento instance.
Admin access: https://i-26520-2-4-develop.instances.magento-community.engineering/admin_53ef
Login: 0881875e Password: 79b45c776599
Instance will be terminated in up to 3 hours.

[ramesh-durairajaram]

@magento give me 2.4-develop instance

[magento-engcom-team]

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

[magento-engcom-team]

Hi @ramesh-durairajaram, here is your Magento instance.
Admin access: https://i-26520-2-4-develop.instances.magento-community.engineering/admin_7919
Login: 3c73da5a Password: fcdb398c71d1
Instance will be terminated in up to 3 hours.

[m2-assistant]

Hi @ramesh-durairajaram. 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.

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

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

[Usik2203]

@magento give me 2.4-develop instance

[magento-engcom-team]

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

[magento-engcom-team]

Hi @Usik2203, here is your Magento instance.
Admin access: https://i-26520-2-4-develop.instances.magento-community.engineering/admin_d597
Login: 448fdece Password: c12d5625fa00
Instance will be terminated in up to 3 hours.

[ramesh-durairajaram]

Hi @akaplya,
Please find the issue and cause for #26520

Issue: catalogsearch_fulltext_scope1 table is not found in database after a fresh installation of 2.4-develop branch. Hence search query not able to be completed.

Cause: This table was created when re-indexing is triggered during installation. Your commit c4c36dc to Removed force reindex from the database patch is preventing the re-indexing trigger during installation.

Kindly advice how to proceed.

[novikor]

@ramesh-durairajaram, please check my reply to your PR . Thank you for your collaboration.

[m2-assistant]

Hi @ramesh-durairajaram. 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.

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

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

[novikor]

As discussed in #appdesign Slack channel:
The issue must be solved by adding full reindex execution at the very end of the Magento installation process.

[magento-engcom-team]

Hi @deepaksnair, @novikor, @ramesh-durairajaram.

Thank you for your report and collaboration!

The related internal Jira ticket MC-30767 was closed as non-reproducible in 2.4-develop.
It means that Magento team either unable to reproduce this issue using provided Steps to Reproduce from the Description section on clean Magento instance or the issue has been already fixed in the scope of other tasks.

But if you still run into this problem please update or provide additional information/steps/preconditions in the Description section and reopen this issue.