[jira] [Commented] (AMBARI-19005) 'conf.server' dir for HIVE1 and HIVE2 should have 700 permission and files in it should have 600 permission.

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15707746#comment-15707746
 ] 

Hadoop QA commented on AMBARI-19005:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12840962/AMBARI-19005.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/9452//console

This message is automatically generated.

> 'conf.server' dir for HIVE1 and HIVE2 should have 700 permission and files in 
> it should have 600 permission.
> 
>
> Key: AMBARI-19005
> URL: https://issues.apache.org/jira/browse/AMBARI-19005
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19005.patch
>
>
> **Existing permissions for Hive1 and Hive2's 'conf.server' and files in it 
> were :**
> **hive1:**
> -
> $ ls -ltr /usr/hdp/current/hive-server2/conf/ | grep conf.server
> drwxr-xr-x. 2 hive hadoop   4096 Nov 22 00:17 conf.server
> $ ls -ltr /usr/hdp/current/hive-server2/conf/conf.server/
> total 56
> -rw-r--r--. 1 hive hadoop  6784 Nov 16 00:16 mapred-site.xml
> -rw-r--r--. 1 hive hadoop 0 Nov 16 00:16 hive-default.xml.template
> -rw-r--r--. 1 hive hadoop 0 Nov 16 00:16 hive-env.sh.template
> -rw-r--r--. 1 hive hadoop  2652 Nov 16 00:16 hive-exec-log4j.properties
> -rw-r--r--. 1 hive hadoop  3050 Nov 16 00:16 hive-log4j.properties
> -rw-r--r--. 1 hive hadoop   563 Nov 16 00:16 hivemetastore-site.xml
> -rw-r--r--. 1 hive hadoop   898 Nov 16 00:16 
> hadoop-metrics2-hivemetastore.properties
> -rw-r--r--. 1 hive hadoop   677 Nov 16 00:17 hiveserver2-site.xml
> -rw-r--r--. 1 hive hadoop   898 Nov 16 00:17 
> hadoop-metrics2-hiveserver2.properties
> -rw-r--r--. 1 hive hadoop 19625 Nov 16 09:22 hive-site.xml
> -rw-r--r--. 1 hive hadoop  2163 Nov 16 10:08 hive-env.sh
> -
> **hive2:**
> -
> $ ls -ltr /usr/hdp/current/hive-server2-hive2/conf/ | grep conf.server
> drwxr-xr-x. 2 hive hadoop   4096 Nov 22 08:10 conf.server
> $ ls -ltr /etc/hive2/conf/conf.server/
> total 76
> -rw-r--r--. 1 hive hadoop  6784 Nov 16 08:10 mapred-site.xml
> -rw-r--r--. 1 hive hadoop 0 Nov 16 08:10 hive-default.xml.template
> -rw-r--r--. 1 hive hadoop 0 Nov 16 08:10 hive-env.sh.template
> -rw-r--r--. 1 hive hadoop   793 Nov 16 08:10 hiveserver2-site.xml
> -rw-r--r--. 1 hive hadoop  1675 Nov 16 08:10 hive-env.sh
> -rw-r--r--. 1 hive hadoop  6378 Nov 16 08:10 llap-daemon-log4j2.properties
> -rw-r--r--. 1 hive hadoop  2715 Nov 16 08:10 llap-cli-log4j2.properties
> -rw-r--r--. 1 hive hadoop  2757 Nov 16 08:10 hive-log4j2.properties
> -rw-r--r--. 1 hive hadoop  2287 Nov 16 08:10 hive-exec-log4j2.properties
> -rw-r--r--. 1 hive hadoop  1596 Nov 16 08:10 beeline-log4j2.properties
> -rw-r--r--. 1 hive hadoop   898 Nov 16 08:10 
> hadoop-metrics2-hiveserver2.properties
> -rw-r--r--. 1 hive hadoop   898 Nov 16 08:10 
> hadoop-metrics2-llapdaemon.properties
> -rw-r--r--. 1 hive hadoop   898 Nov 16 08:10 
> hadoop-metrics2-llaptaskscheduler.properties
> -rw-r--r--. 1 hive hadoop 23688 Nov 22 20:27 hive-site.xml
> -
> **New updated permissions for Hive1 and Hive2's 'conf.server' and files in it 
> are :**
> **hive1:**
> -
> $ ls -ltr /usr/hdp/current/hive-server2/conf/ | grep conf.server
> drwx--. 2 hive hadoop   4096 Nov 16 00:17 conf.server
> $ ls -ltr /usr/hdp/current/hive-server2/conf/conf.server
> total 56
> -rw---. 1 hive hadoop 0 Nov 16 00:16 hive-default.xml.template
> -rw---. 1 hive hadoop 0 Nov 16 00:16 hive-env.sh.template
> -rw---. 1 hive hadoop  2652 Nov 16 00:16 hive-exec-log4j.properties
> -rw---. 1 hive hadoop  3050 Nov 16 00:16 hive-log4j.properties
> -rw---. 1 hive hadoop   563 Nov 16 00:16 hivemetastore-site.xml
> -rw---. 1 hive hadoop   898 Nov 16 00:16 
> hadoop-metrics2-hivemetastore.properties
> -rw---. 1 hive hadoop   677 Nov 16 00:17 hiveserver2-site.xml
> -rw---. 1 hive hadoop   898 Nov 16 00:17 
> hadoop-metrics2-hiveserver2.properties
> -rw---. 1 hive hadoop 19625 Nov 16 09:22 

[jira] [Commented] (AMBARI-19023) After adding an Atlas server the first restart command fails since stop doesn't have any configs; if no pid dir exists during stop, perform no-op

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15707743#comment-15707743
 ] 

Hadoop QA commented on AMBARI-19023:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12840970/AMBARI-19023.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 
ambari-server.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9451//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9451//console

This message is automatically generated.

> After adding an Atlas server the first restart command fails since stop 
> doesn't have any configs; if no pid dir exists during stop, perform no-op
> -
>
> Key: AMBARI-19023
> URL: https://issues.apache.org/jira/browse/AMBARI-19023
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
> Attachments: AMBARI-19023.patch
>
>
> Whenever adding an Atlas Server on a host, if the user executes the first 
> command as a "restart" (stop+start) instead of a "start" command, then the 
> stop command will fail because Ambari will not have generated any configs yet 
> so Atlas' atlas_stop.py will fail.
> To fix it, during a stop command,
> If the pid dir doesn't exist, this means either
> 1. The user just added Atlas service and issued a restart command 
> (stop+start). So stop should be a no-op since there's nothing to stop because 
> the pid dir does not exist.
> OR
> 2. The user changed the value of the pid dir config and incorrectly issued a 
> restart command.
> In which case the stop command cannot do anything since Ambari doesn't know 
> which process to kill.
> The start command will spawn another instance.
> The user should have issued a stop, changed the config, and then started it.
> Ambari generated this error.
> {code}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py",
>  line 199, in 
> MetadataServer().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 280, in execute
> method(env)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 685, in restart
> self.stop(env, upgrade_type=upgrade_type)
>   File 
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py",
>  line 95, in stop
> user=params.metadata_user,
>   File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
> line 155, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 160, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 124, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 273, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 71, in inner
> result = function(command, **kwargs)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 93, in checked_call
> tries=tries, try_sleep=try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'source 
> /etc/atlas/conf/atlas-env.sh; 
> /usr/hdp/current/atlas-server/bin/atlas_stop.py' returned 255.
> Exception: [Errno 13] Permission denied: '/usr/hdp/2.5.0.0-1169/atlas/logs' 
> Traceback (most recent call last):
>   File "/usr/hdp/current/atlas-server/bin/atlas_stop.py", line 68, in 
> returncode = main()
>   File 

[jira] [Commented] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information

[Hadoop QA (JIRA)]

[ 
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] [Updated] (AMBARI-19025) Livy Configuration Change for HDP 2.6

[Jeff Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jeff Zhang updated AMBARI-19025:

Description: We would use livy 0.3 in HDP 2.6. and need to add 
livy.spark.master to livy.conf and also update spark-blacklist.conf  (was: Need 
to add livy.spark.master to livy.conf and also update spark-blacklist.conf)

> Livy Configuration Change for HDP 2.6
> -
>
> Key: AMBARI-19025
> URL: https://issues.apache.org/jira/browse/AMBARI-19025
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Jeff Zhang
>Assignee: Jeff Zhang
>
> We would use livy 0.3 in HDP 2.6. and need to add livy.spark.master to 
> livy.conf and also update spark-blacklist.conf



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19025) Livy Configuration Change for HDP 2.6

[Jeff Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jeff Zhang updated AMBARI-19025:

Summary: Livy Configuration Change for HDP 2.6  (was: Livy Configuration 
Change for 2.6)

> Livy Configuration Change for HDP 2.6
> -
>
> Key: AMBARI-19025
> URL: https://issues.apache.org/jira/browse/AMBARI-19025
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Jeff Zhang
>Assignee: Jeff Zhang
>
> Need to add livy.spark.master to livy.conf and also update 
> spark-blacklist.conf



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-19025) Livy Configuration Change for 2.6

[Jeff Zhang (JIRA)]

Jeff Zhang created AMBARI-19025:
---

 Summary: Livy Configuration Change for 2.6
 Key: AMBARI-19025
 URL: https://issues.apache.org/jira/browse/AMBARI-19025
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.4.0
Reporter: Jeff Zhang
Assignee: Jeff Zhang


Need to add livy.spark.master to livy.conf and also update spark-blacklist.conf



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19022) Ambari-server: Remove credential store from KNOX stack definition since it does not support credential store

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15707613#comment-15707613
 ] 

Hudson commented on AMBARI-19022:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6112 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6112/])
AMBARI-19022: Ambari-server: Remove credential store from KNOX stack 
(nsomasundaram: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1fb8d0799eb9117868eb2a5df2312569fd07ed43])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/services/KNOX/metainfo.xml


> Ambari-server: Remove credential store from KNOX stack definition since it 
> does not support credential store
> 
>
> Key: AMBARI-19022
> URL: https://issues.apache.org/jira/browse/AMBARI-19022
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb54186.patch
>
>
> Remove *credential-store* information from HDP-2.5 stack definition for KNOX 
> since it does not support credential store.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19022) Ambari-server: Remove credential store from KNOX stack definition since it does not support credential store

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15707604#comment-15707604
 ] 

Hudson commented on AMBARI-19022:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #409 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/409/])
AMBARI-19022: Ambari-server: Remove credential store from KNOX stack 
(nsomasundaram: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8036eb247691f7e5278ab13bb36b60eaac4973df])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/services/KNOX/metainfo.xml


> Ambari-server: Remove credential store from KNOX stack definition since it 
> does not support credential store
> 
>
> Key: AMBARI-19022
> URL: https://issues.apache.org/jira/browse/AMBARI-19022
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb54186.patch
>
>
> Remove *credential-store* information from HDP-2.5 stack definition for KNOX 
> since it does not support credential store.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-19024) Handle Ambari upgrade changes to set hook flag if Atlas is available in cluster

[Mugdha Varadkar (JIRA)]

Mugdha Varadkar created AMBARI-19024:


 Summary: Handle Ambari upgrade changes to set hook flag if Atlas 
is available in cluster
 Key: AMBARI-19024
 URL: https://issues.apache.org/jira/browse/AMBARI-19024
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Reporter: Mugdha Varadkar
Assignee: Mugdha Varadkar
Priority: Critical
 Fix For: 3.0.0, 2.5.0


As a part of changes done in AMBARI-19007, need to handle Ambari upgrade 
scenario which will update the hook flag if ATLAS and hook supported services 
are present in existing cluster.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19022) Ambari-server: Remove credential store from KNOX stack definition since it does not support credential store

