You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Oleksandr Diachenko (JIRA)" <ji...@apache.org> on 2013/12/24 18:54:50 UTC

[jira] [Commented] (AMBARI-4163) Ambari host registering freezes if wrong ssh key provided.

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

Oleksandr Diachenko commented on AMBARI-4163:
---------------------------------------------

+1

> Ambari host registering freezes if wrong ssh key provided.
> ----------------------------------------------------------
>
>                 Key: AMBARI-4163
>                 URL: https://issues.apache.org/jira/browse/AMBARI-4163
>             Project: Ambari
>          Issue Type: Bug
>          Components: controller
>    Affects Versions: 1.4.3
>            Reporter: Myroslav Papirkovskyy
>            Assignee: Myroslav Papirkovskyy
>             Fix For: 1.4.3
>
>         Attachments: AMBARI-4163.patch
>
>
> Steps to reproduce:
> Run Ambari installer UI.
> Provide wrong private key
> Register Hosts
> Expected 
> Message about wrong SSH key
> Actual 
> Installation freezes for long time. If you click on host link, you can see:
> STDERR
> Permission denied (publickey,gssapi-with-mic,password).
> lost connection
> scp /usr/lib/python2.6/site-packages/ambari_server/os_type_check.sh done for host c5901.ambari.apache.org, exitcode=1
> Copying os type check script finished.
> And there is no obvious way to interrupt that process. It seems that it lasts forever. I think UI must have some message about whats wrong, and ability to interrupt registering process if something goes wrong.
> I have tried to workaround this problem by deleting this hosts and going back to step 3. If I do that way in first few minutes, messagebox appears (see screenshot attached). I think it is not expected behaviour. After a few(aprox 5 or more) minutes, it is possible to delete hosts, go to step 3 and retry.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)