ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandor Magyari (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-15184) Host with uppercased symbols was not registered during deploy via blueprints
Date Mon, 29 Feb 2016 12:25:18 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-15184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sandor Magyari updated AMBARI-15184:
------------------------------------
    Attachment:     (was: AMBARI-15184.patch)

> 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_v2.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)

Mime
View raw message