Release date: Feb 28th, 2018
Important: Upgrade to this version should be performed simultaneously for all nodes (with force=True).
Component Version Information
| Components | Version Numbers |
|---|---|
| indy-plenum | 1.2.34 |
| indy-anoncreds | 1.0.11 |
| indy-node | 1.3.55 |
Major Fixes
| Description | Additional Information | Ticket Number |
|---|---|---|
| Transactions were missing from the config ledger after the upgrade. | INDY-799 | |
| The node was broken after a load_test.py run. | INDY-960 | |
| The pool stopped taking transactions after sending 1,000 simultaneous transactions. | INDY-911 | |
| The pool stopped working: Node services stop with 1,000 simultaneous clients doing GET_NYM reads | INDY-986 | |
| The node is broken after adding it to the pool. | INDY-948 | |
| The generate_indy_pool_transactions command can be run only by an indy user. | INDY-1048 | |
| Made it so that updates to existing Schemas are not allowed. | INDY-1035 | |
| The pool was unable to write txns after two nodes adding. | INDY-1018 | |
| Fixed a bug where it was possible to override CLAIM_DEF for existing schema-did pair. | INDY-1083 | |
| Fixed a bug where here was a huge amount of calls and a lot of execution time in kv_store.py. | INDY-1077 | |
| One of added nodes wasn't catching up. | INDY-1029 | |
| The pool stopped working and lost consensus while new node was performing a catch-up. | INDY-1025 | |
| Performing a View Change on large pools of 19 or more nodes can cause pool to stop functioning. | INDY-1054 | |
| Performing a View Change issue stopped the pool from accepting new transactions. | INDY-1034 | |
| We were unable to send transactions in STN. | INDY-1076 INDY-1079 | |
| Replica.lastPrePrepareSeqNo may not be reset on view change. | INDY-1061 | |
| We were unable to send an upgrade transaction without including demoted nodes. | INDY-897 | |
| The Nym request to STN was resulting in inconsistent responses. | INDY-1069 | |
| The validator node was being re-promoted during view change. | INDY-959 | |
| There was a false cancel message during an upgrade. | INDY-1078 | |
| Transactions were being added to nodes in STN during system reboot.. | INDY-1045 | |
| There were problems with nodes demotion during load test. | INDY-1033 | |
| The node monitoring tool (email plugin) wasn't working. | INDY-995 | |
| ATTRIB transaction with ENC and HASH wasn't working. | INDY-1074 | |
| When returning N-F nodes to the pool, View Change does not occur if Primary node is stopped. | INDY-1151 | |
| We were unable to recover write consensus at n-f after f+1 descent. | INDY-1166 | |
| Newly upgraded STN fails to accept transactions (pool has been broken after upgrade because of one not upgraded node). | INDY-1183 | |
| We were unable to submit upgrade transactions to STN. | INDY-1190 | |
Changes - Additions - Known Issues
| Description | Workaround | Ticket |
|---|---|---|
| Added indy-sdk test dependency to plenum and use indy-sdk for plenum tests. | INDY-900 INDY-901 | |
| Published docker images to dockerhub. | INDY-962 | |
| Simplified the view change code. | INDY-480 | |
| Refactored config.py to reflect file folder re-factoring for Incubation. | INDY-878 | |
| Added Abstract Observers Support. | INDY-628 | |
| Updated information in "Getting Started with Indy". | INDY-1062 | |
| Updated information in "Setting Up a Test Indy Network in VMs". | INDY-1062 | |
| Add iptables rules to limit the number of clients connections. | INDY-1087 | |
| Knowledge transfer on Indy build processes. | INDY-1088 | |
| Incubation: Move CI part of pipelines to Hyperledger infrastructure. | INDY-837 | |
| Made it so that a user can revoke a connection by rotating the new key to nothing. | INDY-582 | |
| Client needs to be able to make sure that we have the latest State Proof. | INDY-928 | |
| Created it so that anyone could have access to an up-to-date Technical overview of plenum and indy. | INDY-1022 | |
| Known Issue: Pool has lost consensus after primary demotion (with 4 nodes setup only). | INDY-1163 | |
| Known Issue: Ambiguous behavior after node demotion. | INDY-1179 | |
| Known Issue: One of the nodes does not respond to libindy after several running load test. | INDY-1180 | |
| Known Issue: Pool does not work after not simultaneous manual pool upgrades. | INDY-1197 | |
| Known Issue: Pool stops working if the primary node was not included to schedule in the upgrade transaction. | INDY-1198 | |
Additional Information:
Node promoting is not recommended for 1.3.52 version according to known issues because backup protocol instances may work incorrectly until next view change.
As mentioned above, upgrade to this version should be performed simultaneously for all nodes (with force=True).