2.2.6 Products with global Tier Prices cannot be updated

[davidverholen]

Preconditions

1. Magento 2.2.6

Steps to reproduce

1. Set Price Scope to Website (Stores -> Configuration -> Catalog -> Catalog -> Prices)
2. Create a Product that has at least one tier price with global scope (all websites)
3. Save Product
4. Try to update Product (reproduced via Rest API - without even sending new tier prices - and Backend Save)

Expected result

1. Product Values are updated

Actual result

1. Exception: Unique constraint violation

The Problem seems to be here:
https://github.com/magento/magento2/blob/2.2.6/app/code/Magento/Catalog/Model/Product/Attribute/Backend/TierPrice/UpdateHandler.php#L86

While the Interface defines int as return type (not strict, only per type hint), the actual model behind the interface also allows string and returns a string.

As a result $isGlobal is false (although it should be true) because of strict comparison.

This leads to the $old array being empty and finally to Magento trying to insert the values although they already exist in the db (which then causes the Unique Constraint Violation error).

An elegant workaround with a plugin on getWebsiteId (cast value to int) seems very risky if in some other place the system expects it to be a string.

[magento-engcom-team]

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

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

• yes
• no

[davidverholen]

@magento-engcom-team give me 2.2.6 instance

[magento-engcom-team]

Hi @davidverholen. Thank you for your request. I'm working on Magento 2.2.6 instance for you

[magento-engcom-team]

Hi @davidverholen, here is your Magento instance.
Admin access: https://i-18154-2-2-6.engcom.dev.magento.com/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 G1 Passed will be added to the issue automatically. Please, edit issue description if needed, until label G1 Passed appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add G2 Passed 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

• 6. Add label acknowledged once verification is complete.

• 7. Make sure that automatic system confirms that report is acknowledged.

[davidverholen]

@engcom-backlog-nazar could not reproduce it on vanilla instance so far. investigating further

[davidverholen]

ok there is another precondition, added it to the issue:
the price scope in the store configuration has to be set to website

[davidverholen]

changed the config on https://i-18154-2-2-6.engcom.dev.magento.com/ and now could reproduce it there