[jira] [Updated] (AMBARI-18356) ZEPPELIN user won't get created in ZEPPELIN group

[ https://issues.apache.org/jira/browse/AMBARI-18356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18356: - Attachment: AMBARI-18356.patch > ZEPPELIN user won't get created in ZEPPELIN group >

[jira] [Updated] (AMBARI-18356) ZEPPELIN user won't get created in ZEPPELIN group

[ https://issues.apache.org/jira/browse/AMBARI-18356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18356: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk

[jira] [Updated] (AMBARI-18357) Ambari fails to start nodemanager due to unexpected return code from sudo su command on the pid file

[ https://issues.apache.org/jira/browse/AMBARI-18357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18357: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk

[jira] [Commented] (AMBARI-18356) ZEPPELIN user won't get created in ZEPPELIN group

[ https://issues.apache.org/jira/browse/AMBARI-18356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483688#comment-15483688 ] Hadoop QA commented on AMBARI-18356: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Comment Edited] (AMBARI-17728) Error message does not deliver when executing ambari-server command as a non-root user

[ https://issues.apache.org/jira/browse/AMBARI-17728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15477199#comment-15477199 ] wangyaoxin edited comment on AMBARI-17728 at 9/12/16 8:35 AM: -- Hi

[jira] [Updated] (AMBARI-18356) ZEPPELIN user won't get created in ZEPPELIN group

[ https://issues.apache.org/jira/browse/AMBARI-18356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18356: - Status: Patch Available (was: Open) > ZEPPELIN user won't get created in ZEPPELIN

[jira] [Created] (AMBARI-18356) ZEPPELIN user won't get created in ZEPPELIN group

Andrew Onischuk created AMBARI-18356: Summary: ZEPPELIN user won't get created in ZEPPELIN group Key: AMBARI-18356 URL: https://issues.apache.org/jira/browse/AMBARI-18356 Project: Ambari

[jira] [Updated] (AMBARI-18357) Ambari fails to start nodemanager due to unexpected return code from sudo su command on the pid file

[ https://issues.apache.org/jira/browse/AMBARI-18357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18357: - Attachment: AMBARI-18357.patch > Ambari fails to start nodemanager due to unexpected

[jira] [Created] (AMBARI-18357) Ambari fails to start nodemanager due to unexpected return code from sudo su command on the pid file

Andrew Onischuk created AMBARI-18357: Summary: Ambari fails to start nodemanager due to unexpected return code from sudo su command on the pid file Key: AMBARI-18357 URL:

[jira] [Updated] (AMBARI-18357) Ambari fails to start nodemanager due to unexpected return code from sudo su command on the pid file

[ https://issues.apache.org/jira/browse/AMBARI-18357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18357: - Status: Patch Available (was: Open) > Ambari fails to start nodemanager due to

[jira] [Created] (AMBARI-18358) Deleting a service with node specific configuration makes Ambari unstable

Gonzalo Herreros created AMBARI-18358: - Summary: Deleting a service with node specific configuration makes Ambari unstable Key: AMBARI-18358 URL: https://issues.apache.org/jira/browse/AMBARI-18358

[jira] [Updated] (AMBARI-18358) Deleting a service with node specific configuration makes Ambari unstable

[ https://issues.apache.org/jira/browse/AMBARI-18358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gonzalo Herreros updated AMBARI-18358: -- Description: Always reproduced. On any service, change some setting to be node

[jira] [Commented] (AMBARI-18357) Ambari fails to start nodemanager due to unexpected return code from sudo su command on the pid file

[ https://issues.apache.org/jira/browse/AMBARI-18357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483730#comment-15483730 ] Hadoop QA commented on AMBARI-18357: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Updated] (AMBARI-18237) Certain configuration files cannot be modified through Ambari api.

[ https://issues.apache.org/jira/browse/AMBARI-18237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18237: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk

[jira] [Updated] (AMBARI-18358) Deleting a service with node specific configuration makes Ambari unstable

[ https://issues.apache.org/jira/browse/AMBARI-18358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gonzalo Herreros updated AMBARI-18358: -- Description: Always reproduced. On any service, change some setting to be node

[jira] [Updated] (AMBARI-18286) Processes children are not killed on timeout

[ https://issues.apache.org/jira/browse/AMBARI-18286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18286: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to

[jira] [Updated] (AMBARI-18260) Journal node restart failing on RU from dergM10 to erie on Wire Encrypted cluster

[ https://issues.apache.org/jira/browse/AMBARI-18260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18260: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk

[jira] [Created] (AMBARI-18359) Get LDAP tests to run in concurrent forked JVMs

Doroszlai, Attila created AMBARI-18359: -- Summary: Get LDAP tests to run in concurrent forked JVMs Key: AMBARI-18359 URL: https://issues.apache.org/jira/browse/AMBARI-18359 Project: Ambari

[jira] [Commented] (AMBARI-18237) Certain configuration files cannot be modified through Ambari api.

[ https://issues.apache.org/jira/browse/AMBARI-18237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483867#comment-15483867 ] Hudson commented on AMBARI-18237: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5649 (See

[jira] [Commented] (AMBARI-18355) Introduce conditional dependencies in stack defition to handle blueprint validation gracefully

[ https://issues.apache.org/jira/browse/AMBARI-18355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483968#comment-15483968 ] Hadoop QA commented on AMBARI-18355: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Commented] (AMBARI-18237) Certain configuration files cannot be modified through Ambari api.

[ https://issues.apache.org/jira/browse/AMBARI-18237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483849#comment-15483849 ] Hudson commented on AMBARI-18237: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #15 (See

[jira] [Commented] (AMBARI-18286) Processes children are not killed on timeout

[ https://issues.apache.org/jira/browse/AMBARI-18286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483850#comment-15483850 ] Hudson commented on AMBARI-18286: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #15 (See

[jira] [Updated] (AMBARI-18359) Get LDAP tests to run in concurrent forked JVMs

[ https://issues.apache.org/jira/browse/AMBARI-18359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-18359: --- Attachment: AMBARI-18359.patch > Get LDAP tests to run in concurrent forked JVMs >

[jira] [Commented] (AMBARI-18357) Ambari fails to start nodemanager due to unexpected return code from sudo su command on the pid file

[ https://issues.apache.org/jira/browse/AMBARI-18357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484064#comment-15484064 ] Hudson commented on AMBARI-18357: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #16 (See

[jira] [Updated] (AMBARI-18360) ambari-agent check for unset variables (AMBARI-18317)

[ https://issues.apache.org/jira/browse/AMBARI-18360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18360: - Attachment: AMBARI-18360.patch > ambari-agent check for unset variables (AMBARI-18317)

[jira] [Created] (AMBARI-18360) ambari-agent check for unset variables (AMBARI-18317)

Andrew Onischuk created AMBARI-18360: Summary: ambari-agent check for unset variables (AMBARI-18317) Key: AMBARI-18360 URL: https://issues.apache.org/jira/browse/AMBARI-18360 Project: Ambari

[jira] [Updated] (AMBARI-18360) ambari-agent check for unset variables (AMBARI-18317)

[ https://issues.apache.org/jira/browse/AMBARI-18360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18360: - Status: Patch Available (was: Open) > ambari-agent check for unset variables

[jira] [Updated] (AMBARI-18359) Get LDAP tests to run in concurrent forked JVMs

[ https://issues.apache.org/jira/browse/AMBARI-18359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-18359: --- Status: Patch Available (was: Open) > Get LDAP tests to run in concurrent forked

[jira] [Commented] (AMBARI-18323) Cluster creation complete is missing from ambari-server log

[ https://issues.apache.org/jira/browse/AMBARI-18323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484030#comment-15484030 ] Sandor Magyari commented on AMBARI-18323: - Committed to trunk & 'branch-2.5'. > Cluster

[jira] [Comment Edited] (AMBARI-17728) Error message does not deliver when executing ambari-server command as a non-root user

[ https://issues.apache.org/jira/browse/AMBARI-17728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15477199#comment-15477199 ] wangyaoxin edited comment on AMBARI-17728 at 9/12/16 1:13 PM: -- Hi

[jira] [Commented] (AMBARI-18360) ambari-agent check for unset variables (AMBARI-18317)

[ https://issues.apache.org/jira/browse/AMBARI-18360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484091#comment-15484091 ] Hadoop QA commented on AMBARI-18360: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Commented] (AMBARI-18357) Ambari fails to start nodemanager due to unexpected return code from sudo su command on the pid file

[ https://issues.apache.org/jira/browse/AMBARI-18357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484112#comment-15484112 ] Hudson commented on AMBARI-18357: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5650 (See

[jira] [Commented] (AMBARI-18356) ZEPPELIN user won't get created in ZEPPELIN group

[ https://issues.apache.org/jira/browse/AMBARI-18356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484110#comment-15484110 ] Hudson commented on AMBARI-18356: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5650 (See

[jira] [Updated] (AMBARI-18323) Cluster creation complete is missing from ambari-server log

[ https://issues.apache.org/jira/browse/AMBARI-18323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-18323: Resolution: Fixed Status: Resolved (was: Patch Available) > Cluster creation

[jira] [Commented] (AMBARI-18356) ZEPPELIN user won't get created in ZEPPELIN group

[ https://issues.apache.org/jira/browse/AMBARI-18356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484062#comment-15484062 ] Hudson commented on AMBARI-18356: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #16 (See

[jira] [Updated] (AMBARI-18361) All classes recompiled due to Maven bug, even if none changed

[ https://issues.apache.org/jira/browse/AMBARI-18361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-18361: --- Status: Patch Available (was: Open) > All classes recompiled due to Maven bug,

[jira] [Created] (AMBARI-18364) Ambari authentication with Kerberos token

Robert Levas created AMBARI-18364: - Summary: Ambari authentication with Kerberos token Key: AMBARI-18364 URL: https://issues.apache.org/jira/browse/AMBARI-18364 Project: Ambari Issue Type:

[jira] [Updated] (AMBARI-18366) YAML Maps For Storm Are Not Being Escaped Correctly

[ https://issues.apache.org/jira/browse/AMBARI-18366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-18366: - Attachment: AMBARI-18366.patch > YAML Maps For Storm Are Not Being Escaped Correctly >

[jira] [Updated] (AMBARI-18366) YAML Maps For Storm Are Not Being Escaped Correctly

[ https://issues.apache.org/jira/browse/AMBARI-18366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-18366: - Status: Patch Available (was: Open) > YAML Maps For Storm Are Not Being Escaped

[jira] [Updated] (AMBARI-18362) Update sinks to read multiple collector hostnames from configs

[ https://issues.apache.org/jira/browse/AMBARI-18362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-18362: Attachment: AMBARI-18362.patch > Update sinks to read multiple collector hostnames from configs >

[jira] [Commented] (AMBARI-17728) Error message does not deliver when executing ambari-server command as a non-root user

[ https://issues.apache.org/jira/browse/AMBARI-17728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484945#comment-15484945 ] Hudson commented on AMBARI-17728: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5653 (See

[jira] [Commented] (AMBARI-18237) Certain configuration files cannot be modified through Ambari api.

[ https://issues.apache.org/jira/browse/AMBARI-18237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15485122#comment-15485122 ] Hudson commented on AMBARI-18237: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #18 (See

[jira] [Updated] (AMBARI-18334) Password in the configurations.json file in the ambari-agent cache is not encrypted

[ https://issues.apache.org/jira/browse/AMBARI-18334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-18334: -- Attachment: AMBARI-18334-Sep12.patch > Password in the

[jira] [Updated] (AMBARI-18355) Introduce conditional dependencies in stack defition to handle blueprint validation gracefully

[ https://issues.apache.org/jira/browse/AMBARI-18355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-18355: --- Status: Patch Available (was: In Progress) > Introduce conditional dependencies in stack

[jira] [Updated] (AMBARI-18355) Introduce conditional dependencies in stack defition to handle blueprint validation gracefully

[ https://issues.apache.org/jira/browse/AMBARI-18355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-18355: --- Attachment: AMBARI-18355_v1.patch > Introduce conditional dependencies in stack defition to

[jira] [Created] (AMBARI-18363) Ambari authentication with Kerberos token

Robert Levas created AMBARI-18363: - Summary: Ambari authentication with Kerberos token Key: AMBARI-18363 URL: https://issues.apache.org/jira/browse/AMBARI-18363 Project: Ambari Issue Type:

[jira] [Commented] (AMBARI-18324) Externalize skip repo url check to ambari.properties instead of hardcoding it in Ambari Java code

[ https://issues.apache.org/jira/browse/AMBARI-18324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484632#comment-15484632 ] Hudson commented on AMBARI-18324: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5652 (See

[jira] [Commented] (AMBARI-18359) Get LDAP tests to run in concurrent forked JVMs

[ https://issues.apache.org/jira/browse/AMBARI-18359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484519#comment-15484519 ] Hadoop QA commented on AMBARI-18359: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Created] (AMBARI-18362) Update sinks to read multiple collector hostnames from configs

Dmytro Sen created AMBARI-18362: --- Summary: Update sinks to read multiple collector hostnames from configs Key: AMBARI-18362 URL: https://issues.apache.org/jira/browse/AMBARI-18362 Project: Ambari

[jira] [Updated] (AMBARI-18362) Update sinks to read multiple collector hostnames from configs

[ https://issues.apache.org/jira/browse/AMBARI-18362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-18362: Status: Patch Available (was: Open) > Update sinks to read multiple collector hostnames from

[jira] [Updated] (AMBARI-18355) Introduce conditional dependencies in stack defition to handle blueprint validation gracefully

[ https://issues.apache.org/jira/browse/AMBARI-18355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-18355: --- Status: Open (was: Patch Available) > Introduce conditional dependencies in stack defition

[jira] [Updated] (AMBARI-18051) Services should be able to provide their own pre-req checks by supplying a jar file

[ https://issues.apache.org/jira/browse/AMBARI-18051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-18051: Description: Services should be able to provide their own pre-req checks by supplying a jar

[jira] [Created] (AMBARI-18365) Add Ambari configuration options to support Kerberos token authentication

Robert Levas created AMBARI-18365: - Summary: Add Ambari configuration options to support Kerberos token authentication Key: AMBARI-18365 URL: https://issues.apache.org/jira/browse/AMBARI-18365

[jira] [Updated] (AMBARI-17728) Error message does not deliver when executing ambari-server command as a non-root user

[ https://issues.apache.org/jira/browse/AMBARI-17728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-17728: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Error message does not

[jira] [Commented] (AMBARI-17728) Error message does not deliver when executing ambari-server command as a non-root user

[ https://issues.apache.org/jira/browse/AMBARI-17728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484609#comment-15484609 ] Jayush Luniya commented on AMBARI-17728: commit e4cb41e0ab469788180f3ac5741d331706b46ea0 Author:

[jira] [Updated] (AMBARI-15538) Support service-specific repo for add-on services

[ https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-15538: --- Attachment: (was: AMBARI-15538-trunk-v1.patch) > Support service-specific repo

[jira] [Updated] (AMBARI-15538) Support service-specific repo for add-on services

[ https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-15538: --- Status: Open (was: Patch Available) > Support service-specific repo for add-on

[jira] [Created] (AMBARI-18368) Atlas web UI alert after performing stack upgrade to HDP 2.5 and adding Atlas Service

Alejandro Fernandez created AMBARI-18368: Summary: Atlas web UI alert after performing stack upgrade to HDP 2.5 and adding Atlas Service Key: AMBARI-18368 URL:

[jira] [Assigned] (AMBARI-18364) Ambari authentication with Kerberos token

[ https://issues.apache.org/jira/browse/AMBARI-18364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas reassigned AMBARI-18364: - Assignee: Robert Levas > Ambari authentication with Kerberos token >

[jira] [Updated] (AMBARI-18365) Add Ambari configuration options to support Kerberos token authentication

[ https://issues.apache.org/jira/browse/AMBARI-18365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-18365: -- Status: Patch Available (was: Open) > Add Ambari configuration options to support Kerberos

[jira] [Created] (AMBARI-18367) Create authentication filter to encapsulate the various Ambari authentication methods

Robert Levas created AMBARI-18367: - Summary: Create authentication filter to encapsulate the various Ambari authentication methods Key: AMBARI-18367 URL: https://issues.apache.org/jira/browse/AMBARI-18367

[jira] [Commented] (AMBARI-18237) Certain configuration files cannot be modified through Ambari api.

[ https://issues.apache.org/jira/browse/AMBARI-18237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15485220#comment-15485220 ] Hudson commented on AMBARI-18237: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5654 (See

[jira] [Commented] (AMBARI-18351) Preserve output while executing HSI/LLAP's "run.sh" command for launching LLAP.

[ https://issues.apache.org/jira/browse/AMBARI-18351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15485221#comment-15485221 ] Hudson commented on AMBARI-18351: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5654 (See

[jira] [Updated] (AMBARI-18365) Add Ambari configuration options to support Kerberos token authentication

[ https://issues.apache.org/jira/browse/AMBARI-18365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-18365: -- Attachment: AMBARI-18365_trunk_01.patch AMBARI-18365_branch-2.5_01.patch >

[jira] [Updated] (AMBARI-15538) Support service-specific repo for add-on services

[ https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-15538: --- Attachment: AMBARI-15538-custom-repos-patch3-trunk.diff Latest patch. > Support

[jira] [Updated] (AMBARI-15538) Support service-specific repo for add-on services

[ https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-15538: --- Status: Patch Available (was: Open) > Support service-specific repo for add-on

[jira] [Updated] (AMBARI-18051) Services should be able to provide their own pre-req checks by supplying a jar file

[ https://issues.apache.org/jira/browse/AMBARI-18051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-18051: Summary: Services should be able to provide their own pre-req checks by supplying a jar file

[jira] [Commented] (AMBARI-18324) Externalize skip repo url check to ambari.properties instead of hardcoding it in Ambari Java code

[ https://issues.apache.org/jira/browse/AMBARI-18324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484657#comment-15484657 ] Di Li commented on AMBARI-18324: [ERROR] Failed to execute goal

[jira] [Updated] (AMBARI-18368) Atlas web UI alert after performing stack upgrade to HDP 2.5 and adding Atlas Service

[ https://issues.apache.org/jira/browse/AMBARI-18368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18368: - Attachment: (was: AMBARI-18368.patch) > Atlas web UI alert after performing

[jira] [Created] (AMBARI-18366) YAML Maps For Storm Are Not Being Escaped Correctly

Jonathan Hurley created AMBARI-18366: Summary: YAML Maps For Storm Are Not Being Escaped Correctly Key: AMBARI-18366 URL: https://issues.apache.org/jira/browse/AMBARI-18366 Project: Ambari

[jira] [Updated] (AMBARI-18334) Password in the configurations.json file in the ambari-agent cache is not encrypted

[ https://issues.apache.org/jira/browse/AMBARI-18334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-18334: -- Attachment: (was: AMBARI-18334-Sep12.patch) > Password in the

[jira] [Updated] (AMBARI-18334) Password in the configurations.json file in the ambari-agent cache is not encrypted

[ https://issues.apache.org/jira/browse/AMBARI-18334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-18334: -- Attachment: AMBARI-18334-Sep12.patch > Password in the

[jira] [Commented] (AMBARI-18355) Introduce conditional dependencies in stack defition to handle blueprint validation gracefully

[ https://issues.apache.org/jira/browse/AMBARI-18355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15485151#comment-15485151 ] Hadoop QA commented on AMBARI-18355: {color:green}+1 overall{color}. Here are the results of

[jira] [Updated] (AMBARI-18334) Password in the configurations.json file in the ambari-agent cache is not encrypted

[ https://issues.apache.org/jira/browse/AMBARI-18334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-18334: -- Status: Patch Available (was: Open) > Password in the

[jira] [Updated] (AMBARI-18334) Password in the configurations.json file in the ambari-agent cache is not encrypted

[ https://issues.apache.org/jira/browse/AMBARI-18334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-18334: -- Status: Open (was: Patch Available) > Password in the

[jira] [Commented] (AMBARI-18368) Atlas web UI alert after performing stack upgrade to HDP 2.5 and adding Atlas Service

[ https://issues.apache.org/jira/browse/AMBARI-18368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15485944#comment-15485944 ] Alejandro Fernandez commented on AMBARI-18368: -- To summarize, Atlas is failing because

[jira] [Updated] (AMBARI-18368) Atlas web UI alert after performing stack upgrade to HDP 2.5 and adding Atlas Service

[ https://issues.apache.org/jira/browse/AMBARI-18368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18368: - Attachment: AMBARI-18368.patch > Atlas web UI alert after performing stack

[jira] [Updated] (AMBARI-18368) Atlas web UI alert after performing stack upgrade to HDP 2.5 and adding Atlas Service

[ https://issues.apache.org/jira/browse/AMBARI-18368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18368: - Status: Patch Available (was: Open) > Atlas web UI alert after performing

[jira] [Updated] (AMBARI-18368) Atlas web UI alert after performing stack upgrade to HDP 2.5 and adding Atlas Service

[ https://issues.apache.org/jira/browse/AMBARI-18368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18368: - Attachment: AMBARI-18368.patch > Atlas web UI alert after performing stack

[jira] [Commented] (AMBARI-18362) Update sinks to read multiple collector hostnames from configs

[ https://issues.apache.org/jira/browse/AMBARI-18362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15485445#comment-15485445 ] Hadoop QA commented on AMBARI-18362: {color:green}+1 overall{color}. Here are the results of

[jira] [Updated] (AMBARI-18334) Password in the configurations.json file in the ambari-agent cache is not encrypted

[ https://issues.apache.org/jira/browse/AMBARI-18334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-18334: -- Status: Open (was: Patch Available) > Password in the

[jira] [Updated] (AMBARI-18334) Password in the configurations.json file in the ambari-agent cache is not encrypted

[ https://issues.apache.org/jira/browse/AMBARI-18334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-18334: -- Attachment: (was: AMBARI-18334-Sep12.patch) > Password in the

[jira] [Commented] (AMBARI-18361) All classes recompiled due to Maven bug, even if none changed

[ https://issues.apache.org/jira/browse/AMBARI-18361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15485543#comment-15485543 ] Hadoop QA commented on AMBARI-18361: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Updated] (AMBARI-18334) Password in the configurations.json file in the ambari-agent cache is not encrypted

[ https://issues.apache.org/jira/browse/AMBARI-18334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-18334: -- Status: Patch Available (was: Open) > Password in the

[jira] [Commented] (AMBARI-18255) Add unique constraint to host_version table

[ https://issues.apache.org/jira/browse/AMBARI-18255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15485702#comment-15485702 ] Hudson commented on AMBARI-18255: - ABORTED: Integrated in Jenkins build Ambari-branch-2.5 #19 (See

[jira] [Updated] (AMBARI-18332) Blueprints: API should make available "setting" property from blueprint

[ https://issues.apache.org/jira/browse/AMBARI-18332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18332: --- Description: The following APIs do not retrieve *setting* section from the

[jira] [Updated] (AMBARI-18334) Password in the configurations.json file in the ambari-agent cache is not encrypted

[ https://issues.apache.org/jira/browse/AMBARI-18334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-18334: -- Attachment: AMBARI-18334-Sep12.patch > Password in the

[jira] [Updated] (AMBARI-18368) Atlas web UI alert after performing stack upgrade to HDP 2.5 and adding Atlas Service

[ https://issues.apache.org/jira/browse/AMBARI-18368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-18368: --- Fix Version/s: 2.5.0 > Atlas web UI alert after performing stack upgrade to HDP 2.5 and

[jira] [Commented] (AMBARI-17457) Modify the AMS stack scripts to support distributed collector

[ https://issues.apache.org/jira/browse/AMBARI-17457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15485490#comment-15485490 ] Hadoop QA commented on AMBARI-17457: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Commented] (AMBARI-8458) Add support for "add hosts" specifying host name, blueprint name and host group name

[ https://issues.apache.org/jira/browse/AMBARI-8458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15485695#comment-15485695 ] Amruta Borkar commented on AMBARI-8458: --- Hi Jeff, In point 1. The blueprint that is created. The

[jira] [Commented] (AMBARI-18368) Atlas web UI alert after performing stack upgrade to HDP 2.5 and adding Atlas Service

[ https://issues.apache.org/jira/browse/AMBARI-18368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15486256#comment-15486256 ] Hadoop QA commented on AMBARI-18368: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Commented] (AMBARI-18324) Externalize skip repo url check to ambari.properties instead of hardcoding it in Ambari Java code

[ https://issues.apache.org/jira/browse/AMBARI-18324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484240#comment-15484240 ] Di Li commented on AMBARI-18324: pushed to trunk as

[jira] [Updated] (AMBARI-18324) Externalize skip repo url check to ambari.properties instead of hardcoding it in Ambari Java code

[ https://issues.apache.org/jira/browse/AMBARI-18324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-18324: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Externalize skip repo url check to

[jira] [Commented] (AMBARI-17228) Blueprint deployments should support a "START_ONLY" provision_action for clusters

[ https://issues.apache.org/jira/browse/AMBARI-17228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484336#comment-15484336 ] Hudson commented on AMBARI-17228: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #17 (See

[jira] [Commented] (AMBARI-18260) Journal node restart failing on RU from HDP 2.4.x to 2.5 on Wire Encrypted cluster

[ https://issues.apache.org/jira/browse/AMBARI-18260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484380#comment-15484380 ] Hudson commented on AMBARI-18260: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5651 (See

[jira] [Commented] (AMBARI-18050) Upgrade pre-req check code needs to be decoupled from CheckDescription class

[ https://issues.apache.org/jira/browse/AMBARI-18050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484381#comment-15484381 ] Hudson commented on AMBARI-18050: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5651 (See

[jira] [Commented] (AMBARI-18360) ambari-agent check for unset variables (AMBARI-18317)

[ https://issues.apache.org/jira/browse/AMBARI-18360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484246#comment-15484246 ] Hadoop QA commented on AMBARI-18360: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Updated] (AMBARI-18050) Upgrade pre-req check code needs to be decoupled from CheckDescription class

[ https://issues.apache.org/jira/browse/AMBARI-18050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-18050: Resolution: Fixed Fix Version/s: trunk Status: Resolved (was: Patch Available)

[jira] [Commented] (AMBARI-18323) Cluster creation complete is missing from ambari-server log

[ https://issues.apache.org/jira/browse/AMBARI-18323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484335#comment-15484335 ] Hudson commented on AMBARI-18323: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #17 (See

[jira] [Updated] (AMBARI-18260) Journal node restart failing on RU from HDP 2.4.x to 2.5 on Wire Encrypted cluster

[ https://issues.apache.org/jira/browse/AMBARI-18260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-18260: --- Description: Type of upgrade : RU Upgrade from HDP (2.4.2.0) to 2.5 (on secure, Wire

  1   2   >