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

Hadoop QA commented on AMBARI-15711:
------------------------------------

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

    {color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/6205//console

This message is automatically generated.

> Exception thrown when host with unsupported OS is to be mapped to cluster is 
> silently swallowed
> -----------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-15711
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15711
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-15711.patch
>
>
> When hosts are being mapped to a clusters (see
> ClustersImpl.java:mapHostToCluster) it verifies if the OS type of the host
> matches the OS types supported by the stack that is being deployed.
> If the OS type of the host is not supported than a warning message is logged
> and an exception is thrown which is silently swallowed.
>     
>     
>     
>     ....
>     if (!isOsSupportedByClusterStack(cluster, host)) {
>           String message = "Trying to map host to cluster where stack does 
> not"
>               + " support host's os type" + ", clusterName=" + clusterName
>               + ", clusterStackId=" + 
> cluster.getDesiredStackVersion().getStackId()
>               + ", hostname=" + hostname + ", hostOsFamily=" + 
> host.getOsFamily();
>           LOG.warn(message);
>           throw new AmbariException(message);
>         }
>     ...
>     
> This message should be logged as ERROR to make easier troubleshooting as most
> of the time people search for exceptions and ERRORs in the log when looking
> into issues with cluster.



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

Reply via email to