[jira] [Commented] (AMBARI-20782) Add config changes from AMBARI-20537 to hive component upgrade path
[ https://issues.apache.org/jira/browse/AMBARI-20782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973881#comment-15973881 ] Hudson commented on AMBARI-20782: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1413 (See [https://builds.apache.org/job/Ambari-branch-2.5/1413/]) AMBARI-20782. Add config changes from AMBARI-20537 to hive component (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8be765f1d08b8b28c5170a11a97ea7da4ec67671]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml > Add config changes from AMBARI-20537 to hive component upgrade path > --- > > Key: AMBARI-20782 > URL: https://issues.apache.org/jira/browse/AMBARI-20782 > Project: Ambari > Issue Type: Bug > Components: HiveServer2, Metastore, and Client Heap Sizes to Smart > Configs >Affects Versions: 2.5.0 >Reporter: Prasanth Jayachandran >Assignee: Prasanth Jayachandran > Fix For: trunk, 2.5.1 > > Attachments: AMBARI-20782.1.patch, AMBARI-20782.2.patch > > > AMBARI-20537 introduced 2 changes to LLAP configs. Add them to hive component > upgrade path. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20537) Some config changes for LLAP to avoid daemon getting killed
[
https://issues.apache.org/jira/browse/AMBARI-20537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973882#comment-15973882
]
Hudson commented on AMBARI-20537:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1413 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1413/])
AMBARI-20782. Add config changes from AMBARI-20537 to hive component
(sshridhar:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8be765f1d08b8b28c5170a11a97ea7da4ec67671])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml
> Some config changes for LLAP to avoid daemon getting killed
> ---
>
> Key: AMBARI-20537
> URL: https://issues.apache.org/jira/browse/AMBARI-20537
> Project: Ambari
> Issue Type: Bug
> Components: HiveServer2, Metastore, and Client Heap Sizes to Smart
> Configs
>Affects Versions: 2.5.0
>Reporter: Prasanth Jayachandran
>Assignee: Prasanth Jayachandran
> Fix For: 2.5.1
>
> Attachments: AMBARI-20537.2.patch, AMBARI-20537.patch
>
>
> Following changes are required to improve the stability of LLAP daemons
> {code}
> tez.runtime.shuffle.parallel.copies=8
> Add "-Xss512k" to LLAP app java opts
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20537) Some config changes for LLAP to avoid daemon getting killed
[
https://issues.apache.org/jira/browse/AMBARI-20537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973879#comment-15973879
]
Hudson commented on AMBARI-20537:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7313 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7313/])
AMBARI-20782. Add config changes from AMBARI-20537 to hive component
(sshridhar:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f516b6c5ad384ceb52181bee6b1553089563182e])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml
> Some config changes for LLAP to avoid daemon getting killed
> ---
>
> Key: AMBARI-20537
> URL: https://issues.apache.org/jira/browse/AMBARI-20537
> Project: Ambari
> Issue Type: Bug
> Components: HiveServer2, Metastore, and Client Heap Sizes to Smart
> Configs
>Affects Versions: 2.5.0
>Reporter: Prasanth Jayachandran
>Assignee: Prasanth Jayachandran
> Fix For: 2.5.1
>
> Attachments: AMBARI-20537.2.patch, AMBARI-20537.patch
>
>
> Following changes are required to improve the stability of LLAP daemons
> {code}
> tez.runtime.shuffle.parallel.copies=8
> Add "-Xss512k" to LLAP app java opts
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20782) Add config changes from AMBARI-20537 to hive component upgrade path
[ https://issues.apache.org/jira/browse/AMBARI-20782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973878#comment-15973878 ] Hudson commented on AMBARI-20782: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7313 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7313/]) AMBARI-20782. Add config changes from AMBARI-20537 to hive component (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f516b6c5ad384ceb52181bee6b1553089563182e]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml > Add config changes from AMBARI-20537 to hive component upgrade path > --- > > Key: AMBARI-20782 > URL: https://issues.apache.org/jira/browse/AMBARI-20782 > Project: Ambari > Issue Type: Bug > Components: HiveServer2, Metastore, and Client Heap Sizes to Smart > Configs >Affects Versions: 2.5.0 >Reporter: Prasanth Jayachandran >Assignee: Prasanth Jayachandran > Fix For: trunk, 2.5.1 > > Attachments: AMBARI-20782.1.patch, AMBARI-20782.2.patch > > > AMBARI-20537 introduced 2 changes to LLAP configs. Add them to hive component > upgrade path. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20784) Able to hide the "Why public repo not selected" when no stacks have repoinfo.xml with the "latest" section
[
https://issues.apache.org/jira/browse/AMBARI-20784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973855#comment-15973855
]
Hadoop QA commented on AMBARI-20784:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12863881/AMBARI-20784.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/11415//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11415//console
This message is automatically generated.
> Able to hide the "Why public repo not selected" when no stacks have
> repoinfo.xml with the "latest" section
> --
>
> Key: AMBARI-20784
> URL: https://issues.apache.org/jira/browse/AMBARI-20784
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-20784.patch
>
>
> Able to hide the "Why public repo not selected" when no stacks have
> repoinfo.xml with the "latest" section. There is no point of display the
> error based on the stackDefault checking when no stacks even offer the
> "latest" section in their repoinfo.xml.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20782) Add config changes from AMBARI-20537 to hive component upgrade path
[
https://issues.apache.org/jira/browse/AMBARI-20782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973825#comment-15973825
]
Swapan Shridhar commented on AMBARI-20782:
--
commit
trunk:
{code}
commit f516b6c5ad384ceb52181bee6b1553089563182e
Author: Swapan Shridhar
Date: Tue Apr 18 18:01:35 2017 -0700
AMBARI-20782. Add config changes from AMBARI-20537 to hive component
upgrade path. (Swapan Shridhar via Prasanth Jayachandran).
{code}
branch-2.5:
{code}
commit 8be765f1d08b8b28c5170a11a97ea7da4ec67671
Author: Swapan Shridhar
Date: Tue Apr 18 17:58:27 2017 -0700
AMBARI-20782. Add config changes from AMBARI-20537 to hive component
upgrade path. (Swapan Shridhar via Prasanth Jayachandran).
{code}
> Add config changes from AMBARI-20537 to hive component upgrade path
> ---
>
> Key: AMBARI-20782
> URL: https://issues.apache.org/jira/browse/AMBARI-20782
> Project: Ambari
> Issue Type: Bug
> Components: HiveServer2, Metastore, and Client Heap Sizes to Smart
> Configs
>Affects Versions: 2.5.0
>Reporter: Prasanth Jayachandran
>Assignee: Prasanth Jayachandran
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-20782.1.patch, AMBARI-20782.2.patch
>
>
> AMBARI-20537 introduced 2 changes to LLAP configs. Add them to hive component
> upgrade path.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20782) Add config changes from AMBARI-20537 to hive component upgrade path
[ https://issues.apache.org/jira/browse/AMBARI-20782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20782: - Resolution: Fixed Fix Version/s: trunk Status: Resolved (was: Patch Available) > Add config changes from AMBARI-20537 to hive component upgrade path > --- > > Key: AMBARI-20782 > URL: https://issues.apache.org/jira/browse/AMBARI-20782 > Project: Ambari > Issue Type: Bug > Components: HiveServer2, Metastore, and Client Heap Sizes to Smart > Configs >Affects Versions: 2.5.0 >Reporter: Prasanth Jayachandran >Assignee: Prasanth Jayachandran > Fix For: trunk, 2.5.1 > > Attachments: AMBARI-20782.1.patch, AMBARI-20782.2.patch > > > AMBARI-20537 introduced 2 changes to LLAP configs. Add them to hive component > upgrade path. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20782) Add config changes from AMBARI-20537 to hive component upgrade path
[ https://issues.apache.org/jira/browse/AMBARI-20782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanth Jayachandran updated AMBARI-20782: --- Attachment: AMBARI-20782.2.patch Fixed summary in .2 patch > Add config changes from AMBARI-20537 to hive component upgrade path > --- > > Key: AMBARI-20782 > URL: https://issues.apache.org/jira/browse/AMBARI-20782 > Project: Ambari > Issue Type: Bug > Components: HiveServer2, Metastore, and Client Heap Sizes to Smart > Configs >Affects Versions: 2.5.0 >Reporter: Prasanth Jayachandran >Assignee: Prasanth Jayachandran > Fix For: 2.5.1 > > Attachments: AMBARI-20782.1.patch, AMBARI-20782.2.patch > > > AMBARI-20537 introduced 2 changes to LLAP configs. Add them to hive component > upgrade path. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20782) Add config changes from AMBARI-20537 to hive component upgrade path
[
https://issues.apache.org/jira/browse/AMBARI-20782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973729#comment-15973729
]
Sumit Mohanty commented on AMBARI-20782:
One nit:
{code}
+
+
+ Updating the Hive Log4J2 properties to include
parameterizations
+
+
{code}
[~prasanth_j]/[~sseth], the summary above seems to be incorrect. Can we fix
that too?
> Add config changes from AMBARI-20537 to hive component upgrade path
> ---
>
> Key: AMBARI-20782
> URL: https://issues.apache.org/jira/browse/AMBARI-20782
> Project: Ambari
> Issue Type: Bug
> Components: HiveServer2, Metastore, and Client Heap Sizes to Smart
> Configs
>Affects Versions: 2.5.0
>Reporter: Prasanth Jayachandran
>Assignee: Prasanth Jayachandran
> Fix For: 2.5.1
>
> Attachments: AMBARI-20782.1.patch
>
>
> AMBARI-20537 introduced 2 changes to LLAP configs. Add them to hive component
> upgrade path.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20786) Installation fails when trying to install Hive with Mysql as metastore db
Sriharsha Chintalapani created AMBARI-20786: --- Summary: Installation fails when trying to install Hive with Mysql as metastore db Key: AMBARI-20786 URL: https://issues.apache.org/jira/browse/AMBARI-20786 Project: Ambari Issue Type: Bug Reporter: Sriharsha Chintalapani Assignee: Madhuvanthi Radhakrishnan Priority: Critical When I tried select Hive and configured meta store to use mysql running into below exception = function(command, **kwargs) File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 102, in checked_call tries=tries, try_sleep=try_sleep, timeout_kill_strategy=timeout_kill_strategy) File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 150, in _call_wrapper result = _call(command, **kwargs_copy) File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 303, in _call raise ExecutionFailed(err_msg, code, out, err) resource_management.core.exceptions.ExecutionFailed: Execution of '/usr/bin/yum -d 0 -e 0 -y install 'hive_package None is not installed'' returned 1. Error: Nothing to do -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20782) Add config changes from AMBARI-20537 to hive component upgrade path
[ https://issues.apache.org/jira/browse/AMBARI-20782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20782: --- Fix Version/s: 2.5.1 > Add config changes from AMBARI-20537 to hive component upgrade path > --- > > Key: AMBARI-20782 > URL: https://issues.apache.org/jira/browse/AMBARI-20782 > Project: Ambari > Issue Type: Bug > Components: HiveServer2, Metastore, and Client Heap Sizes to Smart > Configs >Affects Versions: 2.5.0 >Reporter: Prasanth Jayachandran >Assignee: Prasanth Jayachandran > Fix For: 2.5.1 > > Attachments: AMBARI-20782.1.patch > > > AMBARI-20537 introduced 2 changes to LLAP configs. Add them to hive component > upgrade path. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20782) Add config changes from AMBARI-20537 to hive component upgrade path
[ https://issues.apache.org/jira/browse/AMBARI-20782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973719#comment-15973719 ] Swapan Shridhar commented on AMBARI-20782: -- +1 for [^AMBARI-20782.1.patch] cc [~sumitmohanty] | [~prasanth_j] > Add config changes from AMBARI-20537 to hive component upgrade path > --- > > Key: AMBARI-20782 > URL: https://issues.apache.org/jira/browse/AMBARI-20782 > Project: Ambari > Issue Type: Bug > Components: HiveServer2, Metastore, and Client Heap Sizes to Smart > Configs >Affects Versions: 2.5.0 >Reporter: Prasanth Jayachandran >Assignee: Prasanth Jayachandran > Attachments: AMBARI-20782.1.patch > > > AMBARI-20537 introduced 2 changes to LLAP configs. Add them to hive component > upgrade path. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20782) Add config changes from AMBARI-20537 to hive component upgrade path
[ https://issues.apache.org/jira/browse/AMBARI-20782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973705#comment-15973705 ] Swapan Shridhar commented on AMBARI-20782: -- [~prasanth_j] Got it. confirmed. > Add config changes from AMBARI-20537 to hive component upgrade path > --- > > Key: AMBARI-20782 > URL: https://issues.apache.org/jira/browse/AMBARI-20782 > Project: Ambari > Issue Type: Bug > Components: HiveServer2, Metastore, and Client Heap Sizes to Smart > Configs >Affects Versions: 2.5.0 >Reporter: Prasanth Jayachandran >Assignee: Prasanth Jayachandran > Attachments: AMBARI-20782.1.patch > > > AMBARI-20537 introduced 2 changes to LLAP configs. Add them to hive component > upgrade path. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20782) Add config changes from AMBARI-20537 to hive component upgrade path
[ https://issues.apache.org/jira/browse/AMBARI-20782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973703#comment-15973703 ] Prasanth Jayachandran commented on AMBARI-20782: [~swapanshridhar] it is not removed. It is moved to correct section. Earlier it was in HDFS section. Now it got moved to HIVE section. > Add config changes from AMBARI-20537 to hive component upgrade path > --- > > Key: AMBARI-20782 > URL: https://issues.apache.org/jira/browse/AMBARI-20782 > Project: Ambari > Issue Type: Bug > Components: HiveServer2, Metastore, and Client Heap Sizes to Smart > Configs >Affects Versions: 2.5.0 >Reporter: Prasanth Jayachandran >Assignee: Prasanth Jayachandran > Attachments: AMBARI-20782.1.patch > > > AMBARI-20537 introduced 2 changes to LLAP configs. Add them to hive component > upgrade path. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20782) Add config changes from AMBARI-20537 to hive component upgrade path
[
https://issues.apache.org/jira/browse/AMBARI-20782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973691#comment-15973691
]
Swapan Shridhar commented on AMBARI-20782:
--
[~prasanth_j] Confirming.. Why are these 2 removed?
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml
{code}
697
698 Updating the Hive Log4J2 properties to include
parameterizations
699
700
701
702
703
704 Updating Hash Aggregation settings for
LLAP
705
706
{code}
> Add config changes from AMBARI-20537 to hive component upgrade path
> ---
>
> Key: AMBARI-20782
> URL: https://issues.apache.org/jira/browse/AMBARI-20782
> Project: Ambari
> Issue Type: Bug
> Components: HiveServer2, Metastore, and Client Heap Sizes to Smart
> Configs
>Affects Versions: 2.5.0
>Reporter: Prasanth Jayachandran
>Assignee: Prasanth Jayachandran
> Attachments: AMBARI-20782.1.patch
>
>
> AMBARI-20537 introduced 2 changes to LLAP configs. Add them to hive component
> upgrade path.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20366) Filter out kerberos rules in exported blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20366: --- Description: If blueprint is exported from a kerberos enabled cluster Kerberos rules export principal names which contain cluster name and Realm, this patch filter out kerberos rules properties so that hardcoded cluster name and realm are not exported. (was: If blueprint is exported from a kerberos enabled cluster Kerberos rules export principal names which contain cluster name and Realm, this exports existing cluster name and realm name as tokens and replaces those tokens with new values of cluster name and realm during successive cluster deployments.) > Filter out kerberos rules in exported blueprint > --- > > Key: AMBARI-20366 > URL: https://issues.apache.org/jira/browse/AMBARI-20366 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20366.patch > > > If blueprint is exported from a kerberos enabled cluster Kerberos rules > export principal names which contain cluster name and Realm, this patch > filter out kerberos rules properties so that hardcoded cluster name and realm > are not exported. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20366) Filter out kerberos rules in exported blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20366: --- Summary: Filter out kerberos rules in exported blueprint (was: Tokenize kerberos principal name appearing in kerberos rules in exported blueprint) > Filter out kerberos rules in exported blueprint > --- > > Key: AMBARI-20366 > URL: https://issues.apache.org/jira/browse/AMBARI-20366 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20366.patch > > > If blueprint is exported from a kerberos enabled cluster Kerberos rules > export principal names which contain cluster name and Realm, this exports > existing cluster name and realm name as tokens and replaces those tokens with > new values of cluster name and realm during successive cluster deployments. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20785) Ambari report datanode decommissioned but datanode is still in decommissing
Chen He created AMBARI-20785: Summary: Ambari report datanode decommissioned but datanode is still in decommissing Key: AMBARI-20785 URL: https://issues.apache.org/jira/browse/AMBARI-20785 Project: Ambari Issue Type: Bug Components: infra Affects Versions: 2.4.0 Reporter: Chen He If we decommission HDFS datanode through ambari REST API call. It will create a new request http://ambari_server:8080/api/v1/clusters/cluster_name/requests/ However, the request quickly response "COMPLETED" only after it added the given datanode into dfs.exclude. It does not block till datanode fully decommissioned. It should block till the datanode completely decommissioned. At the same time, org.apache.ambari.groovy.client.decommissionDataNode() is using the same way to decommission datanode. It could cause data loss if cluster shutdown this node instantly after decommission the datanode. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20780) Update HBase Configuration group is ignored in upgrade.xml
[
https://issues.apache.org/jira/browse/AMBARI-20780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973606#comment-15973606
]
Hadoop QA commented on AMBARI-20780:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12863832/AMBARI-20780.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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler 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/11414//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11414//console
This message is automatically generated.
> Update HBase Configuration group is ignored in upgrade.xml
> --
>
> Key: AMBARI-20780
> URL: https://issues.apache.org/jira/browse/AMBARI-20780
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Tim Thorpe
>Assignee: Tim Thorpe
> Fix For: trunk
>
> Attachments: AMBARI-20780.patch
>
>
> The Update HBase Configuration group is ignored in upgrade.xml because it has
> an invalid syntax. It should be of xsi:type="cluster" because it contains an
> execute-stage.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-15754) configs.sh expands ***** in config values to a local file list, causing broken config files
[
https://issues.apache.org/jira/browse/AMBARI-15754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-15754:
---
Fix Version/s: 2.4.3
> configs.sh expands * in config values to a local file list, causing
> broken config files
> ---
>
> Key: AMBARI-15754
> URL: https://issues.apache.org/jira/browse/AMBARI-15754
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.0.0, 2.0.1, 2.1.0, 2.3.0, 2.0.2, 2.1.1, 2.1.2, trunk,
> 2.0.3, 2.2.0, 2.4.0, 2.2.1, 2.2.2, 2.4.1
>Reporter: Asger Askov Blekinge
>Assignee: Asger Askov Blekinge
> Labels: easyfix, patch
> Fix For: trunk, 2.5.0, 2.4.3
>
> Attachments: AMBARI-15754-branch-2.5.patch,
> AMBARI-15754_trunk_v3.patch, AMBARI-15754.v2.patch
>
>
> When you try to get the value of, say, pig-log4j like this, it outputs
> correctly
> {code}
> curl -k -s -u $AMBARI_USER:$AMBARI_PASSWORD
> "$AMBARI_HOST:$AMBARI_PORT/api/v1/clusters/$CLUSTER_NAME/configurations?type=pig-log4j=version1"
> {code}
> If you use configs.sh to do the same
> {code}
> configs.sh -u $AMBARI_USER -p $AMBARI_PASSWORD -port $AMBARI_PORT get
> $AMBARI_HOST $CLUSTER_NAME pig-log4j
> {code}
> it will have replaced the * with the file list in the working directory
> So,
> {code}
> "content" : "\n#\n#\n# Licensed to the Apache Software Foundation (ASF)
> under one\n# or more contributor license agreements. See the NOTICE file\n#
> distributed with this work for additional information\n# regarding copyright
> ownership. The ASF licenses this file\n# to you under the Apache License,
> Version 2.0 (the\n# \"License\"); you may not use this file except in
> compliance\n# with the License. You may obtain a copy of the License
> at\n#\n# http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required
> by applicable law or agreed to in writing,\n# software distributed under the
> License is distributed on an\n# \"AS IS\" BASIS, WITHOUT WARRANTIES OR
> CONDITIONS OF ANY\n# KIND, either express or implied. See the License for
> the\n# specific language governing permissions and limitations\n# under the
> License.\n#\n#\n#\n\n# * Set root logger level to DEBUG and its only
> appender to A.\nlog4j.logger.org.apache.pig=info, A\n\n# * A is set to be
> a ConsoleAppender.\nlog4j.appender.A=org.apache.log4j.ConsoleAppender\n#
> * A uses
> PatternLayout.\nlog4j.appender.A.layout=org.apache.log4j.PatternLayout\nlog4j.appender.A.layout.ConversionPattern=%-4r
> [%t] %-5p %c %x - %m%n"
> {code}
> will be output as
> {code}
> "content" : "\n#\n#\n# Licensed to the Apache Software Foundation (ASF) under
> one\n# or more contributor license agreements. See the NOTICE file\n#
> distributed with this work for additional information\n# regarding copyright
> ownership. The ASF licenses this file\n# to you under the Apache License,
> Version 2.0 (the\n# \"License\"); you may not use this file except in
> compliance\n# with the License. You may obtain a copy of the License at\n#\n#
> http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required by
> applicable law or agreed to in writing,\n# software distributed under the
> License is distributed on an\n# \"AS IS\" BASIS, WITHOUT WARRANTIES OR
> CONDITIONS OF ANY\n# KIND, either express or implied. See the License for
> the\n# specific language governing permissions and limitations\n# under the
> License.\n#\n#\n#\n\n# bigr configs.sh gpfs mmls ssh symphony Set root logger
> level to DEBUG and its only appender to A.\nlog4j.logger.org.apache.pig=info,
> A\n\n# bigr configs.sh gpfs mmls ssh symphony A is set to be a
> ConsoleAppender.\nlog4j.appender.A=org.apache.log4j.ConsoleAppender\n# bigr
> configs.sh gpfs mmls ssh symphony A uses
> PatternLayout.\nlog4j.appender.A.layout=org.apache.log4j.PatternLayout\nlog4j.appender.A.layout.ConversionPattern=%-4r
> [%t] %-5p %c %x - %m%n"
> {code}
> As you can see, there are no * string in the output any longer, but
> instead it has been replaced with "bigr configs.sh gpfs mmls ssh symphony"
> which happened to be the local files in my working dir.
> It all comes from this line in configs.sh, line 241-247
> {code}
> if [ "$propertiesStarted" -gt "0" ]; then
> if [ -z $FILENAME ]; then
> echo $line
> else
> echo $line >> $FILENAME
> fi
> fi
> {code}
> where the echo do not quote the $line to output
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20774) Service Upgrade VDF Creates Host Version Entries For All Hosts With INSTALLING
[
https://issues.apache.org/jira/browse/AMBARI-20774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973547#comment-15973547
]
Hadoop QA commented on AMBARI-20774:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12863859/AMBARI-20774.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11413//console
This message is automatically generated.
> Service Upgrade VDF Creates Host Version Entries For All Hosts With INSTALLING
> --
>
> Key: AMBARI-20774
> URL: https://issues.apache.org/jira/browse/AMBARI-20774
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-20774.patch
>
>
> When a VDF for a {{SERVICE}} upgrade targets only a subset of hosts in the
> cluster, there is a host version entry created for all hosts with the state
> of {{INSTALLING}}. This causes the web client to think that the installation
> is not complete and it prevents the upgrade button from displaying.
> STR:
> - Install a cluster with ZK and Storm
> -- ZK should be on all 3 hosts, Storm only on 2
> - Upload a VDF for Storm only and distribute it
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20782) Add config changes from AMBARI-20537 to hive component upgrade path
[
https://issues.apache.org/jira/browse/AMBARI-20782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973546#comment-15973546
]
Hadoop QA commented on AMBARI-20782:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12863865/AMBARI-20782.1.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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler 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/11412//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11412//console
This message is automatically generated.
> Add config changes from AMBARI-20537 to hive component upgrade path
> ---
>
> Key: AMBARI-20782
> URL: https://issues.apache.org/jira/browse/AMBARI-20782
> Project: Ambari
> Issue Type: Bug
> Components: HiveServer2, Metastore, and Client Heap Sizes to Smart
> Configs
>Affects Versions: 2.5.0
>Reporter: Prasanth Jayachandran
>Assignee: Prasanth Jayachandran
> Attachments: AMBARI-20782.1.patch
>
>
> AMBARI-20537 introduced 2 changes to LLAP configs. Add them to hive component
> upgrade path.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20777) AMS changes to use instanceId for cluster based segregation of data
[ https://issues.apache.org/jira/browse/AMBARI-20777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973496#comment-15973496 ] Hudson commented on AMBARI-20777: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7312 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7312/]) AMBARI-20777 : AMS changes to use instanceId for cluster based (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=323da508944626c8ee82118ce67a000b8e5a511c]) * (edit) ambari-metrics/ambari-metrics-hadoop-sink/src/main/java/org/apache/hadoop/metrics2/sink/timeline/HadoopTimelineMetricsSink.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/TimelineMetricClusterAggregatorSecond.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/HBaseTimelineMetricStore.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/discovery/TestMetadataSync.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/discovery/TimelineMetricMetadataSync.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/discovery/TimelineMetricMetadataManager.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/PhoenixHBaseAccessor.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/webapp/TimelineWebServices.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/query/PhoenixTransactSQL.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/discovery/TestMetadataManager.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/TimelineMetricStore.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/TestTimelineMetricStore.java > AMS changes to use instanceId for cluster based segregation of data > --- > > Key: AMBARI-20777 > URL: https://issues.apache.org/jira/browse/AMBARI-20777 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.5.1 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.1 > > Attachments: AMBARI-20777.patch > > > This issue tracks changes in the following work items to facilitate the use > of the "instanceId" field in AMS to capture per cluster metric data. > * Collector API > * Schema > * Metadata -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20366) Tokenize kerberos principal name appearing in kerberos rules in exported blueprint
[
https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973494#comment-15973494
]
Hadoop QA commented on AMBARI-20366:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12863868/AMBARI-20366.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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.state.UpgradeHelperTest
org.apache.ambari.server.state.cluster.ClustersDeadlockTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/11411//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11411//console
This message is automatically generated.
> Tokenize kerberos principal name appearing in kerberos rules in exported
> blueprint
> --
>
> Key: AMBARI-20366
> URL: https://issues.apache.org/jira/browse/AMBARI-20366
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, blueprints
>Affects Versions: trunk
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-20366.patch
>
>
> If blueprint is exported from a kerberos enabled cluster Kerberos rules
> export principal names which contain cluster name and Realm, this exports
> existing cluster name and realm name as tokens and replaces those tokens with
> new values of cluster name and realm during successive cluster deployments.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20777) AMS changes to use instanceId for cluster based segregation of data
[ https://issues.apache.org/jira/browse/AMBARI-20777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973460#comment-15973460 ] Hudson commented on AMBARI-20777: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1412 (See [https://builds.apache.org/job/Ambari-branch-2.5/1412/]) AMBARI-20777 : AMS changes to use instanceId for cluster based (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=71399b7f7f02813e20813719816a1e82710ff3d3]) * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/PhoenixHBaseAccessor.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/discovery/TimelineMetricMetadataManager.java * (edit) ambari-metrics/ambari-metrics-hadoop-sink/src/main/java/org/apache/hadoop/metrics2/sink/timeline/HadoopTimelineMetricsSink.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/discovery/TestMetadataSync.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/TimelineMetricStore.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/query/PhoenixTransactSQL.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/discovery/TimelineMetricMetadataSync.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/discovery/TestMetadataManager.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/TimelineMetricClusterAggregatorSecond.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/TestTimelineMetricStore.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/HBaseTimelineMetricStore.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/webapp/TimelineWebServices.java > AMS changes to use instanceId for cluster based segregation of data > --- > > Key: AMBARI-20777 > URL: https://issues.apache.org/jira/browse/AMBARI-20777 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.5.1 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.1 > > Attachments: AMBARI-20777.patch > > > This issue tracks changes in the following work items to facilitate the use > of the "instanceId" field in AMS to capture per cluster metric data. > * Collector API > * Schema > * Metadata -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20784) Able to hide the "Why public repo not selected" when no stacks have repoinfo.xml with the "latest" section
[ https://issues.apache.org/jira/browse/AMBARI-20784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-20784: --- Status: Patch Available (was: Open) > Able to hide the "Why public repo not selected" when no stacks have > repoinfo.xml with the "latest" section > -- > > Key: AMBARI-20784 > URL: https://issues.apache.org/jira/browse/AMBARI-20784 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-20784.patch > > > Able to hide the "Why public repo not selected" when no stacks have > repoinfo.xml with the "latest" section. There is no point of display the > error based on the stackDefault checking when no stacks even offer the > "latest" section in their repoinfo.xml. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20784) Able to hide the "Why public repo not selected" when no stacks have repoinfo.xml with the "latest" section
[ https://issues.apache.org/jira/browse/AMBARI-20784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-20784: --- Attachment: AMBARI-20784.patch > Able to hide the "Why public repo not selected" when no stacks have > repoinfo.xml with the "latest" section > -- > > Key: AMBARI-20784 > URL: https://issues.apache.org/jira/browse/AMBARI-20784 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-20784.patch > > > Able to hide the "Why public repo not selected" when no stacks have > repoinfo.xml with the "latest" section. There is no point of display the > error based on the stackDefault checking when no stacks even offer the > "latest" section in their repoinfo.xml. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20784) Able to hide the "Why public repo not selected" when no stacks have repoinfo.xml with the "latest" section
Di Li created AMBARI-20784: -- Summary: Able to hide the "Why public repo not selected" when no stacks have repoinfo.xml with the "latest" section Key: AMBARI-20784 URL: https://issues.apache.org/jira/browse/AMBARI-20784 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: trunk Reporter: Di Li Assignee: Di Li Fix For: trunk Able to hide the "Why public repo not selected" when no stacks have repoinfo.xml with the "latest" section. There is no point of display the error based on the stackDefault checking when no stacks even offer the "latest" section in their repoinfo.xml. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20783) Enable Ambari to fully decommission an agent
Chen He created AMBARI-20783: Summary: Enable Ambari to fully decommission an agent Key: AMBARI-20783 URL: https://issues.apache.org/jira/browse/AMBARI-20783 Project: Ambari Issue Type: Improvement Components: infra Reporter: Chen He Priority: Minor Not sure if there is a feature that provides a REST API for customer to fully and gracefully delete an agent. For example, if an ambari agent has running following components: zk, datanode, nodemanager, etc. It first decommission datanode and nodemanager, then delete all components, and finally delete agent from ambari host list. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20777) AMS changes to use instanceId for cluster based segregation of data
[ https://issues.apache.org/jira/browse/AMBARI-20777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-20777. Resolution: Fixed Pushed to trunk and branch-2.5 > AMS changes to use instanceId for cluster based segregation of data > --- > > Key: AMBARI-20777 > URL: https://issues.apache.org/jira/browse/AMBARI-20777 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.5.1 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.1 > > Attachments: AMBARI-20777.patch > > > This issue tracks changes in the following work items to facilitate the use > of the "instanceId" field in AMS to capture per cluster metric data. > * Collector API > * Schema > * Metadata -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-19632) Ldap sync fails when there are special characters in distinguished names
[
https://issues.apache.org/jira/browse/AMBARI-19632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas resolved AMBARI-19632.
---
Resolution: Fixed
Committed to branch-2.4
{noformat}
commit f613941aabb78b600ea627f89bb78aa014bf1e79
Author: Robert Levas
Date: Tue Apr 18 16:08:55 2017 -0400
{noformat}
> Ldap sync fails when there are special characters in distinguished names
>
>
> Key: AMBARI-19632
> URL: https://issues.apache.org/jira/browse/AMBARI-19632
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: ldap
> Fix For: 2.5.0, 2.4.3
>
> Attachments: AMBARI-19632_branch-2.5_01.patch,
> AMBARI-19632_trunk_01.patch
>
>
> Ldap sync fails when there are special characters in distinguished names.
> For example if there was a user with the distinguished name of
> {{OU=test/test,OU=users,DC=EXAMPLE,DC=COM}} and that user was a member of a
> synced group, then the lookup of the user using the membership attribute in
> the group would fail due to the special character.
> The error would look something like
> {noformat}
> REASON: Caught exception running LDAP sync. Uncategorized exception occured
> during LDAP processing; nested exception is javax.naming.NamingException:
> [LDAP: error code 1 - 20D6: SvcErr: DSID-031007DB, problem 5012
> (DIR_ERROR), data 0
> ]; remaining name 'OU=test/test,OU=users,DC=EXAMPLE,DC=COM'
> {noformat}
> *Solution*
> Update the library versionf for Spring LDAP
> * {{org.springframework.security/spring-security-ldap}} to {{4.0.4.RELEASE}}
> * {{org.springframework.ldap/spring-ldap-core}} to {{2.0.4.RELEASE}}
> Then use {{LdapUtils.newLdapName}} to convert a String representing a DN into
> a {{javax.naming.ldap.LdapName}} and use that object in the search facility
> executed in
> {{org.apache.ambari.server.security.ldap.AmbariLdapDataPopulator#getFilteredLdapUsers(java.lang.String,
> org.springframework.ldap.filter.Filter)}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Reopened] (AMBARI-19632) Ldap sync fails when there are special characters in distinguished names
[
https://issues.apache.org/jira/browse/AMBARI-19632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas reopened AMBARI-19632:
---
Reopening to add to branch-2.4
> Ldap sync fails when there are special characters in distinguished names
>
>
> Key: AMBARI-19632
> URL: https://issues.apache.org/jira/browse/AMBARI-19632
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: ldap
> Fix For: 2.5.0, 2.4.3
>
> Attachments: AMBARI-19632_branch-2.5_01.patch,
> AMBARI-19632_trunk_01.patch
>
>
> Ldap sync fails when there are special characters in distinguished names.
> For example if there was a user with the distinguished name of
> {{OU=test/test,OU=users,DC=EXAMPLE,DC=COM}} and that user was a member of a
> synced group, then the lookup of the user using the membership attribute in
> the group would fail due to the special character.
> The error would look something like
> {noformat}
> REASON: Caught exception running LDAP sync. Uncategorized exception occured
> during LDAP processing; nested exception is javax.naming.NamingException:
> [LDAP: error code 1 - 20D6: SvcErr: DSID-031007DB, problem 5012
> (DIR_ERROR), data 0
> ]; remaining name 'OU=test/test,OU=users,DC=EXAMPLE,DC=COM'
> {noformat}
> *Solution*
> Update the library versionf for Spring LDAP
> * {{org.springframework.security/spring-security-ldap}} to {{4.0.4.RELEASE}}
> * {{org.springframework.ldap/spring-ldap-core}} to {{2.0.4.RELEASE}}
> Then use {{LdapUtils.newLdapName}} to convert a String representing a DN into
> a {{javax.naming.ldap.LdapName}} and use that object in the search facility
> executed in
> {{org.apache.ambari.server.security.ldap.AmbariLdapDataPopulator#getFilteredLdapUsers(java.lang.String,
> org.springframework.ldap.filter.Filter)}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19632) Ldap sync fails when there are special characters in distinguished names
[
https://issues.apache.org/jira/browse/AMBARI-19632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-19632:
--
Fix Version/s: 2.4.3
> Ldap sync fails when there are special characters in distinguished names
>
>
> Key: AMBARI-19632
> URL: https://issues.apache.org/jira/browse/AMBARI-19632
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: ldap
> Fix For: 2.5.0, 2.4.3
>
> Attachments: AMBARI-19632_branch-2.5_01.patch,
> AMBARI-19632_trunk_01.patch
>
>
> Ldap sync fails when there are special characters in distinguished names.
> For example if there was a user with the distinguished name of
> {{OU=test/test,OU=users,DC=EXAMPLE,DC=COM}} and that user was a member of a
> synced group, then the lookup of the user using the membership attribute in
> the group would fail due to the special character.
> The error would look something like
> {noformat}
> REASON: Caught exception running LDAP sync. Uncategorized exception occured
> during LDAP processing; nested exception is javax.naming.NamingException:
> [LDAP: error code 1 - 20D6: SvcErr: DSID-031007DB, problem 5012
> (DIR_ERROR), data 0
> ]; remaining name 'OU=test/test,OU=users,DC=EXAMPLE,DC=COM'
> {noformat}
> *Solution*
> Update the library versionf for Spring LDAP
> * {{org.springframework.security/spring-security-ldap}} to {{4.0.4.RELEASE}}
> * {{org.springframework.ldap/spring-ldap-core}} to {{2.0.4.RELEASE}}
> Then use {{LdapUtils.newLdapName}} to convert a String representing a DN into
> a {{javax.naming.ldap.LdapName}} and use that object in the search facility
> executed in
> {{org.apache.ambari.server.security.ldap.AmbariLdapDataPopulator#getFilteredLdapUsers(java.lang.String,
> org.springframework.ldap.filter.Filter)}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20777) AMS changes to use instanceId for cluster based segregation of data
[ https://issues.apache.org/jira/browse/AMBARI-20777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-20777: --- Attachment: AMBARI-20777.patch > AMS changes to use instanceId for cluster based segregation of data > --- > > Key: AMBARI-20777 > URL: https://issues.apache.org/jira/browse/AMBARI-20777 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.5.1 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.1 > > Attachments: AMBARI-20777.patch > > > This issue tracks changes in the following work items to facilitate the use > of the "instanceId" field in AMS to capture per cluster metric data. > * Collector API > * Schema > * Metadata -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20366) Tokenize kerberos principal name appearing in kerberos rules in exported blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20366: --- Attachment: (was: AMBARI-20366.patch) > Tokenize kerberos principal name appearing in kerberos rules in exported > blueprint > -- > > Key: AMBARI-20366 > URL: https://issues.apache.org/jira/browse/AMBARI-20366 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20366.patch > > > If blueprint is exported from a kerberos enabled cluster Kerberos rules > export principal names which contain cluster name and Realm, this exports > existing cluster name and realm name as tokens and replaces those tokens with > new values of cluster name and realm during successive cluster deployments. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20366) Tokenize kerberos principal name appearing in kerberos rules in exported blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20366: --- Status: Open (was: Patch Available) > Tokenize kerberos principal name appearing in kerberos rules in exported > blueprint > -- > > Key: AMBARI-20366 > URL: https://issues.apache.org/jira/browse/AMBARI-20366 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20366.patch > > > If blueprint is exported from a kerberos enabled cluster Kerberos rules > export principal names which contain cluster name and Realm, this exports > existing cluster name and realm name as tokens and replaces those tokens with > new values of cluster name and realm during successive cluster deployments. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20366) Tokenize kerberos principal name appearing in kerberos rules in exported blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20366: --- Attachment: AMBARI-20366.patch > Tokenize kerberos principal name appearing in kerberos rules in exported > blueprint > -- > > Key: AMBARI-20366 > URL: https://issues.apache.org/jira/browse/AMBARI-20366 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20366.patch > > > If blueprint is exported from a kerberos enabled cluster Kerberos rules > export principal names which contain cluster name and Realm, this exports > existing cluster name and realm name as tokens and replaces those tokens with > new values of cluster name and realm during successive cluster deployments. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20366) Tokenize kerberos principal name appearing in kerberos rules in exported blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20366: --- Status: Patch Available (was: In Progress) > Tokenize kerberos principal name appearing in kerberos rules in exported > blueprint > -- > > Key: AMBARI-20366 > URL: https://issues.apache.org/jira/browse/AMBARI-20366 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20366.patch > > > If blueprint is exported from a kerberos enabled cluster Kerberos rules > export principal names which contain cluster name and Realm, this exports > existing cluster name and realm name as tokens and replaces those tokens with > new values of cluster name and realm during successive cluster deployments. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20782) Add config changes from AMBARI-20537 to hive component upgrade path
[ https://issues.apache.org/jira/browse/AMBARI-20782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973244#comment-15973244 ] Prasanth Jayachandran commented on AMBARI-20782: [~sumitmohanty]/[~swapanshridhar] can you please review the patch? cc/ [~sseth] > Add config changes from AMBARI-20537 to hive component upgrade path > --- > > Key: AMBARI-20782 > URL: https://issues.apache.org/jira/browse/AMBARI-20782 > Project: Ambari > Issue Type: Bug > Components: HiveServer2, Metastore, and Client Heap Sizes to Smart > Configs >Affects Versions: 2.5.0 >Reporter: Prasanth Jayachandran >Assignee: Prasanth Jayachandran > Attachments: AMBARI-20782.1.patch > > > AMBARI-20537 introduced 2 changes to LLAP configs. Add them to hive component > upgrade path. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20782) Add config changes from AMBARI-20537 to hive component upgrade path
[ https://issues.apache.org/jira/browse/AMBARI-20782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanth Jayachandran updated AMBARI-20782: --- Status: Patch Available (was: Open) > Add config changes from AMBARI-20537 to hive component upgrade path > --- > > Key: AMBARI-20782 > URL: https://issues.apache.org/jira/browse/AMBARI-20782 > Project: Ambari > Issue Type: Bug > Components: HiveServer2, Metastore, and Client Heap Sizes to Smart > Configs >Affects Versions: 2.5.0 >Reporter: Prasanth Jayachandran >Assignee: Prasanth Jayachandran > Attachments: AMBARI-20782.1.patch > > > AMBARI-20537 introduced 2 changes to LLAP configs. Add them to hive component > upgrade path. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20782) Add config changes from AMBARI-20537 to hive component upgrade path
[ https://issues.apache.org/jira/browse/AMBARI-20782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanth Jayachandran updated AMBARI-20782: --- Attachment: AMBARI-20782.1.patch > Add config changes from AMBARI-20537 to hive component upgrade path > --- > > Key: AMBARI-20782 > URL: https://issues.apache.org/jira/browse/AMBARI-20782 > Project: Ambari > Issue Type: Bug > Components: HiveServer2, Metastore, and Client Heap Sizes to Smart > Configs >Affects Versions: 2.5.0 >Reporter: Prasanth Jayachandran >Assignee: Prasanth Jayachandran > Attachments: AMBARI-20782.1.patch > > > AMBARI-20537 introduced 2 changes to LLAP configs. Add them to hive component > upgrade path. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-18576) When multiple requests are running, aborting any will incorrectly abort all requests instead the desired one
[ https://issues.apache.org/jira/browse/AMBARI-18576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18576: - Fix Version/s: 2.4.3 > When multiple requests are running, aborting any will incorrectly abort all > requests instead the desired one > > > Key: AMBARI-18576 > URL: https://issues.apache.org/jira/browse/AMBARI-18576 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Critical > Fix For: trunk, 2.5.0, 2.4.3 > > Attachments: AMBARI-18576.branch-2.5.patch, AMBARI-18576.trunk.patch > > > STR: > * Install Ambari 2.4.0.1 with any HDP stack (e.g., 2.5) and HDFS, YARN, ZK > * Run multiple commands in parallel (such as service checks) > * Attempt to abort any one of them > Instead of aborting just the desired one, it will abort all requests. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20782) Add config changes from AMBARI-20537 to hive component upgrade path
Prasanth Jayachandran created AMBARI-20782: -- Summary: Add config changes from AMBARI-20537 to hive component upgrade path Key: AMBARI-20782 URL: https://issues.apache.org/jira/browse/AMBARI-20782 Project: Ambari Issue Type: Bug Components: HiveServer2, Metastore, and Client Heap Sizes to Smart Configs Affects Versions: 2.5.0 Reporter: Prasanth Jayachandran Assignee: Prasanth Jayachandran AMBARI-20537 introduced 2 changes to LLAP configs. Add them to hive component upgrade path. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-18576) When multiple requests are running, aborting any will incorrectly abort all requests instead the desired one
[ https://issues.apache.org/jira/browse/AMBARI-18576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973242#comment-15973242 ] Alejandro Fernandez commented on AMBARI-18576: -- Just pushed to branch-2.4 to also make a 2.4.3 release, commit 36226da099b1e6311595fcc732d0d06681ce105b > When multiple requests are running, aborting any will incorrectly abort all > requests instead the desired one > > > Key: AMBARI-18576 > URL: https://issues.apache.org/jira/browse/AMBARI-18576 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Critical > Fix For: trunk, 2.5.0, 2.4.3 > > Attachments: AMBARI-18576.branch-2.5.patch, AMBARI-18576.trunk.patch > > > STR: > * Install Ambari 2.4.0.1 with any HDP stack (e.g., 2.5) and HDFS, YARN, ZK > * Run multiple commands in parallel (such as service checks) > * Attempt to abort any one of them > Instead of aborting just the desired one, it will abort all requests. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20774) Service Upgrade VDF Creates Host Version Entries For All Hosts With INSTALLING
[
https://issues.apache.org/jira/browse/AMBARI-20774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-20774:
-
Status: Patch Available (was: Open)
> Service Upgrade VDF Creates Host Version Entries For All Hosts With INSTALLING
> --
>
> Key: AMBARI-20774
> URL: https://issues.apache.org/jira/browse/AMBARI-20774
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-20774.patch
>
>
> When a VDF for a {{SERVICE}} upgrade targets only a subset of hosts in the
> cluster, there is a host version entry created for all hosts with the state
> of {{INSTALLING}}. This causes the web client to think that the installation
> is not complete and it prevents the upgrade button from displaying.
> STR:
> - Install a cluster with ZK and Storm
> -- ZK should be on all 3 hosts, Storm only on 2
> - Upload a VDF for Storm only and distribute it
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20774) Service Upgrade VDF Creates Host Version Entries For All Hosts With INSTALLING
[
https://issues.apache.org/jira/browse/AMBARI-20774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-20774:
-
Attachment: AMBARI-20774.patch
> Service Upgrade VDF Creates Host Version Entries For All Hosts With INSTALLING
> --
>
> Key: AMBARI-20774
> URL: https://issues.apache.org/jira/browse/AMBARI-20774
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-20774.patch
>
>
> When a VDF for a {{SERVICE}} upgrade targets only a subset of hosts in the
> cluster, there is a host version entry created for all hosts with the state
> of {{INSTALLING}}. This causes the web client to think that the installation
> is not complete and it prevents the upgrade button from displaying.
> STR:
> - Install a cluster with ZK and Storm
> -- ZK should be on all 3 hosts, Storm only on 2
> - Upload a VDF for Storm only and distribute it
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (AMBARI-18938) NPE when authenticating via a Centrify LDAP proxy
[
https://issues.apache.org/jira/browse/AMBARI-18938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas resolved AMBARI-18938.
---
Resolution: Fixed
Committed to branch-2.4
{noformat}
commit f4d7a3fdbf26ef1900647a31121f2b7ceb5b1a2b
Author: Robert Levas
Date: Tue Apr 18 13:34:17 2017 -0400
{noformat}
> NPE when authenticating via a Centrify LDAP proxy
> -
>
> Key: AMBARI-18938
> URL: https://issues.apache.org/jira/browse/AMBARI-18938
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: ldap
> Fix For: 2.5.0, 2.4.3
>
> Attachments: AMBARI-18938_branch-2.5_01.patch,
> AMBARI-18938_trunk_01.patch
>
>
> When authenticating using LDAP where the LDAP server is a Centrify LDAP
> proxy, a {{NullPointerException}} is being thrown due to unexpected missing
> LDAP user object attributes.
> {noformat}
> 10 Nov 2016 08:23:38,789 ERROR [ambari-client-thread-25]
> AmbariLdapBindAuthenticator:95 - Caught exception
> java.lang.NullPointerException
> at
> org.apache.ambari.server.security.authorization.AmbariLdapBindAuthenticator.authenticate(AmbariLdapBindAuthenticator.java:83)
> at
> org.springframework.security.ldap.authentication.LdapAuthenticationProvider.doAuthentication(LdapAuthenticationProvider.java:178)
> at
> org.springframework.security.ldap.authentication.AbstractLdapAuthenticationProvider.authenticate(AbstractLdapAuthenticationProvider.java:61)
> at
> org.apache.ambari.server.security.authorization.AmbariLdapAuthenticationProvider.authenticate(AmbariLdapAuthenticationProvider.java:73)
> at
> org.springframework.security.authentication.ProviderManager.authenticate(ProviderManager.java:156)
> at
> org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:168)
> at
> org.apache.ambari.server.security.authentication.AmbariAuthenticationFilter.doFilter(AmbariAuthenticationFilter.java:88)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.apache.ambari.server.security.authorization.AmbariUserAuthorizationFilter.doFilter(AmbariUserAuthorizationFilter.java:91)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:87)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:192)
> at
> org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:160)
> at
> org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:237)
> at
> org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:167)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1478)
> at
> org.apache.ambari.server.api.MethodOverrideFilter.doFilter(MethodOverrideFilter.java:72)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1478)
> at
> org.apache.ambari.server.api.AmbariPersistFilter.doFilter(AmbariPersistFilter.java:47)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1478)
> at
> org.apache.ambari.server.security.AbstractSecurityHeaderFilter.doFilter(AbstractSecurityHeaderFilter.java:109)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1478)
> at
> org.eclipse.jetty.servlets.UserAgentFilter.doFilter(UserAgentFilter.java:82)
> at org.eclipse.jetty.servlets.GzipFilter.doFilter(GzipFilter.java:294)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1478)
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:557)
> at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)
> at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:427)
> at
>
[jira] [Updated] (AMBARI-18938) NPE when authenticating via a Centrify LDAP proxy
[
https://issues.apache.org/jira/browse/AMBARI-18938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-18938:
--
Fix Version/s: 2.4.3
> NPE when authenticating via a Centrify LDAP proxy
> -
>
> Key: AMBARI-18938
> URL: https://issues.apache.org/jira/browse/AMBARI-18938
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: ldap
> Fix For: 2.5.0, 2.4.3
>
> Attachments: AMBARI-18938_branch-2.5_01.patch,
> AMBARI-18938_trunk_01.patch
>
>
> When authenticating using LDAP where the LDAP server is a Centrify LDAP
> proxy, a {{NullPointerException}} is being thrown due to unexpected missing
> LDAP user object attributes.
> {noformat}
> 10 Nov 2016 08:23:38,789 ERROR [ambari-client-thread-25]
> AmbariLdapBindAuthenticator:95 - Caught exception
> java.lang.NullPointerException
> at
> org.apache.ambari.server.security.authorization.AmbariLdapBindAuthenticator.authenticate(AmbariLdapBindAuthenticator.java:83)
> at
> org.springframework.security.ldap.authentication.LdapAuthenticationProvider.doAuthentication(LdapAuthenticationProvider.java:178)
> at
> org.springframework.security.ldap.authentication.AbstractLdapAuthenticationProvider.authenticate(AbstractLdapAuthenticationProvider.java:61)
> at
> org.apache.ambari.server.security.authorization.AmbariLdapAuthenticationProvider.authenticate(AmbariLdapAuthenticationProvider.java:73)
> at
> org.springframework.security.authentication.ProviderManager.authenticate(ProviderManager.java:156)
> at
> org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:168)
> at
> org.apache.ambari.server.security.authentication.AmbariAuthenticationFilter.doFilter(AmbariAuthenticationFilter.java:88)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.apache.ambari.server.security.authorization.AmbariUserAuthorizationFilter.doFilter(AmbariUserAuthorizationFilter.java:91)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:87)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:192)
> at
> org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:160)
> at
> org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:237)
> at
> org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:167)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1478)
> at
> org.apache.ambari.server.api.MethodOverrideFilter.doFilter(MethodOverrideFilter.java:72)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1478)
> at
> org.apache.ambari.server.api.AmbariPersistFilter.doFilter(AmbariPersistFilter.java:47)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1478)
> at
> org.apache.ambari.server.security.AbstractSecurityHeaderFilter.doFilter(AbstractSecurityHeaderFilter.java:109)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1478)
> at
> org.eclipse.jetty.servlets.UserAgentFilter.doFilter(UserAgentFilter.java:82)
> at org.eclipse.jetty.servlets.GzipFilter.doFilter(GzipFilter.java:294)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1478)
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:557)
> at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)
> at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:427)
> at
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)
> at
>
[jira] [Reopened] (AMBARI-18938) NPE when authenticating via a Centrify LDAP proxy
[
https://issues.apache.org/jira/browse/AMBARI-18938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas reopened AMBARI-18938:
---
Reopening to commit to branch-2.4.
> NPE when authenticating via a Centrify LDAP proxy
> -
>
> Key: AMBARI-18938
> URL: https://issues.apache.org/jira/browse/AMBARI-18938
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: ldap
> Fix For: 2.5.0, 2.4.3
>
> Attachments: AMBARI-18938_branch-2.5_01.patch,
> AMBARI-18938_trunk_01.patch
>
>
> When authenticating using LDAP where the LDAP server is a Centrify LDAP
> proxy, a {{NullPointerException}} is being thrown due to unexpected missing
> LDAP user object attributes.
> {noformat}
> 10 Nov 2016 08:23:38,789 ERROR [ambari-client-thread-25]
> AmbariLdapBindAuthenticator:95 - Caught exception
> java.lang.NullPointerException
> at
> org.apache.ambari.server.security.authorization.AmbariLdapBindAuthenticator.authenticate(AmbariLdapBindAuthenticator.java:83)
> at
> org.springframework.security.ldap.authentication.LdapAuthenticationProvider.doAuthentication(LdapAuthenticationProvider.java:178)
> at
> org.springframework.security.ldap.authentication.AbstractLdapAuthenticationProvider.authenticate(AbstractLdapAuthenticationProvider.java:61)
> at
> org.apache.ambari.server.security.authorization.AmbariLdapAuthenticationProvider.authenticate(AmbariLdapAuthenticationProvider.java:73)
> at
> org.springframework.security.authentication.ProviderManager.authenticate(ProviderManager.java:156)
> at
> org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:168)
> at
> org.apache.ambari.server.security.authentication.AmbariAuthenticationFilter.doFilter(AmbariAuthenticationFilter.java:88)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.apache.ambari.server.security.authorization.AmbariUserAuthorizationFilter.doFilter(AmbariUserAuthorizationFilter.java:91)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:87)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:192)
> at
> org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:160)
> at
> org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:237)
> at
> org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:167)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1478)
> at
> org.apache.ambari.server.api.MethodOverrideFilter.doFilter(MethodOverrideFilter.java:72)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1478)
> at
> org.apache.ambari.server.api.AmbariPersistFilter.doFilter(AmbariPersistFilter.java:47)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1478)
> at
> org.apache.ambari.server.security.AbstractSecurityHeaderFilter.doFilter(AbstractSecurityHeaderFilter.java:109)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1478)
> at
> org.eclipse.jetty.servlets.UserAgentFilter.doFilter(UserAgentFilter.java:82)
> at org.eclipse.jetty.servlets.GzipFilter.doFilter(GzipFilter.java:294)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1478)
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:557)
> at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)
> at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:427)
> at
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)
> at
>
[jira] [Created] (AMBARI-20781) Hadoop QA test results link is broken
Doroszlai, Attila created AMBARI-20781:
--
Summary: Hadoop QA test results link is broken
Key: AMBARI-20781
URL: https://issues.apache.org/jira/browse/AMBARI-20781
Project: Ambari
Issue Type: Bug
Affects Versions: 3.0.0
Reporter: Doroszlai, Attila
Assignee: Doroszlai, Attila
Priority: Minor
Fix For: 3.0.0
The [test results
link|https://builds.apache.org/job/Ambari-trunk-test-patch/11408//testReport/]
in [this comment by Hadoop
QA|https://issues.apache.org/jira/browse/AMBARI-20775?focusedCommentId=15972797=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15972797]
is broken. The [correct
link|https://builds.apache.org/job/Ambari-trunk-test-patch/11408//artifact/patch-work/testrun_ambari-server.txt]
is available via the [job status
page|https://builds.apache.org/job/Ambari-trunk-test-patch/11408/].
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/11408//testReport/
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19345) Storm REST metrics are not available when Storm UI is running in HTTPS
[ https://issues.apache.org/jira/browse/AMBARI-19345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972988#comment-15972988 ] Dmytro Sen commented on AMBARI-19345: - Committed to branch-2.4 > Storm REST metrics are not available when Storm UI is running in HTTPS > -- > > Key: AMBARI-19345 > URL: https://issues.apache.org/jira/browse/AMBARI-19345 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics, ambari-views >Affects Versions: 2.4.1, 2.4.2 >Reporter: Rahul Pathak >Assignee: Dmytro Sen > Fix For: 2.5.0, 2.4.3 > > Attachments: AMBARI-19345_3.patch, AMBARI-19345_4.patch, storm > summary.png > > > Enable storm ui for https as per below document. > http://storm.apache.org/releases/1.0.1/SECURITY.html > Storm UI works fine and connect successfully using https. > However ambari alert for storm UI breaks, also ambari server keeps trying to > fetch REST metrics using http instead of https. > !storm summary.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19345) Storm REST metrics are not available when Storm UI is running in HTTPS
[ https://issues.apache.org/jira/browse/AMBARI-19345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-19345: Fix Version/s: 2.4.3 > Storm REST metrics are not available when Storm UI is running in HTTPS > -- > > Key: AMBARI-19345 > URL: https://issues.apache.org/jira/browse/AMBARI-19345 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics, ambari-views >Affects Versions: 2.4.1, 2.4.2 >Reporter: Rahul Pathak >Assignee: Dmytro Sen > Fix For: 2.5.0, 2.4.3 > > Attachments: AMBARI-19345_3.patch, AMBARI-19345_4.patch, storm > summary.png > > > Enable storm ui for https as per below document. > http://storm.apache.org/releases/1.0.1/SECURITY.html > Storm UI works fine and connect successfully using https. > However ambari alert for storm UI breaks, also ambari server keeps trying to > fetch REST metrics using http instead of https. > !storm summary.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20537) Some config changes for LLAP to avoid daemon getting killed
[
https://issues.apache.org/jira/browse/AMBARI-20537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-20537:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Some config changes for LLAP to avoid daemon getting killed
> ---
>
> Key: AMBARI-20537
> URL: https://issues.apache.org/jira/browse/AMBARI-20537
> Project: Ambari
> Issue Type: Bug
> Components: HiveServer2, Metastore, and Client Heap Sizes to Smart
> Configs
>Affects Versions: 2.5.0
>Reporter: Prasanth Jayachandran
>Assignee: Prasanth Jayachandran
> Fix For: 2.5.1
>
> Attachments: AMBARI-20537.2.patch, AMBARI-20537.patch
>
>
> Following changes are required to improve the stability of LLAP daemons
> {code}
> tez.runtime.shuffle.parallel.copies=8
> Add "-Xss512k" to LLAP app java opts
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20780) Update HBase Configuration group is ignored in upgrade.xml
[ https://issues.apache.org/jira/browse/AMBARI-20780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-20780: Attachment: AMBARI-20780.patch > Update HBase Configuration group is ignored in upgrade.xml > -- > > Key: AMBARI-20780 > URL: https://issues.apache.org/jira/browse/AMBARI-20780 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk > > Attachments: AMBARI-20780.patch > > > The Update HBase Configuration group is ignored in upgrade.xml because it has > an invalid syntax. It should be of xsi:type="cluster" because it contains an > execute-stage. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20780) Update HBase Configuration group is ignored in upgrade.xml
[ https://issues.apache.org/jira/browse/AMBARI-20780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-20780: Status: Patch Available (was: Open) > Update HBase Configuration group is ignored in upgrade.xml > -- > > Key: AMBARI-20780 > URL: https://issues.apache.org/jira/browse/AMBARI-20780 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk > > Attachments: AMBARI-20780.patch > > > The Update HBase Configuration group is ignored in upgrade.xml because it has > an invalid syntax. It should be of xsi:type="cluster" because it contains an > execute-stage. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20767) Add the Chinese translation files
[
https://issues.apache.org/jira/browse/AMBARI-20767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972879#comment-15972879
]
Hadoop QA commented on AMBARI-20767:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12863733/AMBARI-20767.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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-web
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/11410//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11410//console
This message is automatically generated.
> Add the Chinese translation files
> -
>
> Key: AMBARI-20767
> URL: https://issues.apache.org/jira/browse/AMBARI-20767
> Project: Ambari
> Issue Type: New Feature
> Components: ambari-admin, ambari-web
>Affects Versions: 2.4.0
>Reporter: PetterWang
> Labels: features
> Fix For: 2.4.0
>
> Attachments: AMBARI-20767_branch-2.4.0.patch, AMBARI-20767.patch
>
>
> Need chinese translation files , include
> ambari-admin\src\main\resources\ui\admin-web\app\scripts\i18n.config.js and
> ambari-web\app\locales\zh\messages.js
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20768) Local Ambari user with no cluster role must not be able to access Logsearch UI
[
https://issues.apache.org/jira/browse/AMBARI-20768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972799#comment-15972799
]
Hadoop QA commented on AMBARI-20768:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12863742/AMBARI-20768_branch-2.5.0.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11409//console
This message is automatically generated.
> Local Ambari user with no cluster role must not be able to access Logsearch UI
> --
>
> Key: AMBARI-20768
> URL: https://issues.apache.org/jira/browse/AMBARI-20768
> Project: Ambari
> Issue Type: Bug
> Components: logsearch
>Affects Versions: trunk, 2.5.0
>Reporter: Keta Patel
>Assignee: Keta Patel
> Attachments: all_tests_successful.png, AMBARI-20768_branch-2.5.0.patch
>
>
> A local Ambari user with no cluster roles assigned to it can successfully log
> into the Logsearch UI.
> Logsearch service exercises restriction on who can access its UI using a
> property "logsearch.roles.allowed". This property is a comma-separated list
> of roles to be allowed access to Logsearch UI. This defect deals with the
> following 2 issues:
> 1. If Logsearch service requires that only certain roles be allowed to access
> its UI, then a local Ambari user with no roles must not be allowed to access
> the UI.
> 2. If some user with privilege to edit the config properties, updates
> "logsearch.roles.allowed" by removing the "AMBARI.ADMINISTRATOR" role from
> its list, then the Ambari Admins will not be able to access the Logsearch UI.
> This violates the Ambari Administrator privilege which must be able to access
> all frames of Ambari UI as well as perform all UI operations.
> DESIRED BEHAVIOR:
> =
> 1. A local user with no role assigned to it, must not be able to access
> Logsearch UI.
> 2. Ambari Administrators must be always be allowed to access the Logsearch
> UI. No user is allowed to revoke this access right of Ambari Administrator
> for the Logsearch UI.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20775) VersionAdvertised should be set to False by default in stack_tool.py
[
https://issues.apache.org/jira/browse/AMBARI-20775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972797#comment-15972797
]
Hadoop QA commented on AMBARI-20775:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12863748/AMBARI-20775.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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/11408//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11408//console
This message is automatically generated.
> VersionAdvertised should be set to False by default in stack_tool.py
>
>
> Key: AMBARI-20775
> URL: https://issues.apache.org/jira/browse/AMBARI-20775
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.1
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
> Fix For: 2.5.1
>
> Attachments: AMBARI-20775.patch
>
>
> All the commands.json files should always contain the versionAdvertised
> field. If versionAdvertised is not set in command.json then we should assume
> that versionAdvertised=False when calling stack_tools.py
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (AMBARI-18813) Optionally force username from LDAP authentication data to be lowercase in Ambari
[
https://issues.apache.org/jira/browse/AMBARI-18813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas resolved AMBARI-18813.
---
Resolution: Fixed
Committed to branch-2.4
{noformat}
commit 34f0103f6d50d27fbeb1482e86a03daee7cff795
Author: Robert Levas
Date: Tue Apr 18 09:52:46 2017 -0400
{noformat}
> Optionally force username from LDAP authentication data to be lowercase in
> Ambari
> -
>
> Key: AMBARI-18813
> URL: https://issues.apache.org/jira/browse/AMBARI-18813
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: ldap
> Fix For: 2.5.0, 2.4.3
>
> Attachments: AMBARI-18813_branch-2.4_01.patch,
> AMBARI-18813_branch-2.5_01.patch, AMBARI-18813_trunk_01.patch
>
>
> Optionally force username from LDAP authentication data to be lowercase in
> Ambari based on LDAP import configuration.
> In some cases the username declared in the relevant LDAP object is in all
> uppercase characters when the local Hadoop cluster expects the username to be
> all lowercase. As of Ambari 2.4.0, the username specified from the LDAP data
> is used to override the username known to Ambari. This overwritten data may
> be in all uppercase characters, potentially breaking local username
> conventions.
> To help this scenario, provide a configuration option to force the username
> obtained from the LDAP object to be converted to all lowercase character.
> For example {{authentication.ldap.username.forceLowercase}}.
> This optional configuration value is to default to false to maintain current
> functionality.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20779) Create Ranger KMS HDFS audit folder as part of install
[
https://issues.apache.org/jira/browse/AMBARI-20779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972678#comment-15972678
]
Hadoop QA commented on AMBARI-20779:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12863763/AMBARI-20779-trunk.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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler 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/11407//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11407//console
This message is automatically generated.
> Create Ranger KMS HDFS audit folder as part of install
> --
>
> Key: AMBARI-20779
> URL: https://issues.apache.org/jira/browse/AMBARI-20779
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.1
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.5.1
>
> Attachments: AMBARI-20779.patch, AMBARI-20779-trunk.patch
>
>
> Create audit directory {{/ranger/audit/kms}} in hdfs, if
> {{xasecure.audit.destination.hdfs}} (Audit To HDFS) property is set to true.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19149) Clean up Ambari Server source code warnings
[ https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972660#comment-15972660 ] Hudson commented on AMBARI-19149: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7311 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7311/]) AMBARI-19149. Code cleanup: unresolved references in javadoc (adoroszlai: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8e2abf97bd2f10bad978d176a53bffd0ad2c7b67]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/Cluster.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/LdapServerProperties.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/HeartBeatResponse.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/DBAccessor.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/events/AlertDefinitionDisabledEvent.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/dao/ExtensionDAO.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog300.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AbstractProviderModule.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/rest/BootStrapResource.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/alerts/AlertEventPublisherTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ClusterTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/query/JpaSortBuilder.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/events/jpa/EntityManagerCacheInvalidationEvent.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/UpgradeEntity.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/repository/VersionDefinitionXml.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/HostOrderGrouping.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/orm/OrmTestHelper.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/resources/RequestScheduleResourceDefinition.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ServiceComponentHostConcurrentWriteDeadlockTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/events/listeners/alerts/AlertReceivedListener.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/configgroup/ConfigGroupImpl.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/orm/dao/HostRoleCommandDAOTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/alerts/InitialAlertEventTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/helpers/dbms/DbmsHelper.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ViewURLEntity.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/AlertDefinitionService.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/StackModule.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/services/MetricsRetrievalService.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/alerts/AlertDefinitionHashTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/events/EventsTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/api/query/JpaSortBuilderTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/dao/RequestDAO.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/ConfigImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/configgroup/ConfigGroupFactory.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/VersionDefinitionResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/UpgradeGroupEntity.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/ServicesUpCheck.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/dao/ExtensionLinkDAO.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/alert/AlertDefinitionHash.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/actionmanager/Stage.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/fsm/StateMachineFactory.java * (edit)
[jira] [Created] (AMBARI-20780) Update HBase Configuration group is ignored in upgrade.xml
Tim Thorpe created AMBARI-20780: --- Summary: Update HBase Configuration group is ignored in upgrade.xml Key: AMBARI-20780 URL: https://issues.apache.org/jira/browse/AMBARI-20780 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Reporter: Tim Thorpe Assignee: Tim Thorpe Fix For: trunk The Update HBase Configuration group is ignored in upgrade.xml because it has an invalid syntax. It should be of xsi:type="cluster" because it contains an execute-stage. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-18813) Optionally force username from LDAP authentication data to be lowercase in Ambari
[
https://issues.apache.org/jira/browse/AMBARI-18813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-18813:
--
Attachment: AMBARI-18813_branch-2.4_01.patch
> Optionally force username from LDAP authentication data to be lowercase in
> Ambari
> -
>
> Key: AMBARI-18813
> URL: https://issues.apache.org/jira/browse/AMBARI-18813
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: ldap
> Fix For: 2.5.0, 2.4.3
>
> Attachments: AMBARI-18813_branch-2.4_01.patch,
> AMBARI-18813_branch-2.5_01.patch, AMBARI-18813_trunk_01.patch
>
>
> Optionally force username from LDAP authentication data to be lowercase in
> Ambari based on LDAP import configuration.
> In some cases the username declared in the relevant LDAP object is in all
> uppercase characters when the local Hadoop cluster expects the username to be
> all lowercase. As of Ambari 2.4.0, the username specified from the LDAP data
> is used to override the username known to Ambari. This overwritten data may
> be in all uppercase characters, potentially breaking local username
> conventions.
> To help this scenario, provide a configuration option to force the username
> obtained from the LDAP object to be converted to all lowercase character.
> For example {{authentication.ldap.username.forceLowercase}}.
> This optional configuration value is to default to false to maintain current
> functionality.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Reopened] (AMBARI-18813) Optionally force username from LDAP authentication data to be lowercase in Ambari
[
https://issues.apache.org/jira/browse/AMBARI-18813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas reopened AMBARI-18813:
---
Reopening to apply patch to Ambari 2.4.3.
> Optionally force username from LDAP authentication data to be lowercase in
> Ambari
> -
>
> Key: AMBARI-18813
> URL: https://issues.apache.org/jira/browse/AMBARI-18813
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: ldap
> Fix For: 2.5.0, 2.4.3
>
> Attachments: AMBARI-18813_branch-2.5_01.patch,
> AMBARI-18813_trunk_01.patch
>
>
> Optionally force username from LDAP authentication data to be lowercase in
> Ambari based on LDAP import configuration.
> In some cases the username declared in the relevant LDAP object is in all
> uppercase characters when the local Hadoop cluster expects the username to be
> all lowercase. As of Ambari 2.4.0, the username specified from the LDAP data
> is used to override the username known to Ambari. This overwritten data may
> be in all uppercase characters, potentially breaking local username
> conventions.
> To help this scenario, provide a configuration option to force the username
> obtained from the LDAP object to be converted to all lowercase character.
> For example {{authentication.ldap.username.forceLowercase}}.
> This optional configuration value is to default to false to maintain current
> functionality.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-18813) Optionally force username from LDAP authentication data to be lowercase in Ambari
[
https://issues.apache.org/jira/browse/AMBARI-18813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-18813:
--
Fix Version/s: 2.4.3
> Optionally force username from LDAP authentication data to be lowercase in
> Ambari
> -
>
> Key: AMBARI-18813
> URL: https://issues.apache.org/jira/browse/AMBARI-18813
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: ldap
> Fix For: 2.5.0, 2.4.3
>
> Attachments: AMBARI-18813_branch-2.5_01.patch,
> AMBARI-18813_trunk_01.patch
>
>
> Optionally force username from LDAP authentication data to be lowercase in
> Ambari based on LDAP import configuration.
> In some cases the username declared in the relevant LDAP object is in all
> uppercase characters when the local Hadoop cluster expects the username to be
> all lowercase. As of Ambari 2.4.0, the username specified from the LDAP data
> is used to override the username known to Ambari. This overwritten data may
> be in all uppercase characters, potentially breaking local username
> conventions.
> To help this scenario, provide a configuration option to force the username
> obtained from the LDAP object to be converted to all lowercase character.
> For example {{authentication.ldap.username.forceLowercase}}.
> This optional configuration value is to default to false to maintain current
> functionality.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20779) Create Ranger KMS HDFS audit folder as part of install
[
https://issues.apache.org/jira/browse/AMBARI-20779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-20779:
-
Status: Patch Available (was: In Progress)
> Create Ranger KMS HDFS audit folder as part of install
> --
>
> Key: AMBARI-20779
> URL: https://issues.apache.org/jira/browse/AMBARI-20779
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.1
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.5.1
>
> Attachments: AMBARI-20779.patch, AMBARI-20779-trunk.patch
>
>
> Create audit directory {{/ranger/audit/kms}} in hdfs, if
> {{xasecure.audit.destination.hdfs}} (Audit To HDFS) property is set to true.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20779) Create Ranger KMS HDFS audit folder as part of install
[
https://issues.apache.org/jira/browse/AMBARI-20779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-20779:
-
Attachment: AMBARI-20779-trunk.patch
AMBARI-20779.patch
> Create Ranger KMS HDFS audit folder as part of install
> --
>
> Key: AMBARI-20779
> URL: https://issues.apache.org/jira/browse/AMBARI-20779
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.1
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.5.1
>
> Attachments: AMBARI-20779.patch, AMBARI-20779-trunk.patch
>
>
> Create audit directory {{/ranger/audit/kms}} in hdfs, if
> {{xasecure.audit.destination.hdfs}} (Audit To HDFS) property is set to true.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20779) Create Ranger KMS HDFS audit folder as part of install
Mugdha Varadkar created AMBARI-20779:
Summary: Create Ranger KMS HDFS audit folder as part of install
Key: AMBARI-20779
URL: https://issues.apache.org/jira/browse/AMBARI-20779
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.1
Reporter: Mugdha Varadkar
Assignee: Mugdha Varadkar
Fix For: 2.5.1
Create audit directory {{/ranger/audit/kms}} in hdfs, if
{{xasecure.audit.destination.hdfs}} (Audit To HDFS) property is set to true.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20775) VersionAdvertised should be set to False by default in stack_tool.py
[ https://issues.apache.org/jira/browse/AMBARI-20775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan updated AMBARI-20775: --- Status: Patch Available (was: Open) > VersionAdvertised should be set to False by default in stack_tool.py > > > Key: AMBARI-20775 > URL: https://issues.apache.org/jira/browse/AMBARI-20775 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.1 >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.1 > > Attachments: AMBARI-20775.patch > > > All the commands.json files should always contain the versionAdvertised > field. If versionAdvertised is not set in command.json then we should assume > that versionAdvertised=False when calling stack_tools.py -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20775) VersionAdvertised should be set to False by default in stack_tool.py
[ https://issues.apache.org/jira/browse/AMBARI-20775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan updated AMBARI-20775: --- Attachment: AMBARI-20775.patch > VersionAdvertised should be set to False by default in stack_tool.py > > > Key: AMBARI-20775 > URL: https://issues.apache.org/jira/browse/AMBARI-20775 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.1 >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.1 > > Attachments: AMBARI-20775.patch > > > All the commands.json files should always contain the versionAdvertised > field. If versionAdvertised is not set in command.json then we should assume > that versionAdvertised=False when calling stack_tools.py -- This message was sent by Atlassian JIRA (v6.3.15#6346)