[Nahappan Somasundaram (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nahappan Somasundaram updated AMBARI-19022:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Ambari-server: Remove credential store from KNOX stack definition since it 
> does not support credential store
> 
>
> Key: AMBARI-19022
> URL: https://issues.apache.org/jira/browse/AMBARI-19022
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb54186.patch
>
>
> Remove *credential-store* information from HDP-2.5 stack definition for KNOX 
> since it does not support credential store.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information

[Nahappan Somasundaram (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nahappan Somasundaram updated AMBARI-1:
---
Status: Patch Available  (was: Open)

> 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] [Updated] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information

[Nahappan Somasundaram (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nahappan Somasundaram updated AMBARI-1:
---
Attachment: rb53747.patch

> 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] [Updated] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information

[Nahappan Somasundaram (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nahappan Somasundaram updated AMBARI-1:
---
Attachment: (was: rb53747.patch)

> 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] [Updated] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information

[Nahappan Somasundaram (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nahappan Somasundaram updated AMBARI-1:
---
Status: Open  (was: Patch Available)

> 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-18903) Implement Create Alerts: Create a base wizard for all steps

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-18903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15707266#comment-15707266
 ] 

Hudson commented on AMBARI-18903:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #408 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/408/])
Revert "AMBARI-18903. Implement Create Alerts: Create a base wizard for 
(xiwang: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=40fde4a65a4d21477db53d402af422348f1821eb])
* (edit) 
ambari-web/app/controllers/main/alerts/alert_definitions_actions_controller.js


> Implement Create Alerts: Create a base wizard for all steps
> ---
>
> Key: AMBARI-18903
> URL: https://issues.apache.org/jira/browse/AMBARI-18903
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Xi Wang
>Assignee: Xi Wang
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18903.patch
>
>
> This is a FE task to implement the "Create Alerts Wizard " based on the 
> design attached.
> This task is to create the the following files so that we have a blank base 
> wizard as a start point.
> *4 controllers* in folder: controllers/main/alerts/create
> wizard_controller.js  (should extend App.WizardController)
> step1_controller.js
> step2_controller.js
> step3_controller.js
> *4 views* in folder: views/main/alerts/create
> wizard_view.js  (extend sApp.WizardMenuMixin)
> step1_view.js
> step2_view.js
> step3_view.js
> *4 templates* in folder: templates/main/alerts/create
> wizard.hbs 
> step1.hbs
> step2.hbs
> step3.hbs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18912) Implement Create Alerts: step 1 select alert type

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-18912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15707267#comment-15707267
 ] 

Hudson commented on AMBARI-18912:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #408 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/408/])
Revert "AMBARI-18912. Implement Create Alerts: step 1 select alert (xiwang: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=be8354a5a987e9e92ca79cffb72496fc9a34fb4f])
* (edit) ambari-web/app/models/alerts/alert_definition.js
* (edit) ambari-web/app/styles/alerts.less
* (edit) ambari-web/app/controllers/main/alerts/definition_configs_controller.js
* (edit) ambari-web/app/messages.js
* (edit) ambari-web/app/views/main/alerts/add_alert_definition/step1_view.js
* (edit) 
ambari-web/app/controllers/main/alerts/add_alert_definition/step1_controller.js
* (edit) 
ambari-web/test/controllers/main/alerts/add_alert_definition/step1_controller_test.js
* (edit) ambari-web/app/templates/main/alerts/add_alert_definition/step1.hbs


> Implement Create Alerts: step 1 select alert type
> -
>
> Key: AMBARI-18912
> URL: https://issues.apache.org/jira/browse/AMBARI-18912
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 2.5.0
>
> Attachments: AMBARI-18912-branch-2.5.patch, AMBARI-18912.patch, 
> AMBARI-18912.patch, Screen Shot 2016-11-16 at 6.13.51 PM.png, Screen Shot 
> 2016-11-17 at 5.59.59 PM.png
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> This is a FE task to implement the "Create Alerts Wizard " based on the 
> design attached.
> In this task, should implement the step 1 in the design. All available alert 
> types should be displayed as options with icon, type and description. Make 
> sure that on clicking a type use would jump to next step.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19022) Ambari-server: Remove credential store from KNOX stack definition since it does not support credential store

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15707252#comment-15707252
 ] 

Hadoop QA commented on AMBARI-19022:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12840942/rb54186.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 test build failed in ambari-server 

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9449//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9449//console

This message is automatically generated.

> Ambari-server: Remove credential store from KNOX stack definition since it 
> does not support credential store
> 
>
> Key: AMBARI-19022
> URL: https://issues.apache.org/jira/browse/AMBARI-19022
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb54186.patch
>
>
> Remove *credential-store* information from HDP-2.5 stack definition for KNOX 
> since it does not support credential store.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18929) Yarn service check fails when either resource manager is down in HA enabled cluster

[Weiwei Yang (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-18929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15707233#comment-15707233
 ] 

Weiwei Yang commented on AMBARI-18929:
--

Hello [~afernandez]

Can you please help to review the v2 patch in the ReviewBoard? 

> Yarn service check fails when either resource manager is down in HA enabled 
> cluster
> ---
>
> Key: AMBARI-18929
> URL: https://issues.apache.org/jira/browse/AMBARI-18929
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Weiwei Yang
> Attachments: AMBARI-18929_trunk.02.patch, AMBARI-18929_trunk.patch
>
>
> When HA is enabled, yarn service_check.py fails if one of RM is down, even 
> the other one is active. This gives user the wrong impression the yarn 
> cluster is not healthy. Instead, service check should pass, or at least pass 
> with warning that lets user know there is one RM down.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18736) Perf: Simulate alerts for multiple Ambari Agents running on single Host

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-18736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15707182#comment-15707182
 ] 

Hadoop QA commented on AMBARI-18736:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12840943/AMBARI-18736.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:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9448//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9448//console

This message is automatically generated.

> Perf: Simulate alerts for multiple Ambari Agents running on single Host
> ---
>
> Key: AMBARI-18736
> URL: https://issues.apache.org/jira/browse/AMBARI-18736
> Project: Ambari
>  Issue Type: Story
>  Components: ambari-agent
>Affects Versions: 2.5.0
>Reporter: Alejandro Fernandez
>Assignee: Vitaly Brodetskyi
> Fix For: 2.5.0
>
> Attachments: AMBARI-18736.patch
>
>
> The PERF stack can actually create Python scripts to run actual alerts whose 
> behavior is controlled by configs to either always pass, always fail, pass 
> with some success %, flip/thrash, timeout, etc.
> For other types of alerts (web, host:port), we will need to override the 
> Alert Scheduler on the Ambari Agent to return fake values.
> The goal is to stress test Ambari Server when multiple Ambari Agents run on a 
> single host.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19023) After adding an Atlas server the first restart command fails since stop doesn't have any configs; if no pid dir exists during stop, perform no-op

[Alejandro Fernandez (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alejandro Fernandez updated AMBARI-19023:
-
Status: Patch Available  (was: Open)

> After adding an Atlas server the first restart command fails since stop 
> doesn't have any configs; if no pid dir exists during stop, perform no-op
> -
>
> Key: AMBARI-19023
> URL: https://issues.apache.org/jira/browse/AMBARI-19023
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
> Attachments: AMBARI-19023.patch
>
>
> Whenever adding an Atlas Server on a host, if the user executes the first 
> command as a "restart" (stop+start) instead of a "start" command, then the 
> stop command will fail because Ambari will not have generated any configs yet 
> so Atlas' atlas_stop.py will fail.
> To fix it, during a stop command,
> If the pid dir doesn't exist, this means either
> 1. The user just added Atlas service and issued a restart command 
> (stop+start). So stop should be a no-op since there's nothing to stop because 
> the pid dir does not exist.
> OR
> 2. The user changed the value of the pid dir config and incorrectly issued a 
> restart command.
> In which case the stop command cannot do anything since Ambari doesn't know 
> which process to kill.
> The start command will spawn another instance.
> The user should have issued a stop, changed the config, and then started it.
> Ambari generated this error.
> {code}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py",
>  line 199, in 
> MetadataServer().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 280, in execute
> method(env)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 685, in restart
> self.stop(env, upgrade_type=upgrade_type)
>   File 
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py",
>  line 95, in stop
> user=params.metadata_user,
>   File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
> line 155, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 160, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 124, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 273, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 71, in inner
> result = function(command, **kwargs)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 93, in checked_call
> tries=tries, try_sleep=try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'source 
> /etc/atlas/conf/atlas-env.sh; 
> /usr/hdp/current/atlas-server/bin/atlas_stop.py' returned 255.
> Exception: [Errno 13] Permission denied: '/usr/hdp/2.5.0.0-1169/atlas/logs' 
> Traceback (most recent call last):
>   File "/usr/hdp/current/atlas-server/bin/atlas_stop.py", line 68, in 
> returncode = main()
>   File "/usr/hdp/current/atlas-server/bin/atlas_stop.py", line 31, in main
> mc.dirMustExist(mc.logDir(atlas_home))
>   File "/usr/hdp/2.5.0.0-1169/atlas/bin/atlas_config.py", line 147, in 
> dirMustExist
> os.mkdir(dirname)
> OSError: [Errno 13] Permission denied: '/usr/hdp/2.5.0.0-1169/atlas/logs'
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19023) After adding an Atlas server the first restart command fails since stop doesn't have any configs; if no pid dir exists during stop, perform no-op

[Alejandro Fernandez (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alejandro Fernandez updated AMBARI-19023:
-
Attachment: AMBARI-19023.patch

> After adding an Atlas server the first restart command fails since stop 
> doesn't have any configs; if no pid dir exists during stop, perform no-op
> -
>
> Key: AMBARI-19023
> URL: https://issues.apache.org/jira/browse/AMBARI-19023
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
> Attachments: AMBARI-19023.patch
>
>
> Whenever adding an Atlas Server on a host, if the user executes the first 
> command as a "restart" (stop+start) instead of a "start" command, then the 
> stop command will fail because Ambari will not have generated any configs yet 
> so Atlas' atlas_stop.py will fail.
> To fix it, during a stop command,
> If the pid dir doesn't exist, this means either
> 1. The user just added Atlas service and issued a restart command 
> (stop+start). So stop should be a no-op since there's nothing to stop because 
> the pid dir does not exist.
> OR
> 2. The user changed the value of the pid dir config and incorrectly issued a 
> restart command.
> In which case the stop command cannot do anything since Ambari doesn't know 
> which process to kill.
> The start command will spawn another instance.
> The user should have issued a stop, changed the config, and then started it.
> Ambari generated this error.
> {code}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py",
>  line 199, in 
> MetadataServer().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 280, in execute
> method(env)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 685, in restart
> self.stop(env, upgrade_type=upgrade_type)
>   File 
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py",
>  line 95, in stop
> user=params.metadata_user,
>   File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
> line 155, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 160, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 124, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 273, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 71, in inner
> result = function(command, **kwargs)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 93, in checked_call
> tries=tries, try_sleep=try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'source 
> /etc/atlas/conf/atlas-env.sh; 
> /usr/hdp/current/atlas-server/bin/atlas_stop.py' returned 255.
> Exception: [Errno 13] Permission denied: '/usr/hdp/2.5.0.0-1169/atlas/logs' 
> Traceback (most recent call last):
>   File "/usr/hdp/current/atlas-server/bin/atlas_stop.py", line 68, in 
> returncode = main()
>   File "/usr/hdp/current/atlas-server/bin/atlas_stop.py", line 31, in main
> mc.dirMustExist(mc.logDir(atlas_home))
>   File "/usr/hdp/2.5.0.0-1169/atlas/bin/atlas_config.py", line 147, in 
> dirMustExist
> os.mkdir(dirname)
> OSError: [Errno 13] Permission denied: '/usr/hdp/2.5.0.0-1169/atlas/logs'
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18792) Update some configuration properties for hive interactive for the HDP 2.6 stack

[Sumit Mohanty (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sumit Mohanty updated AMBARI-18792:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Update some configuration properties for hive interactive for the HDP 2.6 
> stack
> ---
>
> Key: AMBARI-18792
> URL: https://issues.apache.org/jira/browse/AMBARI-18792
> Project: Ambari
>  Issue Type: Task
>  Components: stacks
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-18792.01.patch, AMBARI-18792.02.patch, 
> AMBARI-18792.03.patch, AMBARI-18792.04.patch, AMBARI-18792.05.patch, 
> AMBARI-18792.05.patch, AMBARI-18792.06.patch, AMBARI-18792.07.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19006) EU to message users to start YARN queues if work preserving recovery is disabled

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15707124#comment-15707124
 ] 

Hadoop QA commented on AMBARI-19006:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12840953/AMBARI-19006.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.upgrade.UpgradeCatalog250Test

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9447//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9447//console

This message is automatically generated.

> EU to message users to start YARN queues if work preserving recovery is 
> disabled
> 
>
> Key: AMBARI-19006
> URL: https://issues.apache.org/jira/browse/AMBARI-19006
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
> Attachments: AMBARI-19006.patch
>
>
> Today, the Express Upgrade packs message users to stop YARN queues if they do 
> not have work preserving recovery enabled.
> However, there's no message reminding users to enable it again.
> E.g.,
> {code}
> 
>   false
>   true
>   
>   
>  property="yarn.resourcemanager.work-preserving-recovery.enabled" value="true" 
> comparison="not-equal"/>
> 
>   Before continuing, please start all YARN queues if you 
> stopped them in a previous step.
> 
>   
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-19023) After adding an Atlas server the first restart command fails since stop doesn't have any configs; if no pid dir exists during stop, perform no-op

[Alejandro Fernandez (JIRA)]

Alejandro Fernandez created AMBARI-19023:


 Summary: After adding an Atlas server the first restart command 
fails since stop doesn't have any configs; if no pid dir exists during stop, 
perform no-op
 Key: AMBARI-19023
 URL: https://issues.apache.org/jira/browse/AMBARI-19023
 Project: Ambari
  Issue Type: Bug
  Components: stacks
Affects Versions: 2.4.0
Reporter: Alejandro Fernandez
Assignee: Alejandro Fernandez
 Fix For: 2.5.0


Whenever adding an Atlas Server on a host, if the user executes the first 
command as a "restart" (stop+start) instead of a "start" command, then the stop 
command will fail because Ambari will not have generated any configs yet so 
Atlas' atlas_stop.py will fail.

To fix it, during a stop command,
If the pid dir doesn't exist, this means either
1. The user just added Atlas service and issued a restart command (stop+start). 
So stop should be a no-op since there's nothing to stop because the pid dir 
does not exist.

OR

2. The user changed the value of the pid dir config and incorrectly issued a 
restart command.
In which case the stop command cannot do anything since Ambari doesn't know 
which process to kill.
The start command will spawn another instance.
The user should have issued a stop, changed the config, and then started it.

Ambari generated this error.
{code}
Traceback (most recent call last):
  File 
"/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py",
 line 199, in 
MetadataServer().execute()
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
 line 280, in execute
method(env)
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
 line 685, in restart
self.stop(env, upgrade_type=upgrade_type)
  File 
"/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py",
 line 95, in stop
user=params.metadata_user,
  File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
line 155, in __init__
self.env.run()
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
line 160, in run
self.run_action(resource, action)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
line 124, in run_action
provider_action()
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
 line 273, in action_run
tries=self.resource.tries, try_sleep=self.resource.try_sleep)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 71, in inner
result = function(command, **kwargs)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 93, in checked_call
tries=tries, try_sleep=try_sleep)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 141, in _call_wrapper
result = _call(command, **kwargs_copy)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 294, in _call
raise Fail(err_msg)
resource_management.core.exceptions.Fail: Execution of 'source 
/etc/atlas/conf/atlas-env.sh; /usr/hdp/current/atlas-server/bin/atlas_stop.py' 
returned 255.
Exception: [Errno 13] Permission denied: '/usr/hdp/2.5.0.0-1169/atlas/logs' 
Traceback (most recent call last):
  File "/usr/hdp/current/atlas-server/bin/atlas_stop.py", line 68, in 
