[
https://issues.apache.org/jira/browse/HDDS-5789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Viswanadham updated HDDS-5789:
-------------------------------------
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
{code:java}
String certId = scmCertificateClient.getCertificate().getSerialNumber()
.toString();
{code}
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.
was:Once a cluster is upgraded from 1.1.0 to latest master with SCM HA code.
SCM fails to come up.
> Enabling container tokens on a upgraded cluster fails SCM to start up
> ---------------------------------------------------------------------
>
> Key: HDDS-5789
> URL: https://issues.apache.org/jira/browse/HDDS-5789
> Project: Apache Ozone
> Issue Type: Bug
> Reporter: Bharat Viswanadham
> Assignee: Bharat Viswanadham
> Priority: Major
>
> 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
> {code:java}
> String certId = scmCertificateClient.getCertificate().getSerialNumber()
> .toString();
> {code}
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
