[jira] [Commented] (AMBARI-18378) View instance cloning functionality

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18378:


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

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

This message is automatically generated.

> View instance cloning functionality
> ---
>
> Key: AMBARI-18378
> URL: https://issues.apache.org/jira/browse/AMBARI-18378
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-admin, ambari-views
>Affects Versions: trunk
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
>  Labels: patch
> Fix For: trunk
>
> Attachments: AMBARI-18378, ViewCloneIcon.jpg, ViewCloneInstance.jpg
>
>
> This task is for providing an option to clone / copy a view instance. 
> A new "copy" icon will appear next to a view instance. Clicking on this opens 
> up the existing view with instance name and display name of the view appended 
> with _Copy.
> This will be useful when creating multiple view instances with mild 
> configuration differences between them.



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

[jira] [Commented] (AMBARI-18375) Ranger Plugin configs are not generated for Hive interactive

[Mugdha Varadkar (JIRA)]

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

Mugdha Varadkar commented on AMBARI-18375:
--

Committed to 
[branch-2.5|https://github.com/apache/ambari/commit/762f4b46969e9802695d1b5631bfda79a8a7e5f3]
 and 
[trunk|https://github.com/apache/ambari/commit/532b689f3158f8c90b9bc69e1d62d3816f3e81b1]

> Ranger Plugin configs are not generated for Hive interactive
> 
>
> Key: AMBARI-18375
> URL: https://issues.apache.org/jira/browse/AMBARI-18375
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Blocker
> Fix For: 2.4.1, 2.4.2
>
> Attachments: AMBARI-18375.patch
>
>
> If audit to hdfs is OFF for ranger hive plugin, configs related to plugins 
> are not generated for Hive interactive



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

[jira] [Updated] (AMBARI-18378) View instance cloning functionality

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-18378:

Attachment: AMBARI-18378

> View instance cloning functionality
> ---
>
> Key: AMBARI-18378
> URL: https://issues.apache.org/jira/browse/AMBARI-18378
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-admin, ambari-views
>Affects Versions: trunk
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
>  Labels: patch
> Fix For: trunk
>
> Attachments: AMBARI-18378, ViewCloneIcon.jpg, ViewCloneInstance.jpg
>
>
> This task is for providing an option to clone / copy a view instance. 
> A new "copy" icon will appear next to a view instance. Clicking on this opens 
> up the existing view with instance name and display name of the view appended 
> with _Copy.
> This will be useful when creating multiple view instances with mild 
> configuration differences between them.



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

[jira] [Updated] (AMBARI-18378) View instance cloning functionality

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-18378:

Affects Version/s: trunk

> View instance cloning functionality
> ---
>
> Key: AMBARI-18378
> URL: https://issues.apache.org/jira/browse/AMBARI-18378
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-admin, ambari-views
>Affects Versions: trunk
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
>  Labels: patch
> Fix For: trunk
>
> Attachments: AMBARI-18378, ViewCloneIcon.jpg, ViewCloneInstance.jpg
>
>
> This task is for providing an option to clone / copy a view instance. 
> A new "copy" icon will appear next to a view instance. Clicking on this opens 
> up the existing view with instance name and display name of the view appended 
> with _Copy.
> This will be useful when creating multiple view instances with mild 
> configuration differences between them.



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

[jira] [Updated] (AMBARI-18378) View instance cloning functionality

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-18378:

Labels: patch  (was: )
Status: Patch Available  (was: Open)

> View instance cloning functionality
> ---
>
> Key: AMBARI-18378
> URL: https://issues.apache.org/jira/browse/AMBARI-18378
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-admin, ambari-views
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
>  Labels: patch
> Fix For: trunk
>
> Attachments: AMBARI-18378, ViewCloneIcon.jpg, ViewCloneInstance.jpg
>
>
> This task is for providing an option to clone / copy a view instance. 
> A new "copy" icon will appear next to a view instance. Clicking on this opens 
> up the existing view with instance name and display name of the view appended 
> with _Copy.
> This will be useful when creating multiple view instances with mild 
> configuration differences between them.



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

[jira] [Updated] (AMBARI-18378) View instance cloning functionality

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-18378:

Attachment: (was: AMBARI-18378)

> View instance cloning functionality
> ---
>
> Key: AMBARI-18378
> URL: https://issues.apache.org/jira/browse/AMBARI-18378
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-admin, ambari-views
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: trunk
>
> Attachments: ViewCloneIcon.jpg, ViewCloneInstance.jpg
>
>
> This task is for providing an option to clone / copy a view instance. 
> A new "copy" icon will appear next to a view instance. Clicking on this opens 
> up the existing view with instance name and display name of the view appended 
> with _Copy.
> This will be useful when creating multiple view instances with mild 
> configuration differences between them.



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

[jira] [Commented] (AMBARI-18385) Add HDF management pack

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-18385:


Trunk
commit 37e71db741cacb5acc4113131a27d2c1b7ac5791
Author: Jayush Luniya 
Date:   Tue Sep 13 22:26:38 2016 -0700

AMBARI-18385: Add HDF management pack (jluniya)

> Add HDF management pack
> ---
>
> Key: AMBARI-18385
> URL: https://issues.apache.org/jira/browse/AMBARI-18385
> Project: Ambari
>  Issue Type: Bug
>  Components: contrib
>Affects Versions: trunk
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: trunk
>
> Attachments: AMBARI-18385.patch
>
>
> Add HDF management pack to Ambari



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

[jira] [Updated] (AMBARI-18378) View instance cloning functionality

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-18378:

Status: Open  (was: Patch Available)

> View instance cloning functionality
> ---
>
> Key: AMBARI-18378
> URL: https://issues.apache.org/jira/browse/AMBARI-18378
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-admin, ambari-views
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: trunk
>
> Attachments: ViewCloneIcon.jpg, ViewCloneInstance.jpg
>
>
> This task is for providing an option to clone / copy a view instance. 
> A new "copy" icon will appear next to a view instance. Clicking on this opens 
> up the existing view with instance name and display name of the view appended 
> with _Copy.
> This will be useful when creating multiple view instances with mild 
> configuration differences between them.



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

[jira] [Commented] (AMBARI-18384) Analyze and Optimize Ambari Server Unit Tests - Group 3

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18384:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12828364/AMBARI-18384.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 6 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/8660//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8660//console

This message is automatically generated.

> Analyze and Optimize Ambari Server Unit Tests - Group 3
> ---
>
> Key: AMBARI-18384
> URL: https://issues.apache.org/jira/browse/AMBARI-18384
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
> Fix For: trunk
>
> Attachments: AMBARI-18384.patch
>
>
> ||Test||Count||Time (s)||
> |org.apache.ambari.server.security.authorization.TestUsers|31|50.4|
> |org.apache.ambari.server.upgrade.UpgradeCatalog210Test   |18|46.497|
> |org.apache.ambari.server.state.svccomphost.ServiceComponentHostTest|15|43.899|
> |org.apache.ambari.server.serveraction.upgrades.UpgradeActionTest|9|35.136|
> |org.apache.ambari.server.agent.TestHeartbeatMonitor|6|28.146|



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

[jira] [Updated] (AMBARI-18375) Ranger Plugin configs are not generated for Hive interactive

[Mugdha Varadkar (JIRA)]

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

Mugdha Varadkar updated AMBARI-18375:
-
Summary: Ranger Plugin configs are not generated for Hive interactive  
(was: Ranger Plugin configs is not generated for Hive interactive)

> Ranger Plugin configs are not generated for Hive interactive
> 
>
> Key: AMBARI-18375
> URL: https://issues.apache.org/jira/browse/AMBARI-18375
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Blocker
> Fix For: 2.4.1, 2.4.2
>
> Attachments: AMBARI-18375.patch
>
>
> If audit to hdfs is OFF for ranger hive plugin, configs related to plugins 
> are not generated for Hive interactive



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

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

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18332:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12828306/rb51851.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/8659//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8659//console

This message is automatically generated.

> Blueprints: API should make available "setting" property from blueprint
> ---
>
> Key: AMBARI-18332
> URL: https://issues.apache.org/jira/browse/AMBARI-18332
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb51851.patch
>
>
> The following APIs do not retrieve *setting* section from the blueprint that 
> was used during deployment:
> {code}
> http://:/api/v1/blueprints/ 
> {code}



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

[jira] [Commented] (AMBARI-18383) Oozie spark failed due to incomplete spark share-lib directory

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18383:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5664 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5664/])
AMBARI-18383 : Oozie spark failed due to incomplete spark share-lib (avijayan: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1e21842e3ac9e2b6a4552cb0d58294a22d3c2e40])
* (edit) ambari-server/src/main/resources/scripts/Ambaripreupload.py
* (edit) 
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py