returncode = main()
  File "/usr/hdp/current/atlas-server/bin/atlas_stop.py", line 31, in main
mc.dirMustExist(mc.logDir(atlas_home))
  File "/usr/hdp/2.5.0.0-1169/atlas/bin/atlas_config.py", line 147, in 
dirMustExist
os.mkdir(dirname)
OSError: [Errno 13] Permission denied: '/usr/hdp/2.5.0.0-1169/atlas/logs'
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18792) Update some configuration properties for hive interactive for the HDP 2.6 stack

[Sumit Mohanty (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sumit Mohanty updated AMBARI-18792:
---
Status: Patch Available  (was: Open)

> Update some configuration properties for hive interactive for the HDP 2.6 
> stack
> ---
>
> Key: AMBARI-18792
> URL: https://issues.apache.org/jira/browse/AMBARI-18792
> Project: Ambari
>  Issue Type: Task
>  Components: stacks
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-18792.01.patch, AMBARI-18792.02.patch, 
> AMBARI-18792.03.patch, AMBARI-18792.04.patch, AMBARI-18792.05.patch, 
> AMBARI-18792.05.patch, AMBARI-18792.06.patch, AMBARI-18792.07.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18792) Update some configuration properties for hive interactive for the HDP 2.6 stack

[Sumit Mohanty (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sumit Mohanty updated AMBARI-18792:
---
Status: Open  (was: Patch Available)

> Update some configuration properties for hive interactive for the HDP 2.6 
> stack
> ---
>
> Key: AMBARI-18792
> URL: https://issues.apache.org/jira/browse/AMBARI-18792
> Project: Ambari
>  Issue Type: Task
>  Components: stacks
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-18792.01.patch, AMBARI-18792.02.patch, 
> AMBARI-18792.03.patch, AMBARI-18792.04.patch, AMBARI-18792.05.patch, 
> AMBARI-18792.05.patch, AMBARI-18792.06.patch, AMBARI-18792.07.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18792) Update some configuration properties for hive interactive for the HDP 2.6 stack

[Sumit Mohanty (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sumit Mohanty updated AMBARI-18792:
---
Attachment: AMBARI-18792.07.patch

> Update some configuration properties for hive interactive for the HDP 2.6 
> stack
> ---
>
> Key: AMBARI-18792
> URL: https://issues.apache.org/jira/browse/AMBARI-18792
> Project: Ambari
>  Issue Type: Task
>  Components: stacks
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-18792.01.patch, AMBARI-18792.02.patch, 
> AMBARI-18792.03.patch, AMBARI-18792.04.patch, AMBARI-18792.05.patch, 
> AMBARI-18792.05.patch, AMBARI-18792.06.patch, AMBARI-18792.07.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18792) Update some configuration properties for hive interactive for the HDP 2.6 stack

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-18792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15707093#comment-15707093
 ] 

Hudson commented on AMBARI-18792:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6111 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6111/])
AMBARI-18792. Update some configuration properties for hive interactive 
(smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ca7e071f044d70186c7bf9d18bf24c29f3767730])
* (add) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/tez-interactive-site.xml
* (add) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/hive-interactive-site.xml
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java


> Update some configuration properties for hive interactive for the HDP 2.6 
> stack
> ---
>
> Key: AMBARI-18792
> URL: https://issues.apache.org/jira/browse/AMBARI-18792
> Project: Ambari
>  Issue Type: Task
>  Components: stacks
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-18792.01.patch, AMBARI-18792.02.patch, 
> AMBARI-18792.03.patch, AMBARI-18792.04.patch, AMBARI-18792.05.patch, 
> AMBARI-18792.05.patch, AMBARI-18792.06.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19005) 'conf.server' dir for HIVE1 and HIVE2 should have 700 permission and files in it should have 600 permission.

