Known issues

This page describes known issues that you might encounter when you use IBM Blockchain Platform 2.5.1.

Running a different version of IBM Blockchain Platform? Switch to version 2.1.3, 2.5, 2.5.1, 2.5.2, 2.5.3.

Nil pointer when creating HSM-configmap

Creating the HSM configmap fails with the error:

2020-10-13T15:13:17.324077030Z  goroutine 327 [running]:
2020-10-13T15:13:17.324088954Z  k8s.io/apimachinery/pkg/util/runtime.logPanic(0x1be65c0, 0x3205df0)
2020-10-13T15:13:17.324098097Z      src/github.ibm.com/ibp/operator/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:74 +0xa3
2020-10-13T15:13:17.324106701Z  k8s.io/apimachinery/pkg/util/runtime.HandleCrash(0x0, 0x0, 0x0)
2020-10-13T15:13:17.324114817Z      src/github.ibm.com/ibp/operator/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:48 +0x82
2020-10-13T15:13:17.324122356Z  panic(0x1be65c0, 0x3205df0)
2020-10-13T15:13:17.324129558Z      /usr/local/go1.14.7b4/src/runtime/panic.go:969 +0x166
2020-10-13T15:13:17.324136882Z  github.ibm.com/ibp/operator/pkg/initializer/common/config.(*HSMConfig).BuildPullSecret(...)
2020-10-13T15:13:17.324147032Z      src/github.ibm.com/ibp/operator/pkg/initializer/common/config/hsmconfig.go:97

This error is caused by not specifying a value for the <IMAGE_PULL_SECRET> in the HSM configmap. Even if your HSM client image is public and no image pull secret is required, you still need to provide a value of "" for the <IMAGE_PULL_SECRET> field.

Smart contract instantiation timeout

When running the IBM® Blockchain Platform on s390x architecture, it is possible that Node.js smart contract instantiation can fail. Customers should wait for five minutes after the failure occurs and then retry the instantiation again. It will then work successfully on the subsequent attempt.