Magento2: Incorrect generate of "url_rewrite" (301) when change "url_key" more than two times

[DmitriiChukhnov1]

Preconditions

1. Magento CE 2.1.2
2. PHP 5.6.24
3. MySQL 5.7.13

Steps to reproduce

1. Create and save new visible and active product with 'url_key' = 'test-product-1';
2. Change 'url_key' to 'test-product-2' and save product again.
3. Change 'url_key' to 'test-product-3' and save product again.

Expected result

1. should be three url rewrites in table 'url_rewrite':
   
   
   
   • test-product-3.html => catalog/product/view/id/ (redirect_type = 0)
   
   
   • test-product-1.html => test-product-3.html (redirect_type = 301)
   
   
   • test-product-2.html => test-product-3.html (redirect_type = 301)
   
   

Actual result

1. only two url rewrites:
   
   
   
   • test-product-3.html => catalog/product/view/id/ (redirect_type = 0)
   
   
   • test-product-1.html => test-product-3.html (redirect_type = 301)
   
   

Bug: Url rewrite "test-product-2.html => test-product-3.html (redirect_type = 301)" is absent.

How to fix

The bug is in class \Magento\CatalogUrlRewrite\Model\ProductUrlRewriteGenerator (/vendor/magento/module-catalog-url-rewrite/Model/ProductUrlRewriteGenerator.php line 181):

We should use getRequestPath() instead of getTargetPath().

[dthampy]

We already have an internal jira ticket MAGETWO-60911, which once fixed will resolve this issue.
Thanks for your report.

[hezide]

I have the same issue on magento 2.1.6.
This ticket is since Nov 2016, what's the status of the issue?

[magento-engcom-team]

@DmitryChukhnov, thank you for your report.
The issue is already fixed in develop branch
But we will consider to backport the fix to patch releases

[magento-engcom-team]

Hi @TomashKhamlai. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if your want to validate it one more time, please, go though the following instruction:

• [x] 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [x] 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.

[TomashKhamlai]

The issue was re-tested and we can confirm that it was fixed on the 2.3 release branch. We closing this issue as fixed due to upcoming 2.3 release that will be available soon.