[jira] [Commented] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information
[ https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735694#comment-15735694 ] Hudson commented on AMBARI-1: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #500 (See [https://builds.apache.org/job/Ambari-branch-2.5/500/]) Revert "Revert "AMBARI-1: Ambari-agent: Create configuration files (nsomasundaram: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=24ac5cdae228c0f421034f5c897f0635eb9bf52e]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/agent/TestHeartbeatHandler.java * (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/ExecutionCommand.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java * (edit) ambari-agent/conf/unix/ambari-agent.ini * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/HeartBeatHandler.java * (edit) ambari-agent/src/packages/tarball/all.xml > Ambari-agent: Create configuration files with JCEKS information > --- > > Key: AMBARI-1 > URL: https://issues.apache.org/jira/browse/AMBARI-1 > 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)
[jira] [Commented] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information
[ https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15716943#comment-15716943 ] Hudson commented on AMBARI-1: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6147 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6147/]) Revert "Revert "AMBARI-1: Ambari-agent: Create configuration files (nsomasundaram: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=db46822fbf50c5e5222bdec094b3a011584f8ee8]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/HeartBeatHandler.java * (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/ExecutionCommand.java * (edit) ambari-agent/src/packages/tarball/all.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/agent/TestHeartbeatHandler.java * (edit) ambari-agent/conf/unix/ambari-agent.ini > Ambari-agent: Create configuration files with JCEKS information > --- > > Key: AMBARI-1 > URL: https://issues.apache.org/jira/browse/AMBARI-1 > 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)
[jira] [Commented] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information
[
https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15716773#comment-15716773
]
Hadoop QA commented on AMBARI-1:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841554/rb53747.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:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.state.ServicePropertiesTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9511//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9511//console
This message is automatically generated.
> Ambari-agent: Create configuration files with JCEKS information
> ---
>
> Key: AMBARI-1
> URL: https://issues.apache.org/jira/browse/AMBARI-1
> 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)
[jira] [Commented] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information
[ https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15715625#comment-15715625 ] Hudson commented on AMBARI-1: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6140 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6140/]) Revert "AMBARI-1: Ambari-agent: Create configuration files with (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=60a6bd4575fb87fc26c4a277cbabf850ef2089e1]) * (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/ExecutionCommand.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/HeartBeatHandler.java * (edit) ambari-agent/conf/unix/ambari-agent.ini * (edit) ambari-server/src/test/java/org/apache/ambari/server/agent/TestHeartbeatHandler.java * (edit) ambari-agent/src/packages/tarball/all.xml > Ambari-agent: Create configuration files with JCEKS information > --- > > Key: AMBARI-1 > URL: https://issues.apache.org/jira/browse/AMBARI-1 > 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)
[jira] [Commented] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information
[ https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15715602#comment-15715602 ] Hudson commented on AMBARI-1: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #442 (See [https://builds.apache.org/job/Ambari-branch-2.5/442/]) Revert "AMBARI-1: Ambari-agent: Create configuration files with (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5c67068d6a29e2ab09591c73a5dca4ac2ae2f622]) * (edit) ambari-agent/conf/unix/ambari-agent.ini * (edit) ambari-agent/src/packages/tarball/all.xml * (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py * (edit) ambari-server/src/test/java/org/apache/ambari/server/agent/TestHeartbeatHandler.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/ExecutionCommand.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/HeartBeatHandler.java > Ambari-agent: Create configuration files with JCEKS information > --- > > Key: AMBARI-1 > URL: https://issues.apache.org/jira/browse/AMBARI-1 > 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)
[jira] [Commented] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information
[ https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15713553#comment-15713553 ] Hudson commented on AMBARI-1: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #436 (See [https://builds.apache.org/job/Ambari-branch-2.5/436/]) AMBARI-1: Ambari-agent: Create configuration files with JCEKS (nsomasundaram: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=033989e7fd5a28a431eb9bdf64bd68d732e5ee69]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/HeartBeatHandler.java * (edit) ambari-agent/src/packages/tarball/all.xml * (edit) ambari-agent/conf/unix/ambari-agent.ini * (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/ExecutionCommand.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/agent/TestHeartbeatHandler.java > Ambari-agent: Create configuration files with JCEKS information > --- > > Key: AMBARI-1 > URL: https://issues.apache.org/jira/browse/AMBARI-1 > 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)
[jira] [Commented] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information
[ https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15713510#comment-15713510 ] Hudson commented on AMBARI-1: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6132 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6132/]) AMBARI-1: Ambari-agent: Create configuration files with JCEKS (nsomasundaram: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=615438b272e6bd8efd37481ef684ae7d68921e64]) * (edit) ambari-agent/src/packages/tarball/all.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/ExecutionCommand.java * (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py * (edit) ambari-agent/conf/unix/ambari-agent.ini * (edit) ambari-server/src/test/java/org/apache/ambari/server/agent/TestHeartbeatHandler.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/HeartBeatHandler.java > Ambari-agent: Create configuration files with JCEKS information > --- > > Key: AMBARI-1 > URL: https://issues.apache.org/jira/browse/AMBARI-1 > 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)
[jira] [Commented] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information
[
https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15710460#comment-15710460
]
Hadoop QA commented on AMBARI-1:
{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-1
> URL: https://issues.apache.org/jira/browse/AMBARI-1
> 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)
[jira] [Commented] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information
[
https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15707685#comment-15707685
]
Hadoop QA commented on AMBARI-1:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12840982/rb53747.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:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.upgrade.UpgradeCatalog250Test
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9450//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9450//console
This message is automatically generated.
> Ambari-agent: Create configuration files with JCEKS information
> ---
>
> Key: AMBARI-1
> URL: https://issues.apache.org/jira/browse/AMBARI-1
> 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)
[jira] [Commented] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information
[
https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15707019#comment-15707019
]
Hadoop QA commented on AMBARI-1:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12840954/rb53747.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.agent.TestHeartbeatHandler
org.apache.ambari.server.controller.metrics.JMXPropertyProviderTest
org.apache.ambari.server.upgrade.UpgradeCatalog250Test
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9446//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9446//console
This message is automatically generated.
> Ambari-agent: Create configuration files with JCEKS information
> ---
>
> Key: AMBARI-1
> URL: https://issues.apache.org/jira/browse/AMBARI-1
> 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)
[jira] [Commented] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information
[
https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15706064#comment-15706064
]
Hadoop QA commented on AMBARI-1:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12840895/rb53747.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.agent.TestHeartbeatHandler
org.apache.ambari.server.controller.internal.UpgradeResourceProviderTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9440//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9440//console
This message is automatically generated.
> Ambari-agent: Create configuration files with JCEKS information
> ---
>
> Key: AMBARI-1
> URL: https://issues.apache.org/jira/browse/AMBARI-1
> 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)
