[
https://issues.apache.org/jira/browse/AMBARI-10294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389115#comment-14389115
]
Hadoop QA commented on AMBARI-10294:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12708471/AMBARI-10294.2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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/2196//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/2196//console
This message is automatically generated.
> 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)
