[HDDS-5789] Enabling container tokens on a upgraded cluster fails SCM to start up

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 1.2.0
• Labels: pull-request-available
• Target Version/s: 1.2.0
• Assignee: Bharat Viswanadham
• Reporter: Bharat Viswanadham
• Created: 27/Sep/21 22:31
• Updated: 30/Sep/21 00:44
• Resolved: 29/Sep/21 21:13

Description

Once a cluster is upgraded from 1.1.0 to latest master with SCM HA code. SCM fails to come up.
When hdds.container.token.enabled is enabled in the cluster.

This is due to below piece of code

    String certId = scmCertificateClient.getCertificate().getSerialNumber()
        .toString();

On an upgraded cluster SCMCertificateClient is not initialized. It is initialized only for HA Clusters and when the cluster is freshly setup with SCM HA version code.

Exception is posted in the comments.

Issue Links

• links to: GitHub Pull Request #2691