[
https://issues.apache.org/jira/browse/AMBARI-11728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14583233#comment-14583233
]
Hudson commented on AMBARI-11728:
---------------------------------
FAILURE: Integrated in Ambari-branch-2.1 #14 (See
[https://builds.apache.org/job/Ambari-branch-2.1/14/])
AMBARI-11728. Upgrade Ambari from 1.7 to Ambari 2.0. I'm on HDP 2.2.0.0, but
the version is not showing up in the Stacks and Versions page. (dlysnichenko)
(dlysnichenko:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a3a626c40ca3c2f64eb3c29e2fdb2d8d1d9b81e4)
*
ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
*
ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ClusterTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/agent/HeartBeatHandler.java
> Upgrade Ambari from 1.7 to Ambari 2.0. I'm on HDP 2.2.0.0, but the version is
> not showing up in the Stacks and Versions page.
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-11728
> URL: https://issues.apache.org/jira/browse/AMBARI-11728
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Fix For: 2.1.0
>
> Attachments: AMBARI-11728.2.patch, AMBARI-11728.patch
>
>
> I've upgraded from Ambari 1.7 to 2.0 on my own cluster and I'm seeing the
> same problem
> Under ‘stacks and versions’, versions gives no information.
> After going through a number of troubleshooting steps, such as refreshing
> browser cache, restarting services, datanodes, rebooting etc, I think we can
> come to the conclusion that this is a bug.
> The upgrade document mentions this, however the advised actions don’t work.
> If using HDP 2.2 Stack, you must get the cluster hosts to advertise the
> "current version". This can be done by restarting a master or slave component
> (such as a DataNode) on each host to have the host advertise it's version so
> Ambari can record the version. For example, in Ambari Web, navigate to the
> Hosts page and select any Host that has the DataNode component, then restart
> that DataNode component on that single host.
> Actually, we should relax it even more, because some hosts may only have
> client components. So either,
> A. All hosts with at least one master/slave must have at least one component
> advertise the version.
> This means that hosts with only clients don't need to do anything; and if a
> host has say NameNode and DataNode, only one is needed, but all such hosts
> need to advertise a version.
> B. Take the version of the first host to advertise a value. So only one
> component on one host is needed. This is the simplest thing to do, but we
> better not have clusters with a mix of versions, say 2.2.0.0-1 and
> 2.2.0.0-2B. Take the version of the first host to advertise a value. So only
> one component on one host is needed. This is the simplest thing to do, but we
> better not have clusters with a mix of versions, say 2.2.0.0-1 and 2.2.0.0-2
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
