ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-20542) Fixed configuration type validation in case of blueprint deployments.
Date Thu, 23 Mar 2017 15:49:41 GMT

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

Hadoop QA commented on AMBARI-20542:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12860138/AMBARI-20542.b-2.5.v2.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:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/11138//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/11138//console

This message is automatically generated.

> Fixed configuration type validation in case of blueprint deployments.
> ---------------------------------------------------------------------
>
>                 Key: AMBARI-20542
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20542
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Laszlo Puskas
>            Assignee: Laszlo Puskas
>            Priority: Blocker
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-20542.b-2.5.v2.patch
>
>
> Extended configuration type validation to the configurations posted in blueprints. (Previously
only the configurations posted in the cluster template were considered) 
> Also a bug prohibits blueprint deployments that doesn't contain all the config types
for services listed in the blueprint.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message