ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Onischuk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-10294) Usability: bootstrapping hosts shows "Preparing" without any information and seems stuck
Date Wed, 01 Apr 2015 11:24:53 GMT

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

Andrew Onischuk commented on AMBARI-10294:
------------------------------------------

+1

> Usability: bootstrapping hosts shows "Preparing" without any information and seems stuck
> ----------------------------------------------------------------------------------------
>
>                 Key: AMBARI-10294
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10294
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-10294.2.patch, AMBARI-10294.patch
>
>
> This is a regression introduced in 2.0.0.
> When doing SSH bootstrap of hosts via Install Wizard, the hosts are shown as "Preparing".
When you click on the host, no information shows up. It gets stuck in this state until "Registering".
> In 1.7.0, "Preparing" state was very brief and immediately switched to "Installing".
> This is a BE issue.
> API returns "RUNNING" without any information when installing Ambari Agent on the hosts.
> This issue caused by absent of propagation fail of runing bootstrap.py (server side)
to HostStatus which are pooled by UI.
> So If bootstrap.py has syntax errors or fails while imports python modules it cant create
*.log and *.done files, so java code can wait infinitely until *.done file will be created.
> So solution of this issue is to propagate fatal errors of bootstrap.py to hostStatus
info. In this case, setup of agents will fail and root cause of issue will be sent to UI



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

Mime
View raw message