[
https://issues.apache.org/jira/browse/AMBARI-18711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15610638#comment-15610638
]
Hadoop QA commented on AMBARI-18711:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12835451/rb53216.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.api.services.AmbariMetaInfoTest
org.apache.ambari.server.agent.TestHeartbeatHandler
org.apache.ambari.server.api.services.KerberosServiceMetaInfoTest
org.apache.ambari.server.state.kerberos.KerberosDescriptorUpdateHelperTest
org.apache.ambari.server.stack.StackManagerTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9027//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9027//console
This message is automatically generated.
> Ambari-server: DB changes to enable/disable credential store support
> --------------------------------------------------------------------
>
> Key: AMBARI-18711
> URL: https://issues.apache.org/jira/browse/AMBARI-18711
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: 2.4.2
> Reporter: Nahappan Somasundaram
> Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb53216.patch
>
>
> To enable or disable a component to use credential store, changes are
> required in the DB to keep track of this information. The
> _servicedesiredstate_ table can keep track of this information using a new
> *credential_store_enabled* column.
> If a service supports reading passwords from the configuration's JCEKS file,
> then it will specify this information in its stack definition. Services that
> support using the credential store can be enabled or disabled to use it.
> Services that do not, will always be disabled from using the credential store.
> The option to enable or disable the components of a service that has
> credential store support is provided via the UI and blueprint. This
> information will then be captured in the _servicedesiredstate_ table in the
> *credential_store_enabled* column.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
