Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Install 2.4.6-p8 (also 2.4.7-p3) Unable to apply patch #39514

Open
1 of 5 tasks
hdezela opened this issue Dec 30, 2024 · 1 comment
Open
1 of 5 tasks

Install 2.4.6-p8 (also 2.4.7-p3) Unable to apply patch #39514

hdezela opened this issue Dec 30, 2024 · 1 comment
Labels
Issue: ready for confirmation Reported on 2.4.7-p3 Indicates original Magento version for the Issue report.

Comments

@hdezela
Copy link

hdezela commented Dec 30, 2024

Preconditions and environment

  • Magento 2.4.6-p8 / 2.4.7-p3
  • ArchLinux December 2024
  • PHP 8.2.26
  • Nginx 1.26.2
  • MariaDB 10.6.20
  • Redis 7.2.5
  • Opensearch 2.12.0
  • Composer 2.7.9

Steps to reproduce

  1. composer create-project --repository-url=https://repo.magento.com/ magento/project-community-edition=2.4.6-p8
  2. bin/magento setup:install --base-url=https://[redacted] --db-host=localhost --db-name=[redacted] --db-user=[redacted] --db-password=[redacted] --admin-firstname=[redacted] --admin-lastname=[redacted] --admin-email=[redacted] --admin-user=[redacted] --admin-password=[redacted] --language=es_ES --currency=CLP --timezone=America/Santiago --use-rewrites=1 --search-engine=opensearch --opensearch-host=[redacted] --opensearch-port=[redacted] --opensearch-index-prefix=magento2 --opensearch-timeout=15

Expected result

Magento installs

Actual result

Installation fails at:

[Progress: 115 / 1331]
Module 'Magento_InventorySales':

with error:

In PatchApplier.php line 251:

Unable to apply patch Magento\InventorySales\Setup\Patch\Schema\InitializeWebsiteDefaultSock for module Magento_InventorySales. Original exception message: The default website isn't defined. Set the website and try again.

Screenshot 2024-12-30 011935

Additional information

I have tried all the fixes shown in this issue but none of them work. I've also tried the patches supplied in this thread and it also does not work.

I've tried disabling the module but it locks out due to dependencies, and patching it to omit the step creates another chain of errors. Also hardcoding the default website in the code so it's not looked up also fails.

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”.
Copy link

m2-assistant bot commented Dec 30, 2024

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


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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: ready for confirmation Reported on 2.4.7-p3 Indicates original Magento version for the Issue report.
Projects
Status: Ready for Confirmation
Development

No branches or pull requests

2 participants