[FW][FIX] stock: add an automated way to fix unreserve issue#81127
Closed
[FW][FIX] stock: add an automated way to fix unreserve issue#81127
Conversation
Contributor
|
|
Contributor
Author
|
Ping @amoyaux, @Whenrow cherrypicking of pull request #79180 failed. stderr: Either perform the forward-port manually (and push to this branch, proceeding as usual) or close this PR (maybe?). In the former case, you may want to edit this PR message as well. |
It happens that the `stock.quant.reserved_quantity` and `stock.move.line.product_qty` for the same parameters are not equals (due to some bugs in the past) It could implies that it doesn't exist enough reserved quantity on the quant when a user try to unreserve a stock.move.line resulting in the UserError 'It is not possible to unreserve more products of %s than you have in stock' However on current stable version (13.0 and 14.0) a lot of PR already fixed a lot of issue as: odoo#69377 odoo#66347 odoo#61758 odoo#54355 odoo#43180 odoo#70975 for example (there is more than that) So the idea is to provide a way to unlock the database manually for stable but not in the new version to be able to analyse them and find possible bugs responssible for the desynchronization. The server action check all the quants and their relative move line to check if match correctly. If not it will remove the reservation from both. It could remove the reservation from some `pickings` and `stock.move` related to odoo#62139 X-original-commit: d99e173
500e84b to
911a38f
Compare
Contributor
|
robodoo r+ |
robodoo
pushed a commit
that referenced
this pull request
Dec 9, 2021
It happens that the `stock.quant.reserved_quantity` and `stock.move.line.product_qty` for the same parameters are not equals (due to some bugs in the past) It could implies that it doesn't exist enough reserved quantity on the quant when a user try to unreserve a stock.move.line resulting in the UserError 'It is not possible to unreserve more products of %s than you have in stock' However on current stable version (13.0 and 14.0) a lot of PR already fixed a lot of issue as: #69377 #66347 #61758 #54355 #43180 #70975 for example (there is more than that) So the idea is to provide a way to unlock the database manually for stable but not in the new version to be able to analyse them and find possible bugs responssible for the desynchronization. The server action check all the quants and their relative move line to check if match correctly. If not it will remove the reservation from both. It could remove the reservation from some `pickings` and `stock.move` related to #62139 closes #81127 X-original-commit: d99e173 Signed-off-by: William Henrotin (whe) <whe@odoo.com> Signed-off-by: Arnold Moyaux <arm@odoo.com>
odooaktiv
pushed a commit
to odooaktiv/odoo
that referenced
this pull request
Jun 13, 2022
It happens that the `stock.quant.reserved_quantity` and `stock.move.line.product_qty` for the same parameters are not equals (due to some bugs in the past) It could implies that it doesn't exist enough reserved quantity on the quant when a user try to unreserve a stock.move.line resulting in the UserError 'It is not possible to unreserve more products of %s than you have in stock' However on current stable version (13.0 and 14.0) a lot of PR already fixed a lot of issue as: odoo#69377 odoo#66347 odoo#61758 odoo#54355 odoo#43180 odoo#70975 for example (there is more than that) So the idea is to provide a way to unlock the database manually for stable but not in the new version to be able to analyse them and find possible bugs responssible for the desynchronization. The server action check all the quants and their relative move line to check if match correctly. If not it will remove the reservation from both. It could remove the reservation from some `pickings` and `stock.move` related to odoo#62139 closes odoo#81127 X-original-commit: d99e173 Signed-off-by: William Henrotin (whe) <whe@odoo.com> Signed-off-by: Arnold Moyaux <arm@odoo.com>
sergiocorato
pushed a commit
to efatto/OCB
that referenced
this pull request
Sep 15, 2022
It happens that the `stock.quant.reserved_quantity` and `stock.move.line.product_qty` for the same parameters are not equals (due to some bugs in the past) It could implies that it doesn't exist enough reserved quantity on the quant when a user try to unreserve a stock.move.line resulting in the UserError 'It is not possible to unreserve more products of %s than you have in stock' However on current stable version (13.0 and 14.0) a lot of PR already fixed a lot of issue as: odoo#69377 odoo#66347 odoo#61758 odoo#54355 odoo#43180 odoo#70975 for example (there is more than that) So the idea is to provide a way to unlock the database manually for stable but not in the new version to be able to analyse them and find possible bugs responssible for the desynchronization. The server action check all the quants and their relative move line to check if match correctly. If not it will remove the reservation from both. It could remove the reservation from some `pickings` and `stock.move` related to odoo#62139 closes odoo#81127 X-original-commit: d99e173 Signed-off-by: William Henrotin (whe) <whe@odoo.com> Signed-off-by: Arnold Moyaux <arm@odoo.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
It happens that the
stock.quant.reserved_quantityandstock.move.line.product_qtyfor the same parameters are not equals (due to some bugs in the past)
It could implies that it doesn't exist enough reserved quantity on the
quant when a user try to unreserve a stock.move.line resulting in the
UserError 'It is not possible to unreserve more products of %s than you
have in stock'
However on current stable version (13.0 and 14.0) a lot of PR already
fixed a lot of issue as:
#69377
#66347
#61758
#54355
#43180
#70975
for example (there is more than that)
So the idea is to provide a way to unlock the database manually for
stable but not in the new version to be able to analyse them and find
possible bugs responssible for the desynchronization.
The server action check all the quants and their relative move line
to check if match correctly. If not it will remove the reservation
from both. It could remove the reservation from some
pickingsandstock.moverelated to #62139
Forward-Port-Of: #79180