[Swapan Shridhar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapan Shridhar updated AMBARI-19005:
-
Status: Patch Available  (was: Open)

> 'conf.server' dir for HIVE1 and HIVE2 should have 700 permission and files in 
> it should have 600 permission.
> 
>
> Key: AMBARI-19005
> URL: https://issues.apache.org/jira/browse/AMBARI-19005
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19005.patch
>
>
> **Existing permissions for Hive1 and Hive2's 'conf.server' and files in it 
> were :**
> **hive1:**
> -
> $ ls -ltr /usr/hdp/current/hive-server2/conf/ | grep conf.server
> drwxr-xr-x. 2 hive hadoop   4096 Nov 22 00:17 conf.server
> $ ls -ltr /usr/hdp/current/hive-server2/conf/conf.server/
> total 56
> -rw-r--r--. 1 hive hadoop  6784 Nov 16 00:16 mapred-site.xml
> -rw-r--r--. 1 hive hadoop 0 Nov 16 00:16 hive-default.xml.template
> -rw-r--r--. 1 hive hadoop 0 Nov 16 00:16 hive-env.sh.template
> -rw-r--r--. 1 hive hadoop  2652 Nov 16 00:16 hive-exec-log4j.properties
> -rw-r--r--. 1 hive hadoop  3050 Nov 16 00:16 hive-log4j.properties
> -rw-r--r--. 1 hive hadoop   563 Nov 16 00:16 hivemetastore-site.xml
> -rw-r--r--. 1 hive hadoop   898 Nov 16 00:16 
> hadoop-metrics2-hivemetastore.properties
> -rw-r--r--. 1 hive hadoop   677 Nov 16 00:17 hiveserver2-site.xml
> -rw-r--r--. 1 hive hadoop   898 Nov 16 00:17 
> hadoop-metrics2-hiveserver2.properties
> -rw-r--r--. 1 hive hadoop 19625 Nov 16 09:22 hive-site.xml
> -rw-r--r--. 1 hive hadoop  2163 Nov 16 10:08 hive-env.sh
> -
> **hive2:**
> -
> $ ls -ltr /usr/hdp/current/hive-server2-hive2/conf/ | grep conf.server
> drwxr-xr-x. 2 hive hadoop   4096 Nov 22 08:10 conf.server
> $ ls -ltr /etc/hive2/conf/conf.server/
> total 76
> -rw-r--r--. 1 hive hadoop  6784 Nov 16 08:10 mapred-site.xml
> -rw-r--r--. 1 hive hadoop 0 Nov 16 08:10 hive-default.xml.template
> -rw-r--r--. 1 hive hadoop 0 Nov 16 08:10 hive-env.sh.template
> -rw-r--r--. 1 hive hadoop   793 Nov 16 08:10 hiveserver2-site.xml
> -rw-r--r--. 1 hive hadoop  1675 Nov 16 08:10 hive-env.sh
> -rw-r--r--. 1 hive hadoop  6378 Nov 16 08:10 llap-daemon-log4j2.properties
> -rw-r--r--. 1 hive hadoop  2715 Nov 16 08:10 llap-cli-log4j2.properties
> -rw-r--r--. 1 hive hadoop  2757 Nov 16 08:10 hive-log4j2.properties
> -rw-r--r--. 1 hive hadoop  2287 Nov 16 08:10 hive-exec-log4j2.properties
> -rw-r--r--. 1 hive hadoop  1596 Nov 16 08:10 beeline-log4j2.properties
> -rw-r--r--. 1 hive hadoop   898 Nov 16 08:10 
> hadoop-metrics2-hiveserver2.properties
> -rw-r--r--. 1 hive hadoop   898 Nov 16 08:10 
> hadoop-metrics2-llapdaemon.properties
> -rw-r--r--. 1 hive hadoop   898 Nov 16 08:10 
> hadoop-metrics2-llaptaskscheduler.properties
> -rw-r--r--. 1 hive hadoop 23688 Nov 22 20:27 hive-site.xml
> -
> **New updated permissions for Hive1 and Hive2's 'conf.server' and files in it 
> are :**
> **hive1:**
> -
> $ ls -ltr /usr/hdp/current/hive-server2/conf/ | grep conf.server
> drwx--. 2 hive hadoop   4096 Nov 16 00:17 conf.server
> $ ls -ltr /usr/hdp/current/hive-server2/conf/conf.server
> total 56
> -rw---. 1 hive hadoop 0 Nov 16 00:16 hive-default.xml.template
> -rw---. 1 hive hadoop 0 Nov 16 00:16 hive-env.sh.template
> -rw---. 1 hive hadoop  2652 Nov 16 00:16 hive-exec-log4j.properties
> -rw---. 1 hive hadoop  3050 Nov 16 00:16 hive-log4j.properties
> -rw---. 1 hive hadoop   563 Nov 16 00:16 hivemetastore-site.xml
> -rw---. 1 hive hadoop   898 Nov 16 00:16 
> hadoop-metrics2-hivemetastore.properties
> -rw---. 1 hive hadoop   677 Nov 16 00:17 hiveserver2-site.xml
> -rw---. 1 hive hadoop   898 Nov 16 00:17 
> hadoop-metrics2-hiveserver2.properties
> -rw---. 1 hive hadoop 19625 Nov 16 09:22 hive-site.xml
> -rw---. 1 hive hadoop  6781 Nov 23 22:54 mapred-site.xml
> -rw---. 1 hive hadoop  2163 Nov 28 23:31 hive-env.sh
> -
> **hive2:**
> -
> $ ls -ltr /usr/hdp/current/hive-server2-hive2/conf/ | grep conf.server

[jira] [Updated] (AMBARI-19005) 'conf.server' dir for HIVE1 and HIVE2 should have 700 permission and files in it should have 600 permission.

[Swapan Shridhar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapan Shridhar updated AMBARI-19005:
-
Status: Open  (was: Patch Available)

> 'conf.server' dir for HIVE1 and HIVE2 should have 700 permission and files in 
> it should have 600 permission.
> 
>
> Key: AMBARI-19005
> URL: https://issues.apache.org/jira/browse/AMBARI-19005
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19005.patch
>
>
> **Existing permissions for Hive1 and Hive2's 'conf.server' and files in it 
> were :**
> **hive1:**
> -
> $ ls -ltr /usr/hdp/current/hive-server2/conf/ | grep conf.server
> drwxr-xr-x. 2 hive hadoop   4096 Nov 22 00:17 conf.server
> $ ls -ltr /usr/hdp/current/hive-server2/conf/conf.server/
> total 56
> -rw-r--r--. 1 hive hadoop  6784 Nov 16 00:16 mapred-site.xml
> -rw-r--r--. 1 hive hadoop 0 Nov 16 00:16 hive-default.xml.template
> -rw-r--r--. 1 hive hadoop 0 Nov 16 00:16 hive-env.sh.template
> -rw-r--r--. 1 hive hadoop  2652 Nov 16 00:16 hive-exec-log4j.properties
> -rw-r--r--. 1 hive hadoop  3050 Nov 16 00:16 hive-log4j.properties
> -rw-r--r--. 1 hive hadoop   563 Nov 16 00:16 hivemetastore-site.xml
> -rw-r--r--. 1 hive hadoop   898 Nov 16 00:16 
> hadoop-metrics2-hivemetastore.properties
> -rw-r--r--. 1 hive hadoop   677 Nov 16 00:17 hiveserver2-site.xml
> -rw-r--r--. 1 hive hadoop   898 Nov 16 00:17 
> hadoop-metrics2-hiveserver2.properties
> -rw-r--r--. 1 hive hadoop 19625 Nov 16 09:22 hive-site.xml
> -rw-r--r--. 1 hive hadoop  2163 Nov 16 10:08 hive-env.sh
> -
> **hive2:**
> -
> $ ls -ltr /usr/hdp/current/hive-server2-hive2/conf/ | grep conf.server
> drwxr-xr-x. 2 hive hadoop   4096 Nov 22 08:10 conf.server
> $ ls -ltr /etc/hive2/conf/conf.server/
> total 76
> -rw-r--r--. 1 hive hadoop  6784 Nov 16 08:10 mapred-site.xml
> -rw-r--r--. 1 hive hadoop 0 Nov 16 08:10 hive-default.xml.template
> -rw-r--r--. 1 hive hadoop 0 Nov 16 08:10 hive-env.sh.template
> -rw-r--r--. 1 hive hadoop   793 Nov 16 08:10 hiveserver2-site.xml
> -rw-r--r--. 1 hive hadoop  1675 Nov 16 08:10 hive-env.sh
> -rw-r--r--. 1 hive hadoop  6378 Nov 16 08:10 llap-daemon-log4j2.properties
> -rw-r--r--. 1 hive hadoop  2715 Nov 16 08:10 llap-cli-log4j2.properties
> -rw-r--r--. 1 hive hadoop  2757 Nov 16 08:10 hive-log4j2.properties
> -rw-r--r--. 1 hive hadoop  2287 Nov 16 08:10 hive-exec-log4j2.properties
> -rw-r--r--. 1 hive hadoop  1596 Nov 16 08:10 beeline-log4j2.properties
> -rw-r--r--. 1 hive hadoop   898 Nov 16 08:10 
> hadoop-metrics2-hiveserver2.properties
> -rw-r--r--. 1 hive hadoop   898 Nov 16 08:10 
> hadoop-metrics2-llapdaemon.properties
> -rw-r--r--. 1 hive hadoop   898 Nov 16 08:10 
> hadoop-metrics2-llaptaskscheduler.properties
> -rw-r--r--. 1 hive hadoop 23688 Nov 22 20:27 hive-site.xml
> -
> **New updated permissions for Hive1 and Hive2's 'conf.server' and files in it 
> are :**
> **hive1:**
> -
> $ ls -ltr /usr/hdp/current/hive-server2/conf/ | grep conf.server
> drwx--. 2 hive hadoop   4096 Nov 16 00:17 conf.server
> $ ls -ltr /usr/hdp/current/hive-server2/conf/conf.server
> total 56
> -rw---. 1 hive hadoop 0 Nov 16 00:16 hive-default.xml.template
> -rw---. 1 hive hadoop 0 Nov 16 00:16 hive-env.sh.template
> -rw---. 1 hive hadoop  2652 Nov 16 00:16 hive-exec-log4j.properties
> -rw---. 1 hive hadoop  3050 Nov 16 00:16 hive-log4j.properties
> -rw---. 1 hive hadoop   563 Nov 16 00:16 hivemetastore-site.xml
> -rw---. 1 hive hadoop   898 Nov 16 00:16 
> hadoop-metrics2-hivemetastore.properties
> -rw---. 1 hive hadoop   677 Nov 16 00:17 hiveserver2-site.xml
> -rw---. 1 hive hadoop   898 Nov 16 00:17 
> hadoop-metrics2-hiveserver2.properties
> -rw---. 1 hive hadoop 19625 Nov 16 09:22 hive-site.xml
> -rw---. 1 hive hadoop  6781 Nov 23 22:54 mapred-site.xml
> -rw---. 1 hive hadoop  2163 Nov 28 23:31 hive-env.sh
> -
> **hive2:**
> -
> $ ls -ltr /usr/hdp/current/hive-server2-hive2/conf/ | grep conf.server

[jira] [Updated] (AMBARI-19005) 'conf.server' dir for HIVE1 and HIVE2 should have 700 permission and files in it should have 600 permission.

[Swapan Shridhar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapan Shridhar updated AMBARI-19005:
-
Attachment: (was: AMBARI-19005.patch)

> 'conf.server' dir for HIVE1 and HIVE2 should have 700 permission and files in 
> it should have 600 permission.
> 
>
> Key: AMBARI-19005
> URL: https://issues.apache.org/jira/browse/AMBARI-19005
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19005.patch
>
>
> **Existing permissions for Hive1 and Hive2's 'conf.server' and files in it 
> were :**
> **hive1:**
> -
> $ ls -ltr /usr/hdp/current/hive-server2/conf/ | grep conf.server
> drwxr-xr-x. 2 hive hadoop   4096 Nov 22 00:17 conf.server
> $ ls -ltr /usr/hdp/current/hive-server2/conf/conf.server/
> total 56
> -rw-r--r--. 1 hive hadoop  6784 Nov 16 00:16 mapred-site.xml
> -rw-r--r--. 1 hive hadoop 0 Nov 16 00:16 hive-default.xml.template
> -rw-r--r--. 1 hive hadoop 0 Nov 16 00:16 hive-env.sh.template
> -rw-r--r--. 1 hive hadoop  2652 Nov 16 00:16 hive-exec-log4j.properties
> -rw-r--r--. 1 hive hadoop  3050 Nov 16 00:16 hive-log4j.properties
> -rw-r--r--. 1 hive hadoop   563 Nov 16 00:16 hivemetastore-site.xml
> -rw-r--r--. 1 hive hadoop   898 Nov 16 00:16 
> hadoop-metrics2-hivemetastore.properties
> -rw-r--r--. 1 hive hadoop   677 Nov 16 00:17 hiveserver2-site.xml
> -rw-r--r--. 1 hive hadoop   898 Nov 16 00:17 
> hadoop-metrics2-hiveserver2.properties
> -rw-r--r--. 1 hive hadoop 19625 Nov 16 09:22 hive-site.xml
> -rw-r--r--. 1 hive hadoop  2163 Nov 16 10:08 hive-env.sh
> -
> **hive2:**
> -
> $ ls -ltr /usr/hdp/current/hive-server2-hive2/conf/ | grep conf.server
> drwxr-xr-x. 2 hive hadoop   4096 Nov 22 08:10 conf.server
> $ ls -ltr /etc/hive2/conf/conf.server/
> total 76
> -rw-r--r--. 1 hive hadoop  6784 Nov 16 08:10 mapred-site.xml
> -rw-r--r--. 1 hive hadoop 0 Nov 16 08:10 hive-default.xml.template
> -rw-r--r--. 1 hive hadoop 0 Nov 16 08:10 hive-env.sh.template
> -rw-r--r--. 1 hive hadoop   793 Nov 16 08:10 hiveserver2-site.xml
> -rw-r--r--. 1 hive hadoop  1675 Nov 16 08:10 hive-env.sh
> -rw-r--r--. 1 hive hadoop  6378 Nov 16 08:10 llap-daemon-log4j2.properties
> -rw-r--r--. 1 hive hadoop  2715 Nov 16 08:10 llap-cli-log4j2.properties
> -rw-r--r--. 1 hive hadoop  2757 Nov 16 08:10 hive-log4j2.properties
> -rw-r--r--. 1 hive hadoop  2287 Nov 16 08:10 hive-exec-log4j2.properties
> -rw-r--r--. 1 hive hadoop  1596 Nov 16 08:10 beeline-log4j2.properties
> -rw-r--r--. 1 hive hadoop   898 Nov 16 08:10 
> hadoop-metrics2-hiveserver2.properties
> -rw-r--r--. 1 hive hadoop   898 Nov 16 08:10 
> hadoop-metrics2-llapdaemon.properties
> -rw-r--r--. 1 hive hadoop   898 Nov 16 08:10 
> hadoop-metrics2-llaptaskscheduler.properties
> -rw-r--r--. 1 hive hadoop 23688 Nov 22 20:27 hive-site.xml
> -
> **New updated permissions for Hive1 and Hive2's 'conf.server' and files in it 
> are :**
> **hive1:**
> -
> $ ls -ltr /usr/hdp/current/hive-server2/conf/ | grep conf.server
> drwx--. 2 hive hadoop   4096 Nov 16 00:17 conf.server
> $ ls -ltr /usr/hdp/current/hive-server2/conf/conf.server
> total 56
> -rw---. 1 hive hadoop 0 Nov 16 00:16 hive-default.xml.template
> -rw---. 1 hive hadoop 0 Nov 16 00:16 hive-env.sh.template
> -rw---. 1 hive hadoop  2652 Nov 16 00:16 hive-exec-log4j.properties
> -rw---. 1 hive hadoop  3050 Nov 16 00:16 hive-log4j.properties
> -rw---. 1 hive hadoop   563 Nov 16 00:16 hivemetastore-site.xml
> -rw---. 1 hive hadoop   898 Nov 16 00:16 
> hadoop-metrics2-hivemetastore.properties
> -rw---. 1 hive hadoop   677 Nov 16 00:17 hiveserver2-site.xml
> -rw---. 1 hive hadoop   898 Nov 16 00:17 
> hadoop-metrics2-hiveserver2.properties
> -rw---. 1 hive hadoop 19625 Nov 16 09:22 hive-site.xml
> -rw---. 1 hive hadoop  6781 Nov 23 22:54 mapred-site.xml
> -rw---. 1 hive hadoop  2163 Nov 28 23:31 hive-env.sh
> -
> **hive2:**
> -
> $ ls -ltr /usr/hdp/current/hive-server2-hive2/conf/ | grep 

[jira] [Updated] (AMBARI-19005) 'conf.server' dir for HIVE1 and HIVE2 should have 700 permission and files in it should have 600 permission.

[Swapan Shridhar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapan Shridhar updated AMBARI-19005:
-
Attachment: AMBARI-19005.patch

> 'conf.server' dir for HIVE1 and HIVE2 should have 700 permission and files in 
> it should have 600 permission.
> 
>
> Key: AMBARI-19005
> URL: https://issues.apache.org/jira/browse/AMBARI-19005
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19005.patch
>
>
> **Existing permissions for Hive1 and Hive2's 'conf.server' and files in it 
> were :**
> **hive1:**
> -
> $ ls -ltr /usr/hdp/current/hive-server2/conf/ | grep conf.server
> drwxr-xr-x. 2 hive hadoop   4096 Nov 22 00:17 conf.server
> $ ls -ltr /usr/hdp/current/hive-server2/conf/conf.server/
> total 56
> -rw-r--r--. 1 hive hadoop  6784 Nov 16 00:16 mapred-site.xml
> -rw-r--r--. 1 hive hadoop 0 Nov 16 00:16 hive-default.xml.template
> -rw-r--r--. 1 hive hadoop 0 Nov 16 00:16 hive-env.sh.template
> -rw-r--r--. 1 hive hadoop  2652 Nov 16 00:16 hive-exec-log4j.properties
> -rw-r--r--. 1 hive hadoop  3050 Nov 16 00:16 hive-log4j.properties
> -rw-r--r--. 1 hive hadoop   563 Nov 16 00:16 hivemetastore-site.xml
> -rw-r--r--. 1 hive hadoop   898 Nov 16 00:16 
> hadoop-metrics2-hivemetastore.properties
> -rw-r--r--. 1 hive hadoop   677 Nov 16 00:17 hiveserver2-site.xml
> -rw-r--r--. 1 hive hadoop   898 Nov 16 00:17 
> hadoop-metrics2-hiveserver2.properties
> -rw-r--r--. 1 hive hadoop 19625 Nov 16 09:22 hive-site.xml
> -rw-r--r--. 1 hive hadoop  2163 Nov 16 10:08 hive-env.sh
> -
> **hive2:**
> -
> $ ls -ltr /usr/hdp/current/hive-server2-hive2/conf/ | grep conf.server
> drwxr-xr-x. 2 hive hadoop   4096 Nov 22 08:10 conf.server
> $ ls -ltr /etc/hive2/conf/conf.server/
> total 76
> -rw-r--r--. 1 hive hadoop  6784 Nov 16 08:10 mapred-site.xml
> -rw-r--r--. 1 hive hadoop 0 Nov 16 08:10 hive-default.xml.template
> -rw-r--r--. 1 hive hadoop 0 Nov 16 08:10 hive-env.sh.template
> -rw-r--r--. 1 hive hadoop   793 Nov 16 08:10 hiveserver2-site.xml
> -rw-r--r--. 1 hive hadoop  1675 Nov 16 08:10 hive-env.sh
> -rw-r--r--. 1 hive hadoop  6378 Nov 16 08:10 llap-daemon-log4j2.properties
> -rw-r--r--. 1 hive hadoop  2715 Nov 16 08:10 llap-cli-log4j2.properties
> -rw-r--r--. 1 hive hadoop  2757 Nov 16 08:10 hive-log4j2.properties
> -rw-r--r--. 1 hive hadoop  2287 Nov 16 08:10 hive-exec-log4j2.properties
> -rw-r--r--. 1 hive hadoop  1596 Nov 16 08:10 beeline-log4j2.properties
> -rw-r--r--. 1 hive hadoop   898 Nov 16 08:10 
> hadoop-metrics2-hiveserver2.properties
> -rw-r--r--. 1 hive hadoop   898 Nov 16 08:10 
> hadoop-metrics2-llapdaemon.properties
> -rw-r--r--. 1 hive hadoop   898 Nov 16 08:10 
> hadoop-metrics2-llaptaskscheduler.properties
> -rw-r--r--. 1 hive hadoop 23688 Nov 22 20:27 hive-site.xml
> -
> **New updated permissions for Hive1 and Hive2's 'conf.server' and files in it 
> are :**
> **hive1:**
> -
> $ ls -ltr /usr/hdp/current/hive-server2/conf/ | grep conf.server
> drwx--. 2 hive hadoop   4096 Nov 16 00:17 conf.server
> $ ls -ltr /usr/hdp/current/hive-server2/conf/conf.server
> total 56
> -rw---. 1 hive hadoop 0 Nov 16 00:16 hive-default.xml.template
> -rw---. 1 hive hadoop 0 Nov 16 00:16 hive-env.sh.template
> -rw---. 1 hive hadoop  2652 Nov 16 00:16 hive-exec-log4j.properties
> -rw---. 1 hive hadoop  3050 Nov 16 00:16 hive-log4j.properties
> -rw---. 1 hive hadoop   563 Nov 16 00:16 hivemetastore-site.xml
> -rw---. 1 hive hadoop   898 Nov 16 00:16 
> hadoop-metrics2-hivemetastore.properties
> -rw---. 1 hive hadoop   677 Nov 16 00:17 hiveserver2-site.xml
> -rw---. 1 hive hadoop   898 Nov 16 00:17 
> hadoop-metrics2-hiveserver2.properties
> -rw---. 1 hive hadoop 19625 Nov 16 09:22 hive-site.xml
> -rw---. 1 hive hadoop  6781 Nov 23 22:54 mapred-site.xml
> -rw---. 1 hive hadoop  2163 Nov 28 23:31 hive-env.sh
> -
> **hive2:**
> -
> $ ls -ltr /usr/hdp/current/hive-server2-hive2/conf/ | grep conf.server
> 

[jira] [Commented] (AMBARI-18792) Update some configuration properties for hive interactive for the HDP 2.6 stack

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-18792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15707082#comment-15707082
 ] 

Hudson commented on AMBARI-18792:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #407 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/407/])
AMBARI-18792. Update some configuration properties for hive interactive 
(smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=20735887018d4de6e4e5d67839a2aa30eea0f2ad])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java


> Update some configuration properties for hive interactive for the HDP 2.6 
> stack
> ---
>
> Key: AMBARI-18792
> URL: https://issues.apache.org/jira/browse/AMBARI-18792
> Project: Ambari
>  Issue Type: Task
>  Components: stacks
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-18792.01.patch, AMBARI-18792.02.patch, 
> AMBARI-18792.03.patch, AMBARI-18792.04.patch, AMBARI-18792.05.patch, 
> AMBARI-18792.05.patch, AMBARI-18792.06.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information

[Hadoop QA (JIRA)]

[ 
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-18871) HTTP responses needs to have the character encoding specified in the content type header

[Anita Gnanamalar Jebaraj (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-18871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15706951#comment-15706951
 ] 

Anita Gnanamalar Jebaraj commented on AMBARI-18871:
---

Thank you Sangeeta for pushing the changes

> HTTP responses needs to have the character encoding specified in the content 
> type header
> 
>
> Key: AMBARI-18871
> URL: https://issues.apache.org/jira/browse/AMBARI-18871
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Anita Gnanamalar Jebaraj
>Assignee: Anita Gnanamalar Jebaraj
> Fix For: trunk
>
> Attachments: AMBARI-18871-updated.patch, AMBARI-18871.patch
>
>
> The charset information(UTF-8) can be added to all the response headers to 
> harden the security for the client. When the charset information is not 
> specified the web browser may choose a different encoding by guessing which 
> encoding is actually being used by the web page. 
> This specific issue is mentioned in the section 3.1.1.5 of RFC7231



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information

[Nahappan Somasundaram (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nahappan Somasundaram updated AMBARI-1:
---
Attachment: rb53747.patch

> 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] [Updated] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information

[Nahappan Somasundaram (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nahappan Somasundaram updated AMBARI-1:
---
Status: Patch Available  (was: Open)

> 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] [Updated] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information

[Nahappan Somasundaram (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nahappan Somasundaram updated AMBARI-1:
---
Status: Open  (was: Patch Available)

> 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] [Updated] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information

[Nahappan Somasundaram (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nahappan Somasundaram updated AMBARI-1:
---
Attachment: (was: rb53747.patch)

> 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
>
> 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] [Updated] (AMBARI-19006) EU to message users to start YARN queues if work preserving recovery is disabled

[Alejandro Fernandez (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alejandro Fernandez updated AMBARI-19006:
-
Status: Patch Available  (was: Open)

> EU to message users to start YARN queues if work preserving recovery is 
> disabled
> 
>
> Key: AMBARI-19006
> URL: https://issues.apache.org/jira/browse/AMBARI-19006
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
> Attachments: AMBARI-19006.patch
>
>
> Today, the Express Upgrade packs message users to stop YARN queues if they do 
> not have work preserving recovery enabled.
> However, there's no message reminding users to enable it again.
> E.g.,
> {code}
> 
>   false
>   true
>   
>   
>  property="yarn.resourcemanager.work-preserving-recovery.enabled" value="true" 
> comparison="not-equal"/>
> 
>   Before continuing, please start all YARN queues if you 
> stopped them in a previous step.
> 
>   
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19006) EU to message users to start YARN queues if work preserving recovery is disabled

[Alejandro Fernandez (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alejandro Fernandez updated AMBARI-19006:
-
Status: Open  (was: Patch Available)

> EU to message users to start YARN queues if work preserving recovery is 
> disabled
> 
>
> Key: AMBARI-19006
> URL: https://issues.apache.org/jira/browse/AMBARI-19006
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
> Attachments: AMBARI-19006.patch
>
>
> Today, the Express Upgrade packs message users to stop YARN queues if they do 
> not have work preserving recovery enabled.
> However, there's no message reminding users to enable it again.
> E.g.,
> {code}
> 
>   false
>   true
>   
>   
>  property="yarn.resourcemanager.work-preserving-recovery.enabled" value="true" 
> comparison="not-equal"/>
> 
>   Before continuing, please start all YARN queues if you 
> stopped them in a previous step.
> 
>   
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19006) EU to message users to start YARN queues if work preserving recovery is disabled

[Alejandro Fernandez (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alejandro Fernandez updated AMBARI-19006:
-
Attachment: AMBARI-19006.patch

> EU to message users to start YARN queues if work preserving recovery is 
> disabled
> 
>
> Key: AMBARI-19006
> URL: https://issues.apache.org/jira/browse/AMBARI-19006
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
> Attachments: AMBARI-19006.patch
>
>
> Today, the Express Upgrade packs message users to stop YARN queues if they do 
> not have work preserving recovery enabled.
> However, there's no message reminding users to enable it again.
> E.g.,
> {code}
> 
>   false
>   true
>   
>   
>  property="yarn.resourcemanager.work-preserving-recovery.enabled" value="true" 
> comparison="not-equal"/>
> 
>   Before continuing, please start all YARN queues if you 
> stopped them in a previous step.
> 
>   
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19006) EU to message users to start YARN queues if work preserving recovery is disabled

[Alejandro Fernandez (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alejandro Fernandez updated AMBARI-19006:
-
Attachment: (was: AMBARI-19006.patch)

> EU to message users to start YARN queues if work preserving recovery is 
> disabled
> 
>
> Key: AMBARI-19006
> URL: https://issues.apache.org/jira/browse/AMBARI-19006
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
> Attachments: AMBARI-19006.patch
>
>
> Today, the Express Upgrade packs message users to stop YARN queues if they do 
> not have work preserving recovery enabled.
> However, there's no message reminding users to enable it again.
> E.g.,
> {code}
> 
>   false
>   true
>   
>   
>  property="yarn.resourcemanager.work-preserving-recovery.enabled" value="true" 
> comparison="not-equal"/>
> 
>   Before continuing, please start all YARN queues if you 
> stopped them in a previous step.
> 
>   
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19019) Knox HA Wizard

[Jaimin Jetly (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15706835#comment-15706835
 ] 

Jaimin Jetly commented on AMBARI-19019:
---

[~jeffreyr97] can you please share the wizard mockups that you are planning to 
implement ?

> Knox HA Wizard
> --
>
> Key: AMBARI-19019
> URL: https://issues.apache.org/jira/browse/AMBARI-19019
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Affects Versions: 2.5.0
> Environment: All
>Reporter: Jeffrey E  Rodriguez
>Assignee: Jeffrey E  Rodriguez
> Fix For: 2.5.0
>
>
> This feature is to  implement a Knox HA Wizard. (Model after existing HA 
> wizards).
> 1. Add HA Knox instances through Knox HA Wizard.
>- Sync up the topologies keystores for all Knox nodes. (to the initial 
> Knox topology).
>- Hook either HA Proxy or Apache server + ssl_mod + balancer_mod + 
> proxy_mod ( we could provide Wizard instructions).
>- Service check for Knox HA.
>- Restart Knox server.
>  
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19018) Services should be able to specify their own resources subdirs for sync'ing to agents

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15706837#comment-15706837
 ] 

Hadoop QA commented on AMBARI-19018:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12840908/AMBARI-19018.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 7 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 
ambari-server.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9445//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9445//console

This message is automatically generated.

> Services should be able to specify their own resources subdirs for sync'ing 
> to agents
> -
>
> Key: AMBARI-19018
> URL: https://issues.apache.org/jira/browse/AMBARI-19018
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-agent, ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Tim Thorpe
>Assignee: Tim Thorpe
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19018.patch
>
>
> A component should be able to specify a custom folder to sync to the agents 
> in the metainfo.xml.
> For example:
> 
>   METRICS_GRAFANA
>   Grafana
>   MASTER
>   dashboards
>   
> scripts/metrics_grafana.py
> This will sync the resources/dashboards directory to the agents if the 
> directory exists on the server.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18736) Perf: Simulate alerts for multiple Ambari Agents running on single Host

[Vitaly Brodetskyi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vitaly Brodetskyi updated AMBARI-18736:
---
Status: Patch Available  (was: Open)

> Perf: Simulate alerts for multiple Ambari Agents running on single Host
> ---
>
> Key: AMBARI-18736
> URL: https://issues.apache.org/jira/browse/AMBARI-18736
> Project: Ambari
>  Issue Type: Story
>  Components: ambari-agent
>Affects Versions: 2.5.0
>Reporter: Alejandro Fernandez
>Assignee: Vitaly Brodetskyi
> Fix For: 2.5.0
>
> Attachments: AMBARI-18736.patch
>
>
> The PERF stack can actually create Python scripts to run actual alerts whose 
> behavior is controlled by configs to either always pass, always fail, pass 
> with some success %, flip/thrash, timeout, etc.
> For other types of alerts (web, host:port), we will need to override the 
> Alert Scheduler on the Ambari Agent to return fake values.
> The goal is to stress test Ambari Server when multiple Ambari Agents run on a 
> single host.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (AMBARI-18736) Perf: Simulate alerts for multiple Ambari Agents running on single Host

[Vitaly Brodetskyi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vitaly Brodetskyi reassigned AMBARI-18736:
--

Assignee: Vitaly Brodetskyi

> Perf: Simulate alerts for multiple Ambari Agents running on single Host
> ---
>
> Key: AMBARI-18736
> URL: https://issues.apache.org/jira/browse/AMBARI-18736
> Project: Ambari
>  Issue Type: Story
>  Components: ambari-agent
>Affects Versions: 2.5.0
>Reporter: Alejandro Fernandez
>Assignee: Vitaly Brodetskyi
> Fix For: 2.5.0
>
> Attachments: AMBARI-18736.patch
>
>
> The PERF stack can actually create Python scripts to run actual alerts whose 
> behavior is controlled by configs to either always pass, always fail, pass 
> with some success %, flip/thrash, timeout, etc.
> For other types of alerts (web, host:port), we will need to override the 
> Alert Scheduler on the Ambari Agent to return fake values.
> The goal is to stress test Ambari Server when multiple Ambari Agents run on a 
> single host.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18736) Perf: Simulate alerts for multiple Ambari Agents running on single Host

[Vitaly Brodetskyi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vitaly Brodetskyi updated AMBARI-18736:
---
Attachment: AMBARI-18736.patch

> Perf: Simulate alerts for multiple Ambari Agents running on single Host
> ---
>
> Key: AMBARI-18736
> URL: https://issues.apache.org/jira/browse/AMBARI-18736
> Project: Ambari
>  Issue Type: Story
>  Components: ambari-agent
>Affects Versions: 2.5.0
>Reporter: Alejandro Fernandez
>Assignee: Vitaly Brodetskyi
> Fix For: 2.5.0
>
> Attachments: AMBARI-18736.patch
>
>
> The PERF stack can actually create Python scripts to run actual alerts whose 
> behavior is controlled by configs to either always pass, always fail, pass 
> with some success %, flip/thrash, timeout, etc.
> For other types of alerts (web, host:port), we will need to override the 
> Alert Scheduler on the Ambari Agent to return fake values.
> The goal is to stress test Ambari Server when multiple Ambari Agents run on a 
> single host.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19022) Ambari-server: Remove credential store from KNOX stack definition since it does not support credential store

[Nahappan Somasundaram (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nahappan Somasundaram updated AMBARI-19022:
---
Status: Patch Available  (was: Open)

> Ambari-server: Remove credential store from KNOX stack definition since it 
> does not support credential store
> 
>
> Key: AMBARI-19022
> URL: https://issues.apache.org/jira/browse/AMBARI-19022
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb54186.patch
>
>
> Remove *credential-store* information from HDP-2.5 stack definition for KNOX 
> since it does not support credential store.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19022) Ambari-server: Remove credential store from KNOX stack definition since it does not support credential store

[Nahappan Somasundaram (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nahappan Somasundaram updated AMBARI-19022:
---
Attachment: rb54186.patch

> Ambari-server: Remove credential store from KNOX stack definition since it 
> does not support credential store
> 
>
> Key: AMBARI-19022
> URL: https://issues.apache.org/jira/browse/AMBARI-19022
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb54186.patch
>
>
> Remove *credential-store* information from HDP-2.5 stack definition for KNOX 
> since it does not support credential store.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-19022) Ambari-server: Remove credential store from KNOX stack definition since it does not support credential store

[Nahappan Somasundaram (JIRA)]

Nahappan Somasundaram created AMBARI-19022:
--

 Summary: Ambari-server: Remove credential store from KNOX stack 
definition since it does not support credential store
 Key: AMBARI-19022
 URL: https://issues.apache.org/jira/browse/AMBARI-19022
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.5.0
Reporter: Nahappan Somasundaram
Assignee: Nahappan Somasundaram
 Fix For: 2.5.0


Remove *credential-store* information from HDP-2.5 stack definition for KNOX 
since it does not support credential store.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18871) HTTP responses needs to have the character encoding specified in the content type header

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-18871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15706778#comment-15706778
 ] 

Hudson commented on AMBARI-18871:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6110 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6110/])
AMBARI-18871 HTTP responses needs to have the character encoding (sangeetar: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2cc4c9ed7009be2e894fec7d24c3cb4f0dd9f24c])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/security/AmbariViewsSecurityHeaderFilter.java
* (edit) ambari-server/conf/windows/ambari.properties
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/security/AmbariServerSecurityHeaderFilter.java
* (edit) ambari-server/conf/unix/ambari.properties
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/security/AbstractSecurityHeaderFilter.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/security/AbstractSecurityHeaderFilterTest.java


> HTTP responses needs to have the character encoding specified in the content 
> type header
> 
>
> Key: AMBARI-18871
> URL: https://issues.apache.org/jira/browse/AMBARI-18871
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Anita Gnanamalar Jebaraj
>Assignee: Anita Gnanamalar Jebaraj
> Fix For: trunk
>
> Attachments: AMBARI-18871-updated.patch, AMBARI-18871.patch
>
>
> The charset information(UTF-8) can be added to all the response headers to 
> harden the security for the client. When the charset information is not 
> specified the web browser may choose a different encoding by guessing which 
> encoding is actually being used by the web page. 
> This specific issue is mentioned in the section 3.1.1.5 of RFC7231



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18792) Update some configuration properties for hive interactive for the HDP 2.6 stack

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-18792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15706752#comment-15706752
 ] 

Hudson commented on AMBARI-18792:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #406 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/406/])
AMBARI-18792. Update some configuration properties for hive interactive 
(smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f8bfa056574d1f8dc695615eea70fae74b156fc2])
* (add) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/hive-interactive-site.xml
* (add) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/tez-interactive-site.xml
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java


> Update some configuration properties for hive interactive for the HDP 2.6 
> stack
> ---
>
> Key: AMBARI-18792
> URL: https://issues.apache.org/jira/browse/AMBARI-18792
> Project: Ambari
>  Issue Type: Task
>  Components: stacks
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-18792.01.patch, AMBARI-18792.02.patch, 
> AMBARI-18792.03.patch, AMBARI-18792.04.patch, AMBARI-18792.05.patch, 
> AMBARI-18792.05.patch, AMBARI-18792.06.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19003) Perf: Fix deploy-gce-perf-cluster.py to deploy separate server onto own cluster with different settings for more cores and MySQL DB

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15706751#comment-15706751
 ] 

Hudson commented on AMBARI-19003:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #406 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/406/])
AMBARI-19003. Perf: Fix deploy-gce-perf-cluster.py to deploy separate 
(afernandez: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=052da577bcf5c3130337b7e783bda2b9c0207127])
* (edit) contrib/utils/perf/deploy-gce-perf-cluster.py


> Perf: Fix deploy-gce-perf-cluster.py to deploy separate server onto own 
> cluster with different settings for more cores and MySQL DB
> ---
>
> Key: AMBARI-19003
> URL: https://issues.apache.org/jira/browse/AMBARI-19003
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
> Attachments: AMBARI-19003.patch
>
>
> Right now, deploy-gce-perf-cluster.py puts Ambari Server on the same 4 core 
> VM where it puts 50 agents. Instead, we need to create a separate 16-core VM 
> for the server without any agents.
> Next, Ambari Server should be installed with MySQL database instead since it 
> has more configuration options that the default postgres.
> Further, the sorting of the VMs is not numeric since "perf-9" comes after 
> "perf-42". The incorrect sorting means that VM #i isn't getting the agents 
> starting with number (i-1)*50+1



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18871) HTTP responses needs to have the character encoding specified in the content type header

