Magento 2.2.0 One page checkout initial postage calculation ignores "default country" using table rate shipping.

[XOR37H]

Magento 2.2.0 When using table rate shipping the shipping cost shown initially on the one page checkout defaults to US shipping table rate price irrespective of the default country being set to United Kingdom.

Our store is based in the UK and has a domestic table rate shipping cost of £5.20, the default country is set to 'United Kingdom' one page checkout correctly sets the country in the dropdown, however the initial postage price shown is £18.20 our USA table rate price, initially showing the incorrect (higher price) is off putting to customers.

Preconditions

1. Magento CE 2.2.0
2. PHP 7.0.24
3. Nginx 1.10.2
4. tablerates.csv example

Country,Region/State,Zip/Postal Code,Weight (and above),Shipping Price
USA,*,*,0,1
GBR,*,*,0,2
*,*,*,0,3

Steps to reproduce

1. Set Default country to "United Kingdom".
2. Setup table rate shipping.
3. Add item to cart.
4. Proceed to one page checkout.
5. Default country is set automatically to "United Kingdom" as expected.
6. The initial shipping price displayed is that of the USA but should be the UK.
7. Deselect then reselect "United Kingdom" the shipping price refreshes correctly.

Expected result

1. Initial (table rate) shipping price shown on one page checkout should be the shipping price of the "default country" or it should not display any shipping price until a valid country is selected.

Actual result

1. Despite the default country (United Kingdom) being correctly set in the one page checkout country dropdown, the Initial shipping price shown incorrectly defaults to the USA table rate shipping price.

2. Deselecting then reselecting the country (United Kingdom) refreshes the price correctly.

[magento-engcom-team]

@XOR37H, thank you for your report.
We've acknowledged the issue and added to our backlog.

[AleksLi]

@magento-engcom-team I would like to have this issue, but I can't assign it to me. Please take a look at my permissions.

[magento-engcom-team]

Hi @AleksLi. 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.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!

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

• 4. If the issue is not relevant or is not reproducible any more, feel free to close it.