[jira] [Updated] (AMBARI-16852) Update metrics collector pom.xml to use httpclient-4.2.5.jar
[ https://issues.apache.org/jira/browse/AMBARI-16852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-16852: - Description: httpclient-4.0.1.jar used by AMS collector does not have method URLEncodedUtils.parse (final URI uri, final String encoding). This will cause the metrics not to be populated and the collector log to be flooded with the following exception when when the Ambari-Metrics service is in distributed mode and the user configures http authentication filter without enabling Kerberos: 21:54:08,215 ERROR [1831490216@qtp-1883237069-7582] log:87 - Error for /ws/v1/timeline/metrics java.lang.NoSuchMethodError: org.apache.http.client.utils.URLEncodedUtils.parse(Ljava/lang/String;Ljava/nio/charset/Charset;)Ljava/util/List; at org.apache.hadoop.security.authentication.server.PseudoAuthenticationHandler.getUserName(PseudoAuthenticationHandler.java:143) at org.apache.hadoop.security.authentication.server.PseudoAuthenticationHandler.authenticate(PseudoAuthenticationHandler.java:179) at org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:507) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at org.apache.hadoop.http.HttpServer2$QuotingInputFilter.doFilter(HttpServer2.java:1224) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at org.apache.hadoop.http.NoCacheFilter.doFilter(NoCacheFilter.java:45) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) Steps to reproduce: 1. install a cluster with default from Ambari Web UI 2. configure Ambari Metrics service in distributed mode 3. Add the following properties in Custom core-site from Ambari Web UI: 1). hadoop.http.authentication.signature.secret.file=/etc/security/http_secret 2). hadoop.http.filter.initializers=org.apache.hadoop.security.AuthenticationFilterInitializer 4. create /etc/security/http_secret text file on each node 5. restart HDFS, YARN, Mapreduce2, HBase, Kafka, and Ambari Metrics service 6. Metrics on dashboard and HDFS, YARN, HBase, Kafka, and Amabari Metrics will show No Data Available. was: httpclient-4.0.1.jar used by AMS collector does not have method URLEncodedUtils.parse (final URI uri, final String encoding). This will cause the metrics not to be populated and the collector log to be flooded with the following exception when when the Ambari-Metrics service is in distributed mode and the user configures http authentication filter without enabling Kerberos: 21:54:08,215 ERROR [1831490216@qtp-1883237069-7582] log:87 - Error for /ws/v1/timeline/metrics java.lang.NoSuchMethodError: org.apache.http.client.utils.URLEncodedUtils.parse(Ljava/lang/String;Ljava/nio/charset/Charset;)Ljava/util/List; at org.apache.hadoop.security.authentication.server.PseudoAuthenticationHandler.getUserName(PseudoAuthenticationHandler.java:143) at org.apache.hadoop.security.authentication.server.PseudoAuthenticationHandler.authenticate(PseudoAuthenticationHandler.java:179) at org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:507) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at org.apache.hadoop.http.HttpServer2$QuotingInputFilter.doFilter(HttpServer2.java:1224) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at org.apache.hadoop.http.NoCacheFilter.doFilter(NoCacheFilter.java:45) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) Steps to reproduce: 1. install a cluster with default from Ambari Web UI 2. configure Ambari Metrics service in distributed mode 3. Add the following properties in Custom core-site from Ambari Web UI: 1). hadoop.http.authentication.signature.secret.file=/etc/security/http_secret 2). hadoop.http.filter.initializers=org.apache.hadoop.security.AuthenticationFilterInitialize 4. create /etc/security/http_secret text file on each node 5. restart HDFS, YARN, Mapreduce2, HBase, Kafka, and Ambari Metrics service 6. Metrics on dashboard and HDFS, YARN, HBase, Kafka, and Amabari Metrics will show No Data Available. > Update metrics collector pom.xml to use httpclient-4.2.5.jar > > > Key: AMBARI-16852 >
[jira] [Updated] (AMBARI-17180) Fix HA enabled logic in the alerts
[ https://issues.apache.org/jira/browse/AMBARI-17180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-17180: Description: base_alert.py puts a warning into the log if there are properties referenced in the HA nameservice or the alias which are not present in the configuration. The absence of these properties is an indicator that the HA is not enabled, it is not a cause for warning. (was: base_alert.py puts a warning into the log if there are properties referenced in the HA nameservice or the alias which are not present. The absence of these properties is an indicator that the HA is not enabled, it is not a cause for warning.) > Fix HA enabled logic in the alerts > -- > > Key: AMBARI-17180 > URL: https://issues.apache.org/jira/browse/AMBARI-17180 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.4.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.4.0 > > > base_alert.py puts a warning into the log if there are properties referenced > in the HA nameservice or the alias which are not present in the > configuration. The absence of these properties is an indicator that the HA is > not enabled, it is not a cause for warning. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17180) Fix HA enabled logic in the alerts
[ https://issues.apache.org/jira/browse/AMBARI-17180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-17180: Description: base_alert.py puts a warning into the log if there are properties referenced in the HA nameservice or the alias which are not present. The absence of these properties is an indicator that the HA is not enabled, it is not a cause for warning. (was: base_alert.py puts a warning into the log if there are properties referenced in the HA nameservice or the alias which are not present. The abscence of these properties is an indicator that the HA is not enabled, it is not a cause for warning.) > Fix HA enabled logic in the alerts > -- > > Key: AMBARI-17180 > URL: https://issues.apache.org/jira/browse/AMBARI-17180 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.4.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.4.0 > > > base_alert.py puts a warning into the log if there are properties referenced > in the HA nameservice or the alias which are not present. The absence of > these properties is an indicator that the HA is not enabled, it is not a > cause for warning. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17180) Fix HA enabled logic in the alerts
[ https://issues.apache.org/jira/browse/AMBARI-17180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-17180: Description: base_alert.py puts a warning into the log if there are properties referenced in the HA nameservice or the alias which are not present. The abscence of these properties is an indicator that the HA is not enabled, it is not a cause for warning. (was: base_alert.py puts a warning into the log if there are properties referenced in the HA nameservice or the alias which are not present. The fact that these properties are not present is just an indicator that the HA is not enabled, it is not a cause for warning.) > Fix HA enabled logic in the alerts > -- > > Key: AMBARI-17180 > URL: https://issues.apache.org/jira/browse/AMBARI-17180 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.4.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.4.0 > > > base_alert.py puts a warning into the log if there are properties referenced > in the HA nameservice or the alias which are not present. The abscence of > these properties is an indicator that the HA is not enabled, it is not a > cause for warning. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17180) Fix HA enabled logic in the alerts
[ https://issues.apache.org/jira/browse/AMBARI-17180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-17180: Description: base_alert.py puts a warning into the log if there are properties referenced in the HA nameservice or the alias which are not present. The fact that these properties are not present is just an indicator that the HA is not enabled, it is not a cause for warning. (was: base_alert.py considers HA to be enabled even if the HA nameservice is referenced in the alias but there is no HA nameservice (not specified or the expression is not evaluable as it references properties that are not specified). ) > Fix HA enabled logic in the alerts > -- > > Key: AMBARI-17180 > URL: https://issues.apache.org/jira/browse/AMBARI-17180 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.4.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.4.0 > > > base_alert.py puts a warning into the log if there are properties referenced > in the HA nameservice or the alias which are not present. The fact that these > properties are not present is just an indicator that the HA is not enabled, > it is not a cause for warning. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17180) Fix HA enabled logic in the alerts
Miklos Gergely created AMBARI-17180: --- Summary: Fix HA enabled logic in the alerts Key: AMBARI-17180 URL: https://issues.apache.org/jira/browse/AMBARI-17180 Project: Ambari Issue Type: Bug Components: ambari-agent Affects Versions: 2.4.0 Reporter: Miklos Gergely Assignee: Miklos Gergely Fix For: 2.4.0 base_alert.py considers HA to be enabled even if the HA nameservice is referenced in the alias but there is no HA nameservice (not specified or the expression is not evaluable as it references properties that are not specified). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17179) Allow 'LLAP related calculations' to be done for any selected queue instead of existing for only 'llap' named queue.
Swapan Shridhar created AMBARI-17179: Summary: Allow 'LLAP related calculations' to be done for any selected queue instead of existing for only 'llap' named queue. Key: AMBARI-17179 URL: https://issues.apache.org/jira/browse/AMBARI-17179 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0 Reporter: Swapan Shridhar Assignee: Swapan Shridhar Fix For: 2.4.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17118) Incorrect formated external url in ranger configuration - causes Namenode startup failure
[
https://issues.apache.org/jira/browse/AMBARI-17118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325993#comment-15325993
]
Hudson commented on AMBARI-17118:
-
FAILURE: Integrated in Ambari-trunk-Commit #5060 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5060/])
Revert "AMBARI-17118. Incorrect formated external url in ranger (smohanty:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=dc048aaa52cba4333ee0b350a900ba82302dedbc])
* ambari-server/src/main/resources/stacks/HDP/2.3/services/stack_advisor.py
*
ambari-server/src/main/resources/common-services/RANGER_KMS/0.5.0.2.3/package/scripts/params.py
*
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py
*
ambari-server/src/main/resources/common-services/STORM/0.9.1/package/scripts/params_linux.py
*
ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/package/scripts/params_linux.py
*
ambari-common/src/main/python/resource_management/libraries/functions/setup_ranger_plugin_xml.py
*
ambari-server/src/main/resources/common-services/RANGER_KMS/0.5.0.2.3/package/scripts/kms.py
*
ambari-common/src/main/python/resource_management/libraries/functions/ranger_functions_v2.py
*
ambari-common/src/main/python/resource_management/libraries/functions/ranger_functions.py
*
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py
*
ambari-server/src/main/resources/common-services/KAFKA/0.8.1/package/scripts/params.py
*
ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/scripts/params_linux.py
*
ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/params.py
*
ambari-server/src/main/resources/stacks/HDP/2.5/services/HDFS/configuration/ranger-hdfs-plugin-properties.xml
* ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py
*
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py
*
ambari-common/src/main/python/resource_management/libraries/functions/setup_ranger_plugin.py
> Incorrect formated external url in ranger configuration - causes Namenode
> startup failure
> -
>
> Key: AMBARI-17118
> URL: https://issues.apache.org/jira/browse/AMBARI-17118
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.1.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.4.0
>
> Attachments: AMBARI-17118.1.patch, AMBARI-17118.patch
>
>
> STR:
> 1. install ambari and HDP with HDFS,YARN,HIVE
> 2. install ranger and configure *External URL*
> https://c6401.ambari.apache.org:6182/ ( means slash at the end of the URL
> which is allowed without any problem and installation is done successfully)
> 3. enable ranger plugin in hdfs config and restart it
> Result: NN startup fails and even after failure , error message in stack
> trace is confusing
> ERROR:
> ==
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/ranger_functions.py",
> line 108, in create_ranger_repository
> raise Fail('Ambari admin username and password are blank ')
> resource_management.core.exceptions.Fail: Ambari admin username and password
> are blank
> but actual reason is a slash at the end of the External URL,
> it fails the following point in
> usr/lib/python2.6/site-packages/resource_management/libraries/functions/ranger_functions.py:
> result = urllib2.urlopen(request)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17178) Tez View: Load public host names
[ https://issues.apache.org/jira/browse/AMBARI-17178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated AMBARI-17178: Fix Version/s: (was: ambari-2.4.0) > Tez View: Load public host names > > > Key: AMBARI-17178 > URL: https://issues.apache.org/jira/browse/AMBARI-17178 > Project: Ambari > Issue Type: Bug >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Attachments: AMBARI-17178.1.patch > > > Load public_host_name, parse and set the cnames configuration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17178) Tez View: Load public host names
[ https://issues.apache.org/jira/browse/AMBARI-17178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated AMBARI-17178: Status: Patch Available (was: Open) > Tez View: Load public host names > > > Key: AMBARI-17178 > URL: https://issues.apache.org/jira/browse/AMBARI-17178 > Project: Ambari > Issue Type: Bug >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Fix For: ambari-2.4.0 > > Attachments: AMBARI-17178.1.patch > > > Load public_host_name, parse and set the cnames configuration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-17118) Incorrect formated external url in ranger configuration - causes Namenode startup failure
[
https://issues.apache.org/jira/browse/AMBARI-17118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty reopened AMBARI-17118:
> Incorrect formated external url in ranger configuration - causes Namenode
> startup failure
> -
>
> Key: AMBARI-17118
> URL: https://issues.apache.org/jira/browse/AMBARI-17118
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.1.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.4.0
>
> Attachments: AMBARI-17118.1.patch, AMBARI-17118.patch
>
>
> STR:
> 1. install ambari and HDP with HDFS,YARN,HIVE
> 2. install ranger and configure *External URL*
> https://c6401.ambari.apache.org:6182/ ( means slash at the end of the URL
> which is allowed without any problem and installation is done successfully)
> 3. enable ranger plugin in hdfs config and restart it
> Result: NN startup fails and even after failure , error message in stack
> trace is confusing
> ERROR:
> ==
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/ranger_functions.py",
> line 108, in create_ranger_repository
> raise Fail('Ambari admin username and password are blank ')
> resource_management.core.exceptions.Fail: Ambari admin username and password
> are blank
> but actual reason is a slash at the end of the External URL,
> it fails the following point in
> usr/lib/python2.6/site-packages/resource_management/libraries/functions/ranger_functions.py:
> result = urllib2.urlopen(request)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-17178) Tez View: Load public host names
Sreenath Somarajapuram created AMBARI-17178: --- Summary: Tez View: Load public host names Key: AMBARI-17178 URL: https://issues.apache.org/jira/browse/AMBARI-17178 Project: Ambari Issue Type: Bug Reporter: Sreenath Somarajapuram Assignee: Sreenath Somarajapuram Fix For: ambari-2.4.0 Load public_host_name, parse and set the cnames configuration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17177) Add SERVICE.VIEW_OPERATIONAL_LOGS authorization to SERVICE.ADMINISTRATOR role and above
Robert Levas created AMBARI-17177:
-
Summary: Add SERVICE.VIEW_OPERATIONAL_LOGS authorization to
SERVICE.ADMINISTRATOR role and above
Key: AMBARI-17177
URL: https://issues.apache.org/jira/browse/AMBARI-17177
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.4.0
Reporter: Robert Levas
Assignee: Robert Levas
Priority: Critical
Fix For: 2.4.0
Add SERVICE.VIEW_OPERATIONAL_LOGS authorization to the following roles:
* AMBARI.ADMINISTRATOR
* CLUSTER.ADMINISTRATOR
* CLUSTER.OPERATOR
* SERVICE.ADMINISTRATOR
This is a DB change adding an authorization record to the {{roleauthorization}}
table and relevant records for the different roles to the
{{permission_roleauthorization}} table.
The description/name of the {{SERVICE.VIEW_OPERATIONAL_LOGS}} authorization
should be
{noformat}
View service operational logs
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17053) Add explicit ambari-server log line indicating cluster creation complete
[ https://issues.apache.org/jira/browse/AMBARI-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Gergely updated AMBARI-17053: Attachment: AMBARI-17053_branch-2.4_and_trunk.patch AMBARI-17053_2.2-next.patch > Add explicit ambari-server log line indicating cluster creation complete > > > Key: AMBARI-17053 > URL: https://issues.apache.org/jira/browse/AMBARI-17053 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: Daniel Gergely >Assignee: Daniel Gergely > Fix For: 2.4.0, 2.2-next > > Attachments: AMBARI-17053_2.2-next.patch, > AMBARI-17053_branch-2.4_and_trunk.patch > > > Add a log message to see when the cluster is ready to use (cluster creation > finishes) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17053) Add explicit ambari-server log line indicating cluster creation complete
[ https://issues.apache.org/jira/browse/AMBARI-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Gergely updated AMBARI-17053: Attachment: (was: AMBARI-17053_2.2-next.patch) > Add explicit ambari-server log line indicating cluster creation complete > > > Key: AMBARI-17053 > URL: https://issues.apache.org/jira/browse/AMBARI-17053 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: Daniel Gergely >Assignee: Daniel Gergely > Fix For: 2.4.0, 2.2-next > > > Add a log message to see when the cluster is ready to use (cluster creation > finishes) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17053) Add explicit ambari-server log line indicating cluster creation complete
[ https://issues.apache.org/jira/browse/AMBARI-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Gergely updated AMBARI-17053: Attachment: (was: AMBARI-17053_branch-2.4_and_trunk.patch) > Add explicit ambari-server log line indicating cluster creation complete > > > Key: AMBARI-17053 > URL: https://issues.apache.org/jira/browse/AMBARI-17053 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: Daniel Gergely >Assignee: Daniel Gergely > Fix For: 2.4.0, 2.2-next > > > Add a log message to see when the cluster is ready to use (cluster creation > finishes) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