[Sangeeta Ravindran (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sangeeta Ravindran updated AMBARI-18871:

Resolution: Fixed
Status: Resolved  (was: Patch Available)

Commited to trunk.
commit 2cc4c9ed7009be2e894fec7d24c3cb4f0dd9f24c
Author: Sangeeta Ravindran 
Date:   Tue Nov 29 13:57:50 2016 -0800

AMBARI-18871 HTTP responses needs to have the character encoding specified in 
the content type header (Anita Jebaraj via sangeetar)

> HTTP responses needs to have the character encoding specified in the content 
> type header
> 
>
> Key: AMBARI-18871
> URL: https://issues.apache.org/jira/browse/AMBARI-18871
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Anita Gnanamalar Jebaraj
>Assignee: Anita Gnanamalar Jebaraj
> Fix For: trunk
>
> Attachments: AMBARI-18871-updated.patch, AMBARI-18871.patch
>
>
> The charset information(UTF-8) can be added to all the response headers to 
> harden the security for the client. When the charset information is not 
> specified the web browser may choose a different encoding by guessing which 
> encoding is actually being used by the web page. 
> This specific issue is mentioned in the section 3.1.1.5 of RFC7231



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19020) Ubuntu14/16 Add Support for Zookeeper on HDP 2.5

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15706716#comment-15706716
 ] 

