Magento 2.4.7-px Installation fails with Elasticsearch 8.11

[kkhebbar89]

Preconditions and environment

• Magento V 2.4.7-px
• symfony/http-client version 7.2.0 which was released on 29th November 2024 is causing Elasticsearch connection issues during installation.
• Before 29th November 2024 when Magento was installed through composer had symfony/http-client version 7.1.9. Fresh installation works fine with this.

Steps to reproduce

1. composer create-project --repository-url=https://repo.magento.com/ magento/project-community-edition .
2. composer require magento/module-elasticsearch-8 --with-all-dependencies
3. Run php bin/magento setup:install ................

Expected result

Magento Installation should be successful

Actual result

Magento Installation fails with below error.
Could not validate a connection to Elasticsearch. Verify that the Elasticsearch host and port are configured correctly.

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

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

[Eikzx]

Hello @kkhebbar89 ,

I can confirm this behavior.

A quick fix would be to add symfony/http-client version in version 7.2.0 as a conflict in the composer.json.

Running a composer update afterwards installs version 7.1.9 and magento set:up will go through.

Caution:
Removing 7.2.0 might break other parts so test everything, to be safe

[Bhavik-kumar]

@magento
I think whole M2 community affecting with this composer update, who using ES8.

[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

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

[novikor]

Not sure whether that should be handled by the Magento, however - a temporary workaround is

Adding

    "conflict": {
        "symfony/http-client": "7.2.0"
    },

To the project's root composer.json.