Fix Readme
Abstract
This document lists fixes that have been delivered in IBM Blockchain Platform 2.5.2.
Content
IBM Blockchain Platform 2.5.2 Fix Pack 12
Release date: 5 April 2022
Installation instructions: Installing IBM Blockchain Platform fix packs
Image identifiers: The images that contain these updates are marked with a 5 April 2022 date to distinguish them from the images previously released for IBM Blockchain Platform 2.5.2.
Fixes included:
- After the console is deployed, the permissions for the CouchDB instance the console uses might change. As a result, it is not possible to log into the console.
IBM Blockchain Platform 2.5.2 Fix Pack 11
Release date: 8 March 2022
Image identifiers: The images that contain these updates are marked with a 8 March 2022 date to distinguish them from the images previously released for IBM Blockchain Platform 2.5.2.
Fixes included:
- This delivery included updated images to address security vulnerabilities.
IBM Blockchain Platform 2.5.2 Fix Pack 10
Release date: 8 February 2022
Image identifiers: The images that contain these updates are marked with a 8 February 2022 date to distinguish them from the images previously released for IBM Blockchain Platform 2.5.2.
Fixes included:
- When using an intermediate certificate authority, it is not possible to associate an identity with a peer or ordering node. For an organization created with an intermediate certificate authority, a peer will not display that it is associated with that organization.
Release date: 11 January 2022
Image identifiers: The images that contain these updates are marked with a 11 January 2022 date to distinguish them from the images previously released for IBM Blockchain Platform 2.5.2.
Fixes included:
- The console may create certificate authorities with eight-character random names.
- The console does not display the option to "refresh certs" for imported ordering nodes.
IBM Blockchain Platform 2.5.2 Fix Pack 8
Release date: 14 December 2021
Image identifiers: The images that contain these updates are marked with a 14 December 2021 date to distinguish them from the images previously released for IBM Blockchain Platform 2.5.2.
Fixes included:
- When multiple organizations are members of a channel, the console does not allow a smart contract to be committed from an instance where the ordering service has been imported.
- The console does not allow peer, ordering, or certificate authority nodes to be created when there are a large number of channels.
Release date: 16 November 2021
Image identifiers: The images that contain these updates are marked with a 16 November 2021 date to distinguish them from the images previously released for IBM Blockchain Platform 2.5.2.
Fixes included:
- This delivery included updated images to address security vulnerabilities.
IBM Blockchain Platform 2.5.2 Fix Pack 6
Release date: 26 October 2021
Image identifiers: The images that contain these updates are marked with a 26 October 2021 date to distinguish them from the images previously released for IBM Blockchain Platform 2.5.2.
Fixes included:
- An ordering node fails to start if its filesystem previously ran out of space.
- A Hyperledger Fabric version 1.4.12 change to allow configuration of maximum gRPC message sizes is included.
- This delivery included updated images to address security vulnerabilities.
IBM Blockchain Platform 2.5.2 Fix Pack 5
Release date: 5 October 2021
Image identifiers: The images that contain these updates are marked with a 5 October 2021 date to distinguish them from the images previously released for IBM Blockchain Platform 2.5.2.
Fixes included:
- The latest version of the Hyperledger Fabric certificate authority (version 1.5.2) is included.
- This delivery included updated images to address security vulnerabilities.
IBM Blockchain Platform 2.5.2 Fix Pack 4
Release date: 10 August 2021
Image identifiers: The images that contain these updates are marked with a 10 August 2021 date to distinguish them from the images previously released for IBM Blockchain Platform 2.5.2.
Fixes included:
- Enabling logging for peer and ordering service nodes through the Blockchain Platform console does not work.
IBM Blockchain Platform 2.5.2 Fix Pack 3
Release date: 13 July 2021
Image identifiers: The images that contain these updates are marked with a 13 July 2021 date to distinguish them from the images previously released for IBM Blockchain Platform 2.5.2.
Fixes included:
- The certificate authority image was updated to use version 1.5.0 of the Hyperledger Fabric certificate authority.
IBM Blockchain Platform 2.5.2 Fix Pack 2
Release date: 16 June 2021
Image identifiers: The images that contain these updates are marked with a 16 June 2021 date to distinguish them from the images previously released for IBM Blockchain Platform 2.5.2.
Fixes included:
- This delivery included updated images to address security vulnerabilities.
IBM Blockchain Platform 2.5.2 Fix Pack 1
Release date: 5 May 2021
Image identifiers: The images that contain these updates are marked with a 5 May 2021 date to distinguish them from the images originally released with IBM Blockchain Platform 2.5.2.
Fixes included:
- The "Log settings" button in the console does not allow logging specifications to be changed for peer and ordering nodes that are using Hyperledger Fabric versions older than 1.4.9.
- Force deleting an ordering node from the console does not work.
- A user log in to the console could fail due to a lock set because of API requests while there was not an active log in session.
- The console does not provide a warning that selecting the same membership services provider (MSP) for an ordering service and a peer organization can lead to an issue when updating this shared MSP in a channel.
- When an ordering node certificate is unable to be renewed by the Blockchain Platform operator, a warning status message is only displayed intermittently rather than continuously to alert the user of this situation.
- Peer TLS certificates that are automatically renewed are created without the necessary subject alternative name (SAN) information.
- Chaincode logs are not generated as expected when using some peers.
Initial IBM Blockchain Platform 2.5.2 release
Release date: 29 March 2021
Fixes included:
- The peer init container could take several minutes to start in some cases.
- The orderer configuration override to skip certificate expiration checks does not take effect as expected.
- Updating a peer to a new Blockchain Platform version fails if the peer.gossip.bootstrap configuration property only contains one peer.
- The CouchDB disk size cannot be changed when creating a new peer.
- There could be a delay starting CouchDB within the peer pod.
- Duplicate orderer, peer, and certificate authority components could be created if a name is not explicitly included in the component creation request (such as when using the Ansible collection).
- If the Blockchain Platform console is created without specifying a TLS certificate, then it is not possible to make an update later with the TLS certificate information.
- An unlimited number of Blockchain Platform components (peers, certificate authorities, and ordering nodes) can be created in a single environment, which can lead to difficulty managing a large number of components in the Blockchain Platform console.
- The logging specification for a Hyperledger Fabric 1.4.7 peer or orderer cannot be changed using the Blockchain Platform console.
- Force deleting an ordering node through the Blockchain Platform console fails.
- When initially logging in to the Blockchain Platform console, it might not be possible to login for two minutes after changing the password.
- The Blockchain Platform console does not provide a warning that an orderer and a peer organization using the same MSP can lead to errors, such as when updating a channel.
[{"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"}}]
Was this topic helpful?
Document Information
Modified date:
01 September 2022
UID
ibm16431203