Hadoop QA commented on AMBARI-19020:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12840918/AMBARI-19020.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 test build failed in ambari-server 

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9444//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9444//console

This message is automatically generated.

> Ubuntu14/16 Add Support for Zookeeper on HDP 2.5
> 
>
> Key: AMBARI-19020
> URL: https://issues.apache.org/jira/browse/AMBARI-19020
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0, 2.5.0
>Reporter: Duc Anh Le
>Assignee: Duc Anh Le
> Fix For: 2.4.0, 2.5.0
>
> Attachments: AMBARI-19020.patch
>
>
> Zookeeper on HDP 2.5 is not configured to support Ubuntu 14/16, which breaks 
> rolling upgrade on those OSes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (AMBARI-18634) Support Offline Stack Upgrades In a Cluster

[Nate Cole (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nate Cole resolved AMBARI-18634.

Resolution: Resolved

This feature is complete.  All changes will go to {{trunk}} (and {{branch-2.5}} 
as needed).

> Support Offline Stack Upgrades In a Cluster
> ---
>
> Key: AMBARI-18634
> URL: https://issues.apache.org/jira/browse/AMBARI-18634
> Project: Ambari
>  Issue Type: Epic
>  Components: ambari-agent, ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: UpgradePackforHostOrdered.pdf
>
>
> The purpose of this Epic is to track the work required for offline upgrades.  
> The general workflow will be:
> * Create a host (VM) that is NOT part of a cluster that duplicates the 
> hostname.
> * Install bits for an upgraded version of the software on a cluster.
> * Make Ambari aware that a new version is installed on the cluster.
> * Host-by-host, instruct Ambari to stop services for a host.
> * Once the components are stopped, stop the agent on the host.
> * After removing the host from the cluster, bring up the new host with the 
> new bits pre-installed.
> * Ambari should accept the versions reported by the new host.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18882) Host-Ordered: Verify YARN

[Nate Cole (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nate Cole updated AMBARI-18882:
---
Assignee: Duc Anh Le  (was: Nate Cole)

> Host-Ordered: Verify YARN
> -
>
> Key: AMBARI-18882
> URL: https://issues.apache.org/jira/browse/AMBARI-18882
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Reporter: Nate Cole
>Assignee: Duc Anh Le
>Priority: Critical
> Fix For: 2.5.0
>
>
> Verify YARN works in end-to-end testing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18883) Host-Ordered: Verify Kafka

[Nate Cole (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nate Cole updated AMBARI-18883:
---
Assignee: Duc Anh Le  (was: Nate Cole)

> Host-Ordered: Verify Kafka
> --
>
> Key: AMBARI-18883
> URL: https://issues.apache.org/jira/browse/AMBARI-18883
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Reporter: Nate Cole
>Assignee: Duc Anh Le
>Priority: Critical
> Fix For: 2.5.0
>
>
> Verify Kafka works in end-to-end testing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18884) Host-Ordered: Verify Hive

[Nate Cole (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nate Cole updated AMBARI-18884:
---
Assignee: Duc Anh Le  (was: Nate Cole)

> Host-Ordered: Verify Hive
> -
>
> Key: AMBARI-18884
> URL: https://issues.apache.org/jira/browse/AMBARI-18884
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Reporter: Nate Cole
>Assignee: Duc Anh Le
>Priority: Critical
> Fix For: 2.5.0
>
>
> Verify Hive works in end-to-end testing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18885) Host-Ordered: Verify Oozie

[Nate Cole (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nate Cole updated AMBARI-18885:
---
Assignee: Duc Anh Le  (was: Nate Cole)

> Host-Ordered: Verify Oozie
> --
>
> Key: AMBARI-18885
> URL: https://issues.apache.org/jira/browse/AMBARI-18885
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Reporter: Nate Cole
>Assignee: Duc Anh Le
>Priority: Critical
> Fix For: 2.5.0
>
>
> Verify Oozie works in end-to-end testing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18880) Host-Ordered: Verify ZooKeeper

[Nate Cole (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nate Cole updated AMBARI-18880:
---
Assignee: Duc Anh Le  (was: Nate Cole)

> Host-Ordered: Verify ZooKeeper
> --
>
> Key: AMBARI-18880
> URL: https://issues.apache.org/jira/browse/AMBARI-18880
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Reporter: Nate Cole
>Assignee: Duc Anh Le
>Priority: Critical
> Fix For: 2.5.0
>
>
> Verify ZooKeeper works in end-to-end testing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18881) Host-Ordered: Verify HDFS

[Nate Cole (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nate Cole updated AMBARI-18881:
---
Assignee: Duc Anh Le  (was: Nate Cole)

> Host-Ordered: Verify HDFS
> -
>
> Key: AMBARI-18881
> URL: https://issues.apache.org/jira/browse/AMBARI-18881
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Reporter: Nate Cole
>Assignee: Duc Anh Le
>Priority: Critical
> Fix For: 2.5.0
>
>
> Verify HDFS works in end-to-end testing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18886) Host-Ordered: Verify HBase

[Nate Cole (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nate Cole updated AMBARI-18886:
---
Assignee: Duc Anh Le  (was: Nate Cole)

> Host-Ordered: Verify HBase
> --
>
> Key: AMBARI-18886
> URL: https://issues.apache.org/jira/browse/AMBARI-18886
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Reporter: Nate Cole
>Assignee: Duc Anh Le
>Priority: Critical
> Fix For: 2.5.0
>
>
> Verify HBase works in end-to-end testing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19003) Perf: Fix deploy-gce-perf-cluster.py to deploy separate server onto own cluster with different settings for more cores and MySQL DB

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15706554#comment-15706554
 ] 

Hudson commented on AMBARI-19003:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6109 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6109/])
AMBARI-19003. Perf: Fix deploy-gce-perf-cluster.py to deploy separate 
(afernandez: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=85c9104ec14dc7b059d41f61dbbc6e57aec216d0])
* (edit) contrib/utils/perf/deploy-gce-perf-cluster.py


> Perf: Fix deploy-gce-perf-cluster.py to deploy separate server onto own 
> cluster with different settings for more cores and MySQL DB
> ---
>
> Key: AMBARI-19003
> URL: https://issues.apache.org/jira/browse/AMBARI-19003
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
> Attachments: AMBARI-19003.patch
>
>
> Right now, deploy-gce-perf-cluster.py puts Ambari Server on the same 4 core 
> VM where it puts 50 agents. Instead, we need to create a separate 16-core VM 
> for the server without any agents.
> Next, Ambari Server should be installed with MySQL database instead since it 
> has more configuration options that the default postgres.
> Further, the sorting of the VMs is not numeric since "perf-9" comes after 
> "perf-42". The incorrect sorting means that VM #i isn't getting the agents 
> starting with number (i-1)*50+1



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-19021) Ambari server java process died with exit code 134 after setting up Ambari kerberos JAAS configuration

[Vivek Rathod (JIRA)]

Vivek Rathod created AMBARI-19021:
-

 Summary: Ambari server java process died with exit code 134 after 
setting up Ambari kerberos JAAS configuration
 Key: AMBARI-19021
 URL: https://issues.apache.org/jira/browse/AMBARI-19021
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.5.0
Reporter: Vivek Rathod
 Fix For: 2.5.0


Ambari server java process died with exit code 134 after setting up Ambari 
kerberos JAAS configuration. While enabling SPNEGO Authentication, after 
setting up JAAS configuration, ambari server restart failed with exitcode 134.

On performing the ambari server setup and start manually on the same cluster, 
everything went through fine and the ambari server is now running on the 
cluster. This may be an intermittent issue.


{noformat}
2016-11-29 06:12:51,092 DEBUG 
com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
 Sending commands to host :
2016-11-29 06:12:51,092 DEBUG 
com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
 Sending command [ambari-server setup-security]
2016-11-29 06:12:51,093 DEBUG 
com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
 Sending command [3]
2016-11-29 06:12:51,093 DEBUG 
com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
 Sending command [ambari-qa-...@example.com]
2016-11-29 06:12:51,093 DEBUG 
com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
 Sending command [/etc/security/keytabs/smokeuser.headless.keytab]
2016-11-29 06:12:51,795 DEBUG 
com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
 [OUTPUT STREAM]
Using python  /usr/bin/python
Security setup options...
===
Choose one of the following options: 
  [1] Enable HTTPS for Ambari server.
  [2] Encrypt passwords stored in ambari.properties file.
  [3] Setup Ambari kerberos JAAS configuration.
  [4] Setup truststore.
  [5] Import certificate to truststore.
===
Enter choice, (1-5): Setting up Ambari kerberos JAAS configuration to access 
secured Hadoop daemons...
Enter ambari server's kerberos principal name (amb...@example.com): Enter 
keytab path for ambari server's kerberos principal: Ambari Server 
'setup-security' completed successfully.

[ERROR STREAM]


[EXIT CODE]
0
2016-11-29 06:12:51,796 INFO 
com.hw.ambari.ui.tests.console.TestConfigureHTTPSpnegoAuthentication.changeKRB5_JAASLOGIN_CONF():
 [Finished]
2016-11-29 06:12:51,797 INFO 
com.hw.ambari.ui.util.cluster_managers.AmbariManager.getStartAmbariServerCommand():
 Trying to restart Ambari server ...
2016-11-29 06:12:51,798 DEBUG 
com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
 Sending commands to host :
2016-11-29 06:12:51,798 DEBUG 
com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
 Sending command [ambari-server restart --debug]
2016-11-29 06:12:52,700 DEBUG 
com.hw.ambari.ui.util.cluster_managers.ProcessData.buildOutputAndErrorStreamData():
 sh: line 1: 419471 Aborted /usr/jdk64/jdk1.8.0_77/bin/java 
-server -XX:NewRatio=2 -XX:+UseConcMarkSweepGC -Xms512m -Xmx2048m 
-XX:MaxPermSize=128m 
-Djava.security.auth.login.config=$ROOT/etc/ambari-server/conf/krb5JAASLogin.conf
 -Djava.security.krb5.conf=/etc/krb5.conf -Djavax.securit
2016-11-29 06:12:52,701 DEBUG 
com.hw.ambari.ui.util.cluster_managers.ProcessData.buildOutputAndErrorStreamData():
 y.auth.useSubjectCredsOnly=false -Xdebug 
-Xrunjdwp:transport=dt_socket,address=5005,server=y,suspend=n -cp 
/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/mysql-connector-java.jar
 org.apache.ambari.server.controller.AmbariServer > 
/var/log/ambari-server/ambari-server.out 2>&1
2016-11-29 06:13:03,521 DEBUG 
com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
 [OUTPUT STREAM]
Using python  /usr/bin/python
Restarting ambari-server
Ambari Server stopped
Ambari Server running with administrator privileges.
Organizing resource files at /var/lib/ambari-server/resources...
Ambari database consistency check started...
Server PID at: /var/run/ambari-server/ambari-server.pid
Server out at: /var/log/ambari-server/ambari-server.out
Server log at: /var/log/ambari-server/ambari-server.log
Waiting for server start.
DB configs consistency check: no errors and warnings were found.
ERROR: Exiting with exit code -1. 
REASON: Ambari Server java process died with exitcode 134. Check 
/var/log/ambari-server/ambari-server.out for more information.

[ERROR STREAM]
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19003) Perf: Fix deploy-gce-perf-cluster.py to deploy separate server onto own cluster with different settings for more cores and MySQL DB

[Alejandro Fernandez (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alejandro Fernandez updated AMBARI-19003:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Pushed to trunk, commit 85c9104ec14dc7b059d41f61dbbc6e57aec216d0
branch-2.5, commit 052da577bcf5c3130337b7e783bda2b9c0207127

> Perf: Fix deploy-gce-perf-cluster.py to deploy separate server onto own 
> cluster with different settings for more cores and MySQL DB
> ---
>
> Key: AMBARI-19003
> URL: https://issues.apache.org/jira/browse/AMBARI-19003
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
> Attachments: AMBARI-19003.patch
>
>
> Right now, deploy-gce-perf-cluster.py puts Ambari Server on the same 4 core 
> VM where it puts 50 agents. Instead, we need to create a separate 16-core VM 
> for the server without any agents.
> Next, Ambari Server should be installed with MySQL database instead since it 
> has more configuration options that the default postgres.
> Further, the sorting of the VMs is not numeric since "perf-9" comes after 
> "perf-42". The incorrect sorting means that VM #i isn't getting the agents 
> starting with number (i-1)*50+1



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19020) Ubuntu14/16 Add Support for Zookeeper on HDP 2.5

[Duc Anh Le (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Duc Anh Le updated AMBARI-19020:

Attachment: AMBARI-19020.patch

> Ubuntu14/16 Add Support for Zookeeper on HDP 2.5
> 
>
> Key: AMBARI-19020
> URL: https://issues.apache.org/jira/browse/AMBARI-19020
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0, 2.5.0
>Reporter: Duc Anh Le
>Assignee: Duc Anh Le
> Fix For: 2.4.0, 2.5.0
>
> Attachments: AMBARI-19020.patch
>
>
> Zookeeper on HDP 2.5 is not configured to support Ubuntu 14/16, which breaks 
> rolling upgrade on those OSes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19020) Ubuntu14/16 Add Support for Zookeeper on HDP 2.5

[Duc Anh Le (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Duc Anh Le updated AMBARI-19020:

Status: Patch Available  (was: Open)

> Ubuntu14/16 Add Support for Zookeeper on HDP 2.5
> 
>
> Key: AMBARI-19020
> URL: https://issues.apache.org/jira/browse/AMBARI-19020
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0, 2.5.0
>Reporter: Duc Anh Le
>Assignee: Duc Anh Le
> Fix For: 2.4.0, 2.5.0
>
> Attachments: AMBARI-19020.patch
>
>
> Zookeeper on HDP 2.5 is not configured to support Ubuntu 14/16, which breaks 
> rolling upgrade on those OSes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-19020) Ubuntu14/16 Add Support for Zookeeper on HDP 2.5

[Duc Anh Le (JIRA)]

Duc Anh Le created AMBARI-19020:
---

 Summary: Ubuntu14/16 Add Support for Zookeeper on HDP 2.5
 Key: AMBARI-19020
 URL: https://issues.apache.org/jira/browse/AMBARI-19020
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.4.0, 2.5.0
Reporter: Duc Anh Le
Assignee: Duc Anh Le
 Fix For: 2.4.0, 2.5.0


Zookeeper on HDP 2.5 is not configured to support Ubuntu 14/16, which breaks 
rolling upgrade on those OSes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18792) Update some configuration properties for hive interactive for the HDP 2.6 stack

[Sumit Mohanty (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-18792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15706316#comment-15706316
 ] 

Sumit Mohanty commented on AMBARI-18792:


+1 to 
https://issues.apache.org/jira/secure/attachment/12839655/AMBARI-18792.06.patch

> Update some configuration properties for hive interactive for the HDP 2.6 
> stack
> ---
>
> Key: AMBARI-18792
> URL: https://issues.apache.org/jira/browse/AMBARI-18792
> Project: Ambari
>  Issue Type: Task
>  Components: stacks
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-18792.01.patch, AMBARI-18792.02.patch, 
> AMBARI-18792.03.patch, AMBARI-18792.04.patch, AMBARI-18792.05.patch, 
> AMBARI-18792.05.patch, AMBARI-18792.06.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18956) Ambari attempts to commit transactions marked as rollback-only

[Doroszlai, Attila (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Doroszlai, Attila updated AMBARI-18956:
---
Status: Open  (was: Patch Available)

> Ambari attempts to commit transactions marked as rollback-only
> --
>
> Key: AMBARI-18956
> URL: https://issues.apache.org/jira/browse/AMBARI-18956
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Minor
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-18956.patch
>
>
> {{EntityTransaction}} may be marked 
> [rollback-only|http://docs.oracle.com/javaee/6/api/javax/persistence/EntityTransaction.html#setRollbackOnly()]
>  due to exception.  If {{@Transactional}} is not marked to {{rollbackOn()}} 
> such exception, Ambari still attempts to commit the transaction.  The end 
> result for the transaction is the same (rollback), but instead of the 
> original exception a {{RollbackException}} is reported, so information is 
> lost.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18956) Ambari attempts to commit transactions marked as rollback-only

[Doroszlai, Attila (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Doroszlai, Attila updated AMBARI-18956:
---
Status: Patch Available  (was: Open)

> Ambari attempts to commit transactions marked as rollback-only
> --
>
> Key: AMBARI-18956
> URL: https://issues.apache.org/jira/browse/AMBARI-18956
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Minor
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-18956.patch
>
>
> {{EntityTransaction}} may be marked 
> [rollback-only|http://docs.oracle.com/javaee/6/api/javax/persistence/EntityTransaction.html#setRollbackOnly()]
>  due to exception.  If {{@Transactional}} is not marked to {{rollbackOn()}} 
> such exception, Ambari still attempts to commit the transaction.  The end 
> result for the transaction is the same (rollback), but instead of the 
> original exception a {{RollbackException}} is reported, so information is 
> lost.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19007) Atlas to support configuration of hooks from separate cluster

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15706202#comment-15706202
 ] 

Hadoop QA commented on AMBARI-19007:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12840898/AMBARI-19007.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/9443//console

This message is automatically generated.

> Atlas to support configuration of hooks from separate cluster
> -
>
> Key: AMBARI-19007
> URL: https://issues.apache.org/jira/browse/AMBARI-19007
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Blocker
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19007.patch
>
>
> *Need support in ambari to allow atlas to communicate with hooks installed on 
> separate clusters*
> # Ambari Stack definition changes (for all four hooks being installed on 
> Separate Cluster) - this information will be stored in blueprints.
> # Need to be able to sync with Atlas to leverage tag based security via 
> tagsync service
> # Ambari driven configuration and addition of flags to support the feature.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18997) ambari-server.pid might not be created on slow hardware

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-18997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15706198#comment-15706198
 ] 

Hadoop QA commented on AMBARI-18997:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12840903/AMBARI-18997_6.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 2 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 
ambari-server.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9442//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9442//console

This message is automatically generated.

> ambari-server.pid might not be created on slow hardware
> ---
>
> Key: AMBARI-18997
> URL: https://issues.apache.org/jira/browse/AMBARI-18997
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18997_6.patch
>
>
> ambari-server.pid file might not be created on slow hardware, but 
> "ambari-server start" exits with 0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19018) Services should be able to specify their own resources subdirs for sync'ing to agents

[Tim Thorpe (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tim Thorpe updated AMBARI-19018:

Attachment: AMBARI-19018.patch

> Services should be able to specify their own resources subdirs for sync'ing 
> to agents
> -
>
> Key: AMBARI-19018
> URL: https://issues.apache.org/jira/browse/AMBARI-19018
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-agent, ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Tim Thorpe
>Assignee: Tim Thorpe
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19018.patch
>
>
> A component should be able to specify a custom folder to sync to the agents 
> in the metainfo.xml.
> For example:
> 
>   METRICS_GRAFANA
>   Grafana
>   MASTER
>   dashboards
>   
> scripts/metrics_grafana.py
> This will sync the resources/dashboards directory to the agents if the 
> directory exists on the server.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19018) Services should be able to specify their own resources subdirs for sync'ing to agents

[Tim Thorpe (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tim Thorpe updated AMBARI-19018:

Status: Patch Available  (was: Open)

> Services should be able to specify their own resources subdirs for sync'ing 
> to agents
> -
>
> Key: AMBARI-19018
> URL: https://issues.apache.org/jira/browse/AMBARI-19018
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-agent, ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Tim Thorpe
>Assignee: Tim Thorpe
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19018.patch
>
>
> A component should be able to specify a custom folder to sync to the agents 
> in the metainfo.xml.
> For example:
> 
>   METRICS_GRAFANA
>   Grafana
>   MASTER
>   dashboards
>   
> scripts/metrics_grafana.py
> This will sync the resources/dashboards directory to the agents if the 
> directory exists on the server.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18980) Add manual confirm task before finalizing host-ordered upgrade

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-18980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15706161#comment-15706161
 ] 

Hudson commented on AMBARI-18980:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6107 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6107/])
AMBARI-18980. Add manual confirm task before finalizing host-ordered (ncole: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2c7c0a704f4230697b6757bdaad954d8c5d71c79])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/host-ordered-upgrade.xml


> Add manual confirm task before finalizing host-ordered upgrade
> --
>
> Key: AMBARI-18980
> URL: https://issues.apache.org/jira/browse/AMBARI-18980
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Duc Anh Le
>Assignee: Duc Anh Le
> Fix For: 2.5.0
>
> Attachments: AMBARI-18980.patch
>
>
> We need to users' confirmation before finalizing upgrade.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18997) ambari-server.pid might not be created on slow hardware

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-18997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15706134#comment-15706134
 ] 

Hadoop QA commented on AMBARI-18997:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12840892/AMBARI-18997_4.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 2 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 
ambari-server.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9441//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9441//console

This message is automatically generated.

> ambari-server.pid might not be created on slow hardware
> ---
>
> Key: AMBARI-18997
> URL: https://issues.apache.org/jira/browse/AMBARI-18997
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18997_6.patch
>
>
> ambari-server.pid file might not be created on slow hardware, but 
> "ambari-server start" exits with 0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19019) Knox HA Wizard

