Details
-
Bug
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
2.5.2
-
None
Description
When installing a new cluster with Atlas, the cluster's version may not transition out of INIT.
This is being caused by Atlas Client - it's version is UNKNOWN.
ATLAS_CLIENT UNKNOWN 6 INSTALLED 2 ATLAS HST_AGENT UNKNOWN 6 STARTED 2 SMARTSENSE INFRA_SOLR_CLIENT UNKNOWN 6 INSTALLED 2 AMBARI_INFRA LOGSEARCH_LOGFEEDER UNKNOWN 6 STARTED 2 LOGSEARCH METRICS_COLLECTOR UNKNOWN 6 STARTED 2 AMBARI_METRICS METRICS_GRAFANA UNKNOWN 6 STARTED 2 AMBARI_METRICS METRICS_MONITOR UNKNOWN 6 STARTED 2 AMBARI_METRICS
This is an HDP-2.6 cluster, which means that Atlas should be using 0.7.0.2.5:
./src/main/resources/common-services/ATLAS/0.7.0.2.5/metainfo.xml: <version>0.7.0.2.5</version> ./src/main/resources/stacks/HDP/2.5/services/ATLAS/metainfo.xml: <version>0.7.0.2.5</version> ./src/main/resources/stacks/HDP/2.5/services/ATLAS/metainfo.xml: <extends>common-services/ATLAS/0.7.0.2.5</extends>
In Atlas 0.7.0.2.5, it advertises a version:
<component>
<name>ATLAS_CLIENT</name>
<cardinality>1+</cardinality>
<versionAdvertised>true</versionAdvertised>
</component>
</components>
The root cause is that the verison is not being sent in the commandParams:
2017-07-19 15:43:49,739 - Stack Feature Version Info: Cluster Stack=2.6, Cluster Current Version=None, Command Stack=None, Command Version=None-> 2.6
Attachments
Attachments
Issue Links
- links to