[7.0][purchase_requisition] procurement workflow get stuck, virtual stock becomes wrongly optimitic

[Raphaël Valyi - http://www.akretion.com]

The procurement creating a purchase_requisition get stuck and the virtual stock move procurement -> stock will never get void when we buy the product, leading to an optimistically wrong virtual stock level.

Please find full process with screenshots here:
https://docs.google.com/document/d/1jyLYhrkjhJ-sKYbCJYB4Jg074x1B4ZSTyQXmpW9zMUM/edit?usp=sharing

Also it didn't work any better on saas2 runbot. On trunk-wms, it seems even worse as you cannot even confirm the procurement.

I'm also reporting the bug using the OPW channel for guaranteed resolution. Thanks for fixing this, it makes purchase_requisition not usable for anyone using even trivial MRP.

Regards.

[Alexandre Fayolle - camptocamp (alexandre-fayolle-c2c)]

any news on this ?

[Raphaël Valyi - http://www.akretion.com (rvalyi)]

Hello,

in fact, the support guy at OpenERP SA couldn't reproduce the problem and Thiago here couldn't reproduce it either. On my side I had no more time for that project until now (but will soon work on it again).

So I would say I tend to believe the bug was produced by something else on my computer. I will soon investigate again and give more information.

[Praveen Kumar (mailtoexpert)]

How can be avoided this bug for such a long time?

[Raphaël Valyi - http://www.akretion.com (rvalyi)]

Praveen,

you mean you can reproduce this bug? Please confirm.

[Praveen Kumar (mailtoexpert)]

Raphael,

Yes, I am Facing this bug

[Raphaël Valyi - http://www.akretion.com (rvalyi)]

So,

Thiago just tried again. In fact he observed the same results as Somesh Khare from the OPW team recorded on this video
http://www.youtube.com/watch?v=YB6l82KqmQM&feature=youtu.be

That is yes it's different than what I reported initially in https://docs.google.com/document/d/1jyLYhrkjhJ-sKYbCJYB4Jg074x1B4ZSTyQXmpW9zMUM/edit?usp=sharing
in the sense that after clicking on "Run Procurement" at 2'15, bothe Thiago and Somesh properly see the workflow with a draft purchase state (unlike me).

Now, confirming the PO or even receiving the PO, won't close this procurement that seems stuck in "running" state. Which still leaves us with the 2 problems I reported:

1) procurement workflow is stuck, procurement.order state is ‘running’
2) the virtual stock move procurement -> stock will stay for ever making virtual stock wrong! Indeed, with just the purchase module, when you confirm the purchase.order the procurement workflow use to get a signal so it will void the procurement -> stock move and transform it to a stock -> stock move while the real stock move is now the purchase order reception stock move.

So it looks that after he have seen he could observe a consistent workflow after running the procurement (unlike what I reported initially), Somesh concluded the report was invalid, stopped the investigation and didn't confirm the final issues 1) and 2) I was reporting, which seems still here.

Praveen, is that what you observe too? Anyone else?

[Alexandre Fayolle - camptocamp (alexandre-fayolle-c2c)]

I've observed an issue with virtual stock level incremented twice today on runbot, while trying to answer someone's question on IRC (mayby Praveen Kumar... hard to tell with irc nicks). I did not check whether the procurement was stuck or not, though.

[Praveen Kumar (mailtoexpert)]

Raphael,

Video is not available at given Youtube Link.

But,Yes
Your reported both Problems are valid and i am facing Same issues. If i go from procurement to Purchase Order VIA PURCHASE REQUISITION.

If PO is Directly generated from Procurement then flow has no problem. and all is going good.

Alexandre,

Yes I asked this Question in IRC.