[Alejandro Fernandez (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alejandro Fernandez updated AMBARI-19019:
-
Assignee: Jeffrey E  Rodriguez

> Knox HA Wizard
> --
>
> Key: AMBARI-19019
> URL: https://issues.apache.org/jira/browse/AMBARI-19019
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Affects Versions: 2.5.0
> Environment: All
>Reporter: Jeffrey E  Rodriguez
>Assignee: Jeffrey E  Rodriguez
> Fix For: 2.5.0
>
>
> This feature is to  implement a Knox HA Wizard. (Model after existing HA 
> wizards).
> 1. Add HA Knox instances through Knox HA Wizard.
>- Sync up the topologies keystores for all Knox nodes. (to the initial 
> Knox topology).
>- Hook either HA Proxy or Apache server + ssl_mod + balancer_mod + 
> proxy_mod ( we could provide Wizard instructions).
>- Service check for Knox HA.
>- Restart Knox server.
>  
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18997) ambari-server.pid might not be created on slow hardware

[Dmytro Sen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmytro Sen updated AMBARI-18997:

Attachment: AMBARI-18997_6.patch

> ambari-server.pid might not be created on slow hardware
> ---
>
> Key: AMBARI-18997
> URL: https://issues.apache.org/jira/browse/AMBARI-18997
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18997_6.patch
>
>
> ambari-server.pid file might not be created on slow hardware, but 
> "ambari-server start" exits with 0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18997) ambari-server.pid might not be created on slow hardware

[Dmytro Sen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmytro Sen updated AMBARI-18997:

Status: Open  (was: Patch Available)

> ambari-server.pid might not be created on slow hardware
> ---
>
> Key: AMBARI-18997
> URL: https://issues.apache.org/jira/browse/AMBARI-18997
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18997_6.patch
>
>
> ambari-server.pid file might not be created on slow hardware, but 
> "ambari-server start" exits with 0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18997) ambari-server.pid might not be created on slow hardware

[Dmytro Sen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmytro Sen updated AMBARI-18997:

Status: Patch Available  (was: Open)

> ambari-server.pid might not be created on slow hardware
> ---
>
> Key: AMBARI-18997
> URL: https://issues.apache.org/jira/browse/AMBARI-18997
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18997_6.patch
>
>
> ambari-server.pid file might not be created on slow hardware, but 
> "ambari-server start" exits with 0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18997) ambari-server.pid might not be created on slow hardware

[Dmytro Sen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmytro Sen updated AMBARI-18997:

Attachment: (was: AMBARI-18997_4.patch)

> ambari-server.pid might not be created on slow hardware
> ---
>
> Key: AMBARI-18997
> URL: https://issues.apache.org/jira/browse/AMBARI-18997
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18997_6.patch
>
>
> ambari-server.pid file might not be created on slow hardware, but 
> "ambari-server start" exits with 0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information

[Hadoop QA (JIRA)]

[ 
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)

[jira] [Commented] (AMBARI-19010) Log Search external login credential let every user in

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15706019#comment-15706019
 ] 

Hudson commented on AMBARI-19010:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6106 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6106/])
AMBARI-19010. Log Search external login credential let every user in (oleewere: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f31f3f646610a2e480279989d6790437e5362cb8])
* (edit) 
ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/common/ExternalServerClient.java


