[Private Transactions]: Sender's state doesn't correspond to validator's

[ngyam]

• Parity Ethereum version: Parity-Ethereum/v2.2.0-unstable-c40f7db-20181010/x86_64-linux-gnu/rustc1.29.0
• Operating system: Linux
• Installation: built from source
• Fully synchronized: yes
• Network: local Tobalaba like config
• Restarted: yes, cleaned chaindb and secretstore too

actual

• Smart contract: Consumption
• Steps: https://github.com/ngyam/tutorial-secretstore-privatetx/tree/privatetx/test_setup_2/src/private-tx-2

The steps include deploying the private contract, then writing some (consumption) values.
When writing/changing the value of a record in the consumption contract (4_consume.js), it doesn't happen, fails silently. In the logs the following message can be read:

2018-10-25 20:07:37  IO Worker #1 WARN privatetx  Sender's state doesn't correspond to validator's
2018-10-25 20:07:37  IO Worker #1 WARN privatetx  Unable to process the signature: State is incorrect
2018-10-25 20:07:37  IO Worker #2 WARN privatetx  Sender's state doesn't correspond to validator's
2018-10-25 20:07:37  IO Worker #2 WARN privatetx  Unable to process the signature: State is incorrect
2018-10-25 20:07:37  IO Worker #3 WARN privatetx  Sender's state doesn't correspond to validator's
2018-10-25 20:07:37  IO Worker #3 WARN privatetx  Unable to process the signature: State is incorrect
2018-10-25 20:07:37  IO Worker #0 WARN privatetx  Sender's state doesn't correspond to validator's
2018-10-25 20:07:37  IO Worker #0 WARN privatetx  Unable to process the signature: State is incorrect

Sometimes it happen on the first try, but when run again with a different value in 4_consume.js, it silently fails with the logs above.

expected
values are written/modified with no problems

steps to reproduce
In this repo branch privatetx/test_setup_2:

• start nodes in nodes_ss_tobalabalocal/ with ./start.sh
• then in src/private-tx-2/ folder run the scripts consequtively as numbered

[ngyam]

@julienbourdette FYI