[jira] [Commented] (AMBARI-10566) Ambari Upgrade from 1.7.0 to 2.0.0 fails to restart ZK server due to missing symlink

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-10566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14502877#comment-14502877 ] 

Hadoop QA commented on AMBARI-10566:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12726565/AMBARI-10566.2.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:red}-1 core tests{color}.  The test build failed in ambari-server 

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/2417//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/2417//console

This message is automatically generated.

> Ambari Upgrade from 1.7.0 to 2.0.0 fails to restart ZK server due to missing symlink
> ------------------------------------------------------------------------------------
>
>                 Key: AMBARI-10566
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10566
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>             Fix For: 2.1.0, 2.0.1
>
>         Attachments: AMBARI-10566.2.0.maint.2.patch, AMBARI-10566.2.0.maint.patch, AMBARI-10566.2.patch, AMBARI-10566.patch
>
>
> Ambari upgrade from 1.7.0 to 2.0.0 had problems on starting/restarting zookeeper server because /usr/hdp/current/zookeeper-server symlink was not found. The customer remedied the issue by calling "hdp-select set zookeeper-server 2.2.3.0-###" on all of the hosts, which created the symlink.
> In Ambari 1.7.0, ZK server was started using the libs from ZK client, so as part of the Ambari Upgrade, we need to first call "hdp-select set zookeeper-server
> {version}
> "
> It's possible that the either exactly one of start/restart command will handle this. Need to verify what the behavior is.



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