ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hari Sekhon (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-18443) Host Stack Version Out of Sync - no option to install correct stack Version to align with rest of cluster
Date Thu, 22 Sep 2016 11:24:20 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-18443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Hari Sekhon updated AMBARI-18443:
---------------------------------
    Attachment: Node_Stack_Versions_No_Option_To_Install.png
                Node_Stack_Version_Out_of_Sync.png
                Ambari_Stack_Version.png

> Host Stack Version Out of Sync - no option to install correct stack Version to align
with rest of cluster
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-18443
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18443
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server, stacks
>    Affects Versions: 2.2.2
>         Environment: HDP 2.3.2
>            Reporter: Hari Sekhon
>         Attachments: Ambari_Stack_Version.png, Node_Stack_Version_Out_of_Sync.png, Node_Stack_Versions_No_Option_To_Install.png
>
>
> While upgrading Ambari on a cluster an issue was detected upon the post install metrics
service upgrade restart due to the one host's stack version being out of sync with the rest
of the cluster.
> There seems to be no way to correct this from within Ambari as it does not give options
to deploy the correct stack that the rest of the nodes have even though it is the main and
only stack version shown in Admin -> Stacks and Versions -> Versions.
> It's not clear how this happened but I've tried installing the correct RPM versions by
hand and then ran
> {code}
> hdp-select set all 2.3.2.0-2950
> {code}
> but this doesn't create and symlink /etc/hadoop/conf correctly nor does it solve the
issue from within Ambari itself, see screenshots I'm attaching.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message