Magento2: Install Magento 2.3.0 : Install fail with unchecked some modules

[alex4allofyou]

Preconditions (*)

1. Magento 2.3.0
2. Wampserver 3.1.6 / Windows 10
3. PHP 7.2.13
4. Apache 2.4.35
5. MySQL 5.7.23

Steps to reproduce (*)

1. Download magento 2.3.0 with Composer and open browser to get setup wizard page
2. Readiness Check approved
3. Add DB
4. Use normal settings, Magento generated key
5. Uncheck some or all additional modules, or check them all, tried every variation
6. Install

Expected result (*)

You'd expect with a clean install, an easy install.

Actual result (*)

I get error seen in the title, well, the first time i did.
Because after the error written down below I thought that maybe I needed to restart computer, that maybe some files of WAMP after upgrade PHP were not properly found,

After I did this I did not get the error below but you see the install not progressing, it stays at : Installing... 15%. Console Log shows that it hangs at: Module 'Magento_InventorySales':

The first time it did not hang but gave this message:
Unable to apply patch for module Magento_InventorySales. Original exception message: The store that was requested wasn't found. Verify the store and try again.

To be complete, this one:

Module 'Magento_InventorySales':

[magento-engcom-team]

Hi @alex4allofyou. 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-engcom-team give me $VERSION instance

where $VERSION is version tags (starting from 2.2.0+) or develop branches (for example: 2.3-develop).
For more details, please, review the Magento Contributor Assistant documentation.

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

• [ ] yes
• [ ] no

[alex4allofyou]

@magento-engcom-team give me 2.3.0 instance

[magento-engcom-team]

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

[magento-engcom-team]

Hi @alex4allofyou, here is your Magento instance.
Admin access: https://i-19882-2-3-0.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[alex4allofyou]

Did not know I had to reproduce it like this, of course I cannot, it is happening during install.

[orlangur]

@alex4allofyou,

Wampserver 3.1.6 / Windows 10

Can you reproduce an issue using a supported operating system: http://devdocs.magento.com/guides/v2.2/install-gde/system-requirements-tech.html? Please reopen then. Note that Windows is not in the list.

[alex4allofyou]

@alex4allofyou,

Wampserver 3.1.6 / Windows 10

Can you reproduce an issue using a supported operating system: http://devdocs.magento.com/guides/v2.2/install-gde/system-requirements-tech.html? Please reopen then. Note that Windows is not in the list.

I have tested it.
Yes I have the same issue with Apache/2.4.6 CentOS with PHP 7.2.13. Hangs at Magento_InventorySales. Have tried many times.

[simonspoerri]

The Problem might be that the store ID was changed through a webserver configuration before the installation. At least that was causing this problem for me. Make sure your webserver sets the MAGE_RUN_CODE to "default" (or not at all) for the URL you're using for the installation process.

[orlangur]

@alex4allofyou sorry, missed your comment. Let's recheck. If you was able to figure out a root cause, please share your findings.

[engcom-Bravo]

Hello @alex4allofyou. Update your newely Preconditions and Actual result

[m2-assistant[bot]]

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

• [ ] 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.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• [ ] 6. Add label Issue: Confirmed once verification is complete.

• [ ] 7. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

@magento give me 2.3-develop instance

[magento-engcom-team]

Hi @engcom-Bravo. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @engcom-Bravo, here is your Magento instance.
Admin access: https://i-19882-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[m2-assistant[bot]]

Hi @sdzhepa. 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: :point_down:

• [ ] 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.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• [ ] 6. Add label Issue: Confirmed once verification is complete.

• [ ] 7. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

Hi @alex4allofyou . We can't reproduce this issue.
We tried on 4 computers and we never met such a problem.
Can you give more information and maybe more steps for testing scenario?
Thanks!

[sdzhepa]

Hello @alex4allofyou

I close this issue as cannot reproduce because we are not able to reproduce it by provided steps.

[sshymko]

As @simonspoerri correctly pointed out, the issue is reproducible when non-existing store code is specified in a web server configuration.

You may have something like this in the Nginx config:

map $host $MAGE_RUN_CODE {
    default                store1;
    store1.example.com     store1;
    store2.example.com     store2;
}

The issue is the Nginx misconfiguration and the fix would be:

map $host $MAGE_RUN_CODE {
    default                "";
    store1.example.com     store1;
    store2.example.com     store2;
}