[ https://issues.apache.org/jira/browse/AMBARI-18888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15710460#comment-15710460 ]
Hadoop QA commented on AMBARI-18888: ------------------------------------ {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12841162/rb53747.patch against trunk revision . {color:red}-1 patch{color}. The patch command could not apply the patch. Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/9469//console This message is automatically generated. > Ambari-agent: Create configuration files with JCEKS information > --------------------------------------------------------------- > > Key: AMBARI-18888 > URL: https://issues.apache.org/jira/browse/AMBARI-18888 > Project: Ambari > Issue Type: Task > Components: ambari-agent > Reporter: Nahappan Somasundaram > Assignee: Nahappan Somasundaram > Attachments: rb53747.patch > > > When a non-status command is received, a command.json file is generated. This > file contains the passwords used in a configuration. When the command is then > executed, ambari agent spawns off a subprocess to execute component-specific > Python scripts to generate the configuration files using the data from the > command.json file. > To avoid storing clear text passwords in command.json file and configuration > files, ambari-agent will first generate the JCEKS files corresponding to the > configuration information in the command JSON blob coming from the server and > then generate the command.json with the path to the JCEKS store instead of > clear text passwords for *password* properties. > Subsequently when executing a command, ambari-agent will generate the > configuration files with the JCEKS path information from command.json. -- This message was sent by Atlassian JIRA (v6.3.4#6332)