ambari-dev 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-9223) Add properties_attributes support to exported Blueprints
Date Wed, 21 Jan 2015 02:10:34 GMT

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

Hadoop QA commented on AMBARI-9223:
-----------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12693405/AMBARI-9223.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 2 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/1406//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/1406//console

This message is automatically generated.

> Add properties_attributes support to exported Blueprints
> --------------------------------------------------------
>
>                 Key: AMBARI-9223
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9223
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Robert Nettleton
>            Assignee: Robert Nettleton
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9223.patch
>
>
> Attributes of configuration properties are not properly included when a Blueprint is
exported from a running cluster.
> To reproduce:
> 1. Start a cluster with the Ambari UI, mark some configuration properties as "final".
> 2. After the cluster has successfully started, use the Blueprint REST API to export a
Blueprint based on this running cluster.
> 3. The configuration elements in the exported Blueprint will not include the proper metadata
about a configuration property.  In this specific case, the Blueprint will not indicate which
configuration elements are "final".  
> This is only a bug in the Blueprint cluster renderer, as most of the support for "properties_attributes"
already exists in the BlueprintResourceProvider and ClusterResourceProvider.  
> The ClusterBlueprintRenderer class needs to be updated to pull out the properties_attributes
from the Cluster resource, and include these within the "configurations" map of the exported
Blueprint. 
> I'm working on a fix for this, and will be submitting a patch shortly.  



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

Mime
View raw message