[
https://issues.apache.org/jira/browse/AMBARI-9450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303371#comment-14303371
]
Hadoop QA commented on AMBARI-9450:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12696185/AMBARI-9450.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 .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/1562//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/1562//console
This message is automatically generated.
> Add Service wizard: Integrate configure Identities page with the API to get
> the current kerberos descriptor
> -----------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-9450
> URL: https://issues.apache.org/jira/browse/AMBARI-9450
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.0.0
> Reporter: Andrii Babiichuk
> Assignee: Andrii Babiichuk
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-9450.patch
>
>
> Configure Identities page on Add service wizard in a kerberized cluster
> should show all the configs for the selected services to be added (not
> currently installed) in editable mode. The configs shown on this page should
> be retrieved from the existing cluster kerberos descriptor (same API used on
> Disable security page link).
> On clicking next button on this page, kerberos descriptor on cluster should
> be updated. This can be done once the API work tracked at BUG-30662 is
> accomplished
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