> Oozie spark failed due to incomplete spark share-lib directory
> --
>
> Key: AMBARI-18383
> URL: https://issues.apache.org/jira/browse/AMBARI-18383
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18383.patch
>
>
> Failed exception:
> {noformat}
> "Failing Oozie Launcher, Main class 
> [org.apache.oozie.action.hadoop.SparkMain], main() 
> threw exception, Missing py4j and/or pyspark zip files. Please add them to 
> the lib folder 
> or to the Spark sharelib.
> org.apache.oozie.action.hadoop.OozieActionConfiguratorException: Missing py4j 
> and/or 
> pyspark zip files. Please add them to the lib folder or to the Spark 
> sharelib."
> {noformat}
> Those two files were not present in the share lib
> hrt_qa@hn0-3ad6fe:~$ hdfs dfs -ls /user/oozie/share/lib/spark/*.zip
> ls: `/user/oozie/share/lib/spark/*.zip': No such file or directory



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

[jira] [Commented] (AMBARI-17458) Add support for distributed collector to Ambari REST API

[Hudson (JIRA)]

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

Hudson commented on AMBARI-17458:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5664 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5664/])
AMBARI-17458 : Add support for distributed collector to Ambari REST API. 
(avijayan: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0855174b815987850d0022ff3c1619c3b2373921])
* (edit) 
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/status.py
* (edit) 
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/events/AmbariEvent.java
* (add) 
ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/MetricsCollectorHAManager.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementController.java
* (add) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostStatusHelper.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/timeline/AMSReportPropertyProvider.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/timeline/AMSPropertyProvider.java
* (edit) 
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AbstractProviderModule.java
* (add) 
ambari-server/src/main/java/org/apache/ambari/server/events/MetricsCollectorHostDownEvent.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/timeline/cache/TimelineMetricCache.java
* (add) 
ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/MetricsCollectorHAClusterState.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/timeline/MetricsRequestHelper.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
* (edit) 
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_monitor.py


> Add support for distributed collector to Ambari REST API
> 
>
> Key: AMBARI-17458
> URL: https://issues.apache.org/jira/browse/AMBARI-17458
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Siddharth Wagle
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 3.0.0
>
>
> _Tasks_:
> - Add a Zookeeper watcher for the AMS znode
> - Find available collectors and round-robin the READ calls from 
> AMSPropertyProvider
> - Tolerate failure by switching to available collector



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

[jira] [Commented] (AMBARI-18385) Add HDF management pack

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-18385:


+1, good to see some fully defined MPacks in the contrib.

> Add HDF management pack
> ---
>
> Key: AMBARI-18385
> URL: https://issues.apache.org/jira/browse/AMBARI-18385
> Project: Ambari
>  Issue Type: Bug
>  Components: contrib
>Affects Versions: trunk
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: trunk
>
> Attachments: AMBARI-18385.patch
>
>
> Add HDF management pack to Ambari



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

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

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18365:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12828327/AMBARI-18365_trunk_02.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/8658//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8658//console

This message is automatically generated.

> Add Ambari configuration options to support Kerberos token authentication
> -
>
> Key: AMBARI-18365
> URL: https://issues.apache.org/jira/browse/AMBARI-18365
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: authentication, kerberos, security
> Fix For: 2.5.0
>
> Attachments: AMBARI-18365_branch-2.5_01.patch, 
> AMBARI-18365_branch-2.5_02.patch, AMBARI-18365_trunk_01.patch, 
> AMBARI-18365_trunk_02.patch
>
>
> Add the followng Ambari configuration options to support Kerberos token 
> authentication
> * {{authentication.kerberos.enabled}}
> ** Determines whether to use Kerberos (SPNEGO) authentication when connecting 
> Ambari:  {{true}} to enable this feature; {{false}}, otherwise
> * {{authentication.kerberos.spnego.principal}}
> ** The Kerberos principal name to use when verifying user-supplied Kerberos 
> tokens for authentication via SPNEGO
> * {{authentication.kerberos.spnego.keytab.file}}
> ** The Kerberos keytab file to use when verifying user-supplied Kerberos 
> tokens for authentication via SPNEGO
> * {{authentication.kerberos.user.types}}
> ** A comma-delimited (ordered) list of preferred user types to use when 
> finding the Ambari user account for the user-supplied Kerberos identity 
> during authentication via SPNEGO
> * {{authentication.kerberos.auth_to_local.rules}}
> ** The auth-to-local rules set to use when translating a user's principal 
> name to a local user name during authentication via SPNEGO.
> NOTE: These properties are in the {{ambari.properties}} file since this 
> feature may be enabled whether the rest of the cluster has Kerberos enabled 
> or not. 



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

[jira] [Commented] (AMBARI-18383) Oozie spark failed due to incomplete spark share-lib directory

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18383:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #29 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/29/])
AMBARI-18383 : Oozie spark failed due to incomplete spark share-lib (avijayan: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=86937ac57e55a921f423f1bd6a2908581fbef774])
* (edit) ambari-server/src/main/resources/scripts/Ambaripreupload.py
* (edit) 
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py


> Oozie spark failed due to incomplete spark share-lib directory
> --
>
> Key: AMBARI-18383
> URL: https://issues.apache.org/jira/browse/AMBARI-18383
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18383.patch
>
>
> Failed exception:
> {noformat}
> "Failing Oozie Launcher, Main class 
> [org.apache.oozie.action.hadoop.SparkMain], main() 
> threw exception, Missing py4j and/or pyspark zip files. Please add them to 
> the lib folder 
> or to the Spark sharelib.
> org.apache.oozie.action.hadoop.OozieActionConfiguratorException: Missing py4j 
> and/or 
> pyspark zip files. Please add them to the lib folder or to the Spark 
> sharelib."
> {noformat}
> Those two files were not present in the share lib
> hrt_qa@hn0-3ad6fe:~$ hdfs dfs -ls /user/oozie/share/lib/spark/*.zip
> ls: `/user/oozie/share/lib/spark/*.zip': No such file or directory



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

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

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18351:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #29 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/29/])
AMBARI-18351. Preserve output while executing HSI/LLAP's run.sh command 
(sshridhar: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=627c1b48ccf94d32396f9ba3061fa01221848d28])
* (edit) ambari-server/src/test/python/stacks/2.5/HIVE/test_hive_server_int.py
* (edit) 
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py


> Preserve output while executing HSI/LLAP's "run.sh" command for launching 
> LLAP.
> ---
>
> Key: AMBARI-18351
> URL: https://issues.apache.org/jira/browse/AMBARI-18351
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18351.patch
>
>
> Ambari currently runs run.sh for LLAP as such:
> {noformat}
> 2016-08-29 20:34:47,770 - 
> Execute['/var/lib/ambari-agent/tmp/llap-slider2016-08-29_20-34-01/run.sh'] 
> {'user': 'hive'}
> 2016-08-29 20:35:51,856 - Submitted LLAP app name : llap0
> {noformat}
> Above is from Hive Interactive start operation output.
> Fix:
> - It would be good to include the output (stdout and stderr) of this command 
> in the operation logs, for debugging purposes.



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

[jira] [Commented] (AMBARI-18345) 'Stack advisor' validation code reports error while trying to access 'yarn.nodemanager.resource.memory-mb' config.

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18345:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #29 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/29/])
AMBARI-18345. 'Stack advisor' validation code reports error while trying 
(sshridhar: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f07f2f81133be1528d29c1689fb6a81fa0345625])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py


> 'Stack advisor' validation code reports error while trying to access 
> 'yarn.nodemanager.resource.memory-mb' config.
> --
>
> Key: AMBARI-18345
> URL: https://issues.apache.org/jira/browse/AMBARI-18345
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.4.1
>
> Attachments: AMBARI-18345.patch
>
>
> 'Stack advisor' validation code reports error while trying to access 
> "yarn.nodemanager.resource.memory-mb" config.
> *Reason:* 
> - Fn. 'validateHiveInteractiveSiteConfigurations' tried to query for config 
> 'yarn.nodemanager.resource.memory-mb'. The config may not be passed in 
> services[configurations], depending on which action triggered the validation. 
> - Fn. 'validateHiveInteractiveSiteConfigurations' was broken because it was 
> trying to query config 'yarn.nodemanager.resource.memory-mb', without 
> checking whether HSI is installed or not.



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

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

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18368:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #29 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/29/])
AMBARI-18368. Atlas web UI alert after performing stack upgrade to HDP 
(afernandez: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=72617ce7339dc0859aa0508d9f7a3d50a477ac3a])
* (edit) 
ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata.py


> Atlas web UI alert after performing stack upgrade to HDP 2.5 and adding Atlas 
> Service
> -
>
> Key: AMBARI-18368
> URL: https://issues.apache.org/jira/browse/AMBARI-18368
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: trunk, 2.4.2
>
> Attachments: AMBARI-18368.patch
>
>
> Steps to Reproduce:
> * Install Ambari 2.2.2 with HDP 2.4 (HBase, Solr)
> * Kerberize the cluster
> * Perform EU/RU to HDP 2.5
> * Add Atlas Service
> Atlas Server log contains,
> {code}
> Caused by: 
> org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error 
> from server at 
> http://natu146-ehbs-dgm10toeriesec-u14-1.openstacklocal:8886/solr: Can not 
> find the specified config set: vertex_index
> at 
> org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:577)
> at 
> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:241)
> at 
> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:230)
> at 
> org.apache.solr.client.solrj.impl.LBHttpSolrClient.doRequest(LBHttpSolrClient.java:372)
> at 
> org.apache.solr.client.solrj.impl.LBHttpSolrClient.request(LBHttpSolrClient.java:325)
> at 
> org.apache.solr.client.solrj.impl.CloudSolrClient.sendRequest(CloudSolrClient.java:1100)
> at 
> org.apache.solr.client.solrj.impl.CloudSolrClient.requestWithRetryOnStaleState(CloudSolrClient.java:870)
> at 
> org.apache.solr.client.solrj.impl.CloudSolrClient.request(CloudSolrClient.java:806)
> at 
> org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:149)
> at 
> org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:166)
> at 
> com.thinkaurelius.titan.diskstorage.solr.Solr5Index.createCollectionIfNotExists(Solr5Index.java:901)
> at 
> com.thinkaurelius.titan.diskstorage.solr.Solr5Index.register(Solr5Index.java:269)
> at 
> com.thinkaurelius.titan.diskstorage.indexing.IndexTransaction.register(IndexTransaction.java:83)
> at 
> com.thinkaurelius.titan.graphdb.database.IndexSerializer.register(IndexSerializer.java:92)
> at 
> com.thinkaurelius.titan.graphdb.database.management.ManagementSystem.addIndexKey(ManagementSystem.java:534)
> at 
> org.apache.atlas.repository.graph.GraphBackedSearchIndexer.enhanceMixedIndex(GraphBackedSearchIndexer.java:405)
> at 
> org.apache.atlas.repository.graph.GraphBackedSearchIndexer.createIndexes(GraphBackedSearchIndexer.java:334)
> at 
> org.apache.atlas.repository.graph.GraphBackedSearchIndexer.initialize(GraphBackedSearchIndexer.java:103)
> ... 71 more
> {code}
> Atlas tables in HBase look ok.
> {code}
> su hbase
> kinit -kt /etc/security/keytabs/hbase.headless.keytab cstm-hb...@example.com
> hbase shell
> hbase(main):001:0> list
> TABLE
> ATLAS_ENTITY_AUDIT_EVENTS
> atlas_titan
> 2 row(s) in 1.4300 seconds
> => ["ATLAS_ENTITY_AUDIT_EVENTS", "atlas_titan"]
> {code}
> h4. Workaround
> 1. Stop Atlas Server
> 2. Copy solr xml files to correct config folder and chown as 
> $atlas_user:$hadoop_group
> {code}
> cp -R /usr/hdp/2.5.0.0-/etc/atlas/conf.dist/solr/* /etc/atlas/conf/solr/
> cp: overwrite `/etc/atlas/conf/solr/solrconfig.xml'? n
> chown atlas:hadoop /etc/atlas/conf/solr/*
> cp /usr/hdp/2.5.0.0-/etc/atlas/conf.dist/users-credentials.properties 
> /etc/atlas/conf/
> cp /usr/hdp/2.5.0.0-/etc/atlas/conf.dist/policy-store.txt /etc/atlas/conf/
> chown atlas:hadoop /etc/atlas/conf/users-credentials.properties
> chown atlas:hadoop /etc/atlas/conf/policy-store.txt
> {code}
> 3. Delete zookeeper znode,
> {code}
> # kinit -kt /etc/security/keytabs/atlas.service.keytab  atlas/@
> # cd /usr/hdp/current/zookeeper-client/bin/ 
> # ./zkCli.sh -server :
> [ .. (CONNECTED) ] rmr  /infra-solr/configs/atlas_configs
> {code}
> 4. Ensure Atlas application-properties are present for,
> atlas.jaas.KafkaClient.option.keyTab = 
> /etc/security/keytabs/atlas.service.keytab
> 

[jira] [Commented] (AMBARI-18385) Add HDF management pack

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-18385:


[~sumitmohanty] [~mahadev]
Can you review the patch for adding HDF mpack?

> Add HDF management pack
> ---
>
> Key: AMBARI-18385
> URL: https://issues.apache.org/jira/browse/AMBARI-18385
> Project: Ambari
>  Issue Type: Bug
>  Components: contrib
>Affects Versions: trunk
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: trunk
>
> Attachments: AMBARI-18385.patch
>
>
> Add HDF management pack to Ambari



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

[jira] [Comment Edited] (AMBARI-18385) Add HDF management pack

[Jayush Luniya (JIRA)]

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

Jayush Luniya edited comment on AMBARI-18385 at 9/14/16 1:16 AM:
-

{code}
mvn clean apache-rat:check
cd contrib/management-packs
mvn clean package
mvn clean apache-rat:check
{code}


was (Author: jluniya):
{code}
 mvn clean apache-rat:check
cd contrib/management-packs
mvn clean package
 mvn clean apache-rat:check
{code}

> Add HDF management pack
> ---
>
> Key: AMBARI-18385
> URL: https://issues.apache.org/jira/browse/AMBARI-18385
> Project: Ambari
>  Issue Type: Bug
>  Components: contrib
>Affects Versions: trunk
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: trunk
>
> Attachments: AMBARI-18385.patch
>
>
> Add HDF management pack to Ambari



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

[jira] [Commented] (AMBARI-18385) Add HDF management pack

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-18385:


{code}
 mvn clean apache-rat:check
cd contrib/management-packs
mvn clean package
 mvn clean apache-rat:check
{code}

> Add HDF management pack
> ---
>
> Key: AMBARI-18385
> URL: https://issues.apache.org/jira/browse/AMBARI-18385
> Project: Ambari
>  Issue Type: Bug
>  Components: contrib
>Affects Versions: trunk
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: trunk
>
> Attachments: AMBARI-18385.patch
>
>
> Add HDF management pack to Ambari



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

[jira] [Updated] (AMBARI-18385) Add HDF management pack

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-18385:
---
Attachment: AMBARI-18385.patch

> Add HDF management pack
> ---
>
> Key: AMBARI-18385
> URL: https://issues.apache.org/jira/browse/AMBARI-18385
> Project: Ambari
>  Issue Type: Bug
>  Components: contrib
>Affects Versions: trunk
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: trunk
>
> Attachments: AMBARI-18385.patch
>
>
> Add HDF management pack to Ambari



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

[jira] [Created] (AMBARI-18385) Add HDF management pack

[Jayush Luniya (JIRA)]

Jayush Luniya created AMBARI-18385:
--

 Summary: Add HDF management pack
 Key: AMBARI-18385
 URL: https://issues.apache.org/jira/browse/AMBARI-18385
 Project: Ambari
  Issue Type: Bug
  Components: contrib
Affects Versions: trunk
Reporter: Jayush Luniya
Assignee: Jayush Luniya
 Fix For: trunk


Add HDF management pack to Ambari



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

[jira] [Updated] (AMBARI-18374) rolling restart datanode cluster name show null

[wangyaoxin (JIRA)]

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

wangyaoxin updated AMBARI-18374:

Attachment: AMBARI-18374-1.patch

> rolling restart datanode cluster name show  null
> 
>
> Key: AMBARI-18374
> URL: https://issues.apache.org/jira/browse/AMBARI-18374
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: wangyaoxin
>Assignee: wangyaoxin
>  Labels: ambari-server
> Attachments: AMBARI-18374-1.patch, AMBARI-18374.patch, c.png, d.png
>
>
> when rolling restart services ( eg:DataNode ) ,cluster name in audit log show 
> null
> 2016-09-13T17:29:22.033+0800, User(admin), RemoteIp(127.0.0.1), 
> Operation(Request from server), RequestType(POST), 
> url(http://localhost:8080/api/v1/clusters/amabri/requests), ResultStatus(202 
> Accepted), Command(RESTART), Cluster name(null)
> 2016-09-13T17:29:22.042+0800, User(admin), 
> Operation(_PARSE_.ROLLING-RESTART.DATANODE.1.1), Status(IN_PROGRESS), 
> RequestId(15)



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

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

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18368:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5663 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5663/])
AMBARI-18368. Atlas web UI alert after performing stack upgrade to HDP 
(afernandez: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a33e2b628f5e6f40377c0c8c8cc348dcfb6d2a6f])
* (edit) 
ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata.py


> Atlas web UI alert after performing stack upgrade to HDP 2.5 and adding Atlas 
> Service
> -
>
> Key: AMBARI-18368
> URL: https://issues.apache.org/jira/browse/AMBARI-18368
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: trunk, 2.4.2
>
> Attachments: AMBARI-18368.patch
>
>
> Steps to Reproduce:
> * Install Ambari 2.2.2 with HDP 2.4 (HBase, Solr)
> * Kerberize the cluster
> * Perform EU/RU to HDP 2.5
> * Add Atlas Service
> Atlas Server log contains,
> {code}
> Caused by: 
> org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error 
> from server at 
> http://natu146-ehbs-dgm10toeriesec-u14-1.openstacklocal:8886/solr: Can not 
> find the specified config set: vertex_index
> at 
> org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:577)
> at 
> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:241)
> at 
> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:230)
> at 
> org.apache.solr.client.solrj.impl.LBHttpSolrClient.doRequest(LBHttpSolrClient.java:372)
> at 
> org.apache.solr.client.solrj.impl.LBHttpSolrClient.request(LBHttpSolrClient.java:325)
> at 
> org.apache.solr.client.solrj.impl.CloudSolrClient.sendRequest(CloudSolrClient.java:1100)
> at 
> org.apache.solr.client.solrj.impl.CloudSolrClient.requestWithRetryOnStaleState(CloudSolrClient.java:870)
> at 
> org.apache.solr.client.solrj.impl.CloudSolrClient.request(CloudSolrClient.java:806)
> at 
> org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:149)
> at 
> org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:166)
> at 
> com.thinkaurelius.titan.diskstorage.solr.Solr5Index.createCollectionIfNotExists(Solr5Index.java:901)
> at 
> com.thinkaurelius.titan.diskstorage.solr.Solr5Index.register(Solr5Index.java:269)
> at 
> com.thinkaurelius.titan.diskstorage.indexing.IndexTransaction.register(IndexTransaction.java:83)
> at 
> com.thinkaurelius.titan.graphdb.database.IndexSerializer.register(IndexSerializer.java:92)
> at 
> com.thinkaurelius.titan.graphdb.database.management.ManagementSystem.addIndexKey(ManagementSystem.java:534)
> at 
> org.apache.atlas.repository.graph.GraphBackedSearchIndexer.enhanceMixedIndex(GraphBackedSearchIndexer.java:405)
> at 
> org.apache.atlas.repository.graph.GraphBackedSearchIndexer.createIndexes(GraphBackedSearchIndexer.java:334)
> at 
> org.apache.atlas.repository.graph.GraphBackedSearchIndexer.initialize(GraphBackedSearchIndexer.java:103)
> ... 71 more
> {code}
> Atlas tables in HBase look ok.
> {code}
> su hbase
> kinit -kt /etc/security/keytabs/hbase.headless.keytab cstm-hb...@example.com
> hbase shell
> hbase(main):001:0> list
> TABLE
> ATLAS_ENTITY_AUDIT_EVENTS
> atlas_titan
> 2 row(s) in 1.4300 seconds
> => ["ATLAS_ENTITY_AUDIT_EVENTS", "atlas_titan"]
> {code}
> h4. Workaround
> 1. Stop Atlas Server
> 2. Copy solr xml files to correct config folder and chown as 
> $atlas_user:$hadoop_group
> {code}
> cp -R /usr/hdp/2.5.0.0-/etc/atlas/conf.dist/solr/* /etc/atlas/conf/solr/
> cp: overwrite `/etc/atlas/conf/solr/solrconfig.xml'? n
> chown atlas:hadoop /etc/atlas/conf/solr/*
> cp /usr/hdp/2.5.0.0-/etc/atlas/conf.dist/users-credentials.properties 
> /etc/atlas/conf/
> cp /usr/hdp/2.5.0.0-/etc/atlas/conf.dist/policy-store.txt /etc/atlas/conf/
> chown atlas:hadoop /etc/atlas/conf/users-credentials.properties
> chown atlas:hadoop /etc/atlas/conf/policy-store.txt
> {code}
> 3. Delete zookeeper znode,
> {code}
> # kinit -kt /etc/security/keytabs/atlas.service.keytab  atlas/@
> # cd /usr/hdp/current/zookeeper-client/bin/ 
> # ./zkCli.sh -server :
> [ .. (CONNECTED) ] rmr  /infra-solr/configs/atlas_configs
> {code}
> 4. Ensure Atlas application-properties are present for,
> atlas.jaas.KafkaClient.option.keyTab = 
> /etc/security/keytabs/atlas.service.keytab
> 

[jira] [Updated] (AMBARI-18384) Analyze and Optimize Ambari Server Unit Tests - Group 3

[Vitaly Brodetskyi (JIRA)]

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

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

> Analyze and Optimize Ambari Server Unit Tests - Group 3
> ---
>
> Key: AMBARI-18384
> URL: https://issues.apache.org/jira/browse/AMBARI-18384
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
> Fix For: trunk
>
> Attachments: AMBARI-18384.patch
>
>
> ||Test||Count||Time (s)||
> |org.apache.ambari.server.security.authorization.TestUsers|31|50.4|
> |org.apache.ambari.server.upgrade.UpgradeCatalog210Test   |18|46.497|
> |org.apache.ambari.server.state.svccomphost.ServiceComponentHostTest|15|43.899|
> |org.apache.ambari.server.serveraction.upgrades.UpgradeActionTest|9|35.136|
> |org.apache.ambari.server.agent.TestHeartbeatMonitor|6|28.146|



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

[jira] [Updated] (AMBARI-18384) Analyze and Optimize Ambari Server Unit Tests - Group 3

[Vitaly Brodetskyi (JIRA)]

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

Vitaly Brodetskyi updated AMBARI-18384:
---
Attachment: (was: AMBARI-18384.patch)

> Analyze and Optimize Ambari Server Unit Tests - Group 3
> ---
>
> Key: AMBARI-18384
> URL: https://issues.apache.org/jira/browse/AMBARI-18384
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
> Fix For: trunk
>
> Attachments: AMBARI-18384.patch
>
>
> ||Test||Count||Time (s)||
> |org.apache.ambari.server.security.authorization.TestUsers|31|50.4|
> |org.apache.ambari.server.upgrade.UpgradeCatalog210Test   |18|46.497|
> |org.apache.ambari.server.state.svccomphost.ServiceComponentHostTest|15|43.899|
> |org.apache.ambari.server.serveraction.upgrades.UpgradeActionTest|9|35.136|
> |org.apache.ambari.server.agent.TestHeartbeatMonitor|6|28.146|



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

[jira] [Updated] (AMBARI-18378) View instance cloning functionality

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-18378:

Status: Patch Available  (was: In Progress)

> View instance cloning functionality
> ---
>
> Key: AMBARI-18378
> URL: https://issues.apache.org/jira/browse/AMBARI-18378
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-admin, ambari-views
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-18378, ViewCloneIcon.jpg, ViewCloneInstance.jpg
>
>
> This task is for providing an option to clone / copy a view instance. 
> A new "copy" icon will appear next to a view instance. Clicking on this opens 
> up the existing view with instance name and display name of the view appended 
> with _Copy.
> This will be useful when creating multiple view instances with mild 
> configuration differences between them.



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

[jira] [Updated] (AMBARI-18378) View instance cloning functionality

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-18378:

Attachment: AMBARI-18378

> View instance cloning functionality
> ---
>
> Key: AMBARI-18378
> URL: https://issues.apache.org/jira/browse/AMBARI-18378
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-admin, ambari-views
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-18378, ViewCloneIcon.jpg, ViewCloneInstance.jpg
>
>
> This task is for providing an option to clone / copy a view instance. 
> A new "copy" icon will appear next to a view instance. Clicking on this opens 
> up the existing view with instance name and display name of the view appended 
> with _Copy.
> This will be useful when creating multiple view instances with mild 
> configuration differences between them.



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

[jira] [Updated] (AMBARI-18378) View instance cloning functionality

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-18378:

Description: 
This task is for providing an option to clone / copy a view instance. 

A new "copy" icon will appear next to a view instance. Clicking on this opens 
up the existing view with instance name and display name of the view appended 
with _Copy.
This will be useful when creating multiple view instances with mild 
configuration differences between them.

  was:
This task is for providing an option to clone / copy a view instance. 



> View instance cloning functionality
> ---
>
> Key: AMBARI-18378
> URL: https://issues.apache.org/jira/browse/AMBARI-18378
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-admin, ambari-views
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: trunk
>
> Attachments: ViewCloneIcon.jpg, ViewCloneInstance.jpg
>
>
> This task is for providing an option to clone / copy a view instance. 
> A new "copy" icon will appear next to a view instance. Clicking on this opens 
> up the existing view with instance name and display name of the view appended 
> with _Copy.
> This will be useful when creating multiple view instances with mild 
> configuration differences between them.



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

[jira] [Commented] (AMBARI-17636) Service Configs page: can't see all config versions in dropdown

[Hudson (JIRA)]

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

Hudson commented on AMBARI-17636:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #28 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/28/])
AMBARI-17636 Service Configs page: can't see all config versions in (zhewang: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2c96b3344606236d7865744bdb426aec625ec491])
* (edit) ambari-web/app/styles/config_history_flow.less
* (add) ambari-web/app/templates/common/configs/config_history_dropdown_row.hbs
* (edit) ambari-web/app/views/common/configs/config_history_flow.js
* (edit) ambari-web/app/templates/common/configs/config_history_flow.hbs


> Service Configs page: can't see all config versions in dropdown
> ---
>
> Key: AMBARI-17636
> URL: https://issues.apache.org/jira/browse/AMBARI-17636
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-17636.v0.patch, AMBARI-17636.v3.patch, 
> AMBARI-17636.v4.patch, bugfix.gif
>
>
> * Go to Service->Configs page (that have more than ~ 30 versions)
> * Open versions dropdown
> *Result:*
> Number of visible versions limited by window height.
>  



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

[jira] [Commented] (AMBARI-18382) Enable Kerberos Wizard: Metrics collector fails to start on a cluster with Ranger installed

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18382:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #28 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/28/])
AMBARI-18382. Enable Kerberos Wizard: Metrics collector fails to start (jaimin: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c2a897199f03449a77d9b3e529159d1dd93773eb])
* (edit) ambari-web/app/controllers/main/admin/kerberos/step4_controller.js


> Enable Kerberos Wizard: Metrics collector fails to start on a cluster with 
> Ranger installed
> ---
>
> Key: AMBARI-18382
> URL: https://issues.apache.org/jira/browse/AMBARI-18382
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18382.patch
>
>




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

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

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18355:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12828336/AMBARI-18355_v2.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/8657//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8657//console

This message is automatically generated.

> Introduce conditional dependencies in stack defition to handle blueprint 
> validation gracefully
> --
>
> Key: AMBARI-18355
> URL: https://issues.apache.org/jira/browse/AMBARI-18355
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-18355.patch, AMBARI-18355_v1.patch, 
> AMBARI-18355_v2.patch, Adding Conditional Dependencies.pdf
>
>
> Currently stack definitions do not list conditional dependencies, adding 
> those to the stack definitions would make it easy to validate errors in case 
> of blueprint deployment. 



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

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

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar updated AMBARI-18351:
-
Fix Version/s: (was: 2.4.2)
   2.5.0

> Preserve output while executing HSI/LLAP's "run.sh" command for launching 
> LLAP.
> ---
>
> Key: AMBARI-18351
> URL: https://issues.apache.org/jira/browse/AMBARI-18351
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18351.patch
>
>
> Ambari currently runs run.sh for LLAP as such:
> {noformat}
> 2016-08-29 20:34:47,770 - 
> Execute['/var/lib/ambari-agent/tmp/llap-slider2016-08-29_20-34-01/run.sh'] 
> {'user': 'hive'}
> 2016-08-29 20:35:51,856 - Submitted LLAP app name : llap0
> {noformat}
> Above is from Hive Interactive start operation output.
> Fix:
> - It would be good to include the output (stdout and stderr) of this command 
> in the operation logs, for debugging purposes.



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

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

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar updated AMBARI-18351:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Preserve output while executing HSI/LLAP's "run.sh" command for launching 
> LLAP.
> ---
>
> Key: AMBARI-18351
> URL: https://issues.apache.org/jira/browse/AMBARI-18351
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18351.patch
>
>
> Ambari currently runs run.sh for LLAP as such:
> {noformat}
> 2016-08-29 20:34:47,770 - 
> Execute['/var/lib/ambari-agent/tmp/llap-slider2016-08-29_20-34-01/run.sh'] 
> {'user': 'hive'}
> 2016-08-29 20:35:51,856 - Submitted LLAP app name : llap0
> {noformat}
> Above is from Hive Interactive start operation output.
> Fix:
> - It would be good to include the output (stdout and stderr) of this command 
> in the operation logs, for debugging purposes.



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

[jira] [Updated] (AMBARI-18383) Oozie spark failed due to incomplete spark share-lib directory

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan updated AMBARI-18383:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Pushed to trunk & branch-2.5

> Oozie spark failed due to incomplete spark share-lib directory
> --
>
> Key: AMBARI-18383
> URL: https://issues.apache.org/jira/browse/AMBARI-18383
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18383.patch
>
>
> Failed exception:
> {noformat}
> "Failing Oozie Launcher, Main class 
> [org.apache.oozie.action.hadoop.SparkMain], main() 
> threw exception, Missing py4j and/or pyspark zip files. Please add them to 
> the lib folder 
> or to the Spark sharelib.
> org.apache.oozie.action.hadoop.OozieActionConfiguratorException: Missing py4j 
> and/or 
> pyspark zip files. Please add them to the lib folder or to the Spark 
> sharelib."
> {noformat}
> Those two files were not present in the share lib
> hrt_qa@hn0-3ad6fe:~$ hdfs dfs -ls /user/oozie/share/lib/spark/*.zip
> ls: `/user/oozie/share/lib/spark/*.zip': No such file or directory



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

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

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar commented on AMBARI-18351:
--

trunk:

{noformat}
commit b44078cc30ac3c5d4fa86efbcaa9e5d68a37bc04
Author: Swapan Shridhar 
Date:   Mon Sep 12 11:27:18 2016 -0700

AMBARI-18351. Preserve output while executing HSI/LLAP's run.sh command for 
launching LLAP.
{noformat}

branch-2.5:

{noformat}
commit 627c1b48ccf94d32396f9ba3061fa01221848d28
Author: Swapan Shridhar 
Date:   Mon Sep 12 11:27:18 2016 -0700

AMBARI-18351. Preserve output while executing HSI/LLAP's run.sh command for 
launching LLAP.
{noformat}

> Preserve output while executing HSI/LLAP's "run.sh" command for launching 
> LLAP.
> ---
>
> Key: AMBARI-18351
> URL: https://issues.apache.org/jira/browse/AMBARI-18351
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18351.patch
>
>
> Ambari currently runs run.sh for LLAP as such:
> {noformat}
> 2016-08-29 20:34:47,770 - 
> Execute['/var/lib/ambari-agent/tmp/llap-slider2016-08-29_20-34-01/run.sh'] 
> {'user': 'hive'}
> 2016-08-29 20:35:51,856 - Submitted LLAP app name : llap0
> {noformat}
> Above is from Hive Interactive start operation output.
> Fix:
> - It would be good to include the output (stdout and stderr) of this command 
> in the operation logs, for debugging purposes.



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

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

[Alejandro Fernandez (JIRA)]

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

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

Pushed to trunk, commit fc10afbce791e01679e51305218363e9eef2822f
branch-2.5, commit 72617ce7339dc0859aa0508d9f7a3d50a477ac3a
branch-2.4, commit 86be233746595a49c4ef1f734d9891fc3692428e

> Atlas web UI alert after performing stack upgrade to HDP 2.5 and adding Atlas 
> Service
> -
>
> Key: AMBARI-18368
> URL: https://issues.apache.org/jira/browse/AMBARI-18368
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: trunk, 2.4.2
>
> Attachments: AMBARI-18368.patch
>
>
> Steps to Reproduce:
> * Install Ambari 2.2.2 with HDP 2.4 (HBase, Solr)
> * Kerberize the cluster
> * Perform EU/RU to HDP 2.5
> * Add Atlas Service
> Atlas Server log contains,
> {code}
> Caused by: 
> org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error 
> from server at 
> http://natu146-ehbs-dgm10toeriesec-u14-1.openstacklocal:8886/solr: Can not 
> find the specified config set: vertex_index
> at 
> org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:577)
> at 
> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:241)
> at 
> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:230)
> at 
> org.apache.solr.client.solrj.impl.LBHttpSolrClient.doRequest(LBHttpSolrClient.java:372)
> at 
> org.apache.solr.client.solrj.impl.LBHttpSolrClient.request(LBHttpSolrClient.java:325)
> at 
> org.apache.solr.client.solrj.impl.CloudSolrClient.sendRequest(CloudSolrClient.java:1100)
> at 
> org.apache.solr.client.solrj.impl.CloudSolrClient.requestWithRetryOnStaleState(CloudSolrClient.java:870)
> at 
> org.apache.solr.client.solrj.impl.CloudSolrClient.request(CloudSolrClient.java:806)
> at 
> org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:149)
> at 
> org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:166)
> at 
> com.thinkaurelius.titan.diskstorage.solr.Solr5Index.createCollectionIfNotExists(Solr5Index.java:901)
> at 
> com.thinkaurelius.titan.diskstorage.solr.Solr5Index.register(Solr5Index.java:269)
> at 
> com.thinkaurelius.titan.diskstorage.indexing.IndexTransaction.register(IndexTransaction.java:83)
> at 
> com.thinkaurelius.titan.graphdb.database.IndexSerializer.register(IndexSerializer.java:92)
> at 
> com.thinkaurelius.titan.graphdb.database.management.ManagementSystem.addIndexKey(ManagementSystem.java:534)
> at 
> org.apache.atlas.repository.graph.GraphBackedSearchIndexer.enhanceMixedIndex(GraphBackedSearchIndexer.java:405)
> at 
> org.apache.atlas.repository.graph.GraphBackedSearchIndexer.createIndexes(GraphBackedSearchIndexer.java:334)
> at 
> org.apache.atlas.repository.graph.GraphBackedSearchIndexer.initialize(GraphBackedSearchIndexer.java:103)
> ... 71 more
> {code}
> Atlas tables in HBase look ok.
> {code}
> su hbase
> kinit -kt /etc/security/keytabs/hbase.headless.keytab cstm-hb...@example.com
> hbase shell
> hbase(main):001:0> list
> TABLE
> ATLAS_ENTITY_AUDIT_EVENTS
> atlas_titan
> 2 row(s) in 1.4300 seconds
> => ["ATLAS_ENTITY_AUDIT_EVENTS", "atlas_titan"]
> {code}
> h4. Workaround
> 1. Stop Atlas Server
> 2. Copy solr xml files to correct config folder and chown as 
> $atlas_user:$hadoop_group
> {code}
> cp -R /usr/hdp/2.5.0.0-/etc/atlas/conf.dist/solr/* /etc/atlas/conf/solr/
> cp: overwrite `/etc/atlas/conf/solr/solrconfig.xml'? n
> chown atlas:hadoop /etc/atlas/conf/solr/*
> cp /usr/hdp/2.5.0.0-/etc/atlas/conf.dist/users-credentials.properties 
> /etc/atlas/conf/
> cp /usr/hdp/2.5.0.0-/etc/atlas/conf.dist/policy-store.txt /etc/atlas/conf/
> chown atlas:hadoop /etc/atlas/conf/users-credentials.properties
> chown atlas:hadoop /etc/atlas/conf/policy-store.txt
> {code}
> 3. Delete zookeeper znode,
> {code}
> # kinit -kt /etc/security/keytabs/atlas.service.keytab  atlas/@
> # cd /usr/hdp/current/zookeeper-client/bin/ 
> # ./zkCli.sh -server :
> [ .. (CONNECTED) ] rmr  /infra-solr/configs/atlas_configs
> {code}
> 4. Ensure Atlas application-properties are present for,
> atlas.jaas.KafkaClient.option.keyTab = 
> /etc/security/keytabs/atlas.service.keytab
> atlas.jaas.KafkaClient.option.principal = atlas/_h...@example.com
> 5. Start Atlas



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

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

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-18368:
-
Fix Version/s: (was: 2.5.0)
   (was: 2.4.1)
   2.4.2

> Atlas web UI alert after performing stack upgrade to HDP 2.5 and adding Atlas 
> Service
> -
>
> Key: AMBARI-18368
> URL: https://issues.apache.org/jira/browse/AMBARI-18368
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: trunk, 2.4.2
>
> Attachments: AMBARI-18368.patch
>
>
> Steps to Reproduce:
> * Install Ambari 2.2.2 with HDP 2.4 (HBase, Solr)
> * Kerberize the cluster
> * Perform EU/RU to HDP 2.5
> * Add Atlas Service
> Atlas Server log contains,
> {code}
> Caused by: 
> org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error 
> from server at 
> http://natu146-ehbs-dgm10toeriesec-u14-1.openstacklocal:8886/solr: Can not 
> find the specified config set: vertex_index
> at 
> org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:577)
> at 
> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:241)
> at 
> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:230)
> at 
> org.apache.solr.client.solrj.impl.LBHttpSolrClient.doRequest(LBHttpSolrClient.java:372)
> at 
> org.apache.solr.client.solrj.impl.LBHttpSolrClient.request(LBHttpSolrClient.java:325)
> at 
> org.apache.solr.client.solrj.impl.CloudSolrClient.sendRequest(CloudSolrClient.java:1100)
> at 
> org.apache.solr.client.solrj.impl.CloudSolrClient.requestWithRetryOnStaleState(CloudSolrClient.java:870)
> at 
> org.apache.solr.client.solrj.impl.CloudSolrClient.request(CloudSolrClient.java:806)
> at 
> org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:149)
> at 
> org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:166)
> at 
> com.thinkaurelius.titan.diskstorage.solr.Solr5Index.createCollectionIfNotExists(Solr5Index.java:901)
> at 
> com.thinkaurelius.titan.diskstorage.solr.Solr5Index.register(Solr5Index.java:269)
> at 
> com.thinkaurelius.titan.diskstorage.indexing.IndexTransaction.register(IndexTransaction.java:83)
> at 
> com.thinkaurelius.titan.graphdb.database.IndexSerializer.register(IndexSerializer.java:92)
> at 
> com.thinkaurelius.titan.graphdb.database.management.ManagementSystem.addIndexKey(ManagementSystem.java:534)
> at 
> org.apache.atlas.repository.graph.GraphBackedSearchIndexer.enhanceMixedIndex(GraphBackedSearchIndexer.java:405)
> at 
> org.apache.atlas.repository.graph.GraphBackedSearchIndexer.createIndexes(GraphBackedSearchIndexer.java:334)
> at 
> org.apache.atlas.repository.graph.GraphBackedSearchIndexer.initialize(GraphBackedSearchIndexer.java:103)
> ... 71 more
> {code}
> Atlas tables in HBase look ok.
> {code}
> su hbase
> kinit -kt /etc/security/keytabs/hbase.headless.keytab cstm-hb...@example.com
> hbase shell
> hbase(main):001:0> list
> TABLE
> ATLAS_ENTITY_AUDIT_EVENTS
> atlas_titan
> 2 row(s) in 1.4300 seconds
> => ["ATLAS_ENTITY_AUDIT_EVENTS", "atlas_titan"]
> {code}
> h4. Workaround
> 1. Stop Atlas Server
> 2. Copy solr xml files to correct config folder and chown as 
> $atlas_user:$hadoop_group
> {code}
> cp -R /usr/hdp/2.5.0.0-/etc/atlas/conf.dist/solr/* /etc/atlas/conf/solr/
> cp: overwrite `/etc/atlas/conf/solr/solrconfig.xml'? n
> chown atlas:hadoop /etc/atlas/conf/solr/*
> cp /usr/hdp/2.5.0.0-/etc/atlas/conf.dist/users-credentials.properties 
> /etc/atlas/conf/
> cp /usr/hdp/2.5.0.0-/etc/atlas/conf.dist/policy-store.txt /etc/atlas/conf/
> chown atlas:hadoop /etc/atlas/conf/users-credentials.properties
> chown atlas:hadoop /etc/atlas/conf/policy-store.txt
> {code}
> 3. Delete zookeeper znode,
> {code}
> # kinit -kt /etc/security/keytabs/atlas.service.keytab  atlas/@
> # cd /usr/hdp/current/zookeeper-client/bin/ 
> # ./zkCli.sh -server :
> [ .. (CONNECTED) ] rmr  /infra-solr/configs/atlas_configs
> {code}
> 4. Ensure Atlas application-properties are present for,
> atlas.jaas.KafkaClient.option.keyTab = 
> /etc/security/keytabs/atlas.service.keytab
> atlas.jaas.KafkaClient.option.principal = atlas/_h...@example.com
> 5. Start Atlas



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

[jira] [Commented] (AMBARI-17458) Add support for distributed collector to Ambari REST API

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan commented on AMBARI-17458:


Pushed to trunk.

> Add support for distributed collector to Ambari REST API
> 
>
> Key: AMBARI-17458
> URL: https://issues.apache.org/jira/browse/AMBARI-17458
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Siddharth Wagle
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 3.0.0
>
>
> _Tasks_:
> - Add a Zookeeper watcher for the AMS znode
> - Find available collectors and round-robin the READ calls from 
> AMSPropertyProvider
> - Tolerate failure by switching to available collector



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

[jira] [Commented] (AMBARI-18281) Expose Disabling of Alert Targets in Web Client

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18281:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5662 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5662/])
Ambari-18281 Expose Disabling of Alert Targets in Web Client (Vivek (zhewang: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9595706527b924cb273723fd1906c6a4b5d3d686])
* (edit) 
ambari-web/app/controllers/main/alerts/alert_definitions_actions_controller.js
* (edit) ambari-web/app/styles/modal_popups.less


> Expose Disabling of Alert Targets in Web Client
> ---
>
> Key: AMBARI-18281
> URL: https://issues.apache.org/jira/browse/AMBARI-18281
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 3.0.0
>
> Attachments: AMBARI-18281.v0.patch, AMBARI-18281.v1.patch, 
> AMBARI-18281.v2.patch
>
>
> Add an option to Enable/ Disable alert notifications in Manage Notifications 
> popup.



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

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

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-18368:
-
Fix Version/s: 2.4.1

> Atlas web UI alert after performing stack upgrade to HDP 2.5 and adding Atlas 
> Service
> -
>
> Key: AMBARI-18368
> URL: https://issues.apache.org/jira/browse/AMBARI-18368
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: trunk, 2.4.1, 2.5.0
>
> Attachments: AMBARI-18368.patch
>
>
> Steps to Reproduce:
> * Install Ambari 2.2.2 with HDP 2.4 (HBase, Solr)
> * Kerberize the cluster
> * Perform EU/RU to HDP 2.5
> * Add Atlas Service
> Atlas Server log contains,
> {code}
> Caused by: 
> org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error 
> from server at 
> http://natu146-ehbs-dgm10toeriesec-u14-1.openstacklocal:8886/solr: Can not 
> find the specified config set: vertex_index
> at 
> org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:577)
> at 
> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:241)
> at 
> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:230)
> at 
> org.apache.solr.client.solrj.impl.LBHttpSolrClient.doRequest(LBHttpSolrClient.java:372)
> at 
> org.apache.solr.client.solrj.impl.LBHttpSolrClient.request(LBHttpSolrClient.java:325)
> at 
> org.apache.solr.client.solrj.impl.CloudSolrClient.sendRequest(CloudSolrClient.java:1100)
> at 
> org.apache.solr.client.solrj.impl.CloudSolrClient.requestWithRetryOnStaleState(CloudSolrClient.java:870)
> at 
> org.apache.solr.client.solrj.impl.CloudSolrClient.request(CloudSolrClient.java:806)
> at 
> org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:149)
> at 
> org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:166)
> at 
> com.thinkaurelius.titan.diskstorage.solr.Solr5Index.createCollectionIfNotExists(Solr5Index.java:901)
> at 
> com.thinkaurelius.titan.diskstorage.solr.Solr5Index.register(Solr5Index.java:269)
> at 
> com.thinkaurelius.titan.diskstorage.indexing.IndexTransaction.register(IndexTransaction.java:83)
> at 
> com.thinkaurelius.titan.graphdb.database.IndexSerializer.register(IndexSerializer.java:92)
> at 
> com.thinkaurelius.titan.graphdb.database.management.ManagementSystem.addIndexKey(ManagementSystem.java:534)
> at 
> org.apache.atlas.repository.graph.GraphBackedSearchIndexer.enhanceMixedIndex(GraphBackedSearchIndexer.java:405)
> at 
> org.apache.atlas.repository.graph.GraphBackedSearchIndexer.createIndexes(GraphBackedSearchIndexer.java:334)
> at 
> org.apache.atlas.repository.graph.GraphBackedSearchIndexer.initialize(GraphBackedSearchIndexer.java:103)
> ... 71 more
> {code}
> Atlas tables in HBase look ok.
> {code}
> su hbase
> kinit -kt /etc/security/keytabs/hbase.headless.keytab cstm-hb...@example.com
> hbase shell
> hbase(main):001:0> list
> TABLE
> ATLAS_ENTITY_AUDIT_EVENTS
> atlas_titan
> 2 row(s) in 1.4300 seconds
> => ["ATLAS_ENTITY_AUDIT_EVENTS", "atlas_titan"]
> {code}
> h4. Workaround
> 1. Stop Atlas Server
> 2. Copy solr xml files to correct config folder and chown as 
> $atlas_user:$hadoop_group
> {code}
> cp -R /usr/hdp/2.5.0.0-/etc/atlas/conf.dist/solr/* /etc/atlas/conf/solr/
> cp: overwrite `/etc/atlas/conf/solr/solrconfig.xml'? n
> chown atlas:hadoop /etc/atlas/conf/solr/*
> cp /usr/hdp/2.5.0.0-/etc/atlas/conf.dist/users-credentials.properties 
> /etc/atlas/conf/
> cp /usr/hdp/2.5.0.0-/etc/atlas/conf.dist/policy-store.txt /etc/atlas/conf/
> chown atlas:hadoop /etc/atlas/conf/users-credentials.properties
> chown atlas:hadoop /etc/atlas/conf/policy-store.txt
> {code}
> 3. Delete zookeeper znode,
> {code}
> # kinit -kt /etc/security/keytabs/atlas.service.keytab  atlas/@
> # cd /usr/hdp/current/zookeeper-client/bin/ 
> # ./zkCli.sh -server :
> [ .. (CONNECTED) ] rmr  /infra-solr/configs/atlas_configs
> {code}
> 4. Ensure Atlas application-properties are present for,
> atlas.jaas.KafkaClient.option.keyTab = 
> /etc/security/keytabs/atlas.service.keytab
> atlas.jaas.KafkaClient.option.principal = atlas/_h...@example.com
> 5. Start Atlas



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

[jira] [Updated] (AMBARI-17458) Add support for distributed collector to Ambari REST API

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan updated AMBARI-17458:
---
Attachment: (was: AMBARI-17458.patch)

> Add support for distributed collector to Ambari REST API
> 
>
> Key: AMBARI-17458
> URL: https://issues.apache.org/jira/browse/AMBARI-17458
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Siddharth Wagle
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 3.0.0
>
>
> _Tasks_:
> - Add a Zookeeper watcher for the AMS znode
> - Find available collectors and round-robin the READ calls from 
> AMSPropertyProvider
> - Tolerate failure by switching to available collector



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

[jira] [Commented] (AMBARI-10908) Usability: ability to perform bulk delete host

[Hudson (JIRA)]

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

Hudson commented on AMBARI-10908:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #27 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/27/])
AMBARI-10908 Usability: ability to perform bulk delete host (zhewang) (zhewang: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4db1a1e982fba628bf876c8bf983ea49b2fdec3a])
* (add) ambari-web/app/templates/main/host/delete_hosts_dry_run_popup.hbs
* (add) ambari-web/app/templates/main/host/delete_hosts_popup.hbs
* (add) ambari-web/app/templates/main/host/delete_hosts_result_popup.hbs
* (edit) ambari-web/app/utils/ajax/ajax.js
* (edit) ambari-web/app/controllers/main/host/bulk_operations_controller.js
* (edit) ambari-web/app/styles/application.less
* (edit) ambari-web/app/views/main/host/hosts_table_menu_view.js
* (edit) ambari-web/app/messages.js


> Usability: ability to perform bulk delete host
> --
>
> Key: AMBARI-10908
> URL: https://issues.apache.org/jira/browse/AMBARI-10908
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Jeff Sposetti
>Assignee: Zhe (Joe) Wang
> Fix For: 2.5.0
>
> Attachments: AMBARI-10908.v0.patch, AMBARI-10908.v1.patch
>
>
> On Hosts page, provide ability to delete hosts in bulk.



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

[jira] [Commented] (AMBARI-18280) Ambari widget graph is not aggregating the data correctly for Total Request Count

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18280:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #27 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/27/])
AMBARI-18280 Ambari widget graph is not aggregating the data correctly 
(zhewang: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8581975f9b08b1edbe4e0807ac50c66c0e7d379f])
* (edit) ambari-web/app/utils/ajax/ajax.js
* (edit) 
ambari-web/app/views/main/service/info/metrics/ambari_metrics/regionserver_requests.js


> Ambari widget graph is not aggregating the data correctly for Total Request 
> Count
> -
>
> Key: AMBARI-18280
> URL: https://issues.apache.org/jira/browse/AMBARI-18280
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
> Fix For: 2.5.0
>
> Attachments: AMBARI-18280.v0.patch
>
>
> *PROBLEM:* Total Request Count is not growing exponentially 
> *IMPACT:* User is not able to monitor the data correctly.



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

[jira] [Updated] (AMBARI-18384) Analyze and Optimize Ambari Server Unit Tests - Group 3

[Vitaly Brodetskyi (JIRA)]

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

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

> Analyze and Optimize Ambari Server Unit Tests - Group 3
> ---
>
> Key: AMBARI-18384
> URL: https://issues.apache.org/jira/browse/AMBARI-18384
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
> Fix For: trunk
>
> Attachments: AMBARI-18384.patch
>
>
> ||Test||Count||Time (s)||
> |org.apache.ambari.server.security.authorization.TestUsers|31|50.4|
> |org.apache.ambari.server.upgrade.UpgradeCatalog210Test   |18|46.497|
> |org.apache.ambari.server.state.svccomphost.ServiceComponentHostTest|15|43.899|
> |org.apache.ambari.server.serveraction.upgrades.UpgradeActionTest|9|35.136|
> |org.apache.ambari.server.agent.TestHeartbeatMonitor|6|28.146|



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

[jira] [Commented] (AMBARI-18185) Selecting one host when topN is set, throws an error

[Siddharth Wagle (JIRA)]

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

Siddharth Wagle commented on AMBARI-18185:
--

+1 LGTM

> Selecting one host when topN is set, throws an error
> 
>
> Key: AMBARI-18185
> URL: https://issues.apache.org/jira/browse/AMBARI-18185
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18185.patch
>
>
> topN is available by default on almost all Grafana templatized dashboards.
> When viewing any of these dashboards, if only one "host" or templated option 
> is chosen, then AMS returns with an exception (screenshot attached).
> Sample query:
> collectorhost:6188/ws/v1/timeline/metrics?metricNames=cpu_system._avg=hostname=HOST=1470925360=1470946960=20=avg=false



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

[jira] [Commented] (AMBARI-18383) Oozie spark failed due to incomplete spark share-lib directory

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18383:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12828337/AMBARI-18383.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/8656//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8656//console

This message is automatically generated.

> Oozie spark failed due to incomplete spark share-lib directory
> --
>
> Key: AMBARI-18383
> URL: https://issues.apache.org/jira/browse/AMBARI-18383
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18383.patch
>
>
> Failed exception:
> {noformat}
> "Failing Oozie Launcher, Main class 
> [org.apache.oozie.action.hadoop.SparkMain], main() 
> threw exception, Missing py4j and/or pyspark zip files. Please add them to 
> the lib folder 
> or to the Spark sharelib.
> org.apache.oozie.action.hadoop.OozieActionConfiguratorException: Missing py4j 
> and/or 
> pyspark zip files. Please add them to the lib folder or to the Spark 
> sharelib."
> {noformat}
> Those two files were not present in the share lib
> hrt_qa@hn0-3ad6fe:~$ hdfs dfs -ls /user/oozie/share/lib/spark/*.zip
> ls: `/user/oozie/share/lib/spark/*.zip': No such file or directory



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

[jira] [Created] (AMBARI-18384) Analyze and Optimize Ambari Server Unit Tests - Group 3

[Vitaly Brodetskyi (JIRA)]

Vitaly Brodetskyi created AMBARI-18384:
--

 Summary: Analyze and Optimize Ambari Server Unit Tests - Group 3
 Key: AMBARI-18384
 URL: https://issues.apache.org/jira/browse/AMBARI-18384
 Project: Ambari
  Issue Type: Task
  Components: ambari-server
Affects Versions: trunk
Reporter: Vitaly Brodetskyi
Assignee: Vitaly Brodetskyi
 Fix For: trunk


||Test||Count||Time (s)||
|org.apache.ambari.server.security.authorization.TestUsers|31|50.4|
|org.apache.ambari.server.upgrade.UpgradeCatalog210Test |18|46.497|
|org.apache.ambari.server.state.svccomphost.ServiceComponentHostTest|15|43.899|
|org.apache.ambari.server.serveraction.upgrades.UpgradeActionTest|9|35.136|
|org.apache.ambari.server.agent.TestHeartbeatMonitor|6|28.146|



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

[jira] [Updated] (AMBARI-18383) Oozie spark failed due to incomplete spark share-lib directory

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan updated AMBARI-18383:
---
Summary: Oozie spark failed due to incomplete spark share-lib directory  
(was: Oozie spark failed due to missing py4j and/or pyspark zip files in share 
lib)

> Oozie spark failed due to incomplete spark share-lib directory
> --
>
> Key: AMBARI-18383
> URL: https://issues.apache.org/jira/browse/AMBARI-18383
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18383.patch
>
>
> Failed exception:
> {noformat}
> "Failing Oozie Launcher, Main class 
> [org.apache.oozie.action.hadoop.SparkMain], main() 
> threw exception, Missing py4j and/or pyspark zip files. Please add them to 
> the lib folder 
> or to the Spark sharelib.
> org.apache.oozie.action.hadoop.OozieActionConfiguratorException: Missing py4j 
> and/or 
> pyspark zip files. Please add them to the lib folder or to the Spark 
> sharelib."
> {noformat}
> Those two files were not present in the share lib
> hrt_qa@hn0-3ad6fe:~$ hdfs dfs -ls /user/oozie/share/lib/spark/*.zip
> ls: `/user/oozie/share/lib/spark/*.zip': No such file or directory



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

[jira] [Updated] (AMBARI-18383) Oozie spark failed due to missing py4j and/or pyspark zip files in share lib

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan updated AMBARI-18383:
---
Status: Patch Available  (was: Open)

> Oozie spark failed due to missing py4j and/or pyspark zip files in share lib
> 
>
> Key: AMBARI-18383
> URL: https://issues.apache.org/jira/browse/AMBARI-18383
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18383.patch
>
>
> Failed exception:
> {noformat}
> "Failing Oozie Launcher, Main class 
> [org.apache.oozie.action.hadoop.SparkMain], main() 
> threw exception, Missing py4j and/or pyspark zip files. Please add them to 
> the lib folder 
> or to the Spark sharelib.
> org.apache.oozie.action.hadoop.OozieActionConfiguratorException: Missing py4j 
> and/or 
> pyspark zip files. Please add them to the lib folder or to the Spark 
> sharelib."
> {noformat}
> Those two files were not present in the share lib
> hrt_qa@hn0-3ad6fe:~$ hdfs dfs -ls /user/oozie/share/lib/spark/*.zip
> ls: `/user/oozie/share/lib/spark/*.zip': No such file or directory



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

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

[Amruta Borkar (JIRA)]

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

Amruta Borkar updated AMBARI-18355:
---
Attachment: AMBARI-18355_v2.patch

> Introduce conditional dependencies in stack defition to handle blueprint 
> validation gracefully
> --
>
> Key: AMBARI-18355
> URL: https://issues.apache.org/jira/browse/AMBARI-18355
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-18355.patch, AMBARI-18355_v1.patch, 
> AMBARI-18355_v2.patch, Adding Conditional Dependencies.pdf
>
>
> Currently stack definitions do not list conditional dependencies, adding 
> those to the stack definitions would make it easy to validate errors in case 
> of blueprint deployment. 



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

[jira] [Updated] (AMBARI-18383) Oozie spark failed due to missing py4j and/or pyspark zip files in share lib

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan updated AMBARI-18383:
---
Attachment: AMBARI-18383.patch

> Oozie spark failed due to missing py4j and/or pyspark zip files in share lib
> 
>
> Key: AMBARI-18383
> URL: https://issues.apache.org/jira/browse/AMBARI-18383
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18383.patch
>
>
> Failed exception:
> {noformat}
> "Failing Oozie Launcher, Main class 
> [org.apache.oozie.action.hadoop.SparkMain], main() 
> threw exception, Missing py4j and/or pyspark zip files. Please add them to 
> the lib folder 
> or to the Spark sharelib.
> org.apache.oozie.action.hadoop.OozieActionConfiguratorException: Missing py4j 
> and/or 
> pyspark zip files. Please add them to the lib folder or to the Spark 
> sharelib."
> {noformat}
> Those two files were not present in the share lib
> hrt_qa@hn0-3ad6fe:~$ hdfs dfs -ls /user/oozie/share/lib/spark/*.zip
> ls: `/user/oozie/share/lib/spark/*.zip': No such file or directory



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

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

[Amruta Borkar (JIRA)]

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

Amruta Borkar updated AMBARI-18355:
---
Status: Patch Available  (was: In Progress)

> Introduce conditional dependencies in stack defition to handle blueprint 
> validation gracefully
> --
>
> Key: AMBARI-18355
> URL: https://issues.apache.org/jira/browse/AMBARI-18355
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-18355.patch, AMBARI-18355_v1.patch, 
> AMBARI-18355_v2.patch, Adding Conditional Dependencies.pdf
>
>
> Currently stack definitions do not list conditional dependencies, adding 
> those to the stack definitions would make it easy to validate errors in case 
> of blueprint deployment. 



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

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

[Amruta Borkar (JIRA)]

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

Amruta Borkar updated AMBARI-18355:
---
Status: Open  (was: Patch Available)

> Introduce conditional dependencies in stack defition to handle blueprint 
> validation gracefully
> --
>
> Key: AMBARI-18355
> URL: https://issues.apache.org/jira/browse/AMBARI-18355
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-18355.patch, AMBARI-18355_v1.patch, 
> AMBARI-18355_v2.patch, Adding Conditional Dependencies.pdf
>
>
> Currently stack definitions do not list conditional dependencies, adding 
> those to the stack definitions would make it easy to validate errors in case 
> of blueprint deployment. 



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

[jira] [Created] (AMBARI-18383) Oozie spark failed due to missing py4j and/or pyspark zip files in share lib

[Aravindan Vijayan (JIRA)]

Aravindan Vijayan created AMBARI-18383:
--

 Summary: Oozie spark failed due to missing py4j and/or pyspark zip 
files in share lib
 Key: AMBARI-18383
 URL: https://issues.apache.org/jira/browse/AMBARI-18383
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.4.0
Reporter: Aravindan Vijayan
Assignee: Aravindan Vijayan
Priority: Blocker
 Fix For: 2.5.0


Failed exception:
{noformat}
"Failing Oozie Launcher, Main class [org.apache.oozie.action.hadoop.SparkMain], 
main() 
threw exception, Missing py4j and/or pyspark zip files. Please add them to the 
lib folder 
or to the Spark sharelib.

org.apache.oozie.action.hadoop.OozieActionConfiguratorException: Missing py4j 
and/or 
pyspark zip files. Please add them to the lib folder or to the Spark sharelib."

{noformat}


Those two files were not present in the share lib
hrt_qa@hn0-3ad6fe:~$ hdfs dfs -ls /user/oozie/share/lib/spark/*.zip
ls: `/user/oozie/share/lib/spark/*.zip': No such file or directory




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

[jira] [Updated] (AMBARI-18382) Enable Kerberos Wizard: Metrics collector fails to start on a cluster with Ranger installed

[Jaimin D Jetly (JIRA)]

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

Jaimin D Jetly updated AMBARI-18382:

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

Received +1 on reviewboard.
Patch committed to trunk, branch-2.5 and branch-2.4

> Enable Kerberos Wizard: Metrics collector fails to start on a cluster with 
> Ranger installed
> ---
>
> Key: AMBARI-18382
> URL: https://issues.apache.org/jira/browse/AMBARI-18382
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18382.patch
>
>




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

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

[Tim Thorpe (JIRA)]

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

Tim Thorpe commented on AMBARI-15538:
-

I will try to look at this tomorrow.  Sorry I've been busy with customer issues 
today.  [~jluniya] do you mean more than one version of the same service in the 
same extension version?  For example in EXT/1.0 containing 2 different 
MY_SERVICE versions?  If so, this won't be supported until the stack is able to 
do the same thing.  If you mean EXT/1.0/services/MY_SERVICE (version 0.1) and 
EXT/1.1/services/MY_SERVICE (version 0.2) then this is already supported.

> Support service-specific repo for add-on services
> -
>
> Key: AMBARI-15538
> URL: https://issues.apache.org/jira/browse/AMBARI-15538
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.0, 2.2.0, 2.4.0
>Reporter: Jayush Luniya
>Assignee: Balázs Bence Sári
> Fix For: 2.5.0, 2.4.2
>
> Attachments: AMBARI-15538-custom-repos-patch3-trunk.diff
>
>
> The approach for custom-services to specify their own repo location will be 
> to provide a {{/repos/repoinfo.xml}} inside the stack-version they will be 
> in. This repo file will be loaded by Ambari during startup into the 
> {{/api/v1/stacks/HDP/versions/2.4/repository_versions}} repos. *Service repo 
> files have a restriction that their (repo-name, base-url) locations should be 
> unique and not conflict*. When conflicts do occur, they will not be loaded 
> into the stacks model.
> Now the management-pack will provide such repos/ folder in 
> {{mpacks/custom-services/8.0.0/repos}} which will be linked into the stacks/ 
> folder.
> {{ambari/ambari-server/src/main/resources/stacks/HDP/2.3/services/SERVICE_NAME/repos
>  -> mpacks/custom-services/8.0.0/repos}}



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

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

[Jayush Luniya (JIRA)]

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

Jayush Luniya edited comment on AMBARI-15538 at 9/13/16 8:42 PM:
-

[~Tim Thorpe]
Latest patch submitted by [~bsari] addresses some of your comments (it handles 
repos defined for a service definition for an extension correctly as well has 
handles stack inheritance correctly). 

Lets say that in an extension we have MYSERVICE/1.0 -> HDP-2.4 and 
MYSERVICE/2.0  -> HDP-2.5. In that case we will need to add different repos for 
MYSERVICE/1.0 and MYSERVICE/2.0 (i.e. we will need to add repos at service 
level). 

BTW, I don't see a way to add more than one versions of a service in an 
extension. I think we need to support that? 


was (Author: jluniya):
[~Tim Thorpe]
Latest patch submitted by [~bsari] addresses some of your comments (it handles 
repos defined for a service definition for an extension correctly as well has 
handles stack inheritance correctly). 

Lets say that in an extension we have MYSERVICE/1.0 -> HDP-2.4 and 
MYSERVICE/2.0  -> HDP-2.5. In that case we will need to add different repos for 
MYSERVICE/1.0 and MYSERVICE/2.0 (i.e. we will need to add repos at service 
level). BTW, I don't see a way to add more than one versions of a service in an 
extension. I think we need to support that? 

> Support service-specific repo for add-on services
> -
>
> Key: AMBARI-15538
> URL: https://issues.apache.org/jira/browse/AMBARI-15538
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.0, 2.2.0, 2.4.0
>Reporter: Jayush Luniya
>Assignee: Balázs Bence Sári
> Fix For: 2.5.0, 2.4.2
>
> Attachments: AMBARI-15538-custom-repos-patch3-trunk.diff
>
>
> The approach for custom-services to specify their own repo location will be 
> to provide a {{/repos/repoinfo.xml}} inside the stack-version they will be 
> in. This repo file will be loaded by Ambari during startup into the 
> {{/api/v1/stacks/HDP/versions/2.4/repository_versions}} repos. *Service repo 
> files have a restriction that their (repo-name, base-url) locations should be 
> unique and not conflict*. When conflicts do occur, they will not be loaded 
> into the stacks model.
> Now the management-pack will provide such repos/ folder in 
> {{mpacks/custom-services/8.0.0/repos}} which will be linked into the stacks/ 
> folder.
> {{ambari/ambari-server/src/main/resources/stacks/HDP/2.3/services/SERVICE_NAME/repos
>  -> mpacks/custom-services/8.0.0/repos}}



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

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

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-15538:


[~Tim Thorpe]
Latest patch submitted by [~bsari] addresses some of your comments (it handles 
repos defined for a service definition for an extension correctly as well has 
handles stack inheritance correctly). 

Lets say that in an extension we have MYSERVICE/1.0 -> HDP-2.4 and 
MYSERVICE/2.0  -> HDP-2.5. In that case we will need to add different repos for 
MYSERVICE/1.0 and MYSERVICE/2.0 (i.e. we will need to add repos at service 
level). BTW, I don't see a way to add more than one versions of a service in an 
extension. I think we need to support that? 

> Support service-specific repo for add-on services
> -
>
> Key: AMBARI-15538
> URL: https://issues.apache.org/jira/browse/AMBARI-15538
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.0, 2.2.0, 2.4.0
>Reporter: Jayush Luniya
>Assignee: Balázs Bence Sári
> Fix For: 2.5.0, 2.4.2
>
> Attachments: AMBARI-15538-custom-repos-patch3-trunk.diff
>
>
> The approach for custom-services to specify their own repo location will be 
> to provide a {{/repos/repoinfo.xml}} inside the stack-version they will be 
> in. This repo file will be loaded by Ambari during startup into the 
> {{/api/v1/stacks/HDP/versions/2.4/repository_versions}} repos. *Service repo 
> files have a restriction that their (repo-name, base-url) locations should be 
> unique and not conflict*. When conflicts do occur, they will not be loaded 
> into the stacks model.
> Now the management-pack will provide such repos/ folder in 
> {{mpacks/custom-services/8.0.0/repos}} which will be linked into the stacks/ 
> folder.
> {{ambari/ambari-server/src/main/resources/stacks/HDP/2.3/services/SERVICE_NAME/repos
>  -> mpacks/custom-services/8.0.0/repos}}



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

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

[Robert Levas (JIRA)]

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

Robert Levas updated AMBARI-18365:
--
Attachment: AMBARI-18365_trunk_02.patch
AMBARI-18365_branch-2.5_02.patch

> Add Ambari configuration options to support Kerberos token authentication
> -
>
> Key: AMBARI-18365
> URL: https://issues.apache.org/jira/browse/AMBARI-18365
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: authentication, kerberos, security
> Fix For: 2.5.0
>
> Attachments: AMBARI-18365_branch-2.5_01.patch, 
> AMBARI-18365_branch-2.5_02.patch, AMBARI-18365_trunk_01.patch, 
> AMBARI-18365_trunk_02.patch
>
>
> Add the followng Ambari configuration options to support Kerberos token 
> authentication
> * {{authentication.kerberos.enabled}}
> ** Determines whether to use Kerberos (SPNEGO) authentication when connecting 
> Ambari:  {{true}} to enable this feature; {{false}}, otherwise
> * {{authentication.kerberos.spnego.principal}}
> ** The Kerberos principal name to use when verifying user-supplied Kerberos 
> tokens for authentication via SPNEGO
> * {{authentication.kerberos.spnego.keytab.file}}
> ** The Kerberos keytab file to use when verifying user-supplied Kerberos 
> tokens for authentication via SPNEGO
> * {{authentication.kerberos.user.types}}
> ** A comma-delimited (ordered) list of preferred user types to use when 
> finding the Ambari user account for the user-supplied Kerberos identity 
> during authentication via SPNEGO
> * {{authentication.kerberos.auth_to_local.rules}}
> ** The auth-to-local rules set to use when translating a user's principal 
> name to a local user name during authentication via SPNEGO.
> NOTE: These properties are in the {{ambari.properties}} file since this 
> feature may be enabled whether the rest of the cluster has Kerberos enabled 
> or not. 



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

[jira] [Updated] (AMBARI-18382) Enable Kerberos Wizard: Metrics collector fails to start on a cluster with Ranger installed

[Jaimin D Jetly (JIRA)]

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

Jaimin D Jetly updated AMBARI-18382:

Status: Patch Available  (was: Open)

Verified that patch fixes the issue on a cluster.
Verified that all ambari-web unit tests passes:

  29244 tests complete (29 seconds)
  154 tests pending



> Enable Kerberos Wizard: Metrics collector fails to start on a cluster with 
> Ranger installed
> ---
>
> Key: AMBARI-18382
> URL: https://issues.apache.org/jira/browse/AMBARI-18382
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18382.patch
>
>




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

[jira] [Commented] (AMBARI-18281) Expose Disabling of Alert Targets in Web Client

[Zhe (Joe) Wang (JIRA)]

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

Zhe (Joe) Wang commented on AMBARI-18281:
-

Committed to trunk 9595706527b924cb273723fd1906c6a4b5d3d686

> Expose Disabling of Alert Targets in Web Client
> ---
>
> Key: AMBARI-18281
> URL: https://issues.apache.org/jira/browse/AMBARI-18281
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 3.0.0
>
> Attachments: AMBARI-18281.v0.patch, AMBARI-18281.v1.patch, 
> AMBARI-18281.v2.patch
>
>
> Add an option to Enable/ Disable alert notifications in Manage Notifications 
> popup.



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

[jira] [Updated] (AMBARI-17636) Service Configs page: can't see all config versions in dropdown

[Vivek Ratnavel Subramanian (JIRA)]

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

Vivek Ratnavel Subramanian updated AMBARI-17636:

Fix Version/s: (was: trunk)
   2.5.0

> Service Configs page: can't see all config versions in dropdown
> ---
>
> Key: AMBARI-17636
> URL: https://issues.apache.org/jira/browse/AMBARI-17636
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-17636.v0.patch, AMBARI-17636.v3.patch, 
> AMBARI-17636.v4.patch, bugfix.gif
>
>
> * Go to Service->Configs page (that have more than ~ 30 versions)
> * Open versions dropdown
> *Result:*
> Number of visible versions limited by window height.
>  



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

[jira] [Commented] (AMBARI-17636) Service Configs page: can't see all config versions in dropdown

[Vivek Ratnavel Subramanian (JIRA)]

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

Vivek Ratnavel Subramanian commented on AMBARI-17636:
-

Back ported to branch-2.5

> Service Configs page: can't see all config versions in dropdown
> ---
>
> Key: AMBARI-17636
> URL: https://issues.apache.org/jira/browse/AMBARI-17636
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-17636.v0.patch, AMBARI-17636.v3.patch, 
> AMBARI-17636.v4.patch, bugfix.gif
>
>
> * Go to Service->Configs page (that have more than ~ 30 versions)
> * Open versions dropdown
> *Result:*
> Number of visible versions limited by window height.
>  



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

[jira] [Updated] (AMBARI-18382) Enable Kerberos Wizard: Metrics collector fails to start on a cluster with Ranger installed

[Jaimin D Jetly (JIRA)]

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

Jaimin D Jetly updated AMBARI-18382:

Attachment: AMBARI-18382.patch

> Enable Kerberos Wizard: Metrics collector fails to start on a cluster with 
> Ranger installed
> ---
>
> Key: AMBARI-18382
> URL: https://issues.apache.org/jira/browse/AMBARI-18382
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18382.patch
>
>




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

[jira] [Updated] (AMBARI-18382) Enable Kerberos Wizard: Metrics collector fails to start on a cluster with Ranger installed

[Jaimin D Jetly (JIRA)]

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

Jaimin D Jetly updated AMBARI-18382:

Fix Version/s: (was: 2.5.0)
   2.4.2

> Enable Kerberos Wizard: Metrics collector fails to start on a cluster with 
> Ranger installed
> ---
>
> Key: AMBARI-18382
> URL: https://issues.apache.org/jira/browse/AMBARI-18382
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
>Priority: Critical
> Fix For: 2.4.2
>
>




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

[jira] [Updated] (AMBARI-10908) Usability: ability to perform bulk delete host

[Zhe (Joe) Wang (JIRA)]

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

Zhe (Joe) Wang updated AMBARI-10908:

Fix Version/s: (was: trunk)
   2.5.0

> Usability: ability to perform bulk delete host
> --
>
> Key: AMBARI-10908
> URL: https://issues.apache.org/jira/browse/AMBARI-10908
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Jeff Sposetti
>Assignee: Zhe (Joe) Wang
> Fix For: 2.5.0
>
> Attachments: AMBARI-10908.v0.patch, AMBARI-10908.v1.patch
>
>
> On Hosts page, provide ability to delete hosts in bulk.



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

[jira] [Commented] (AMBARI-10908) Usability: ability to perform bulk delete host

[Zhe (Joe) Wang (JIRA)]

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

Zhe (Joe) Wang commented on AMBARI-10908:
-

backported to branch-2.5

> Usability: ability to perform bulk delete host
> --
>
> Key: AMBARI-10908
> URL: https://issues.apache.org/jira/browse/AMBARI-10908
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Jeff Sposetti
>Assignee: Zhe (Joe) Wang
> Fix For: 2.5.0
>
> Attachments: AMBARI-10908.v0.patch, AMBARI-10908.v1.patch
>
>
> On Hosts page, provide ability to delete hosts in bulk.



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

[jira] [Commented] (AMBARI-18377) Retry Installing Kerberos Clients skips hosts were it failed (if lost heartbeat)

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18377:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5661 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5661/])
AMBARI-18377. Retry Installing Kerberos Clients skips hosts were it (hiveww: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0d84a7bf39f9127889f216ce4c882534a5af])
* (edit) ambari-web/app/utils/ajax/ajax.js
* (edit) ambari-web/app/controllers/main/admin/kerberos/step3_controller.js
* (edit) ambari-web/app/views/main/admin/kerberos/step3_view.js
* (edit) ambari-web/app/templates/main/admin/kerberos/step3.hbs
* (edit) 
ambari-web/test/controllers/main/admin/kerberos/step3_controller_test.js


> Retry Installing Kerberos Clients skips hosts were it failed (if lost 
> heartbeat)
> 
>
> Key: AMBARI-18377
> URL: https://issues.apache.org/jira/browse/AMBARI-18377
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18377.patch
>
>
> STR:
> * Installed Ambari 2.4 with HDP 2.5
> * Attempted to Kerberize the cluster and looks like one of the agents lost 
> heartbeat
> * The UI showed a "Retry" button, but it completely ignored the host were it 
> lost the heartbeat on
> This means that Kerberos Client did not install on that host and the Wizard 
> proceeded to the next step. Therefore, starting services on that host failed.
> ambari-server-2.4.0.0-1010.x86_64
> ambari-server --hash
> c32861b10d438dea03227d4bf737600f4a7040c9



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

[jira] [Commented] (AMBARI-18280) Ambari widget graph is not aggregating the data correctly for Total Request Count

[Zhe (Joe) Wang (JIRA)]

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

Zhe (Joe) Wang commented on AMBARI-18280:
-

backported to branch-2.5

> Ambari widget graph is not aggregating the data correctly for Total Request 
> Count
> -
>
> Key: AMBARI-18280
> URL: https://issues.apache.org/jira/browse/AMBARI-18280
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
> Fix For: 2.5.0
>
> Attachments: AMBARI-18280.v0.patch
>
>
> *PROBLEM:* Total Request Count is not growing exponentially 
> *IMPACT:* User is not able to monitor the data correctly.



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

[jira] [Commented] (AMBARI-18377) Retry Installing Kerberos Clients skips hosts were it failed (if lost heartbeat)

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18377:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #26 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/26/])
AMBARI-18377. Retry Installing Kerberos Clients skips hosts were it (hiveww: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=52b268af2c3f9fde097dec9299849ae751490250])
* (edit) ambari-web/app/utils/ajax/ajax.js
* (edit) ambari-web/app/templates/main/admin/kerberos/step3.hbs
* (edit) 
ambari-web/test/controllers/main/admin/kerberos/step3_controller_test.js
* (edit) ambari-web/app/views/main/admin/kerberos/step3_view.js
* (edit) ambari-web/app/controllers/main/admin/kerberos/step3_controller.js


> Retry Installing Kerberos Clients skips hosts were it failed (if lost 
> heartbeat)
> 
>
> Key: AMBARI-18377
> URL: https://issues.apache.org/jira/browse/AMBARI-18377
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18377.patch
>
>
> STR:
> * Installed Ambari 2.4 with HDP 2.5
> * Attempted to Kerberize the cluster and looks like one of the agents lost 
> heartbeat
> * The UI showed a "Retry" button, but it completely ignored the host were it 
> lost the heartbeat on
> This means that Kerberos Client did not install on that host and the Wizard 
> proceeded to the next step. Therefore, starting services on that host failed.
> ambari-server-2.4.0.0-1010.x86_64
> ambari-server --hash
> c32861b10d438dea03227d4bf737600f4a7040c9



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

[jira] [Resolved] (AMBARI-17285) Custom service repos in repoinfo.xml got overwritten by public VDFs

[Jayush Luniya (JIRA)]

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

Jayush Luniya resolved AMBARI-17285.

Resolution: Duplicate

AMBARI-15538 should address this issue.

> Custom service repos in repoinfo.xml got overwritten by public VDFs
> ---
>
> Key: AMBARI-17285
> URL: https://issues.apache.org/jira/browse/AMBARI-17285
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Alexander Denissov
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.4.2
>
>
> Ambari 2.4 introduced Version Definition Files that break the functionality 
> of adding a custom service repo, since custom services do not have an entry 
> in the public VDF.
> In the case of HAWQ, the plugin is installed on Ambari host and it adds the 
> new repo information to the repoinfo.xml of all available stacks on the file 
> system. Once Ambari cluster creation wizard queries the latest repo info from 
> the public URLs, it will get the info for all stack repos, but not the custom 
> ones. 
> So, the logic should be:
> 1. Use default repoinfo (from file system) as the base
> 2. Query public VDF, if available
> 3. For each entry in public VDF overwrite values in the default repoinfo
> 4. Entries in default repoinfo that do not have corresponding entries in VDF 
> should stay intact
> This way custom services can be added via file edit and the latest 
> information can still be retrieved and applied for the standard stack.



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

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

[Nahappan Somasundaram (JIRA)]

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

Nahappan Somasundaram updated AMBARI-18332:
---
Attachment: rb51851.patch

> Blueprints: API should make available "setting" property from blueprint
> ---
>
> Key: AMBARI-18332
> URL: https://issues.apache.org/jira/browse/AMBARI-18332
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb51851.patch
>
>
> The following APIs do not retrieve *setting* section from the blueprint that 
> was used during deployment:
> {code}
> http://:/api/v1/blueprints/ 
> {code}



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

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

[Nahappan Somasundaram (JIRA)]

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

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

> Blueprints: API should make available "setting" property from blueprint
> ---
>
> Key: AMBARI-18332
> URL: https://issues.apache.org/jira/browse/AMBARI-18332
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb51851.patch
>
>
> The following APIs do not retrieve *setting* section from the blueprint that 
> was used during deployment:
> {code}
> http://:/api/v1/blueprints/ 
> {code}



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

[jira] [Created] (AMBARI-18381) Kafka alerts fail if more than one listener is configured

[Carson Gaspar (JIRA)]

Carson Gaspar created AMBARI-18381:
--

 Summary: Kafka alerts fail if more than one listener is configured
 Key: AMBARI-18381
 URL: https://issues.apache.org/jira/browse/AMBARI-18381
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.2.2
Reporter: Carson Gaspar
Priority: Minor


If more than one kafka listener is configured (e.g. 
PLAINTEXTSASL://localhost:6667, PLAINTEXT://127.0.0.1:6668), the alert 
definition configures a PORT test with the whole string, which appears to get 
parsed with the first hostname and the last port. This causes the test to fail. 
If there's a way to modify {{kafka-broker/listeners}} so that it splits on the 
first comma, or some other workaround, I can't figure it out.



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

[jira] [Commented] (AMBARI-17957) Remove Falcon UI Quick Link

[Hudson (JIRA)]

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

Hudson commented on AMBARI-17957:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5660 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5660/])
AMBARI-17957. Remove Falcon UI Quick Link. Additional patch (hiveww: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3d99106ac3b75508d4b645241ab9d32657adf0ac])
* (edit) 
ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/metainfo.xml


> Remove Falcon UI Quick Link
> ---
>
> Key: AMBARI-17957
> URL: https://issues.apache.org/jira/browse/AMBARI-17957
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.5.0
>
> Attachments: AMBARI-17957.patch, AMBARI-17957.patch
>
>
> With Erie a new Falcon View option is available, therefore, the Quick Link 
> from the Falcon Ambari page should be removed. Falcon View utilizes Ambari 
> signon and is the only access point that should be available for the UI via 
> Ambari.



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

[jira] [Commented] (AMBARI-17957) Remove Falcon UI Quick Link

[Hudson (JIRA)]

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

Hudson commented on AMBARI-17957:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #25 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/25/])
AMBARI-17957. Remove Falcon UI Quick Link (alexantonenko) (hiveww: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=adfb708236a233996cb65f8463eb86db51365f74])
* (delete) 
ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/quicklinks/quicklinks.json
AMBARI-17957. Remove Falcon UI Quick Link. Additional patch (hiveww: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=fbea1f09bd55cd3750096e3572b46fb9e4b64738])
* (edit) 
ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/metainfo.xml


> Remove Falcon UI Quick Link
> ---
>
> Key: AMBARI-17957
> URL: https://issues.apache.org/jira/browse/AMBARI-17957
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.5.0
>
> Attachments: AMBARI-17957.patch, AMBARI-17957.patch
>
>
> With Erie a new Falcon View option is available, therefore, the Quick Link 
> from the Falcon Ambari page should be removed. Falcon View utilizes Ambari 
> signon and is the only access point that should be available for the UI via 
> Ambari.



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

[jira] [Commented] (AMBARI-18284) Ambari PigView stores the script in HDFS in non UTF-8 format

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18284:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #25 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/25/])
AMBARI-18284. Ambari PigView stores the script in HDFS in non UTF-8 
(pallav.kul: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=fa6e1792f051500bef20b367bcb9614aa2f8e3c8])
* (edit) 
contrib/views/pig/src/main/java/org/apache/ambari/view/pig/resources/files/FileService.java


> Ambari PigView stores the script in HDFS in non UTF-8 format
> 
>
> Key: AMBARI-18284
> URL: https://issues.apache.org/jira/browse/AMBARI-18284
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: trunk
> Environment: All
>Reporter: JaySenSharma
>Assignee: JaySenSharma
>  Labels: patch-available
> Fix For: 2.5.0
>
> Attachments: AMBARI-18284.patch
>
>
> - In Ambari PigView if we have a script like following containing some 
> special characters like 'á'
> {code}
> STOCK_A = LOAD '/user/admin/dummy.csv' USING PigStorage('á'); 
> DESCRIBE STOCK_A;
> {code}
> Then after executing the script we see that in the HDFS it is stored as 
> following:
> {code}
> hdfs dfs -cat /user/admin/pig/scripts/testlatin-2016-08-30_12-15.pig
> STOCK_A = LOAD '/user/admin/dummy.csv' USING PigStorage('?'); 
> DESCRIBE STOCK_A;
> {code}
> *Notice:*  the 'á' is converted to '?'



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

[jira] [Commented] (AMBARI-18338) Microsoft-R client should work in a secured cluster

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18338:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12828287/AMBARI-18338-mpack-kerberos_trunk_v5.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 
contrib/management-packs/microsoft-r_mpack.

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

This message is automatically generated.

> Microsoft-R client should work in a secured cluster
> ---
>
> Key: AMBARI-18338
> URL: https://issues.apache.org/jira/browse/AMBARI-18338
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-trunk
>Affects Versions: 2.4.0
>Reporter: Balázs Bence Sári
>Assignee: Balázs Bence Sári
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18338-mpack-kerberos_trunk_v5.patch
>
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> Microsoft-R client accesses HDFS and YARN to run R commands. We need to 
> determine if any changes are necessary for this client to work in a 
> secured/kerberized environment.



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

[jira] [Commented] (AMBARI-18379) Cover host views with unit tests

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18379:


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

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

This message is automatically generated.

> Cover host views with unit tests
> 
>
> Key: AMBARI-18379
> URL: https://issues.apache.org/jira/browse/AMBARI-18379
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-18379.patch
>
>
> Cover following files:
> * /ambari-web/app/views/main/host/host_alerts_view.js
> * /ambari-web/app/views/main/host/summary.js
> * /ambari-web/app/views/main/host/stack_versions_view.js
> * /ambari-web/app/views/main/host/logs_view.js
> * /ambari-web/app/views/main/host/hosts_table_menu_view.js
> * /ambari-web/app/views/main/host/log_metrics.js
> * /ambari-web/app/views/main/host/combo_search_box.js



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

[jira] [Commented] (AMBARI-18380) For rolling upgrade of Kafka 0.10.0.1 we need to configs for backward compatibility

[Sriharsha Chintalapani (JIRA)]

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

Sriharsha Chintalapani commented on AMBARI-18380:
-

cc [~mahadev] [~sumitmohanty]

> For rolling upgrade of Kafka 0.10.0.1 we need to configs for backward 
> compatibility 
> 
>
> Key: AMBARI-18380
> URL: https://issues.apache.org/jira/browse/AMBARI-18380
> Project: Ambari
>  Issue Type: Bug
>Reporter: Sriharsha Chintalapani
>Assignee: Sriharsha Chintalapani
>Priority: Blocker
>
> following properties need to be set
> {code}
> inter.broker.protocol.version=0.9.0.0
> log.message.format.version=0.9.0.0
> {code}
> after upgrade is done we should delte the inter.broker.protocol.version.
> Users should remove log.message.format.version once they update their clients.



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

[jira] [Created] (AMBARI-18380) For rolling upgrade of Kafka 0.10.0.1 we need to configs for backward compatibility

[Sriharsha Chintalapani (JIRA)]

Sriharsha Chintalapani created AMBARI-18380:
---

 Summary: For rolling upgrade of Kafka 0.10.0.1 we need to configs 
for backward compatibility 
 Key: AMBARI-18380
 URL: https://issues.apache.org/jira/browse/AMBARI-18380
 Project: Ambari
  Issue Type: Bug
Reporter: Sriharsha Chintalapani
Assignee: Sriharsha Chintalapani
Priority: Blocker


following properties need to be set
{code}
inter.broker.protocol.version=0.9.0.0
log.message.format.version=0.9.0.0
{code}
after upgrade is done we should delte the inter.broker.protocol.version.
Users should remove log.message.format.version once they update their clients.



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

[jira] [Updated] (AMBARI-17324) kafka should set zookeeper.set.acl to true when kerberos enabled

[Sriharsha Chintalapani (JIRA)]

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

Sriharsha Chintalapani updated AMBARI-17324:

Fix Version/s: (was: 2.4.1)
   2.4.0

> kafka should set zookeeper.set.acl to true when kerberos enabled
> 
>
> Key: AMBARI-17324
> URL: https://issues.apache.org/jira/browse/AMBARI-17324
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.2.0
>Reporter: Sriharsha Chintalapani
>Assignee: Sriharsha Chintalapani
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17324.patch
>
>




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

[jira] [Updated] (AMBARI-18379) Cover host views with unit tests

[Andrii Tkach (JIRA)]

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

Andrii Tkach updated AMBARI-18379:
--
Status: Patch Available  (was: Open)

> Cover host views with unit tests
> 
>
> Key: AMBARI-18379
> URL: https://issues.apache.org/jira/browse/AMBARI-18379
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-18379.patch
>
>
> Cover following files:
> * /ambari-web/app/views/main/host/host_alerts_view.js
> * /ambari-web/app/views/main/host/summary.js
> * /ambari-web/app/views/main/host/stack_versions_view.js
> * /ambari-web/app/views/main/host/logs_view.js
> * /ambari-web/app/views/main/host/hosts_table_menu_view.js
> * /ambari-web/app/views/main/host/log_metrics.js
> * /ambari-web/app/views/main/host/combo_search_box.js



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

[jira] [Commented] (AMBARI-18379) Cover host views with unit tests

[Andrii Tkach (JIRA)]

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

Andrii Tkach commented on AMBARI-18379:
---

 30277 tests complete (29 seconds)
  151 tests pending

> Cover host views with unit tests
> 
>
> Key: AMBARI-18379
> URL: https://issues.apache.org/jira/browse/AMBARI-18379
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-18379.patch
>
>
> Cover following files:
> * /ambari-web/app/views/main/host/host_alerts_view.js
> * /ambari-web/app/views/main/host/summary.js
> * /ambari-web/app/views/main/host/stack_versions_view.js
> * /ambari-web/app/views/main/host/logs_view.js
> * /ambari-web/app/views/main/host/hosts_table_menu_view.js
> * /ambari-web/app/views/main/host/log_metrics.js
> * /ambari-web/app/views/main/host/combo_search_box.js



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

[jira] [Updated] (AMBARI-18379) Cover host views with unit tests

[Andrii Tkach (JIRA)]

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

Andrii Tkach updated AMBARI-18379:
--
Attachment: AMBARI-18379.patch

> Cover host views with unit tests
> 
>
> Key: AMBARI-18379
> URL: https://issues.apache.org/jira/browse/AMBARI-18379
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-18379.patch
>
>
> Cover following files:
> * /ambari-web/app/views/main/host/host_alerts_view.js
> * /ambari-web/app/views/main/host/summary.js
> * /ambari-web/app/views/main/host/stack_versions_view.js
> * /ambari-web/app/views/main/host/logs_view.js
> * /ambari-web/app/views/main/host/hosts_table_menu_view.js
> * /ambari-web/app/views/main/host/log_metrics.js
> * /ambari-web/app/views/main/host/combo_search_box.js



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

[jira] [Created] (AMBARI-18379) Cover host views with unit tests

[Andrii Tkach (JIRA)]

Andrii Tkach created AMBARI-18379:
-

 Summary: Cover host views with unit tests
 Key: AMBARI-18379
 URL: https://issues.apache.org/jira/browse/AMBARI-18379
 Project: Ambari
  Issue Type: Task
  Components: ambari-web
Affects Versions: 2.4.0
Reporter: Andrii Tkach
Assignee: Andrii Tkach
 Fix For: 3.0.0


Cover following files:
* /ambari-web/app/views/main/host/host_alerts_view.js
* /ambari-web/app/views/main/host/summary.js
* /ambari-web/app/views/main/host/stack_versions_view.js
* /ambari-web/app/views/main/host/logs_view.js
* /ambari-web/app/views/main/host/hosts_table_menu_view.js
* /ambari-web/app/views/main/host/log_metrics.js
* /ambari-web/app/views/main/host/combo_search_box.js



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

[jira] [Updated] (AMBARI-18377) Retry Installing Kerberos Clients skips hosts were it failed (if lost heartbeat)

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander updated AMBARI-18377:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

committed to trunk and branch 2.5

> Retry Installing Kerberos Clients skips hosts were it failed (if lost 
> heartbeat)
> 
>
> Key: AMBARI-18377
> URL: https://issues.apache.org/jira/browse/AMBARI-18377
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18377.patch
>
>
> STR:
> * Installed Ambari 2.4 with HDP 2.5
> * Attempted to Kerberize the cluster and looks like one of the agents lost 
> heartbeat
> * The UI showed a "Retry" button, but it completely ignored the host were it 
> lost the heartbeat on
> This means that Kerberos Client did not install on that host and the Wizard 
> proceeded to the next step. Therefore, starting services on that host failed.
> ambari-server-2.4.0.0-1010.x86_64
> ambari-server --hash
> c32861b10d438dea03227d4bf737600f4a7040c9



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

[jira] [Updated] (AMBARI-18097) Cover configurations mixins with unit tests

[Andrii Tkach (JIRA)]

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

Andrii Tkach updated AMBARI-18097:
--
Fix Version/s: (was: trunk)
   3.0.0

> Cover configurations mixins with unit tests
> ---
>
> Key: AMBARI-18097
> URL: https://issues.apache.org/jira/browse/AMBARI-18097
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-18097.patch
>
>
> Cover following files:
> * 
> /ambari-web/app/mixins/common/configs/config_with_override_recommendation_parser.js
> * /ambari-web/app/mixins/common/configs/configs_comparator.js
> * /ambari-web/app/mixins/common/configs/configs_loader.js
> * /ambari-web/app/mixins/common/configs/configs_saver.js
> * /ambari-web/app/mixins/common/configs/enhanced_configs.js



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

[jira] [Updated] (AMBARI-18159) Cover widget views with unit tests

[Andrii Tkach (JIRA)]

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

Andrii Tkach updated AMBARI-18159:
--
Fix Version/s: (was: trunk)
   3.0.0

> Cover widget views with unit tests
> --
>
> Key: AMBARI-18159
> URL: https://issues.apache.org/jira/browse/AMBARI-18159
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-18159.patch
>
>
> Cover following files:
> * /ambari-web/app/views/common/widget/gauge_widget_view.js
> * /ambari-web/app/views/common/widget/graph_widget_view.js
> * /ambari-web/app/views/common/widget/heatmap_widget_view.js
> * /ambari-web/app/views/common/widget/number_widget_view.js
> * /ambari-web/app/views/common/widget/template_widget_view.js



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

[jira] [Updated] (AMBARI-17881) Cover configurations theme with unit tests

[Andrii Tkach (JIRA)]

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

Andrii Tkach updated AMBARI-17881:
--
Fix Version/s: (was: trunk)
   3.0.0

> Cover configurations theme with unit tests
> --
>
> Key: AMBARI-17881
> URL: https://issues.apache.org/jira/browse/AMBARI-17881
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-17881.patch
>
>
> Cover following files:
> * /ambari-web/app/utils/configs/theme/theme.js



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

[jira] [Updated] (AMBARI-17813) Cover configurations mixin with unit tests

[Andrii Tkach (JIRA)]

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

Andrii Tkach updated AMBARI-17813:
--
Fix Version/s: (was: trunk)
   3.0.0

> Cover configurations mixin with unit tests
> --
>
> Key: AMBARI-17813
> URL: https://issues.apache.org/jira/browse/AMBARI-17813
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-17813.patch
>
>
> Cover following files:
> * /ambari-web/app/mixins/main/service/configs/component_actions_by_configs.js
> * /ambari-web/app/mixins/main/service/configs/config_overridable.js
> * /ambari-web/app/mixins/main/service/configs/widget_popover_support.js



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

[jira] [Updated] (AMBARI-17525) Refactor config: mixins should use the same binding property

[Andrii Tkach (JIRA)]

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

Andrii Tkach updated AMBARI-17525:
--
Fix Version/s: (was: 2.5.0)
   3.0.0

> Refactor config: mixins should use the same binding property
> 
>
> Key: AMBARI-17525
> URL: https://issues.apache.org/jira/browse/AMBARI-17525
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-17525.patch
>
>
> App.PlainConfigTextField should use only "serviceConfig" binding instead of 
> "config".



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

[jira] [Updated] (AMBARI-17525) Refactor config: mixins should use the same binding property

[Andrii Tkach (JIRA)]

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

Andrii Tkach updated AMBARI-17525:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Refactor config: mixins should use the same binding property
> 
>
> Key: AMBARI-17525
> URL: https://issues.apache.org/jira/browse/AMBARI-17525
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-17525.patch
>
>
> App.PlainConfigTextField should use only "serviceConfig" binding instead of 
> "config".



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

[jira] [Commented] (AMBARI-18247) Capacity scheduler's dependent config suggestion is incomprehensible

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18247:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #24 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/24/])
AMBARI-18247 Capacity scheduler's dependent config suggestion is (akovalenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=32af6a811bda73944fc5be6a93d8b4468df4a85c])
* (edit) ambari-web/app/mixins/common/configs/config_recommendations.js
* (edit) ambari-web/app/templates/common/modal_popups/dependent_configs_list.hbs
* (edit) ambari-web/test/mixins/common/configs/config_recommendations_test.js
* (edit) ambari-web/app/utils/config.js
* (edit) ambari-web/config.coffee
* (edit) ambari-web/karma.conf.js
* (add) ambari-web/vendor/styles/diffview.css
* (add) ambari-web/vendor/scripts/difflib.js
* (add) ambari-web/vendor/scripts/diffview.js


> Capacity scheduler's dependent config suggestion is incomprehensible
> 
>
> Key: AMBARI-18247
> URL: https://issues.apache.org/jira/browse/AMBARI-18247
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
> Fix For: 2.5.0
>
> Attachments: AMBARI-18247.v0.patch
>
>
> Dependent configs dialog shows recommended values for capacity scheduler 
> which is incomprehensible to read. It will be good to breakdown the specific 
> changes into separate rows.



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

[jira] [Commented] (AMBARI-18295) Dependent Configurations popup isn't changed after the subsequent property changes

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18295:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #24 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/24/])
AMBARI-18295. Dependent Configurations popup isn't changed after the 
(akovalenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=abfc3d2fb15e0084cf4caa0b3ec305e352039482])
* (edit) ambari-web/test/mixins/common/configs/config_recommendations_test.js
* (edit) ambari-web/app/mixins/common/configs/config_recommendations.js
* (edit) ambari-web/app/templates/common/modal_popups/dependent_configs_list.hbs
* (edit) ambari-web/app/views.js
* (add) ambari-web/app/views/common/configs/config_diff_view.js


> Dependent Configurations popup isn't changed after the subsequent property 
> changes
> --
>
> Key: AMBARI-18295
> URL: https://issues.apache.org/jira/browse/AMBARI-18295
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18295.patch
>
>
> *STR:*
> 1) Deploy a cluster
> 2) Go to YARN -> Configs
> 3) Change 'Minimum Container Size (Memory)'
> 4) Click 'Show Details' to open the 'Dependent Configurations' popup.
> 5) Close the popup and change 'Minimum Container Size (Memory)' again
> 6) Open 'Dependent Configurations' popup again.
> *Result:*
> The 'Recommended values' displayed in the popup are not changed and are stale 
> (it's recommended values for the first property change, not for the second)



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

[jira] [Commented] (AMBARI-18254) DB consistency check should tolerate services with no configuration

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18254:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #24 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/24/])
AMBARI-18254. DB consistency check should tolerate services with no (stoader: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7da8886f770a63ea09905f39650b0c436c75c07d])
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelperTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelper.java


> DB consistency check should tolerate services with no configuration
> ---
>
> Key: AMBARI-18254
> URL: https://issues.apache.org/jira/browse/AMBARI-18254
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Balázs Bence Sári
>Assignee: Balázs Bence Sári
> Fix For: trunk, 2.5.0
>
> Attachments: BUG63433-DB-checker_trunk_v1.patch
>
>
> The Microsoft R service does not have any user settable configuration. This 
> will trigger a DB consistency check failure on Ambari server restart.



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

[jira] [Commented] (AMBARI-18319) Next button on Customize Services page is in invalid state after canceling move to next page

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18319:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #24 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/24/])
AMBARI-18319. Next button on Customize Services page is in invalid state 
(hiveww: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0b51d045cbf4cfdf84b4c03a94f076add8cfdfec])
* (edit) ambari-web/app/controllers/wizard/step7_controller.js


> Next button on Customize Services page is in invalid state after canceling 
> move to next page
> 
>
> Key: AMBARI-18319
> URL: https://issues.apache.org/jira/browse/AMBARI-18319
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18319.patch
>
>
> Steps:
> # Go to Customize Services page.
> # Select any custom DB fot Hive service and click Next.
> # Was appeared "Database Connectivity Warning", cancel moving to next step.
> Result: Customize Services page still opened, but Next button has loading 
> spinner and is inactive. After page reload button works fine.



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