IBM Support

IBM Blockchain Platform 2.5.1 fix list

Fix Readme


Abstract

This document lists fixes that have been delivered in IBM Blockchain Platform 2.5.1. Fix pack deliveries are cumulative, so the most recent fix pack contains fixes from all prior fix packs. Installing the most recent fix pack is recommended and this is the only step needed to update any IBM Blockchain Platform 2.5.1 level to the most current images with all fixes to date.

Content

IBM Blockchain Platform 2.5.1 Fix Pack 3
Release date: 13 January 2021
Image identifiers: The images that contain these updates are marked with a January 12 date to distinguish them from images previously released for IBM Blockchain Platform 2.5.1.
Fixes included:
  • When using the Hyperledger Fabric v2.x chaincode lifecycle, the Blockchain Platform console does not display smart contracts at the channel level if a private data collection does not include an endorsement section.
IBM Blockchain Platform 2.5.1 Fix Pack 2
Release date: 8 December 2020
Image identifiers: The images that contain these updates are marked with a December 8 date to distinguish them from images previously released for IBM Blockchain Platform 2.5.1.
Fixes included:
  • Orderer details are not displayed in the Blockchain Platform console for ordering nodes that were updated from 2.1.3 to 2.5.1.
  • Renewing a certificate authority TLS certificate through the Blockchain Platform console produces a certificate that fails validation with an incorrect subject alternate name.
  • Peers and orderers that utilize certificates from an intermediate certificate authority are unable to communicate with other blockchain nodes.
IBM Blockchain Platform 2.5.1 Fix Pack 1
Release date: 19 November 2020
Image identifiers: The images that contain these updates are marked with a November 19 date to distinguish them from the images originally released with IBM Blockchain Platform 2.5.1.
Fixes included:
  • The console peer node view does not display the resources that are allocated and choosing "Reallocate resources" does not populate the form with correct resource values.
  • Deleting and then recreating a peer with the same name could cause an enrollment failure.
  • After updating from 2.5.0 to 2.5.1, the console pod could go into a crash loop, thus preventing use of the console.
  • A Golang smart contract with go.mod set to 1.14 does not install on a Hyperledger Fabric 2.x peer when using the smart contract lifecycle installation process.
  • An ordering service admin certificate update only updates the certificate for the first ordering service node in a multi-node ordering service cluster.
  • When the first node in an ordering service cluster is unavailable, a consenter cannot be removed.
  • Using a single-node ordering service with a TLS certificate from an external certificate authority could cause the ordering node to crash.
Initial IBM Blockchain Platform 2.5.1 release
Release date: 30 October 2020
Fixes included:
  • The console does not allow identities and affiliations to be removed from a certificate authority.
  • Associating an identity with a peer does not update the channel list in the console to reflect the newly assigned identity.
  • The console allows importing an MSP with a name that is the same as an MSP already listed in the console, thus making it difficult to distinguish between the two MSPs.
  • Opening an update channel signature request for adding a consenter results in a type error when rendering the console panel.
  • A peer restarts continually after an admin certificate update.
  • Components such as peers do not start at times due to a problem obtaining images.
  • The orderer could experience an out of memory condition during the component startup phase.
  • Only one ingress can be used even if a Kubernetes cluster has multiple ingress options.
  • A PKCS11 proxy endpoint is set for the whole environment, so it is not possible for a peer and a certificate authority to use different PKCS11 proxies.
  • References to consenters for removed ordering nodes could still be present.
  • A peer cannot be created in a multi-zone IBM Cloud Private cluster.
  • In cases where a peer is unavailable or there is a communication problem, block dissemination using the gossip protocol could lead to problems obtaining blocks.
  • Multiple certificate authority pods can end up on the same node, so they are not spread across multiple zones as documented.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSNJXM","label":"IBM Blockchain Platform"},"ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
01 September 2022

UID

ibm16344313

Page Feedback