From 8425fd6c44c1411d7ea06c86c46f65fac003a7c1 Mon Sep 17 00:00:00 2001 From: MadelineMurray <43356962+MadelineMurray@users.noreply.github.com> Date: Wed, 22 Apr 2020 14:09:47 +1000 Subject: [PATCH] Added NAT and service start bug fixes and new known issue to changelog (#754) * Added NAT and service start bug fixes and new known issue Signed-off-by: Edward Evans Signed-off-by: MadelineMurray <43356962+MadelineMurray@users.noreply.github.com> --- CHANGELOG.md | 16 +++++++++++++--- KNOWN_ISSUES.md | 12 +++--------- 2 files changed, 16 insertions(+), 12 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 1a2a6afdf9..7f5ad247b4 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -11,17 +11,27 @@ ### Bug Fixes - Flag added to toggle `eth/65` off by default. `eth/65` will remain toggled off by default until -a fix is completed for the [eth/65 known issue](KNOWN_ISSUES.md). +a fix is completed for the [eth/65 known issue](KNOWN_ISSUES.md). [\#741](https://github.com/hyperledger/besu/pull/741) +- Resolve crashing NAT detectors on GKE. [\#731](https://github.com/hyperledger/besu/pull/731) fixes [\#507](https://github.com/hyperledger/besu/issues/507). +[Besu-Kubernetes Readme](https://github.com/PegaSysEng/besu-kubernetes/blob/master/README.md#network-topology-and-high-availability-requirements) +updated to reflect changes. +- Deal with quick service start failures [\#714](https://github.com/hyperledger/besu/pull/714) fixes [\#662](https://github.com/hyperledger/besu/issues/662) ### Known Issues Known issues are open issues categorized as [Very High or High impact](https://wiki.hyperledger.org/display/BESU/Defect+Prioritisation+Policy). + +New known issues: + +- `Intrinsic gas exceeds gas limit` returned when calling `delete mapping[addr]` or `mapping[addr] = 0` [\#696](https://github.com/hyperledger/besu/issues/696) + +Calling delete and set to 0 Solidity mapping in Solidity fail. + Previously identified known issues: - [Eth/65 not backwards compatible](KNOWN_ISSUES.md#eth65-not-backwards-compatible) - [Error full syncing with pruning](KNOWN_ISSUES.md#error-full-syncing-with-pruning) - [Fast sync when running Besu on cloud providers](KNOWN_ISSUES.md#fast-sync-when-running-besu-on-cloud-providers) -- [Fast sync reverting to full sync](KNOWN_ISSUES.md#fast-sync-reverting-to-full-sync) - [Bootnodes must be validators when using onchain permissioning](KNOWN_ISSUES.md#bootnodes-must-be-validators-when-using-onchain-permissioning) - [Privacy users with private transactions created using v1.3.4 or earlier](KNOWN_ISSUES.md#privacy-users-with-private-transactions-created-using-v134-or-earlier) @@ -61,7 +71,7 @@ in 1.5.0 release. [\#639](https://github.com/hyperledger/besu/pull/639) #### Fast sync when running Besu on cloud providers A known [RocksDB issue](https://github.com/facebook/rocksdb/issues/6435) causes fast sync to fail -when running Besu on certain cloud providers. The following errors is displayed repeatedly: +when running Besu on certain cloud providers. The following error is displayed repeatedly: ``` ... diff --git a/KNOWN_ISSUES.md b/KNOWN_ISSUES.md index 62a7dc002f..14b011a35a 100644 --- a/KNOWN_ISSUES.md +++ b/KNOWN_ISSUES.md @@ -7,6 +7,8 @@ Known issues are open issues categorized as [Very High or High impact](https://w ## Eth/65 not backwards compatible +In v1.4.4, `eth/65` is [disabled by default](https://github.com/hyperledger/besu/pull/741). + The `eth/65` change is not [backwards compatible](https://github.com/hyperledger/besu/issues/723). This has the following impact: * In a private network, nodes using the 1.4.3 client cannot interact with nodes using 1.4.2 or earlier @@ -30,7 +32,7 @@ A fix for this issue is being actively worked on. ## Fast sync when running Besu on cloud providers A known [RocksDB issue](https://github.com/facebook/rocksdb/issues/6435) causes fast sync to fail -when running Besu on certain cloud providers. The following errors is displayed repeatedly: +when running Besu on certain cloud providers. The following error is displayed repeatedly: ``` ... @@ -46,14 +48,6 @@ Workaround -> On AWS, a full restart of the AWS VM is required to restart the fa Fast sync is not currently supported on Digital Ocean. We are investigating options to [add support for fast sync on Digital Ocean](https://github.com/hyperledger/besu/issues/591). -## Fast sync reverting to full sync - -In some cases of FastSyncException, fast sync reverts back to a full sync before having reached the -pivot block. [\#683](https://github.com/hyperledger/besu/issues/683) - -Workaround -> To re-attempt fast syncing rather than continue full syncing, stop Besu, delete your -database, and start again. - ## Bootnodes must be validators when using onchain permissioning - Onchain permissioning nodes can't peer when using a non-validator bootnode [\#528](https://github.com/hyperledger/besu/issues/528)