> Log Search external login credential let every user in
> --
>
> Key: AMBARI-19010
> URL: https://issues.apache.org/jira/browse/AMBARI-19010
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19010.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18980) Add manual confirm task before finalizing host-ordered upgrade

[Duc Anh Le (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Duc Anh Le updated AMBARI-18980:

Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Add manual confirm task before finalizing host-ordered upgrade
> --
>
> Key: AMBARI-18980
> URL: https://issues.apache.org/jira/browse/AMBARI-18980
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Duc Anh Le
>Assignee: Duc Anh Le
> Fix For: 2.5.0
>
> Attachments: AMBARI-18980.patch
>
>
> We need to users' confirmation before finalizing upgrade.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19010) Log Search external login credential let every user in

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15706014#comment-15706014
 ] 

Hudson commented on AMBARI-19010:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #404 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/404/])
AMBARI-19010. Log Search external login credential let every user in (oleewere: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=268683220382cb1f0061d1e9135cc882b74c0f97])
* (edit) 
ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/common/ExternalServerClient.java


> Log Search external login credential let every user in
> --
>
> Key: AMBARI-19010
> URL: https://issues.apache.org/jira/browse/AMBARI-19010
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19010.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19007) Atlas to support configuration of hooks from separate cluster

[Mugdha Varadkar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mugdha Varadkar updated AMBARI-19007:
-
Attachment: AMBARI-19007.patch

> Atlas to support configuration of hooks from separate cluster
> -
>
> Key: AMBARI-19007
> URL: https://issues.apache.org/jira/browse/AMBARI-19007
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Blocker
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19007.patch
>
>
> *Need support in ambari to allow atlas to communicate with hooks installed on 
> separate clusters*
> # Ambari Stack definition changes (for all four hooks being installed on 
> Separate Cluster) - this information will be stored in blueprints.
> # Need to be able to sync with Atlas to leverage tag based security via 
> tagsync service
> # Ambari driven configuration and addition of flags to support the feature.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19007) Atlas to support configuration of hooks from separate cluster

[Mugdha Varadkar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mugdha Varadkar updated AMBARI-19007:
-
Component/s: ambari-server

> Atlas to support configuration of hooks from separate cluster
> -
>
> Key: AMBARI-19007
> URL: https://issues.apache.org/jira/browse/AMBARI-19007
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Blocker
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19007.patch
>
>
> *Need support in ambari to allow atlas to communicate with hooks installed on 
> separate clusters*
> # Ambari Stack definition changes (for all four hooks being installed on 
> Separate Cluster) - this information will be stored in blueprints.
> # Need to be able to sync with Atlas to leverage tag based security via 
> tagsync service
> # Ambari driven configuration and addition of flags to support the feature.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19007) Atlas to support configuration of hooks from separate cluster

[Mugdha Varadkar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mugdha Varadkar updated AMBARI-19007:
-
Status: Patch Available  (was: In Progress)

> Atlas to support configuration of hooks from separate cluster
> -
>
> Key: AMBARI-19007
> URL: https://issues.apache.org/jira/browse/AMBARI-19007
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Blocker
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19007.patch
>
>
> *Need support in ambari to allow atlas to communicate with hooks installed on 
> separate clusters*
> # Ambari Stack definition changes (for all four hooks being installed on 
> Separate Cluster) - this information will be stored in blueprints.
> # Need to be able to sync with Atlas to leverage tag based security via 
> tagsync service
> # Ambari driven configuration and addition of flags to support the feature.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19007) Atlas to support configuration of hooks from separate cluster

[Mugdha Varadkar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mugdha Varadkar updated AMBARI-19007:
-
Summary: Atlas to support configuration of hooks from separate cluster  
(was: Shared Services HDC: Atlas)

> Atlas to support configuration of hooks from separate cluster
> -
>
> Key: AMBARI-19007
> URL: https://issues.apache.org/jira/browse/AMBARI-19007
> Project: Ambari
>  Issue Type: New Feature
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Blocker
> Fix For: 3.0.0, 2.5.0
>
>
> *Need support in ambari to allow atlas to communicate with hooks installed on 
> separate clusters*
> # Ambari Stack definition changes (for all four hooks being installed on 
> Separate Cluster) - this information will be stored in blueprints.
> # Need to be able to sync with Atlas to leverage tag based security via 
> tagsync service
> # Ambari driven configuration and addition of flags to support the feature.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19007) Atlas to support configuration of hooks from separate cluster

[Mugdha Varadkar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mugdha Varadkar updated AMBARI-19007:
-
Attachment: (was: AMBARI-19007.patch)

> Atlas to support configuration of hooks from separate cluster
> -
>
> Key: AMBARI-19007
> URL: https://issues.apache.org/jira/browse/AMBARI-19007
> Project: Ambari
>  Issue Type: New Feature
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Blocker
> Fix For: 3.0.0, 2.5.0
>
>
> *Need support in ambari to allow atlas to communicate with hooks installed on 
> separate clusters*
> # Ambari Stack definition changes (for all four hooks being installed on 
> Separate Cluster) - this information will be stored in blueprints.
> # Need to be able to sync with Atlas to leverage tag based security via 
> tagsync service
> # Ambari driven configuration and addition of flags to support the feature.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19007) Shared Services HDC: Atlas

[Mugdha Varadkar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mugdha Varadkar updated AMBARI-19007:
-
Attachment: AMBARI-19007.patch

> Shared Services HDC: Atlas
> --
>
> Key: AMBARI-19007
> URL: https://issues.apache.org/jira/browse/AMBARI-19007
> Project: Ambari
>  Issue Type: New Feature
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Blocker
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19007.patch
>
>
> *Need support in ambari to allow atlas to communicate with hooks installed on 
> separate clusters*
> # Ambari Stack definition changes (for all four hooks being installed on 
> Separate Cluster) - this information will be stored in blueprints.
> # Need to be able to sync with Atlas to leverage tag based security via 
> tagsync service
> # Ambari driven configuration and addition of flags to support the feature.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information

[Nahappan Somasundaram (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nahappan Somasundaram updated AMBARI-1:
---
Status: Patch Available  (was: Open)

> 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] [Updated] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information

[Nahappan Somasundaram (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nahappan Somasundaram updated AMBARI-1:
---
Attachment: rb53747.patch

> 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] [Updated] (AMBARI-18997) ambari-server.pid might not be created on slow hardware

[Dmytro Sen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmytro Sen updated AMBARI-18997:

Attachment: (was: AMBARI-18997_2.patch)

> ambari-server.pid might not be created on slow hardware
> ---
>
> Key: AMBARI-18997
> URL: https://issues.apache.org/jira/browse/AMBARI-18997
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18997_4.patch
>
>
> ambari-server.pid file might not be created on slow hardware, but 
> "ambari-server start" exits with 0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18997) ambari-server.pid might not be created on slow hardware

[Dmytro Sen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmytro Sen updated AMBARI-18997:

Status: Open  (was: Patch Available)

> ambari-server.pid might not be created on slow hardware
> ---
>
> Key: AMBARI-18997
> URL: https://issues.apache.org/jira/browse/AMBARI-18997
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18997_4.patch
>
>
> ambari-server.pid file might not be created on slow hardware, but 
> "ambari-server start" exits with 0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18997) ambari-server.pid might not be created on slow hardware

[Dmytro Sen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmytro Sen updated AMBARI-18997:

Status: Patch Available  (was: Open)

> ambari-server.pid might not be created on slow hardware
> ---
>
> Key: AMBARI-18997
> URL: https://issues.apache.org/jira/browse/AMBARI-18997
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18997_4.patch
>
>
> ambari-server.pid file might not be created on slow hardware, but 
> "ambari-server start" exits with 0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18997) ambari-server.pid might not be created on slow hardware

[Dmytro Sen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmytro Sen updated AMBARI-18997:

Attachment: AMBARI-18997_4.patch

> ambari-server.pid might not be created on slow hardware
> ---
>
> Key: AMBARI-18997
> URL: https://issues.apache.org/jira/browse/AMBARI-18997
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18997_4.patch
>
>
> ambari-server.pid file might not be created on slow hardware, but 
> "ambari-server start" exits with 0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)