You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2016/12/28 14:33:58 UTC
[jira] [Commented] (AMBARI-19308) Non-editable properties should be
handled for add/delete host component
[ https://issues.apache.org/jira/browse/AMBARI-19308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15782999#comment-15782999 ]
Hadoop QA commented on AMBARI-19308:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12844932/AMBARI-19308_trunk.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-web.
Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/9841//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/9841//console
This message is automatically generated.
> Non-editable properties should be handled for add/delete host component
> -----------------------------------------------------------------------
>
> Key: AMBARI-19308
> URL: https://issues.apache.org/jira/browse/AMBARI-19308
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 2.5.0
> Reporter: Andrii Babiichuk
> Assignee: Andrii Babiichuk
> Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19308_trunk.patch
>
>
> Some properties updated after adding/deleting host component may be read-only. For example, user can edit nimbus.seeds value only before cluster install. Such cases should be handled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)