Shipment methods for backend order don't show on multistore setup

[haelbichalex]

Preconditions (*)

1. Magento 2.3.0
2. Commerce and Community

Steps to reproduce (*)

1. Create new Magento 2 Setup
2. Setup second website, store and store view
3. Enable only Flat Rate for first website
4. Enable only Free Shipping for second website
5. Create simple product and assign it to both websites
6. Create backend order for second shop and add the product there
7. Click on "Get shipping methods and rates"

Expected result (*)

1. Only shows "Free Shipping"

Actual result (*)

1. Only shows "Flat Rate"

The behavior itself was quite weird. I described one example here to make clear what I'm talking about, but there are some more examples for configurations which show the incorrect shipping methods.

Any help would be appreciated :-)
Regards

[magento-engcom-team]

Hi @haelbichalex. 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 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

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

• yes
• no

[haelbichalex]

@magento-engcom-team give me 2.3-develop instance

[magento-engcom-team]

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

[magento-engcom-team]

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

[magento-engcom-team]

Hi @engcom-backlog-nazar. 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.3-develop branch

  Details

  - Add the comment @magento-engcom-team 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-engcom-team 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

• Next steps are available in case you are a member of Community Maintainers.

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

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

[haelbichalex]

I was not able to reproduce this on the 2.3-develop system. Was this already fixed?

[ghost]

HI @haelbichalex thank you for you report, seems like this was fixed here -> #16604

[haelbichalex]

@magento-engcom-team give me 2.3.0 instance

[magento-engcom-team]

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

[magento-engcom-team]

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

[haelbichalex]

I fixed this on my 2.3.0 setup by following the guide to apply composer patches here:
https://support.magento.com/hc/en-us/articles/360005484154-Create-a-patch-for-a-Magento-2-Composer-installation-from-a-GitHub-commit

I added two patches to my composer.json:

"extra": {
    "magento-force": "override",
    "composer-exit-on-patch-failure": true,
    "patches": {
        "magento/module-quote": {
            "Fix issue getting rates while placing order from Admin panel - part 1": "patches/composer/patch1.diff",
            "Fix issue getting rates while placing order from Admin panel - part 2": "patches/composer/patch2.diff"
        }
    }
}

Those patches are:

1. b35b681
2. cc00197