You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2016/02/26 17:15:18 UTC
[jira] [Commented] (AMBARI-15184) Host with uppercased symbols was
not registered during deploy via blueprints
[ https://issues.apache.org/jira/browse/AMBARI-15184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15169242#comment-15169242 ]
Hadoop QA commented on AMBARI-15184:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12790116/AMBARI-15184.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new or modified test files.
{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 patch failed these unit tests in ambari-server:
org.apache.ambari.server.controller.internal.ProvisionClusterRequestTest
org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessorTest
Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/5586//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/5586//console
This message is automatically generated.
> Host with uppercased symbols was not registered during deploy via blueprints
> ----------------------------------------------------------------------------
>
> Key: AMBARI-15184
> URL: https://issues.apache.org/jira/browse/AMBARI-15184
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.2.1
> Reporter: Sandor Magyari
> Assignee: Sandor Magyari
> Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15184.patch
>
>
> The main problem is that while hostnames are only stored in the Ambari DB in lowercase letters, it is still possible for a user to specify a host with capital letters or mixed case letters in the Cluster Creation Template (submitted during a cluster deployment).
> The solution would be to convert the hostnames specified in the Cluster Creation template at deployment time to lower case, and use only lower-case hostnames in Blueprints generally (as in the rest of Ambari). This would mean that all hostnames assumed to be lower-case internally.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)