Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ambari-dev@incubator.apache.org
Date: Thu, 11 Apr 2013 16:41:16 +0000 (UTC)
From: "Trevor McKay (JIRA)" <jira@apache.org>
To: ambari-dev@incubator.apache.org
Message-ID: <JIRA.12642059.1365696631907.150277.1365698476362@arcas>
In-Reply-To: <JIRA.12642059.1365696631907@arcas>
References: <JIRA.12642059.1365696631907@arcas>
Subject: [jira] [Commented] (AMBARI-1885) Cluster install wizard says that
 registration fails for ssh install when it has succeeded
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Trevor McKay commented on AMBARI-1885:
--------------------------------------

This test was successful:

In bootstrap.py, I simply set the ssh.returncode to 0 if it was 1 for the remote setupAgent.py command.

This allowed the UI to move successfully through install and registration via ssh key.

So, the question remains -- why is the return code coming back 1?
                
> Cluster install wizard says that registration fails for ssh install when it has succeeded
> -----------------------------------------------------------------------------------------
>
>                 Key: AMBARI-1885
>                 URL: https://issues.apache.org/jira/browse/AMBARI-1885
>             Project: Ambari
>          Issue Type: Bug
>          Components: agent, controller
>    Affects Versions: 1.2.0
>         Environment: Fedora 16 server (branch 1.2)
> RHEL6 agent (ambari-agent-1.2.0.1-1.x86_64)
>            Reporter: Trevor McKay
>         Attachments: ambari-agent.log, bootstrap.out
>
>
> If registration of an agent is done with the ssh key, the initial install process will succeed but the UI will report FAILED.
> If a user leaves the agent running, presses the "BACK" button at this point, selects manual registration, and tries again registration will succeed.
> I believe this may be because the ssh command from the server to run setupAgent.py is returning a bad exit code when it has actually succeeded.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira