[jira] [Created] (AMBARI-17077) Unable to change user role in list view

[Richard Zang (JIRA)]

Richard Zang created AMBARI-17077:
-

 Summary: Unable to change user role in list view
 Key: AMBARI-17077
 URL: https://issues.apache.org/jira/browse/AMBARI-17077
 Project: Ambari
  Issue Type: Bug
  Components: ambari-admin
Affects Versions: 2.4.0
Reporter: Richard Zang
Assignee: Richard Zang
 Fix For: 2.4.0


STR:
1. Go to Manage Ambari.
2. Create user.
3. Go to Roles menu, list view.
4. Set role for newly created user.
5. Change role for that user.

{noformat}Cannot save permissions
t's effective privilege through its Group(s) is higher than your selected 
privilege.{noformat}

No goups was created.

Workaround: change role to None and then change to desired value.



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

[jira] [Commented] (AMBARI-17047) Firewall check returns WARNING even if iptables and firewalld are stopped on CentOS7

[Masahiro Tanaka (JIRA)]

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

Masahiro Tanaka commented on AMBARI-17047:
--

BTW, I would like to be the assignee of this issue, but I can't. (There is no 
"Assign to me" Button)
How can I assign issues to myself ?

> Firewall check returns WARNING even if iptables and firewalld are stopped on 
> CentOS7
> 
>
> Key: AMBARI-17047
> URL: https://issues.apache.org/jira/browse/AMBARI-17047
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent, ambari-server
>Affects Versions: trunk
> Environment: CentOS7.2
>Reporter: Masahiro Tanaka
>  Labels: patch
> Attachments: AMBARI-17047.patch
>
>
> In firewall.py, {{"systemctl is-active iptables || systemctl is-active 
> firewalld"}} is passed to {{run_in_shell}} function, which splits cmd string 
> by using {{shlex.split}}.
> {{run_in_shell}} function finally calls {{subprocess.Popen}} with 
> {{shell=True}}, so the cmd string is evaluated like {{Popen(['/bin/sh', '-c', 
> 'systemctl', 'is-active', 'iptables', '||', 'systemctl', 'is-active', 
> 'firewalld'])}}. This doesn't returns values as expected, because after 
> args[1] (in this case, after the first {{is-active}}) are evaluated as sh 
> arguements.
> {{systemctl is-active}} can take multiple arugments, so we can use it.



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

[jira] [Commented] (AMBARI-17070) Change HAWQ DFS Url from hawq_default to hawq_data

[Hudson (JIRA)]

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

Hudson commented on AMBARI-17070:
-

FAILURE: Integrated in Ambari-trunk-Commit #5016 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5016/])
AMBARI-17070: Change HAWQ DFS Url from hawq_default to hawq_data (matt: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=13248dc109217be1f902b5bbeb3f228cf839c8ce])
* 
ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/params.py
* ambari-web/test/utils/configs/config_initializer_test.js
* ambari-web/app/data/HDP2/ha_properties.js
* ambari-server/src/test/python/stacks/2.3/HAWQ/test_hawqmaster.py
* 
ambari-web/test/controllers/main/admin/highAvailability/nameNode/step3_controller_test.js
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java
* 
ambari-server/src/main/resources/common-services/HAWQ/2.0.0/configuration/hawq-site.xml
* ambari-server/src/test/python/stacks/2.3/configs/hawq_default.json


> Change HAWQ DFS Url from hawq_default to hawq_data
> --
>
> Key: AMBARI-17070
> URL: https://issues.apache.org/jira/browse/AMBARI-17070
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server, ambari-web, stacks
>Reporter: Matt
>Assignee: Matt
>Priority: Trivial
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-17070-trunk-orig.patch
>
>
> Change HAWQ DFS Url from hawq_default to hawq_data



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

[jira] [Commented] (AMBARI-17072) Make QuickLink to HS2 UI work when HTTPS is enabled

[Hudson (JIRA)]

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

Hudson commented on AMBARI-17072:
-

FAILURE: Integrated in Ambari-trunk-Commit #5015 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5015/])
AMBARI-17072. Make QuickLink to HS2 UI work when HTTPS is enabled. (jaimin: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=cd93321095ed32b4242905033f5a0f3769935134])
* 
ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/hive-interactive-site.xml
* 
ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/quicklinks/quicklinks.json


> Make QuickLink to HS2 UI work when HTTPS is enabled
> ---
>
> Key: AMBARI-17072
> URL: https://issues.apache.org/jira/browse/AMBARI-17072
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
> Fix For: 2.4.0
>
> Attachments: AMBARI-17072.patch
>
>
> There are a two important hive-site.xml parameters that govern the url:
> i) hive.server2.webui.port : This is the port on which the webui hosts itself.
> ii) hive.server2.webui.use.ssl : Whether or not ssl is used.
> If ssl is used, we use https:// and if not, we use http:// . Either way, the 
> service seems to be intended to be hosted at :/llap.html 
> this will work only for hive2 and not hive1.



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

[jira] [Commented] (AMBARI-17067) Microsoft-r install script should use Ambari libraries instead of direct shell calls

[Hudson (JIRA)]

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

Hudson commented on AMBARI-17067:
-

FAILURE: Integrated in Ambari-trunk-Commit #5015 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5015/])
AMBARI-17067. Microsoft-r install script should use Ambari libraries (sgunturi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=edc3ac53833a3e212b0567cc683353275667b9f6])
* contrib/management-packs/microsoft-r_mpack/src/main/resources/mpack.json
* 
contrib/management-packs/microsoft-r_mpack/src/main/resources/common-services/MICROSOFT_R/8.0.0/package/scripts/microsoft_r.py


> Microsoft-r install script should use Ambari libraries instead of direct 
> shell calls
> 
>
> Key: AMBARI-17067
> URL: https://issues.apache.org/jira/browse/AMBARI-17067
> Project: Ambari
>  Issue Type: Task
>  Components: contrib
>Affects Versions: 2.4.0
>Reporter: Balázs Bence Sári
>Assignee: Balázs Bence Sári
>Priority: Critical
> Fix For: 2.4.1
>
> Attachments: diff1-trunk.patch
>
>
> In the install script of the management-pack we do everything using shell 
> calls. Instead we should use Ambari's python libraries.
> Example:
> {code}shell.call('sudo -u hdfs hadoop fs -mkdir -p /share'){code}
> As reference you can use the scripts of HDFS: 
> [https://github.com/apache/ambari/tree/trunk/ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts]
>  which make good use of Ambari libraries. Microsoft-R scripts should use just 
> like these.



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

[jira] [Commented] (AMBARI-17070) Change HAWQ DFS Url from hawq_default to hawq_data

[Matt (JIRA)]

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

Matt commented on AMBARI-17070:
---

The above test failure is not related to this patch.

> Change HAWQ DFS Url from hawq_default to hawq_data
> --
>
> Key: AMBARI-17070
> URL: https://issues.apache.org/jira/browse/AMBARI-17070
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server, ambari-web, stacks
>Reporter: Matt
>Assignee: Matt
>Priority: Trivial
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-17070-trunk-orig.patch
>
>
> Change HAWQ DFS Url from hawq_default to hawq_data



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

[jira] [Commented] (AMBARI-17071) VDF: exception when trying to register -> add versions

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-17071:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12808470/AMBARI-17071.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in 
ambari-server:

  org.apache.ambari.server.state.ServicePropertiesTest

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

This message is automatically generated.

> VDF: exception when trying to register -> add versions
> --
>
> Key: AMBARI-17071
> URL: https://issues.apache.org/jira/browse/AMBARI-17071
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17071.patch
>
>
> # Start install wizard, select HDP-2.4, Add Version -> use 2.4.0.0 VDF
> # Click local, click Satellite, confirm, next to move on
> # HDFS + ZK + AMS, install
> # all is fine so far
> # go to Register version
> # click on HDP 2.4 -> add version-> use 2.4.2.0 VDF, which uses the same url 
> as (1)
> # Click local, click Satellite, confirm, click save, EXCEPTION



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

[jira] [Created] (AMBARI-17079) Moved Hue to Ambari migrator to standard view architecture

[Pradarttana (JIRA)]

Pradarttana created AMBARI-17079:


 Summary: Moved Hue to Ambari migrator to standard view 
architecture 
 Key: AMBARI-17079
 URL: https://issues.apache.org/jira/browse/AMBARI-17079
 Project: Ambari
  Issue Type: Bug
  Components: ambari-views
Affects Versions: ambari-2.4.0
Reporter: Pradarttana
 Fix For: ambari-2.4.0


Moved Hue to Ambari Migrator to standard Ambari view architecture. A backend to 
provide API and front end is single page ember application.



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

[jira] [Created] (AMBARI-17078) Make Spark2-ThriftServer and Livy Server as optional by default

[Jeff Zhang (JIRA)]

Jeff Zhang created AMBARI-17078:
---

 Summary: Make Spark2-ThriftServer and Livy Server as optional by 
default
 Key: AMBARI-17078
 URL: https://issues.apache.org/jira/browse/AMBARI-17078
 Project: Ambari
  Issue Type: Bug
Reporter: Jeff Zhang
Assignee: Jeff Zhang


Currently they are selected by default,  but should be non-selected by default. 



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

[jira] [Updated] (AMBARI-16663) Refactor service_advisor apis to remove passing of stack_advisor

[Lav Jain (JIRA)]

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

Lav Jain updated AMBARI-16663:
--
Attachment: AMBARI-16663.v4.patch

> Refactor service_advisor apis to remove passing of stack_advisor
> 
>
> Key: AMBARI-16663
> URL: https://issues.apache.org/jira/browse/AMBARI-16663
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16663.branch24.patch, 
> AMBARI-16663.branch24.v2.patch, AMBARI-16663.branch24.v3.patch, 
> AMBARI-16663.branch24.v4.patch, AMBARI-16663.patch, AMBARI-16663.v2.patch, 
> AMBARI-16663.v3.patch, AMBARI-16663.v4.patch
>
>




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

[jira] [Updated] (AMBARI-16663) Refactor service_advisor apis to remove passing of stack_advisor

[Lav Jain (JIRA)]

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

Lav Jain updated AMBARI-16663:
--
Attachment: AMBARI-16663.branch24.v4.patch

> Refactor service_advisor apis to remove passing of stack_advisor
> 
>
> Key: AMBARI-16663
> URL: https://issues.apache.org/jira/browse/AMBARI-16663
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16663.branch24.patch, 
> AMBARI-16663.branch24.v2.patch, AMBARI-16663.branch24.v3.patch, 
> AMBARI-16663.branch24.v4.patch, AMBARI-16663.patch, AMBARI-16663.v2.patch, 
> AMBARI-16663.v3.patch
>
>




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

[jira] [Commented] (AMBARI-17070) Change HAWQ DFS Url from hawq_default to hawq_data

[Matt (JIRA)]

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

Matt commented on AMBARI-17070:
---

Committed to trunk:
{code}
commit 13248dc109217be1f902b5bbeb3f228cf839c8ce
Author: Matt 
Date:   Mon Jun 6 20:53:42 2016 -0700
{code}
Committed to branch-2.4:
{code}
commit a3b4be1de90979eac5f33958d587c23fb3285a37
Author: Matt 
Date:   Mon Jun 6 20:52:47 2016 -0700
{code}
Marking as resolved.

> Change HAWQ DFS Url from hawq_default to hawq_data
> --
>
> Key: AMBARI-17070
> URL: https://issues.apache.org/jira/browse/AMBARI-17070
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server, ambari-web, stacks
>Reporter: Matt
>Assignee: Matt
>Priority: Trivial
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-17070-trunk-orig.patch
>
>
> Change HAWQ DFS Url from hawq_default to hawq_data



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

[jira] [Updated] (AMBARI-17070) Change HAWQ DFS Url from hawq_default to hawq_data

[Matt (JIRA)]

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

Matt updated AMBARI-17070:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Change HAWQ DFS Url from hawq_default to hawq_data
> --
>
> Key: AMBARI-17070
> URL: https://issues.apache.org/jira/browse/AMBARI-17070
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server, ambari-web, stacks
>Reporter: Matt
>Assignee: Matt
>Priority: Trivial
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-17070-trunk-orig.patch
>
>
> Change HAWQ DFS Url from hawq_default to hawq_data



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

[jira] [Commented] (AMBARI-17073) HDF Management install does not allow one to select public repo

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-17073:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12808515/AMBARI-17073.v1.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-web.

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

This message is automatically generated.

> HDF Management install does not allow one to select public repo
> ---
>
> Key: AMBARI-17073
> URL: https://issues.apache.org/jira/browse/AMBARI-17073
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
> Fix For: 2.4.0
>
> Attachments: AMBARI-17073.v0.patch, AMBARI-17073.v1.patch
>
>
> To fulfill the requirement of enforcing users to choose local repo when they 
> don’t have internet access, in FE we use the logic of checking whether all 
> versions are stack_default versions. That logic is true for HDP for now, but 
> not for HDF.



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

[jira] [Commented] (AMBARI-16852) Update metrics collector pom.xml to use httpclient-4.2.5.jar

[Dmytro Sen (JIRA)]

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

Dmytro Sen commented on AMBARI-16852:
-

Test failures aren't related to this jira.

> Update metrics collector pom.xml to use httpclient-4.2.5.jar
> 
>
> Key: AMBARI-16852
> URL: https://issues.apache.org/jira/browse/AMBARI-16852
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Qin Liu
>Assignee: Qin Liu
> Fix For: 2.4.0
>
> Attachments: AMBARI-16852.patch
>
>
> 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.



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

[jira] [Updated] (AMBARI-17077) Unable to change user role in list view

[Richard Zang (JIRA)]

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

Richard Zang updated AMBARI-17077:
--
Status: Patch Available  (was: Open)

> Unable to change user role in list view
> ---
>
> Key: AMBARI-17077
> URL: https://issues.apache.org/jira/browse/AMBARI-17077
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: 2.4.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.4.0
>
> Attachments: AMBARI-17077.patch
>
>
> STR:
> 1. Go to Manage Ambari.
> 2. Create user.
> 3. Go to Roles menu, list view.
> 4. Set role for newly created user.
> 5. Change role for that user.
> {noformat}Cannot save permissions
> t's effective privilege through its Group(s) is higher than your selected 
> privilege.{noformat}
> No goups was created.
> Workaround: change role to None and then change to desired value.



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

[jira] [Commented] (AMBARI-17073) HDF Management install does not allow one to select public repo

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-17073:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12808515/AMBARI-17073.v1.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-web.

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

This message is automatically generated.

> HDF Management install does not allow one to select public repo
> ---
>
> Key: AMBARI-17073
> URL: https://issues.apache.org/jira/browse/AMBARI-17073
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
> Fix For: 2.4.0
>
> Attachments: AMBARI-17073.v0.patch, AMBARI-17073.v1.patch
>
>
> To fulfill the requirement of enforcing users to choose local repo when they 
> don’t have internet access, in FE we use the logic of checking whether all 
> versions are stack_default versions. That logic is true for HDP for now, but 
> not for HDF.



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

[jira] [Commented] (AMBARI-17022) VDF: install wizard "Select Version" UI issues

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-17022:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12808523/AMBARI-17022.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-web.

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

This message is automatically generated.

> VDF: install wizard "Select Version" UI issues
> --
>
> Key: AMBARI-17022
> URL: https://issues.apache.org/jira/browse/AMBARI-17022
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Xi Wang
>Assignee: Xi Wang
>Priority: Critical
>  Labels: vdf
> Fix For: 2.4.0
>
> Attachments: AMBARI-17022.patch
>
>




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

[jira] [Updated] (AMBARI-16663) Refactor service_advisor apis to remove passing of stack_advisor

[Lav Jain (JIRA)]

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

Lav Jain updated AMBARI-16663:
--
Status: Patch Available  (was: In Progress)

> Refactor service_advisor apis to remove passing of stack_advisor
> 
>
> Key: AMBARI-16663
> URL: https://issues.apache.org/jira/browse/AMBARI-16663
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16663.branch24.patch, 
> AMBARI-16663.branch24.v2.patch, AMBARI-16663.branch24.v3.patch, 
> AMBARI-16663.branch24.v4.patch, AMBARI-16663.patch, AMBARI-16663.v2.patch, 
> AMBARI-16663.v3.patch, AMBARI-16663.v4.patch
>
>




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

[jira] [Commented] (AMBARI-16663) Refactor service_advisor apis to remove passing of stack_advisor

[Lav Jain (JIRA)]

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

Lav Jain commented on AMBARI-16663:
---

Rebased to trunk code

> Refactor service_advisor apis to remove passing of stack_advisor
> 
>
> Key: AMBARI-16663
> URL: https://issues.apache.org/jira/browse/AMBARI-16663
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16663.branch24.patch, 
> AMBARI-16663.branch24.v2.patch, AMBARI-16663.branch24.v3.patch, 
> AMBARI-16663.branch24.v4.patch, AMBARI-16663.patch, AMBARI-16663.v2.patch, 
> AMBARI-16663.v3.patch, AMBARI-16663.v4.patch
>
>




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

[jira] [Updated] (AMBARI-16663) Refactor service_advisor apis to remove passing of stack_advisor

[Lav Jain (JIRA)]

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

Lav Jain updated AMBARI-16663:
--
Status: In Progress  (was: Patch Available)

> Refactor service_advisor apis to remove passing of stack_advisor
> 
>
> Key: AMBARI-16663
> URL: https://issues.apache.org/jira/browse/AMBARI-16663
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16663.branch24.patch, 
> AMBARI-16663.branch24.v2.patch, AMBARI-16663.branch24.v3.patch, 
> AMBARI-16663.branch24.v4.patch, AMBARI-16663.patch, AMBARI-16663.v2.patch, 
> AMBARI-16663.v3.patch, AMBARI-16663.v4.patch
>
>




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

[jira] [Commented] (AMBARI-17075) Set 'hive.server2.tez.default.queues' config value to be the one used by config "hive.llap.daemon.queue.name" for 'llap' app.

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-17075:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12808513/AMBARI-17075.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The test build failed in ambari-server 

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

This message is automatically generated.

> Set 'hive.server2.tez.default.queues' config value to be the one used by 
> config "hive.llap.daemon.queue.name" for 'llap' app.
> -
>
> Key: AMBARI-17075
> URL: https://issues.apache.org/jira/browse/AMBARI-17075
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.4.0
>
> Attachments: AMBARI-17075.patch
>
>
> - Currently, 'hive.server2.tez.default.queues' config value is set to 
> 'default'.
> - Need to update it with the value of 'hive.llap.daemon.queue.name'.



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

[jira] [Commented] (AMBARI-16663) Refactor service_advisor apis to remove passing of stack_advisor

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-16663:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12808544/AMBARI-16663.v4.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 3 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The test build failed in ambari-server 

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

This message is automatically generated.

> Refactor service_advisor apis to remove passing of stack_advisor
> 
>
> Key: AMBARI-16663
> URL: https://issues.apache.org/jira/browse/AMBARI-16663
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16663.branch24.patch, 
> AMBARI-16663.branch24.v2.patch, AMBARI-16663.branch24.v3.patch, 
> AMBARI-16663.branch24.v4.patch, AMBARI-16663.patch, AMBARI-16663.v2.patch, 
> AMBARI-16663.v3.patch, AMBARI-16663.v4.patch
>
>




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

[jira] [Commented] (AMBARI-17077) Unable to change user role in list view

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-17077:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12808539/AMBARI-17077.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-admin.

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

This message is automatically generated.

> Unable to change user role in list view
> ---
>
> Key: AMBARI-17077
> URL: https://issues.apache.org/jira/browse/AMBARI-17077
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: 2.4.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.4.0
>
> Attachments: AMBARI-17077.patch
>
>
> STR:
> 1. Go to Manage Ambari.
> 2. Create user.
> 3. Go to Roles menu, list view.
> 4. Set role for newly created user.
> 5. Change role for that user.
> {noformat}Cannot save permissions
> t's effective privilege through its Group(s) is higher than your selected 
> privilege.{noformat}
> No goups was created.
> Workaround: change role to None and then change to desired value.



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

[jira] [Updated] (AMBARI-17077) Unable to change user role in list view

[Richard Zang (JIRA)]

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

Richard Zang updated AMBARI-17077:
--
Attachment: AMBARI-17077.patch

> Unable to change user role in list view
> ---
>
> Key: AMBARI-17077
> URL: https://issues.apache.org/jira/browse/AMBARI-17077
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: 2.4.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.4.0
>
> Attachments: AMBARI-17077.patch
>
>
> STR:
> 1. Go to Manage Ambari.
> 2. Create user.
> 3. Go to Roles menu, list view.
> 4. Set role for newly created user.
> 5. Change role for that user.
> {noformat}Cannot save permissions
> t's effective privilege through its Group(s) is higher than your selected 
> privilege.{noformat}
> No goups was created.
> Workaround: change role to None and then change to desired value.



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

[jira] [Commented] (AMBARI-16663) Refactor service_advisor apis to remove passing of stack_advisor

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-16663:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12808544/AMBARI-16663.v4.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 3 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The test build failed in ambari-server 

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

This message is automatically generated.

> Refactor service_advisor apis to remove passing of stack_advisor
> 
>
> Key: AMBARI-16663
> URL: https://issues.apache.org/jira/browse/AMBARI-16663
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16663.branch24.patch, 
> AMBARI-16663.branch24.v2.patch, AMBARI-16663.branch24.v3.patch, 
> AMBARI-16663.branch24.v4.patch, AMBARI-16663.patch, AMBARI-16663.v2.patch, 
> AMBARI-16663.v3.patch, AMBARI-16663.v4.patch
>
>




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

[jira] [Created] (AMBARI-17053) Add explicit ambari-server log line indicating cluster creation complete

[Daniel Gergely (JIRA)]

Daniel Gergely created AMBARI-17053:
---

 Summary: 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-17022) VDF: install wizard "Select Version" UI issues

[Xi Wang (JIRA)]

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

Xi Wang updated AMBARI-17022:
-
Status: Patch Available  (was: Open)

> VDF: install wizard "Select Version" UI issues
> --
>
> Key: AMBARI-17022
> URL: https://issues.apache.org/jira/browse/AMBARI-17022
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Xi Wang
>Assignee: Xi Wang
>Priority: Critical
>  Labels: vdf
> Fix For: 2.4.0
>
> Attachments: AMBARI-17022.patch
>
>




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

[jira] [Updated] (AMBARI-17022) VDF: install wizard "Select Version" UI issues

[Xi Wang (JIRA)]

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

Xi Wang updated AMBARI-17022:
-
Attachment: AMBARI-17022.patch

> VDF: install wizard "Select Version" UI issues
> --
>
> Key: AMBARI-17022
> URL: https://issues.apache.org/jira/browse/AMBARI-17022
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Xi Wang
>Assignee: Xi Wang
>Priority: Critical
>  Labels: vdf
> Fix For: 2.4.0
>
> Attachments: AMBARI-17022.patch
>
>




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

[jira] [Commented] (AMBARI-17076) Hive view 2.0.0 Instance has issues connecting to database in secure mode

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-17076:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12808514/AMBARI-17076.trunk.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
contrib/views/hive-next.

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

This message is automatically generated.

> Hive view 2.0.0 Instance has issues connecting to database in secure mode
> -
>
> Key: AMBARI-17076
> URL: https://issues.apache.org/jira/browse/AMBARI-17076
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Ashwin Rajeev
>Assignee: Ashwin Rajeev
> Fix For: 2.4.0
>
> Attachments: AMBARI-17076.trunk.patch
>
>




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

[jira] [Updated] (AMBARI-17055) Show better error message when VIEW USER can not access CAPACITY SCHEDULER View

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-17055:
--
Status: Patch Available  (was: Open)

> Show better error message when VIEW USER can not access CAPACITY SCHEDULER 
> View
> ---
>
> Key: AMBARI-17055
> URL: https://issues.apache.org/jira/browse/AMBARI-17055
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.2.2
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
>
> When view user does not have cluster read permission, view will fail with 
> error.
> Show better error message indicating user does not have permission to view 
> the configurations.
> org.apache.ambari.view.utils.ambari.AmbariApiException: RA040 I/O error while 
> requesting Ambari
> at 
> org.apache.ambari.view.utils.ambari.AmbariApi.requestClusterAPI(AmbariApi.java:176)
> at 
> org.apache.ambari.view.utils.ambari.AmbariApi.requestClusterAPI(AmbariApi.java:142)
> at 
> org.apache.ambari.view.capacityscheduler.ConfigurationService.readFromCluster(ConfigurationService.java:291)
> at 
> org.apache.ambari.view.capacityscheduler.ConfigurationService.readClusterInfo(ConfigurationService.java:148)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at 
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:540)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:715)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:770)
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1496)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
> at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118)
> at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84)
> at 
> 

[jira] [Updated] (AMBARI-17057) RBAC: when on List view, Roles is not selected

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander updated AMBARI-17057:
-
Attachment: AMBARI-17057.patch

> RBAC: when on List view, Roles is not selected
> --
>
> Key: AMBARI-17057
> URL: https://issues.apache.org/jira/browse/AMBARI-17057
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-17057.patch
>
>
>  Block view has Roles highlighted. List view does not.
> Should have Roles highlighted in List view for consistency.



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

[jira] [Commented] (AMBARI-17058) RBAC: missing Delete Service support

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko commented on AMBARI-17058:
--

+1 for the patch

> RBAC: missing Delete Service support
> 
>
> Key: AMBARI-17058
> URL: https://issues.apache.org/jira/browse/AMBARI-17058
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-17058.patch
>
>
> 1. Only Cluster Administrators (and hence Ambari Admins should be able to 
> Delete service).
> 2. Need to make sure the popup table in Admin UI includes Delete Service in 
> list (and only checkbox for ClusterAdmins + Ambari Admins
> 3. Need to make sure that Delete in the Service Actions is not available for 
> the other roles



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

[jira] [Updated] (AMBARI-17056) View config-Custom views are not working after kerberization

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-17056:
--
Status: Patch Available  (was: Open)

> View config-Custom views are not working after kerberization
> 
>
> Key: AMBARI-17056
> URL: https://issues.apache.org/jira/browse/AMBARI-17056
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: screenshot.png
>
>
> custom views are not working after kerberos is enabled.



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

[jira] [Updated] (AMBARI-17057) RBAC: when on List view, Roles is not selected

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander updated AMBARI-17057:
-
Status: Patch Available  (was: Open)

> RBAC: when on List view, Roles is not selected
> --
>
> Key: AMBARI-17057
> URL: https://issues.apache.org/jira/browse/AMBARI-17057
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-17057.patch
>
>
>  Block view has Roles highlighted. List view does not.
> Should have Roles highlighted in List view for consistency.



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

[jira] [Commented] (AMBARI-17058) RBAC: missing Delete Service support

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-17058:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12808384/AMBARI-17058.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-web.

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

This message is automatically generated.

> RBAC: missing Delete Service support
> 
>
> Key: AMBARI-17058
> URL: https://issues.apache.org/jira/browse/AMBARI-17058
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-17058.patch
>
>
> 1. Only Cluster Administrators (and hence Ambari Admins should be able to 
> Delete service).
> 2. Need to make sure the popup table in Admin UI includes Delete Service in 
> list (and only checkbox for ClusterAdmins + Ambari Admins
> 3. Need to make sure that Delete in the Service Actions is not available for 
> the other roles



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

[jira] [Updated] (AMBARI-17058) RBAC: missing Delete Service support

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander updated AMBARI-17058:
-
Attachment: AMBARI-17058.patch

> RBAC: missing Delete Service support
> 
>
> Key: AMBARI-17058
> URL: https://issues.apache.org/jira/browse/AMBARI-17058
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-17058.patch
>
>
> 1. Only Cluster Administrators (and hence Ambari Admins should be able to 
> Delete service).
> 2. Need to make sure the popup table in Admin UI includes Delete Service in 
> list (and only checkbox for ClusterAdmins + Ambari Admins
> 3. Need to make sure that Delete in the Service Actions is not available for 
> the other roles



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

[jira] [Updated] (AMBARI-17056) View config-Custom views are not working after kerberization

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-17056:
--
Attachment: (was: _thumb_91978.png)

> View config-Custom views are not working after kerberization
> 
>
> Key: AMBARI-17056
> URL: https://issues.apache.org/jira/browse/AMBARI-17056
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: screenshot.png
>
>
> custom views are not working after kerberos is enabled.



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

[jira] [Updated] (AMBARI-17056) View config-Custom views are not working after kerberization

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-17056:
--
Attachment: screenshot.png

> View config-Custom views are not working after kerberization
> 
>
> Key: AMBARI-17056
> URL: https://issues.apache.org/jira/browse/AMBARI-17056
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: screenshot.png
>
>
> custom views are not working after kerberos is enabled.



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

[jira] [Created] (AMBARI-17056) View config-Custom views are not working after kerberization

[Gaurav Nagar (JIRA)]

Gaurav Nagar created AMBARI-17056:
-

 Summary: View config-Custom views are not working after 
kerberization
 Key: AMBARI-17056
 URL: https://issues.apache.org/jira/browse/AMBARI-17056
 Project: Ambari
  Issue Type: Bug
  Components: ambari-views
Affects Versions: 2.4.0
Reporter: Gaurav Nagar
Assignee: Gaurav Nagar
 Fix For: 2.4.0


custom views are not working after kerberos is enabled.



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

[jira] [Updated] (AMBARI-17056) View config-Custom views are not working after kerberization

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-17056:
--
Attachment: _thumb_91978.png

> View config-Custom views are not working after kerberization
> 
>
> Key: AMBARI-17056
> URL: https://issues.apache.org/jira/browse/AMBARI-17056
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: _thumb_91978.png
>
>
> custom views are not working after kerberos is enabled.



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

[jira] [Created] (AMBARI-17058) RBAC: missing Delete Service support

[Antonenko Alexander (JIRA)]

Antonenko Alexander created AMBARI-17058:


 Summary: RBAC: missing Delete Service support
 Key: AMBARI-17058
 URL: https://issues.apache.org/jira/browse/AMBARI-17058
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.4.0
Reporter: Antonenko Alexander
Assignee: Antonenko Alexander
 Fix For: 2.4.0


1. Only Cluster Administrators (and hence Ambari Admins should be able to 
Delete service).
2. Need to make sure the popup table in Admin UI includes Delete Service in 
list (and only checkbox for ClusterAdmins + Ambari Admins
3. Need to make sure that Delete in the Service Actions is not available for 
the other roles



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

[jira] [Created] (AMBARI-17057) RBAC: when on List view, Roles is not selected

[Antonenko Alexander (JIRA)]

Antonenko Alexander created AMBARI-17057:


 Summary: RBAC: when on List view, Roles is not selected
 Key: AMBARI-17057
 URL: https://issues.apache.org/jira/browse/AMBARI-17057
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.4.0
Reporter: Antonenko Alexander
Assignee: Antonenko Alexander
 Fix For: 2.4.0


 Block view has Roles highlighted. List view does not.

Should have Roles highlighted in List view for consistency.



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

[jira] [Commented] (AMBARI-17057) RBAC: when on List view, Roles is not selected

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-17057:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12808383/AMBARI-17057.patch
  against trunk revision .

{color:red}-1 patch{color}.  Trunk compilation may be broken.

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7177//console

This message is automatically generated.

> RBAC: when on List view, Roles is not selected
> --
>
> Key: AMBARI-17057
> URL: https://issues.apache.org/jira/browse/AMBARI-17057
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-17057.patch
>
>
>  Block view has Roles highlighted. List view does not.
> Should have Roles highlighted in List view for consistency.



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

[jira] [Updated] (AMBARI-17055) Show better error message when VIEW USER can not access CAPACITY SCHEDULER View

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-17055:
--
Component/s: ambari-views

> Show better error message when VIEW USER can not access CAPACITY SCHEDULER 
> View
> ---
>
> Key: AMBARI-17055
> URL: https://issues.apache.org/jira/browse/AMBARI-17055
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
>
> When view user does not have cluster read permission, view will fail with 
> error.
> Show better error message indicating user does not have permission to view 
> the configurations.
> org.apache.ambari.view.utils.ambari.AmbariApiException: RA040 I/O error while 
> requesting Ambari
> at 
> org.apache.ambari.view.utils.ambari.AmbariApi.requestClusterAPI(AmbariApi.java:176)
> at 
> org.apache.ambari.view.utils.ambari.AmbariApi.requestClusterAPI(AmbariApi.java:142)
> at 
> org.apache.ambari.view.capacityscheduler.ConfigurationService.readFromCluster(ConfigurationService.java:291)
> at 
> org.apache.ambari.view.capacityscheduler.ConfigurationService.readClusterInfo(ConfigurationService.java:148)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at 
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:540)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:715)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:770)
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1496)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
> at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118)
> at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84)
> at 
> 

[jira] [Updated] (AMBARI-17055) Show better error message when VIEW USER can not access CAPACITY SCHEDULER View

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-17055:
--
Affects Version/s: 2.2.2

> Show better error message when VIEW USER can not access CAPACITY SCHEDULER 
> View
> ---
>
> Key: AMBARI-17055
> URL: https://issues.apache.org/jira/browse/AMBARI-17055
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.2.2
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
>
> When view user does not have cluster read permission, view will fail with 
> error.
> Show better error message indicating user does not have permission to view 
> the configurations.
> org.apache.ambari.view.utils.ambari.AmbariApiException: RA040 I/O error while 
> requesting Ambari
> at 
> org.apache.ambari.view.utils.ambari.AmbariApi.requestClusterAPI(AmbariApi.java:176)
> at 
> org.apache.ambari.view.utils.ambari.AmbariApi.requestClusterAPI(AmbariApi.java:142)
> at 
> org.apache.ambari.view.capacityscheduler.ConfigurationService.readFromCluster(ConfigurationService.java:291)
> at 
> org.apache.ambari.view.capacityscheduler.ConfigurationService.readClusterInfo(ConfigurationService.java:148)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at 
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:540)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:715)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:770)
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1496)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
> at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118)
> at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84)
> at 
> 

[jira] [Updated] (AMBARI-17055) Show better error message when VIEW USER can not access CAPACITY SCHEDULER View

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-17055:
--
Attachment: AMBARI-17055_branch-2.4.patch

> Show better error message when VIEW USER can not access CAPACITY SCHEDULER 
> View
> ---
>
> Key: AMBARI-17055
> URL: https://issues.apache.org/jira/browse/AMBARI-17055
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.2.2
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-17055_branch-2.4.patch
>
>
> When view user does not have cluster read permission, view will fail with 
> error.
> Show better error message indicating user does not have permission to view 
> the configurations.
> org.apache.ambari.view.utils.ambari.AmbariApiException: RA040 I/O error while 
> requesting Ambari
> at 
> org.apache.ambari.view.utils.ambari.AmbariApi.requestClusterAPI(AmbariApi.java:176)
> at 
> org.apache.ambari.view.utils.ambari.AmbariApi.requestClusterAPI(AmbariApi.java:142)
> at 
> org.apache.ambari.view.capacityscheduler.ConfigurationService.readFromCluster(ConfigurationService.java:291)
> at 
> org.apache.ambari.view.capacityscheduler.ConfigurationService.readClusterInfo(ConfigurationService.java:148)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at 
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:540)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:715)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:770)
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1496)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
> at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118)
> at 
> 

[jira] [Commented] (AMBARI-17057) RBAC: when on List view, Roles is not selected

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko commented on AMBARI-17057:
--

+1 for the patch

> RBAC: when on List view, Roles is not selected
> --
>
> Key: AMBARI-17057
> URL: https://issues.apache.org/jira/browse/AMBARI-17057
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-17057.patch
>
>
>  Block view has Roles highlighted. List view does not.
> Should have Roles highlighted in List view for consistency.



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

[jira] [Commented] (AMBARI-17004) Unit tests failing because of the order of hash sets/maps

[Miklos Gergely (JIRA)]

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

Miklos Gergely commented on AMBARI-17004:
-

PrivilegeEventCreatorTest.putTest
RepositoryVersionEventCreatorTest:putTest
RepositoryVersionEventCreatorTest:postTest
ViewPrivilegeEventCreatorTest.putTest

ClusterPrivilegeChangeRequestAuditEvent:81 iterates over a HashSet

- the expected result of the test at PrivilegeEventCreatorTest:99 assumes to do 
this in the order [Permission2, Permission1], which may or may not happen so.
- the expected result of the test at RepositoryVersionEventCreatorTest:62 
assumes to do this in the order [Operating system: redhat6, Operating system: 
redhat7], which may or may not happen so. 
- the expected result of the test at RepositoryVersionEventCreatorTest:92 
assumes to do this in the order [Operating system: redhat6, Operating system: 
redhat7], which may or may not happen so. 
- the expected result of the test at ViewPrivilegeEventCreatorTest:77 assumes 
to do this in the order [Permission2, Permission1], which may or may not happen 
so.

Suggested solution: instead of comparing the actual result to one string break 
it up to key-value pairs, and compare them individually. In case of the 
Roles/Repositories the value should be a Set, or a Map.

Suggested solution2: have two expected result strings in both orders. After the 
actual result is ready first check if it contains both the Roles/Repositories , 
and if it does then check their order, and compare to the appropriate expected 
result string


> Unit tests failing because of the order of hash sets/maps
> -
>
> Key: AMBARI-17004
> URL: https://issues.apache.org/jira/browse/AMBARI-17004
> Project: Ambari
>  Issue Type: Bug
>Reporter: Miklos Gergely
>
> Some unit tests are failing because they depend on the order elements are 
> returned by the iterator of a HashSet/HashMap. Usually they are small (2-3 
> entries), so they may easily produce good results. Still in other 
> environments they fail as the order the elements are returned from a 
> HashSet/HashMap may depend on the JVM used.
> The tests will be described in the comments.



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

[jira] [Created] (AMBARI-17055) Show better error message when VIEW USER can not access CAPACITY SCHEDULER View

[Gaurav Nagar (JIRA)]

Gaurav Nagar created AMBARI-17055:
-

 Summary: Show better error message when VIEW USER can not access 
CAPACITY SCHEDULER View
 Key: AMBARI-17055
 URL: https://issues.apache.org/jira/browse/AMBARI-17055
 Project: Ambari
  Issue Type: Bug
Reporter: Gaurav Nagar
Assignee: Gaurav Nagar
 Fix For: 2.4.0


When view user does not have cluster read permission, view will fail with error.
Show better error message indicating user does not have permission to view the 
configurations.

org.apache.ambari.view.utils.ambari.AmbariApiException: RA040 I/O error while 
requesting Ambari
at 
org.apache.ambari.view.utils.ambari.AmbariApi.requestClusterAPI(AmbariApi.java:176)
at 
org.apache.ambari.view.utils.ambari.AmbariApi.requestClusterAPI(AmbariApi.java:142)
at 
org.apache.ambari.view.capacityscheduler.ConfigurationService.readFromCluster(ConfigurationService.java:291)
at 
org.apache.ambari.view.capacityscheduler.ConfigurationService.readClusterInfo(ConfigurationService.java:148)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at 
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
at 
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at 
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
at 
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
at 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:540)
at 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:715)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:770)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1496)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
at 
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118)
at 
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
at 
org.apache.ambari.server.security.authorization.AmbariAuthorizationFilter.doFilter(AmbariAuthorizationFilter.java:207)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
at 
org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113)
at 

[jira] [Updated] (AMBARI-17056) View config-Custom views are not working after kerberization

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-17056:
--
Attachment: AMBARI-17056_branch-2.4.patch

> View config-Custom views are not working after kerberization
> 
>
> Key: AMBARI-17056
> URL: https://issues.apache.org/jira/browse/AMBARI-17056
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-17056_branch-2.4.patch, screenshot.png
>
>
> custom views are not working after kerberos is enabled.



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

[jira] [Updated] (AMBARI-17058) RBAC: missing Delete Service support

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander updated AMBARI-17058:
-
Status: Patch Available  (was: Open)

> RBAC: missing Delete Service support
> 
>
> Key: AMBARI-17058
> URL: https://issues.apache.org/jira/browse/AMBARI-17058
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-17058.patch
>
>
> 1. Only Cluster Administrators (and hence Ambari Admins should be able to 
> Delete service).
> 2. Need to make sure the popup table in Admin UI includes Delete Service in 
> list (and only checkbox for ClusterAdmins + Ambari Admins
> 3. Need to make sure that Delete in the Service Actions is not available for 
> the other roles



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

[jira] [Updated] (AMBARI-17059) Service stop/start fail after Ambari upgrade due to missing config parameters

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-17059:
-
Attachment: AMBARI-17059.patch

> Service stop/start fail after Ambari upgrade due to missing config parameters
> -
>
> Key: AMBARI-17059
> URL: https://issues.apache.org/jira/browse/AMBARI-17059
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-17059.patch
>
>
> ambari-server --hash  
> 43b564767ccf9eaa60f4e352c46ed3cb32dc7e78
> Observed this issue in a couple of scenarios:
> **Scenario #1**
>   1. Deploy HDP-2.4.2.0 with Ambari 2.2.2.0
>   2. Upgrade Ambari to 2.4.0.0-635 build
>   3. Register HDP-2.5.0.0-639 and install the bits
>   4. Start Express Upgrade to 2.5
> Oozie server start failed with below error:
> 
> 
> 
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
>  line 215, in 
> OozieServer().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 257, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
>  line 100, in stop
> oozie_service(action='stop', upgrade_type=upgrade_type)
>   File 
> "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", line 89, 
> in thunk
> return fn(*args, **kwargs)
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py",
>  line 149, in oozie_service
> stop_cmd  = format("cd {oozie_tmp_dir} && 
> {oozie_home}/bin/oozie-stop.sh")
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
>  line 95, in format
> return ConfigurationFormatter().format(format_string, args, **result)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
>  line 59, in format
> result_protected = self.vformat(format_string, args, all_params)
>   File "/usr/lib64/python2.7/string.py", line 549, in vformat
> result = self._vformat(format_string, args, kwargs, used_args, 2)
>   File "/usr/lib64/python2.7/string.py", line 582, in _vformat
> result.append(self.format_field(obj, format_spec))
>   File "/usr/lib64/python2.7/string.py", line 599, in format_field
> return format(value, format_spec)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
>  line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found 
> in configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 
> 'oozie_tmp_dir' was not found in configurations dictionary!
> 
> **Scenario #2**
>   1. Deploy HDP-2.3.4.0 with Ambari 2.2.0.0
>   2. Upgrade Ambari to 2.4.0.0-635 build
>   3. Delete Ranger service
>   4. Restart all services with stale configs
> **Result**  
> ATS, DN, Falcon client restart fails with below error
> 
> 
> 
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
>  line 39, in 
> BeforeStartHook().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 257, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
>  line 28, in hook
> import params
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py",
>  line 316, in 
> immutable_paths = get_not_managed_resources(),
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_not_managed_resources.py",
>  line 38, in get_not_managed_resources
> managed_hdfs_resource_property_list = filter(None, [property.strip() 
> for property in managed_hdfs_resource_property_names.split(',')])
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
>  line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found 
> in configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 
> 'managed_hdfs_resource_property_names' was not found in configurations 
> dictionary!
> Error: Error: Unable to run the custom hook script ['/usr/bin/python', 
> 

[jira] [Updated] (AMBARI-17060) Visual explain unit tests

[Pallav Kulshreshtha (JIRA)]

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

Pallav Kulshreshtha updated AMBARI-17060:
-
Status: Patch Available  (was: Open)

> Visual explain unit tests
> -
>
> Key: AMBARI-17060
> URL: https://issues.apache.org/jira/browse/AMBARI-17060
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.0.0
>Reporter: Pallav Kulshreshtha
>Assignee: Pallav Kulshreshtha
> Fix For: 2.4.0
>
> Attachments: AMBARI-17060_branch-2.4.patch
>
>
> Write visual explain test cases.



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

[jira] [Updated] (AMBARI-17054) Configure Atlas Ranger Plugin

[Gautam Borad (JIRA)]

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

Gautam Borad updated AMBARI-17054:
--
Status: Patch Available  (was: In Progress)

> Configure Atlas Ranger Plugin
> -
>
> Key: AMBARI-17054
> URL: https://issues.apache.org/jira/browse/AMBARI-17054
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Gautam Borad
>Assignee: Gautam Borad
> Fix For: 2.4.0
>
> Attachments: AMBARI-17054.1.patch
>
>
> Need to do following changes to support Ranger Atlas Plugin from Ambari: 
> 1) Check stack support  and provide smart config section to Enable / disable 
> ranger atlas plugin
> 2) Stack advisor changes to suggest recommended configs on enable / disable 
> plugin actions. 
> 3) Ranger service creation on Enable plugin action from Ambari. 



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

[jira] [Commented] (AMBARI-17059) Service stop/start fail after Ambari upgrade due to missing config parameters

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-17059:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12808396/AMBARI-17059.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server.

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

This message is automatically generated.

> Service stop/start fail after Ambari upgrade due to missing config parameters
> -
>
> Key: AMBARI-17059
> URL: https://issues.apache.org/jira/browse/AMBARI-17059
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-17059.patch
>
>
> ambari-server --hash  
> 43b564767ccf9eaa60f4e352c46ed3cb32dc7e78
> Observed this issue in a couple of scenarios:
> **Scenario #1**
>   1. Deploy HDP-2.4.2.0 with Ambari 2.2.2.0
>   2. Upgrade Ambari to 2.4.0.0-635 build
>   3. Register HDP-2.5.0.0-639 and install the bits
>   4. Start Express Upgrade to 2.5
> Oozie server start failed with below error:
> 
> 
> 
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
>  line 215, in 
> OozieServer().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 257, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
>  line 100, in stop
> oozie_service(action='stop', upgrade_type=upgrade_type)
>   File 
> "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", line 89, 
> in thunk
> return fn(*args, **kwargs)
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py",
>  line 149, in oozie_service
> stop_cmd  = format("cd {oozie_tmp_dir} && 
> {oozie_home}/bin/oozie-stop.sh")
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
>  line 95, in format
> return ConfigurationFormatter().format(format_string, args, **result)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
>  line 59, in format
> result_protected = self.vformat(format_string, args, all_params)
>   File "/usr/lib64/python2.7/string.py", line 549, in vformat
> result = self._vformat(format_string, args, kwargs, used_args, 2)
>   File "/usr/lib64/python2.7/string.py", line 582, in _vformat
> result.append(self.format_field(obj, format_spec))
>   File "/usr/lib64/python2.7/string.py", line 599, in format_field
> return format(value, format_spec)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
>  line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found 
> in configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 
> 'oozie_tmp_dir' was not found in configurations dictionary!
> 
> **Scenario #2**
>   1. Deploy HDP-2.3.4.0 with Ambari 2.2.0.0
>   2. Upgrade Ambari to 2.4.0.0-635 build
>   3. Delete Ranger service
>   4. Restart all services with stale configs
> **Result**  
> ATS, DN, Falcon client restart fails with below error
> 
> 
> 
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
>  line 39, in 
> BeforeStartHook().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 257, in execute
> method(env)
>   File 
> 

[jira] [Created] (AMBARI-17061) [ambari] ambari-agent restart is failing due to unsupported locale setting

[Andrew Onischuk (JIRA)]

Andrew Onischuk created AMBARI-17061:


 Summary: [ambari] ambari-agent restart is failing due to 
unsupported locale setting
 Key: AMBARI-17061
 URL: https://issues.apache.org/jira/browse/AMBARI-17061
 Project: Ambari
  Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
 Fix For: 2.4.0


this issue I faced some 5-6 days ago , I was not able to reproduce the same.  
Again i am facing the same issue, incident is as follows:  
1) ambari-agent heartbeat lost  
2) checked the ambari-agent logs couldn't find any valid reason  
3) so restarted the ambari-agent




[root@ds-xa-test-1-re-1 bin]# ambari-agent start
Verifying Python version compatibility...
Using python  /usr/bin/python
Checking for previously running Ambari Agent...
Starting ambari-agent
Verifying ambari-agent process status...
Ambari Agent successfully started
Agent PID at: /var/run/ambari-agent/ambari-agent.pid
Agent out at: /var/log/ambari-agent/ambari-agent.out
Agent log at: /var/log/ambari-agent/ambari-agent.log


**it says ambari-agent successfull started but it does not start actually and 
throws unsupported locale type exception in agent.out**

following is the exception in ambari-agent.out




  File "/usr/lib/python2.6/site-packages/ambari_agent/main.py", line 54, in 

locale.setlocale(locale.LC_ALL, '')
  File "/usr/lib64/python2.6/locale.py", line 513, in setlocale
return _setlocale(category, locale)
locale.Error: unsupported locale setting
^[[?1034h


I checked the locale




[root@ds-xa-test-1-re-1 bin]# locale
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=en_US.UTF-8
LC_CTYPE=UTF-8
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=


since LC_ALL was set to empty so set the export LC_ALL=C

then restarted the ranger and it was successful.

again facing the same issue:


build detail:  
ambari-agent-2.4.0.0-625.x86_64





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

[jira] [Reopened] (AMBARI-17061) [ambari] ambari-agent restart is failing due to unsupported locale setting

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk reopened AMBARI-17061:
--

> [ambari] ambari-agent restart is failing due to unsupported locale setting
> --
>
> Key: AMBARI-17061
> URL: https://issues.apache.org/jira/browse/AMBARI-17061
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-17061.patch
>
>
> this issue I faced some 5-6 days ago , I was not able to reproduce the same.  
> Again i am facing the same issue, incident is as follows:  
> 1) ambari-agent heartbeat lost  
> 2) checked the ambari-agent logs couldn't find any valid reason  
> 3) so restarted the ambari-agent
> 
> 
> 
> [root@ds-xa-test-1-re-1 bin]# ambari-agent start
> Verifying Python version compatibility...
> Using python  /usr/bin/python
> Checking for previously running Ambari Agent...
> Starting ambari-agent
> Verifying ambari-agent process status...
> Ambari Agent successfully started
> Agent PID at: /var/run/ambari-agent/ambari-agent.pid
> Agent out at: /var/log/ambari-agent/ambari-agent.out
> Agent log at: /var/log/ambari-agent/ambari-agent.log
> 
> **it says ambari-agent successfull started but it does not start actually and 
> throws unsupported locale type exception in agent.out**
> following is the exception in ambari-agent.out
> 
> 
> 
>   File "/usr/lib/python2.6/site-packages/ambari_agent/main.py", line 54, 
> in 
> locale.setlocale(locale.LC_ALL, '')
>   File "/usr/lib64/python2.6/locale.py", line 513, in setlocale
> return _setlocale(category, locale)
> locale.Error: unsupported locale setting
> ^[[?1034h
> 
> I checked the locale
> 
> 
> 
> [root@ds-xa-test-1-re-1 bin]# locale
> locale: Cannot set LC_CTYPE to default locale: No such file or directory
> locale: Cannot set LC_ALL to default locale: No such file or directory
> LANG=en_US.UTF-8
> LC_CTYPE=UTF-8
> LC_NUMERIC="en_US.UTF-8"
> LC_TIME="en_US.UTF-8"
> LC_COLLATE="en_US.UTF-8"
> LC_MONETARY="en_US.UTF-8"
> LC_MESSAGES="en_US.UTF-8"
> LC_PAPER="en_US.UTF-8"
> LC_NAME="en_US.UTF-8"
> LC_ADDRESS="en_US.UTF-8"
> LC_TELEPHONE="en_US.UTF-8"
> LC_MEASUREMENT="en_US.UTF-8"
> LC_IDENTIFICATION="en_US.UTF-8"
> LC_ALL=
> 
> since LC_ALL was set to empty so set the export LC_ALL=C
> then restarted the ranger and it was successful.
> again facing the same issue:
> build detail:  
> ambari-agent-2.4.0.0-625.x86_64



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

[jira] [Updated] (AMBARI-17059) Service stop/start fail after Ambari upgrade due to missing config parameters

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-17059:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to branch-2.4

> Service stop/start fail after Ambari upgrade due to missing config parameters
> -
>
> Key: AMBARI-17059
> URL: https://issues.apache.org/jira/browse/AMBARI-17059
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-17059.patch
>
>
> ambari-server --hash  
> 43b564767ccf9eaa60f4e352c46ed3cb32dc7e78
> Observed this issue in a couple of scenarios:
> **Scenario #1**
>   1. Deploy HDP-2.4.2.0 with Ambari 2.2.2.0
>   2. Upgrade Ambari to 2.4.0.0-635 build
>   3. Register HDP-2.5.0.0-639 and install the bits
>   4. Start Express Upgrade to 2.5
> Oozie server start failed with below error:
> 
> 
> 
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
>  line 215, in 
> OozieServer().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 257, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
>  line 100, in stop
> oozie_service(action='stop', upgrade_type=upgrade_type)
>   File 
> "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", line 89, 
> in thunk
> return fn(*args, **kwargs)
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py",
>  line 149, in oozie_service
> stop_cmd  = format("cd {oozie_tmp_dir} && 
> {oozie_home}/bin/oozie-stop.sh")
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
>  line 95, in format
> return ConfigurationFormatter().format(format_string, args, **result)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
>  line 59, in format
> result_protected = self.vformat(format_string, args, all_params)
>   File "/usr/lib64/python2.7/string.py", line 549, in vformat
> result = self._vformat(format_string, args, kwargs, used_args, 2)
>   File "/usr/lib64/python2.7/string.py", line 582, in _vformat
> result.append(self.format_field(obj, format_spec))
>   File "/usr/lib64/python2.7/string.py", line 599, in format_field
> return format(value, format_spec)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
>  line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found 
> in configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 
> 'oozie_tmp_dir' was not found in configurations dictionary!
> 
> **Scenario #2**
>   1. Deploy HDP-2.3.4.0 with Ambari 2.2.0.0
>   2. Upgrade Ambari to 2.4.0.0-635 build
>   3. Delete Ranger service
>   4. Restart all services with stale configs
> **Result**  
> ATS, DN, Falcon client restart fails with below error
> 
> 
> 
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
>  line 39, in 
> BeforeStartHook().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 257, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
>  line 28, in hook
> import params
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py",
>  line 316, in 
> immutable_paths = get_not_managed_resources(),
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_not_managed_resources.py",
>  line 38, in get_not_managed_resources
> managed_hdfs_resource_property_list = filter(None, [property.strip() 
> for property in managed_hdfs_resource_property_names.split(',')])
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
>  line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found 
> in configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 
> 'managed_hdfs_resource_property_names' was not found in configurations 
> dictionary!
> Error: Error: Unable to run the custom hook script 

[jira] [Created] (AMBARI-17059) Service stop/start fail after Ambari upgrade due to missing config parameters

[Andrew Onischuk (JIRA)]

Andrew Onischuk created AMBARI-17059:


 Summary: Service stop/start fail after Ambari upgrade due to 
missing config parameters
 Key: AMBARI-17059
 URL: https://issues.apache.org/jira/browse/AMBARI-17059
 Project: Ambari
  Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
 Fix For: 2.4.0


ambari-server --hash  
43b564767ccf9eaa60f4e352c46ed3cb32dc7e78


Observed this issue in a couple of scenarios:

**Scenario #1**

  1. Deploy HDP-2.4.2.0 with Ambari 2.2.2.0
  2. Upgrade Ambari to 2.4.0.0-635 build
  3. Register HDP-2.5.0.0-639 and install the bits
  4. Start Express Upgrade to 2.5

Oozie server start failed with below error:




Traceback (most recent call last):
  File 
"/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
 line 215, in 
OozieServer().execute()
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
 line 257, in execute
method(env)
  File 
"/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
 line 100, in stop
oozie_service(action='stop', upgrade_type=upgrade_type)
  File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", 
line 89, in thunk
return fn(*args, **kwargs)
  File 
"/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py",
 line 149, in oozie_service
stop_cmd  = format("cd {oozie_tmp_dir} && 
{oozie_home}/bin/oozie-stop.sh")
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
 line 95, in format
return ConfigurationFormatter().format(format_string, args, **result)
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
 line 59, in format
result_protected = self.vformat(format_string, args, all_params)
  File "/usr/lib64/python2.7/string.py", line 549, in vformat
result = self._vformat(format_string, args, kwargs, used_args, 2)
  File "/usr/lib64/python2.7/string.py", line 582, in _vformat
result.append(self.format_field(obj, format_spec))
  File "/usr/lib64/python2.7/string.py", line 599, in format_field
return format(value, format_spec)
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
 line 73, in __getattr__
raise Fail("Configuration parameter '" + self.name + "' was not found 
in configurations dictionary!")
resource_management.core.exceptions.Fail: Configuration parameter 
'oozie_tmp_dir' was not found in configurations dictionary!


**Scenario #2**

  1. Deploy HDP-2.3.4.0 with Ambari 2.2.0.0
  2. Upgrade Ambari to 2.4.0.0-635 build
  3. Delete Ranger service
  4. Restart all services with stale configs

**Result**  
ATS, DN, Falcon client restart fails with below error




Traceback (most recent call last):
  File 
"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
 line 39, in 
BeforeStartHook().execute()
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
 line 257, in execute
method(env)
  File 
"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
 line 28, in hook
import params
  File 
"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py",
 line 316, in 
immutable_paths = get_not_managed_resources(),
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_not_managed_resources.py",
 line 38, in get_not_managed_resources
managed_hdfs_resource_property_list = filter(None, [property.strip() 
for property in managed_hdfs_resource_property_names.split(',')])
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
 line 73, in __getattr__
raise Fail("Configuration parameter '" + self.name + "' was not found 
in configurations dictionary!")
resource_management.core.exceptions.Fail: Configuration parameter 
'managed_hdfs_resource_property_names' was not found in configurations 
dictionary!
Error: Error: Unable to run the custom hook script ['/usr/bin/python', 
'/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py',
 'START', '/var/lib/ambari-agent/data/command-603.json', 
'/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START', 
'/var/lib/ambari-agent/data/structured-out-603.json', 'INFO', 
'/var/lib/ambari-agent/tmp']






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

[jira] [Commented] (AMBARI-17061) [ambari] ambari-agent restart is failing due to unsupported locale setting

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-17061:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12808403/AMBARI-17061.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in .

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

This message is automatically generated.

> [ambari] ambari-agent restart is failing due to unsupported locale setting
> --
>
> Key: AMBARI-17061
> URL: https://issues.apache.org/jira/browse/AMBARI-17061
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-17061.patch
>
>
> this issue I faced some 5-6 days ago , I was not able to reproduce the same.  
> Again i am facing the same issue, incident is as follows:  
> 1) ambari-agent heartbeat lost  
> 2) checked the ambari-agent logs couldn't find any valid reason  
> 3) so restarted the ambari-agent
> 
> 
> 
> [root@ds-xa-test-1-re-1 bin]# ambari-agent start
> Verifying Python version compatibility...
> Using python  /usr/bin/python
> Checking for previously running Ambari Agent...
> Starting ambari-agent
> Verifying ambari-agent process status...
> Ambari Agent successfully started
> Agent PID at: /var/run/ambari-agent/ambari-agent.pid
> Agent out at: /var/log/ambari-agent/ambari-agent.out
> Agent log at: /var/log/ambari-agent/ambari-agent.log
> 
> **it says ambari-agent successfull started but it does not start actually and 
> throws unsupported locale type exception in agent.out**
> following is the exception in ambari-agent.out
> 
> 
> 
>   File "/usr/lib/python2.6/site-packages/ambari_agent/main.py", line 54, 
> in 
> locale.setlocale(locale.LC_ALL, '')
>   File "/usr/lib64/python2.6/locale.py", line 513, in setlocale
> return _setlocale(category, locale)
> locale.Error: unsupported locale setting
> ^[[?1034h
> 
> I checked the locale
> 
> 
> 
> [root@ds-xa-test-1-re-1 bin]# locale
> locale: Cannot set LC_CTYPE to default locale: No such file or directory
> locale: Cannot set LC_ALL to default locale: No such file or directory
> LANG=en_US.UTF-8
> LC_CTYPE=UTF-8
> LC_NUMERIC="en_US.UTF-8"
> LC_TIME="en_US.UTF-8"
> LC_COLLATE="en_US.UTF-8"
> LC_MONETARY="en_US.UTF-8"
> LC_MESSAGES="en_US.UTF-8"
> LC_PAPER="en_US.UTF-8"
> LC_NAME="en_US.UTF-8"
> LC_ADDRESS="en_US.UTF-8"
> LC_TELEPHONE="en_US.UTF-8"
> LC_MEASUREMENT="en_US.UTF-8"
> LC_IDENTIFICATION="en_US.UTF-8"
> LC_ALL=
> 
> since LC_ALL was set to empty so set the export LC_ALL=C
> then restarted the ranger and it was successful.
> again facing the same issue:
> build detail:  
> ambari-agent-2.4.0.0-625.x86_64



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

[jira] [Created] (AMBARI-17063) Retrieve specific metrics when Ambari queries NameNode HA states

[Andrew Onischuk (JIRA)]

Andrew Onischuk created AMBARI-17063:


 Summary: Retrieve specific metrics when Ambari queries NameNode HA 
states
 Key: AMBARI-17063
 URL: https://issues.apache.org/jira/browse/AMBARI-17063
 Project: Ambari
  Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
 Fix For: 2.4.0
 Attachments: AMBARI-17063.patch

This is a follow-on jira of BUG-53459: when Ambari queries NameNode's HA
states, currently it retrieves a group of metrics including some unnecessary
ones that may compete for NameNode lock. It would be better for Ambari to only
retrieve HA state metrics from NameNode.





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

[jira] [Created] (AMBARI-17060) Visual explain unit tests

[Pallav Kulshreshtha (JIRA)]

Pallav Kulshreshtha created AMBARI-17060:


 Summary: Visual explain unit tests
 Key: AMBARI-17060
 URL: https://issues.apache.org/jira/browse/AMBARI-17060
 Project: Ambari
  Issue Type: Bug
  Components: ambari-views
Affects Versions: 2.0.0
Reporter: Pallav Kulshreshtha
Assignee: Pallav Kulshreshtha
 Fix For: 2.4.0


Write visual explain test cases.



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

[jira] [Updated] (AMBARI-17059) Service stop/start fail after Ambari upgrade due to missing config parameters

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-17059:
-
Status: Patch Available  (was: Open)

> Service stop/start fail after Ambari upgrade due to missing config parameters
> -
>
> Key: AMBARI-17059
> URL: https://issues.apache.org/jira/browse/AMBARI-17059
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-17059.patch
>
>
> ambari-server --hash  
> 43b564767ccf9eaa60f4e352c46ed3cb32dc7e78
> Observed this issue in a couple of scenarios:
> **Scenario #1**
>   1. Deploy HDP-2.4.2.0 with Ambari 2.2.2.0
>   2. Upgrade Ambari to 2.4.0.0-635 build
>   3. Register HDP-2.5.0.0-639 and install the bits
>   4. Start Express Upgrade to 2.5
> Oozie server start failed with below error:
> 
> 
> 
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
>  line 215, in 
> OozieServer().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 257, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
>  line 100, in stop
> oozie_service(action='stop', upgrade_type=upgrade_type)
>   File 
> "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", line 89, 
> in thunk
> return fn(*args, **kwargs)
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py",
>  line 149, in oozie_service
> stop_cmd  = format("cd {oozie_tmp_dir} && 
> {oozie_home}/bin/oozie-stop.sh")
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
>  line 95, in format
> return ConfigurationFormatter().format(format_string, args, **result)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
>  line 59, in format
> result_protected = self.vformat(format_string, args, all_params)
>   File "/usr/lib64/python2.7/string.py", line 549, in vformat
> result = self._vformat(format_string, args, kwargs, used_args, 2)
>   File "/usr/lib64/python2.7/string.py", line 582, in _vformat
> result.append(self.format_field(obj, format_spec))
>   File "/usr/lib64/python2.7/string.py", line 599, in format_field
> return format(value, format_spec)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
>  line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found 
> in configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 
> 'oozie_tmp_dir' was not found in configurations dictionary!
> 
> **Scenario #2**
>   1. Deploy HDP-2.3.4.0 with Ambari 2.2.0.0
>   2. Upgrade Ambari to 2.4.0.0-635 build
>   3. Delete Ranger service
>   4. Restart all services with stale configs
> **Result**  
> ATS, DN, Falcon client restart fails with below error
> 
> 
> 
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
>  line 39, in 
> BeforeStartHook().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 257, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
>  line 28, in hook
> import params
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py",
>  line 316, in 
> immutable_paths = get_not_managed_resources(),
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_not_managed_resources.py",
>  line 38, in get_not_managed_resources
> managed_hdfs_resource_property_list = filter(None, [property.strip() 
> for property in managed_hdfs_resource_property_names.split(',')])
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
>  line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found 
> in configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 
> 'managed_hdfs_resource_property_names' was not found in configurations 
> dictionary!
> Error: Error: Unable to run the custom hook script ['/usr/bin/python', 
> 

[jira] [Updated] (AMBARI-15557) YARN service check fails if there is no queue named "default"

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-15557:
-
Attachment: AMBARI-15557.patch

> YARN service check fails if there is no queue named "default"
> -
>
> Key: AMBARI-15557
> URL: https://issues.apache.org/jira/browse/AMBARI-15557
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15557-trunk.patch, AMBARI-15557.patch, 
> AMBARI-15557.patch, AMBARI-15557.patch.1
>
>
> Service check for yarn will fail in case if 
> {{yarn.scheduler.capacity.root.queues}} doesn't declare default queue. This 
> caused due to usage of yarn distributed shell, which use default queue. 



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

[jira] [Updated] (AMBARI-15557) YARN service check fails if there is no queue named "default"

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-15557:
-
Status: Patch Available  (was: Reopened)

> YARN service check fails if there is no queue named "default"
> -
>
> Key: AMBARI-15557
> URL: https://issues.apache.org/jira/browse/AMBARI-15557
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15557-trunk.patch, AMBARI-15557.patch, 
> AMBARI-15557.patch, AMBARI-15557.patch.1
>
>
> Service check for yarn will fail in case if 
> {{yarn.scheduler.capacity.root.queues}} doesn't declare default queue. This 
> caused due to usage of yarn distributed shell, which use default queue. 



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

[jira] [Commented] (AMBARI-17060) Visual explain unit tests

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-17060:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12808399/AMBARI-17060_branch-2.4.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 8 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in 
contrib/views/hive:

  org.apache.ambari.view.hive.resources.jobs.JobServiceTest
  org.apache.ambari.view.hive.resources.jobs.JobLDAPServiceTest

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

This message is automatically generated.

> Visual explain unit tests
> -
>
> Key: AMBARI-17060
> URL: https://issues.apache.org/jira/browse/AMBARI-17060
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.0.0
>Reporter: Pallav Kulshreshtha
>Assignee: Pallav Kulshreshtha
> Fix For: 2.4.0
>
> Attachments: AMBARI-17060_branch-2.4.patch
>
>
> Write visual explain test cases.



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

[jira] [Commented] (AMBARI-17058) RBAC: missing Delete Service support

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-17058:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12808384/AMBARI-17058.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-web.

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

This message is automatically generated.

> RBAC: missing Delete Service support
> 
>
> Key: AMBARI-17058
> URL: https://issues.apache.org/jira/browse/AMBARI-17058
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-17058.patch
>
>
> 1. Only Cluster Administrators (and hence Ambari Admins should be able to 
> Delete service).
> 2. Need to make sure the popup table in Admin UI includes Delete Service in 
> list (and only checkbox for ClusterAdmins + Ambari Admins
> 3. Need to make sure that Delete in the Service Actions is not available for 
> the other roles



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

[jira] [Updated] (AMBARI-17061) [ambari] ambari-agent restart is failing due to unsupported locale setting

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-17061:
-
Status: Patch Available  (was: Open)

> [ambari] ambari-agent restart is failing due to unsupported locale setting
> --
>
> Key: AMBARI-17061
> URL: https://issues.apache.org/jira/browse/AMBARI-17061
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-17061.patch
>
>
> this issue I faced some 5-6 days ago , I was not able to reproduce the same.  
> Again i am facing the same issue, incident is as follows:  
> 1) ambari-agent heartbeat lost  
> 2) checked the ambari-agent logs couldn't find any valid reason  
> 3) so restarted the ambari-agent
> 
> 
> 
> [root@ds-xa-test-1-re-1 bin]# ambari-agent start
> Verifying Python version compatibility...
> Using python  /usr/bin/python
> Checking for previously running Ambari Agent...
> Starting ambari-agent
> Verifying ambari-agent process status...
> Ambari Agent successfully started
> Agent PID at: /var/run/ambari-agent/ambari-agent.pid
> Agent out at: /var/log/ambari-agent/ambari-agent.out
> Agent log at: /var/log/ambari-agent/ambari-agent.log
> 
> **it says ambari-agent successfull started but it does not start actually and 
> throws unsupported locale type exception in agent.out**
> following is the exception in ambari-agent.out
> 
> 
> 
>   File "/usr/lib/python2.6/site-packages/ambari_agent/main.py", line 54, 
> in 
> locale.setlocale(locale.LC_ALL, '')
>   File "/usr/lib64/python2.6/locale.py", line 513, in setlocale
> return _setlocale(category, locale)
> locale.Error: unsupported locale setting
> ^[[?1034h
> 
> I checked the locale
> 
> 
> 
> [root@ds-xa-test-1-re-1 bin]# locale
> locale: Cannot set LC_CTYPE to default locale: No such file or directory
> locale: Cannot set LC_ALL to default locale: No such file or directory
> LANG=en_US.UTF-8
> LC_CTYPE=UTF-8
> LC_NUMERIC="en_US.UTF-8"
> LC_TIME="en_US.UTF-8"
> LC_COLLATE="en_US.UTF-8"
> LC_MONETARY="en_US.UTF-8"
> LC_MESSAGES="en_US.UTF-8"
> LC_PAPER="en_US.UTF-8"
> LC_NAME="en_US.UTF-8"
> LC_ADDRESS="en_US.UTF-8"
> LC_TELEPHONE="en_US.UTF-8"
> LC_MEASUREMENT="en_US.UTF-8"
> LC_IDENTIFICATION="en_US.UTF-8"
> LC_ALL=
> 
> since LC_ALL was set to empty so set the export LC_ALL=C
> then restarted the ranger and it was successful.
> again facing the same issue:
> build detail:  
> ambari-agent-2.4.0.0-625.x86_64



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

[jira] [Updated] (AMBARI-17061) [ambari] ambari-agent restart is failing due to unsupported locale setting

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-17061:
-
Attachment: AMBARI-17061.patch

> [ambari] ambari-agent restart is failing due to unsupported locale setting
> --
>
> Key: AMBARI-17061
> URL: https://issues.apache.org/jira/browse/AMBARI-17061
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-17061.patch
>
>
> this issue I faced some 5-6 days ago , I was not able to reproduce the same.  
> Again i am facing the same issue, incident is as follows:  
> 1) ambari-agent heartbeat lost  
> 2) checked the ambari-agent logs couldn't find any valid reason  
> 3) so restarted the ambari-agent
> 
> 
> 
> [root@ds-xa-test-1-re-1 bin]# ambari-agent start
> Verifying Python version compatibility...
> Using python  /usr/bin/python
> Checking for previously running Ambari Agent...
> Starting ambari-agent
> Verifying ambari-agent process status...
> Ambari Agent successfully started
> Agent PID at: /var/run/ambari-agent/ambari-agent.pid
> Agent out at: /var/log/ambari-agent/ambari-agent.out
> Agent log at: /var/log/ambari-agent/ambari-agent.log
> 
> **it says ambari-agent successfull started but it does not start actually and 
> throws unsupported locale type exception in agent.out**
> following is the exception in ambari-agent.out
> 
> 
> 
>   File "/usr/lib/python2.6/site-packages/ambari_agent/main.py", line 54, 
> in 
> locale.setlocale(locale.LC_ALL, '')
>   File "/usr/lib64/python2.6/locale.py", line 513, in setlocale
> return _setlocale(category, locale)
> locale.Error: unsupported locale setting
> ^[[?1034h
> 
> I checked the locale
> 
> 
> 
> [root@ds-xa-test-1-re-1 bin]# locale
> locale: Cannot set LC_CTYPE to default locale: No such file or directory
> locale: Cannot set LC_ALL to default locale: No such file or directory
> LANG=en_US.UTF-8
> LC_CTYPE=UTF-8
> LC_NUMERIC="en_US.UTF-8"
> LC_TIME="en_US.UTF-8"
> LC_COLLATE="en_US.UTF-8"
> LC_MONETARY="en_US.UTF-8"
> LC_MESSAGES="en_US.UTF-8"
> LC_PAPER="en_US.UTF-8"
> LC_NAME="en_US.UTF-8"
> LC_ADDRESS="en_US.UTF-8"
> LC_TELEPHONE="en_US.UTF-8"
> LC_MEASUREMENT="en_US.UTF-8"
> LC_IDENTIFICATION="en_US.UTF-8"
> LC_ALL=
> 
> since LC_ALL was set to empty so set the export LC_ALL=C
> then restarted the ranger and it was successful.
> again facing the same issue:
> build detail:  
> ambari-agent-2.4.0.0-625.x86_64



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

[jira] [Updated] (AMBARI-17061) [ambari] ambari-agent restart is failing due to unsupported locale setting

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-17061:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to branch-2.4

> [ambari] ambari-agent restart is failing due to unsupported locale setting
> --
>
> Key: AMBARI-17061
> URL: https://issues.apache.org/jira/browse/AMBARI-17061
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-17061.patch
>
>
> this issue I faced some 5-6 days ago , I was not able to reproduce the same.  
> Again i am facing the same issue, incident is as follows:  
> 1) ambari-agent heartbeat lost  
> 2) checked the ambari-agent logs couldn't find any valid reason  
> 3) so restarted the ambari-agent
> 
> 
> 
> [root@ds-xa-test-1-re-1 bin]# ambari-agent start
> Verifying Python version compatibility...
> Using python  /usr/bin/python
> Checking for previously running Ambari Agent...
> Starting ambari-agent
> Verifying ambari-agent process status...
> Ambari Agent successfully started
> Agent PID at: /var/run/ambari-agent/ambari-agent.pid
> Agent out at: /var/log/ambari-agent/ambari-agent.out
> Agent log at: /var/log/ambari-agent/ambari-agent.log
> 
> **it says ambari-agent successfull started but it does not start actually and 
> throws unsupported locale type exception in agent.out**
> following is the exception in ambari-agent.out
> 
> 
> 
>   File "/usr/lib/python2.6/site-packages/ambari_agent/main.py", line 54, 
> in 
> locale.setlocale(locale.LC_ALL, '')
>   File "/usr/lib64/python2.6/locale.py", line 513, in setlocale
> return _setlocale(category, locale)
> locale.Error: unsupported locale setting
> ^[[?1034h
> 
> I checked the locale
> 
> 
> 
> [root@ds-xa-test-1-re-1 bin]# locale
> locale: Cannot set LC_CTYPE to default locale: No such file or directory
> locale: Cannot set LC_ALL to default locale: No such file or directory
> LANG=en_US.UTF-8
> LC_CTYPE=UTF-8
> LC_NUMERIC="en_US.UTF-8"
> LC_TIME="en_US.UTF-8"
> LC_COLLATE="en_US.UTF-8"
> LC_MONETARY="en_US.UTF-8"
> LC_MESSAGES="en_US.UTF-8"
> LC_PAPER="en_US.UTF-8"
> LC_NAME="en_US.UTF-8"
> LC_ADDRESS="en_US.UTF-8"
> LC_TELEPHONE="en_US.UTF-8"
> LC_MEASUREMENT="en_US.UTF-8"
> LC_IDENTIFICATION="en_US.UTF-8"
> LC_ALL=
> 
> since LC_ALL was set to empty so set the export LC_ALL=C
> then restarted the ranger and it was successful.
> again facing the same issue:
> build detail:  
> ambari-agent-2.4.0.0-625.x86_64



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

[jira] [Resolved] (AMBARI-17061) [ambari] ambari-agent restart is failing due to unsupported locale setting

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk resolved AMBARI-17061.
--
Resolution: Fixed

Committed to trunk

> [ambari] ambari-agent restart is failing due to unsupported locale setting
> --
>
> Key: AMBARI-17061
> URL: https://issues.apache.org/jira/browse/AMBARI-17061
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-17061.patch
>
>
> this issue I faced some 5-6 days ago , I was not able to reproduce the same.  
> Again i am facing the same issue, incident is as follows:  
> 1) ambari-agent heartbeat lost  
> 2) checked the ambari-agent logs couldn't find any valid reason  
> 3) so restarted the ambari-agent
> 
> 
> 
> [root@ds-xa-test-1-re-1 bin]# ambari-agent start
> Verifying Python version compatibility...
> Using python  /usr/bin/python
> Checking for previously running Ambari Agent...
> Starting ambari-agent
> Verifying ambari-agent process status...
> Ambari Agent successfully started
> Agent PID at: /var/run/ambari-agent/ambari-agent.pid
> Agent out at: /var/log/ambari-agent/ambari-agent.out
> Agent log at: /var/log/ambari-agent/ambari-agent.log
> 
> **it says ambari-agent successfull started but it does not start actually and 
> throws unsupported locale type exception in agent.out**
> following is the exception in ambari-agent.out
> 
> 
> 
>   File "/usr/lib/python2.6/site-packages/ambari_agent/main.py", line 54, 
> in 
> locale.setlocale(locale.LC_ALL, '')
>   File "/usr/lib64/python2.6/locale.py", line 513, in setlocale
> return _setlocale(category, locale)
> locale.Error: unsupported locale setting
> ^[[?1034h
> 
> I checked the locale
> 
> 
> 
> [root@ds-xa-test-1-re-1 bin]# locale
> locale: Cannot set LC_CTYPE to default locale: No such file or directory
> locale: Cannot set LC_ALL to default locale: No such file or directory
> LANG=en_US.UTF-8
> LC_CTYPE=UTF-8
> LC_NUMERIC="en_US.UTF-8"
> LC_TIME="en_US.UTF-8"
> LC_COLLATE="en_US.UTF-8"
> LC_MONETARY="en_US.UTF-8"
> LC_MESSAGES="en_US.UTF-8"
> LC_PAPER="en_US.UTF-8"
> LC_NAME="en_US.UTF-8"
> LC_ADDRESS="en_US.UTF-8"
> LC_TELEPHONE="en_US.UTF-8"
> LC_MEASUREMENT="en_US.UTF-8"
> LC_IDENTIFICATION="en_US.UTF-8"
> LC_ALL=
> 
> since LC_ALL was set to empty so set the export LC_ALL=C
> then restarted the ranger and it was successful.
> again facing the same issue:
> build detail:  
> ambari-agent-2.4.0.0-625.x86_64



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

[jira] [Commented] (AMBARI-17057) RBAC: when on List view, Roles is not selected

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-17057:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12808383/AMBARI-17057.patch
  against trunk revision .

{color:red}-1 patch{color}.  Trunk compilation may be broken.

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7182//console

This message is automatically generated.

> RBAC: when on List view, Roles is not selected
> --
>
> Key: AMBARI-17057
> URL: https://issues.apache.org/jira/browse/AMBARI-17057
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-17057.patch
>
>
>  Block view has Roles highlighted. List view does not.
> Should have Roles highlighted in List view for consistency.



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

[jira] [Updated] (AMBARI-17062) Namenode failed to start while installing a cluster from UI

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-17062:
-
Attachment: AMBARI-17062.patch

> Namenode failed to start while installing a cluster from UI
> ---
>
> Key: AMBARI-17062
> URL: https://issues.apache.org/jira/browse/AMBARI-17062
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-17062.patch
>
>
> STR: Install a cluster from UI with HDFS, ZK and YARN  
> Namenode fails to start  
> The cluster is live here: 
> 
> 
> 
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
>  line 414, in 
> NameNode().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 257, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
>  line 101, in start
> upgrade_suspended=params.upgrade_suspended, env=env)
>   File 
> "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", line 89, 
> in thunk
> return fn(*args, **kwargs)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py",
>  line 155, in namenode
> create_log_dir=True
>   File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/utils.py",
>  line 269, in service
> Execute(daemon_cmd, not_if=process_id_exists_command, 
> environment=hadoop_env_exports)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 
> 155, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 160, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 124, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 273, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 70, in inner
> result = function(command, **kwargs)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 92, in checked_call
> tries=tries, try_sleep=try_sleep)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 293, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'ambari-sudo.sh su 
> hdfs -l -s /bin/bash -c 'ulimit -c unlimited ;  
> /usr/hdp/current/hadoop-client/sbin/hadoop-daemon.sh --config 
> /usr/hdp/current/hadoop-client/conf start namenode'' returned 1.  
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> starting namenode, logging to 
> /grid/0/log/hdfs/hdfs/hadoop-hdfs-namenode-os-r7-vsrfou-ambari-serv-11r-1.out
> log4j:ERROR setFile(null,true) call failed.
> java.io.FileNotFoundException: ./nm-audit.log (Permission denied)
>   at java.io.FileOutputStream.open(Native Method)
>   at java.io.FileOutputStream.(FileOutputStream.java:221)
>   at java.io.FileOutputStream.(FileOutputStream.java:142)
>   at org.apache.log4j.FileAppender.setFile(FileAppender.java:294)
>   at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165)
>   at 
> org.apache.log4j.DailyRollingFileAppender.activateOptions(DailyRollingFileAppender.java:223)
>   at 
> org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307)
>   at 
> org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:172)
> 



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

[jira] [Updated] (AMBARI-16852) Update metrics collector pom.xml to use httpclient-4.2.5.jar

[Dmytro Sen (JIRA)]

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

Dmytro Sen updated AMBARI-16852:

Fix Version/s: (was: trunk)
   2.4.0

> Update metrics collector pom.xml to use httpclient-4.2.5.jar
> 
>
> Key: AMBARI-16852
> URL: https://issues.apache.org/jira/browse/AMBARI-16852
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Qin Liu
>Assignee: Qin Liu
> Fix For: 2.4.0
>
> Attachments: AMBARI-16852.patch
>
>
> 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.



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

[jira] [Commented] (AMBARI-16663) Refactor service_advisor apis to remove passing of stack_advisor

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-16663:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12808219/AMBARI-16663.v2.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 3 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The test build failed in ambari-server 

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

This message is automatically generated.

> Refactor service_advisor apis to remove passing of stack_advisor
> 
>
> Key: AMBARI-16663
> URL: https://issues.apache.org/jira/browse/AMBARI-16663
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16663.branch24.patch, 
> AMBARI-16663.branch24.v2.patch, AMBARI-16663.patch, AMBARI-16663.v2.patch
>
>




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

[jira] [Updated] (AMBARI-17067) Microsoft-r install script should use Ambari libraries instead of direct shell calls

[JIRA]

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

Balázs Bence Sári updated AMBARI-17067:
---
Attachment: diff1-trunk.patch

> Microsoft-r install script should use Ambari libraries instead of direct 
> shell calls
> 
>
> Key: AMBARI-17067
> URL: https://issues.apache.org/jira/browse/AMBARI-17067
> Project: Ambari
>  Issue Type: Task
>  Components: contrib
>Affects Versions: 2.4.0
>Reporter: Balázs Bence Sári
>Assignee: Balázs Bence Sári
>Priority: Critical
> Fix For: 2.4.1
>
> Attachments: diff1-trunk.patch
>
>
> In the install script of the management-pack we do everything using shell 
> calls. Instead we should use Ambari's python libraries.
> Example:
> {code}shell.call('sudo -u hdfs hadoop fs -mkdir -p /share'){code}
> As reference you can use the scripts of HDFS: 
> [https://github.com/apache/ambari/tree/trunk/ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts]
>  which make good use of Ambari libraries. Microsoft-R scripts should use just 
> like these.



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

[jira] [Updated] (AMBARI-17067) Microsoft-r install script should use Ambari libraries instead of direct shell calls

[JIRA]

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

Balázs Bence Sári updated AMBARI-17067:
---
Status: Patch Available  (was: In Progress)

> Microsoft-r install script should use Ambari libraries instead of direct 
> shell calls
> 
>
> Key: AMBARI-17067
> URL: https://issues.apache.org/jira/browse/AMBARI-17067
> Project: Ambari
>  Issue Type: Task
>  Components: contrib
>Affects Versions: 2.4.0
>Reporter: Balázs Bence Sári
>Assignee: Balázs Bence Sári
>Priority: Critical
> Fix For: 2.4.1
>
> Attachments: diff1-trunk.patch
>
>
> In the install script of the management-pack we do everything using shell 
> calls. Instead we should use Ambari's python libraries.
> Example:
> {code}shell.call('sudo -u hdfs hadoop fs -mkdir -p /share'){code}
> As reference you can use the scripts of HDFS: 
> [https://github.com/apache/ambari/tree/trunk/ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts]
>  which make good use of Ambari libraries. Microsoft-R scripts should use just 
> like these.



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

[jira] [Updated] (AMBARI-17036) Getting JMX Protocol Values On Large Cluster Takes Too Long

[Jonathan Hurley (JIRA)]

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

Jonathan Hurley updated AMBARI-17036:
-
Attachment: AMBARI-17036.patch

> Getting JMX Protocol Values On Large Cluster Takes Too Long
> ---
>
> Key: AMBARI-17036
> URL: https://issues.apache.org/jira/browse/AMBARI-17036
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17036.patch
>
>
> When retrieving JMX properties on large clusters, if there are JMX endpoints 
> which are unreachable, the URI protocol value is never cached. As a result, 
> multiple attempts are made to get the JMX protocol. Normally, this would be 
> fine, except that retrieving the configuration is using the 
> {{ClusterResourceProvider}}, which in turn, builds a {{ClusterHealthReport}}.
> {code}
>   at 
> org.apache.ambari.server.orm.dao.ServiceDesiredStateDAO.findByPK(ServiceDesiredStateDAO.java:41)
>   at 
> org.apache.ambari.server.orm.dao.ServiceDesiredStateDAO$$EnhancerByGuice$$d1ec71cf.CGLIB$findByPK$1()
>   at 
> org.apache.ambari.server.orm.dao.ServiceDesiredStateDAO$$EnhancerByGuice$$d1ec71cf$$FastClassByGuice$$9cad416f.invoke()
>   at 
> com.google.inject.internal.cglib.proxy.$MethodProxy.invokeSuper(MethodProxy.java:228)
>   at 
> com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:72)
>   at 
> org.apache.ambari.server.orm.AmbariLocalSessionInterceptor.invoke(AmbariLocalSessionInterceptor.java:43)
>   at 
> com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:72)
>   at 
> com.google.inject.internal.InterceptorStackCallback.intercept(InterceptorStackCallback.java:52)
>   at 
> org.apache.ambari.server.orm.dao.ServiceDesiredStateDAO$$EnhancerByGuice$$d1ec71cf.findByPK()
>   at 
> org.apache.ambari.server.state.ServiceImpl.getServiceDesiredStateEntity(ServiceImpl.java:759)
>   at 
> org.apache.ambari.server.state.ServiceImpl.getMaintenanceState(ServiceImpl.java:732)
>   at 
> org.apache.ambari.server.controller.MaintenanceStateHelper.getEffectiveState(MaintenanceStateHelper.java:216)
>   at 
> org.apache.ambari.server.controller.MaintenanceStateHelper.getEffectiveState(MaintenanceStateHelper.java:180)
>   at 
> org.apache.ambari.server.controller.MaintenanceStateHelper.getEffectiveState(MaintenanceStateHelper.java:194)
>   at 
> org.apache.ambari.server.state.cluster.ClusterImpl.getClusterHealthReport(ClusterImpl.java:3136)
>   at 
> org.apache.ambari.server.state.cluster.ClusterImpl.convertToResponse(ClusterImpl.java:2084)
>   at 
> org.apache.ambari.server.controller.AmbariManagementControllerImpl.getClusters(AmbariManagementControllerImpl.java:950)
>   at 
> org.apache.ambari.server.controller.AmbariManagementControllerImpl.getClusters(AmbariManagementControllerImpl.java:3082)
>   at 
> org.apache.ambari.server.controller.internal.ClusterResourceProvider$1.invoke(ClusterResourceProvider.java:202)
>   at 
> org.apache.ambari.server.controller.internal.ClusterResourceProvider$1.invoke(ClusterResourceProvider.java:199)
>   at 
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.getResources(AbstractResourceProvider.java:302)
>   at 
> org.apache.ambari.server.controller.internal.ClusterResourceProvider.getResources(ClusterResourceProvider.java:199)
>   at 
> org.apache.ambari.server.controller.internal.AbstractProviderModule.getDesiredConfigVersion(AbstractProviderModule.java:954)
>   at 
> org.apache.ambari.server.controller.internal.AbstractProviderModule.getJMXProtocol(AbstractProviderModule.java:1154)
>   at 
> org.apache.ambari.server.controller.jmx.JMXPropertyProvider.getJMXProtocol(JMXPropertyProvider.java:402)
>   at 
> org.apache.ambari.server.controller.jmx.JMXPropertyProvider.populateResource(JMXPropertyProvider.java:221)
>   at 
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:222)
>   at 
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:219)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> 

[jira] [Commented] (AMBARI-17064) Add Service Wizard-> Install, Start and Test page: Host row does not have message link

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko commented on AMBARI-17064:
--

+1 for the patch

> Add Service Wizard-> Install, Start and Test page: Host row does not have 
> message link
> --
>
> Key: AMBARI-17064
> URL: https://issues.apache.org/jira/browse/AMBARI-17064
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17064.patch
>
>
> *STR:*
> # Deployed a kerberized blueprint 2-node cluster
> # Deleted slider service from the cluster
> # Attempt adding slider service (client only service) via ASW
> *Actual behavior:* On Install, Start and Test page, message link appears only 
> for one host. When doing browser refreshes, sometimes message link appears 
> for another host and hides for the first one



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

[jira] [Created] (AMBARI-17062) Namenode failed to start while installing a cluster from UI

[Andrew Onischuk (JIRA)]

Andrew Onischuk created AMBARI-17062:


 Summary: Namenode failed to start while installing a cluster from 
UI
 Key: AMBARI-17062
 URL: https://issues.apache.org/jira/browse/AMBARI-17062
 Project: Ambari
  Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
 Fix For: 2.4.0


STR: Install a cluster from UI with HDFS, ZK and YARN  
Namenode fails to start  
The cluster is live here: 




Traceback (most recent call last):
  File 
"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
 line 414, in 
NameNode().execute()
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
 line 257, in execute
method(env)
  File 
"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
 line 101, in start
upgrade_suspended=params.upgrade_suspended, env=env)
  File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", 
line 89, in thunk
return fn(*args, **kwargs)
  File 
"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py",
 line 155, in namenode
create_log_dir=True
  File 
"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/utils.py",
 line 269, in service
Execute(daemon_cmd, not_if=process_id_exists_command, 
environment=hadoop_env_exports)
  File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
line 155, in __init__
self.env.run()
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
line 160, in run
self.run_action(resource, action)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
line 124, in run_action
provider_action()
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
 line 273, in action_run
tries=self.resource.tries, try_sleep=self.resource.try_sleep)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 70, 
in inner
result = function(command, **kwargs)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 92, 
in checked_call
tries=tries, try_sleep=try_sleep)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 140, 
in _call_wrapper
result = _call(command, **kwargs_copy)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 293, 
in _call
raise Fail(err_msg)
resource_management.core.exceptions.Fail: Execution of 'ambari-sudo.sh su 
hdfs -l -s /bin/bash -c 'ulimit -c unlimited ;  
/usr/hdp/current/hadoop-client/sbin/hadoop-daemon.sh --config 
/usr/hdp/current/hadoop-client/conf start namenode'' returned 1.  
Hortonworks #
This is MOTD message, added for testing in qe infra
starting namenode, logging to 
/grid/0/log/hdfs/hdfs/hadoop-hdfs-namenode-os-r7-vsrfou-ambari-serv-11r-1.out
log4j:ERROR setFile(null,true) call failed.
java.io.FileNotFoundException: ./nm-audit.log (Permission denied)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.(FileOutputStream.java:221)
at java.io.FileOutputStream.(FileOutputStream.java:142)
at org.apache.log4j.FileAppender.setFile(FileAppender.java:294)
at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165)
at 
org.apache.log4j.DailyRollingFileAppender.activateOptions(DailyRollingFileAppender.java:223)
at 
org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307)
at 
org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:172)






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

[jira] [Updated] (AMBARI-17064) Add Service Wizard-> Install, Start and Test page: Host row does not have message link

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk updated AMBARI-17064:
--
Attachment: AMBARI-17064.patch

> Add Service Wizard-> Install, Start and Test page: Host row does not have 
> message link
> --
>
> Key: AMBARI-17064
> URL: https://issues.apache.org/jira/browse/AMBARI-17064
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17064.patch
>
>
> *STR:*
> # Deployed a kerberized blueprint 2-node cluster
> # Deleted slider service from the cluster
> # Attempt adding slider service (client only service) via ASW
> *Actual behavior:* On Install, Start and Test page, message link appears only 
> for one host. When doing browser refreshes, sometimes message link appears 
> for another host and hides for the first one



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

[jira] [Created] (AMBARI-17065) Memory leak on ambari-agent

[Andrew Onischuk (JIRA)]

Andrew Onischuk created AMBARI-17065:


 Summary: Memory leak on ambari-agent
 Key: AMBARI-17065
 URL: https://issues.apache.org/jira/browse/AMBARI-17065
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.2.2
Reporter: Andrew Onischuk
Priority: Critical
 Fix For: 2.4.0






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

[jira] [Commented] (AMBARI-17055) Show better error message when VIEW USER can not access CAPACITY SCHEDULER View

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-17055:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12808371/AMBARI-17055_branch-2.4.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
contrib/views/capacity-scheduler contrib/views/utils.

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

This message is automatically generated.

> Show better error message when VIEW USER can not access CAPACITY SCHEDULER 
> View
> ---
>
> Key: AMBARI-17055
> URL: https://issues.apache.org/jira/browse/AMBARI-17055
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.2.2
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-17055_branch-2.4.patch
>
>
> When view user does not have cluster read permission, view will fail with 
> error.
> Show better error message indicating user does not have permission to view 
> the configurations.
> org.apache.ambari.view.utils.ambari.AmbariApiException: RA040 I/O error while 
> requesting Ambari
> at 
> org.apache.ambari.view.utils.ambari.AmbariApi.requestClusterAPI(AmbariApi.java:176)
> at 
> org.apache.ambari.view.utils.ambari.AmbariApi.requestClusterAPI(AmbariApi.java:142)
> at 
> org.apache.ambari.view.capacityscheduler.ConfigurationService.readFromCluster(ConfigurationService.java:291)
> at 
> org.apache.ambari.view.capacityscheduler.ConfigurationService.readClusterInfo(ConfigurationService.java:148)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at 
> 

[jira] [Updated] (AMBARI-17065) Memory leak on ambari-agent

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-17065:
-
Description: 
Ambari-agent is leaking memory (3-7GB every few days), requiring the agent to 
be restarted every 2 days.
17718 root 20 0 7343m 5.5g 4348 S 1.3 35.2 650:31.70 python2 --> 
/usr/bin/python2 /usr/lib/python2.6/site-packages/ambari_agent/main.py start

[root@gf0vsxbd022t ~]# ambari-agent --version 
2.2.1.0 
[root@gf0vsxbd022t ~]# rpm -qa|grep ambari-agent 
ambari-agent-2.2.1.0-161.x86_64 

This issue had been resolved in Ambari 2.2.x branch. After Ambari upgrade, 
customer is continuing to see memory leaks on Ambari 2.2.1.
Attaching pmap, lsof, configs and logs from the ambari agent process.

> Memory leak on ambari-agent
> ---
>
> Key: AMBARI-17065
> URL: https://issues.apache.org/jira/browse/AMBARI-17065
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.2.2
>Reporter: Andrew Onischuk
>Priority: Critical
> Fix For: 2.4.0
>
>
> Ambari-agent is leaking memory (3-7GB every few days), requiring the agent to 
> be restarted every 2 days.
> 17718 root 20 0 7343m 5.5g 4348 S 1.3 35.2 650:31.70 python2 --> 
> /usr/bin/python2 /usr/lib/python2.6/site-packages/ambari_agent/main.py start
> [root@gf0vsxbd022t ~]# ambari-agent --version 
> 2.2.1.0 
> [root@gf0vsxbd022t ~]# rpm -qa|grep ambari-agent 
> ambari-agent-2.2.1.0-161.x86_64 
> This issue had been resolved in Ambari 2.2.x branch. After Ambari upgrade, 
> customer is continuing to see memory leaks on Ambari 2.2.1.
> Attaching pmap, lsof, configs and logs from the ambari agent process.



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

[jira] [Updated] (AMBARI-17065) Memory leak on ambari-agent

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-17065:
-
Description: 
Ambari-agent is leaking memory (3-7GB every few days), requiring the agent to 
be restarted every 2 days.
17718 root 20 0 7343m 5.5g 4348 S 1.3 35.2 650:31.70 python2 --> 
/usr/bin/python2 /usr/lib/python2.6/site-packages/ambari_agent/main.py start

[root@gf0vsxbd022t ~]# ambari-agent --version 
2.2.1.0 
[root@gf0vsxbd022t ~]# rpm -qa|grep ambari-agent 
ambari-agent-2.2.1.0-161.x86_64 

This issue had been resolved in Ambari 2.2.x branch. After Ambari upgrade, we 
continue to see memory leaks on Ambari 2.2.1.
Attaching pmap, lsof, configs and logs from the ambari agent process.

  was:
Ambari-agent is leaking memory (3-7GB every few days), requiring the agent to 
be restarted every 2 days.
17718 root 20 0 7343m 5.5g 4348 S 1.3 35.2 650:31.70 python2 --> 
/usr/bin/python2 /usr/lib/python2.6/site-packages/ambari_agent/main.py start

[root@gf0vsxbd022t ~]# ambari-agent --version 
2.2.1.0 
[root@gf0vsxbd022t ~]# rpm -qa|grep ambari-agent 
ambari-agent-2.2.1.0-161.x86_64 

This issue had been resolved in Ambari 2.2.x branch. After Ambari upgrade, 
customer is continuing to see memory leaks on Ambari 2.2.1.
Attaching pmap, lsof, configs and logs from the ambari agent process.


> Memory leak on ambari-agent
> ---
>
> Key: AMBARI-17065
> URL: https://issues.apache.org/jira/browse/AMBARI-17065
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.2.2
>Reporter: Andrew Onischuk
>Priority: Critical
> Fix For: 2.4.0
>
>
> Ambari-agent is leaking memory (3-7GB every few days), requiring the agent to 
> be restarted every 2 days.
> 17718 root 20 0 7343m 5.5g 4348 S 1.3 35.2 650:31.70 python2 --> 
> /usr/bin/python2 /usr/lib/python2.6/site-packages/ambari_agent/main.py start
> [root@gf0vsxbd022t ~]# ambari-agent --version 
> 2.2.1.0 
> [root@gf0vsxbd022t ~]# rpm -qa|grep ambari-agent 
> ambari-agent-2.2.1.0-161.x86_64 
> This issue had been resolved in Ambari 2.2.x branch. After Ambari upgrade, we 
> continue to see memory leaks on Ambari 2.2.1.
> Attaching pmap, lsof, configs and logs from the ambari agent process.



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

[jira] [Created] (AMBARI-17066) User is not able to complete the Ranger HA install incase of Start services failure

[Madhavi Amirneni (JIRA)]

Madhavi Amirneni created AMBARI-17066:
-

 Summary: User is not able to complete the Ranger HA install incase 
of Start services failure
 Key: AMBARI-17066
 URL: https://issues.apache.org/jira/browse/AMBARI-17066
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server, ambari-web
Affects Versions: 2.2.0
 Environment: HDP 2.4 with Ranger installed. Trying to set up Ranger 
HA. 
Reporter: Madhavi Amirneni


Installed HDP 2.4 and try to set up Ranger admin HA, if any of the steps during 
the Ranger admin fails, then the complete button never comes to be active. 

Reproduction Steps:
1. Install HDP and Install Ranger.
3. Perform the Loadbalancer set up for Ranger
4. Go to ambari and go through the step of setting up Ranger admin HA. 

During the Ranger admin HA setup, the install process continues as:
Stop Services - Passed
Install additional Ranger Admin - Passed
Reconfigure Ranger - passed 
Start Services - failed 

Expected results:
Incase of start service failure, user should be allowed to click on "Complete" 
button and warned that some of the services failed to start (As a behavior with 
other Ambari services)

Observations:
User needs to hit on X on the top right corner of the dialog box which informs 
user that "Doing so might leave the cluster unstable".




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

[jira] [Created] (AMBARI-17067) Microsoft-r install script should use Ambari libraries instead of direct shell calls

[JIRA]

Balázs Bence Sári created AMBARI-17067:
--

 Summary: Microsoft-r install script should use Ambari libraries 
instead of direct shell calls
 Key: AMBARI-17067
 URL: https://issues.apache.org/jira/browse/AMBARI-17067
 Project: Ambari
  Issue Type: Task
  Components: contrib
Affects Versions: 2.4.0
Reporter: Balázs Bence Sári
Assignee: Balázs Bence Sári
Priority: Critical
 Fix For: 2.4.1


In the install script of the management-pack we do everything using shell 
calls. Instead we should use Ambari's python libraries.
Example:
{code}shell.call('sudo -u hdfs hadoop fs -mkdir -p /share'){code}

As reference you can use the scripts of HDFS: 
[https://github.com/apache/ambari/tree/trunk/ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts]
 which make good use of Ambari libraries. Microsoft-R scripts should use just 
like these.



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

[jira] [Commented] (AMBARI-16272) Ambari Upgrade shouldn't automatically add stack configs

[Hudson (JIRA)]

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

Hudson commented on AMBARI-16272:
-

FAILURE: Integrated in Ambari-trunk-Commit #5009 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5009/])
revert broken parts of "AMBARI-16272. Ambari Upgrade shouldn't (dlysnichenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=bc9097b146a77a833183cd3d560268644964e87f])
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UpgradeResourceProviderHDP22Test.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
* ambari-server/src/main/java/org/apache/ambari/server/state/ConfigHelper.java
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UpgradeResourceProviderTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/AbstractUpgradeCatalog.java


> Ambari Upgrade shouldn't automatically add stack configs
> 
>
> Key: AMBARI-16272
> URL: https://issues.apache.org/jira/browse/AMBARI-16272
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-16272.patch
>
>
> Today, Ambari Upgrade will automatically add stack configs.
> However, it also causes problems when default properties or properties with 
> default value such as "localhost" end up being added.
> This led to many bugs. E.g., cluster with NameNode HA shouldn't automatically 
> add dfs.namenode.secondary.http-address
> Properties should be explicitly added during RU/EU config packs instead of 
> relying on annotating them with.
> {code}
> DONT_ADD_ON_UPGRADE
> {code}
> This logic today will even add new config types. E.g., add ranger-env even 
> though Ranger is not installed. If the customer then upgrades the stack from 
> HDP 2.2 to 2.3, and then adds Ranger, they can get the wrong configs.
> If we change this behavior, it's good to do so in a major release such as 2.4
> We add required xml tags to properties:
> # If it's a new property from stack X to X+1, we don't want it to be added 
> automatically added. If we do want to add it, we should annotate it with 
> "ADD_ON_UPGRADE"
> # Similar to above, but handle "DELETE_ON_UPGRADE"
> # Similar to above, but handle "CHANGE_ON_UPGRADE" to forcefully set to a new 
> value if it exists



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

[jira] [Commented] (AMBARI-17056) View config-Custom views are not working after kerberization

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-17056:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12808374/AMBARI-17056_branch-2.4.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
contrib/views/hive contrib/views/utils.

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

This message is automatically generated.

> View config-Custom views are not working after kerberization
> 
>
> Key: AMBARI-17056
> URL: https://issues.apache.org/jira/browse/AMBARI-17056
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-17056_branch-2.4.patch, screenshot.png
>
>
> custom views are not working after kerberos is enabled.



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

[jira] [Updated] (AMBARI-17064) Add Service Wizard-> Install, Start and Test page: Host row does not have message link

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk updated AMBARI-17064:
--
Status: Patch Available  (was: Open)

> Add Service Wizard-> Install, Start and Test page: Host row does not have 
> message link
> --
>
> Key: AMBARI-17064
> URL: https://issues.apache.org/jira/browse/AMBARI-17064
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17064.patch
>
>
> *STR:*
> # Deployed a kerberized blueprint 2-node cluster
> # Deleted slider service from the cluster
> # Attempt adding slider service (client only service) via ASW
> *Actual behavior:* On Install, Start and Test page, message link appears only 
> for one host. When doing browser refreshes, sometimes message link appears 
> for another host and hides for the first one



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

[jira] [Updated] (AMBARI-16852) Update metrics collector pom.xml to use httpclient-4.2.5.jar

[Dmytro Sen (JIRA)]

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

Dmytro Sen updated AMBARI-16852:

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

Committed to trunk and branch-2.4

> Update metrics collector pom.xml to use httpclient-4.2.5.jar
> 
>
> Key: AMBARI-16852
> URL: https://issues.apache.org/jira/browse/AMBARI-16852
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Qin Liu
>Assignee: Qin Liu
> Fix For: 2.4.0
>
> Attachments: AMBARI-16852.patch
>
>
> 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.



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

[jira] [Updated] (AMBARI-17030) Agents should automatically restart if there is a memory leak

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-17030:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to trunk and branch-2.4

> Agents should automatically restart if there is a memory leak
> -
>
> Key: AMBARI-17030
> URL: https://issues.apache.org/jira/browse/AMBARI-17030
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-17030.patch
>
>
> Add an agent capability to auto-restart when the memory threshold for the
> agent process exceeds a limit. This should be a configurable property (e.g.
> agent_memory_threshold) where any positive value, say in MB, is a limit at
> which agent should get restarted.
> The restart itself should be executed when there are no
> EXECUTION/AUTO_EXECUTION commands in pipeline. So when the condition is
> reached for agent auto restart, a flag should be set to restart when agent is
> not doing any work.
> A hard limit should also be set where the agent will be restarted even if
> there are commands in pipeline.



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

[jira] [Updated] (AMBARI-17060) Visual explain unit tests

[Pallav Kulshreshtha (JIRA)]

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

Pallav Kulshreshtha updated AMBARI-17060:
-
Attachment: AMBARI-17060_branch-2.4.patch

> Visual explain unit tests
> -
>
> Key: AMBARI-17060
> URL: https://issues.apache.org/jira/browse/AMBARI-17060
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.0.0
>Reporter: Pallav Kulshreshtha
>Assignee: Pallav Kulshreshtha
> Fix For: 2.4.0
>
> Attachments: AMBARI-17060_branch-2.4.patch
>
>
> Write visual explain test cases.



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

[jira] [Updated] (AMBARI-17054) Configure Atlas Ranger Plugin

[Gautam Borad (JIRA)]

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

Gautam Borad updated AMBARI-17054:
--
Attachment: AMBARI-17054.1.patch

> Configure Atlas Ranger Plugin
> -
>
> Key: AMBARI-17054
> URL: https://issues.apache.org/jira/browse/AMBARI-17054
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Gautam Borad
>Assignee: Gautam Borad
> Fix For: 2.4.0
>
> Attachments: AMBARI-17054.1.patch
>
>
> Need to do following changes to support Ranger Atlas Plugin from Ambari: 
> 1) Check stack support  and provide smart config section to Enable / disable 
> ranger atlas plugin
> 2) Stack advisor changes to suggest recommended configs on enable / disable 
> plugin actions. 
> 3) Ranger service creation on Enable plugin action from Ambari. 



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

[jira] [Updated] (AMBARI-17063) Retrieve specific metrics when Ambari queries NameNode HA states

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-17063:
-
Attachment: AMBARI-17063.patch

> Retrieve specific metrics when Ambari queries NameNode HA states
> 
>
> Key: AMBARI-17063
> URL: https://issues.apache.org/jira/browse/AMBARI-17063
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-17063.patch
>
>
> This is a follow-on jira of BUG-53459: when Ambari queries NameNode's HA
> states, currently it retrieves a group of metrics including some unnecessary
> ones that may compete for NameNode lock. It would be better for Ambari to only
> retrieve HA state metrics from NameNode.



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

[jira] [Updated] (AMBARI-17063) Retrieve specific metrics when Ambari queries NameNode HA states

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-17063:
-
Status: Patch Available  (was: Open)

> Retrieve specific metrics when Ambari queries NameNode HA states
> 
>
> Key: AMBARI-17063
> URL: https://issues.apache.org/jira/browse/AMBARI-17063
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-17063.patch
>
>
> This is a follow-on jira of BUG-53459: when Ambari queries NameNode's HA
> states, currently it retrieves a group of metrics including some unnecessary
> ones that may compete for NameNode lock. It would be better for Ambari to only
> retrieve HA state metrics from NameNode.



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

[jira] [Updated] (AMBARI-16663) Refactor service_advisor apis to remove passing of stack_advisor

[Lav Jain (JIRA)]

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

Lav Jain updated AMBARI-16663:
--
Status: Patch Available  (was: In Progress)

> Refactor service_advisor apis to remove passing of stack_advisor
> 
>
> Key: AMBARI-16663
> URL: https://issues.apache.org/jira/browse/AMBARI-16663
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16663.branch24.patch, 
> AMBARI-16663.branch24.v2.patch, AMBARI-16663.branch24.v3.patch, 
> AMBARI-16663.patch, AMBARI-16663.v2.patch, AMBARI-16663.v3.patch
>
>




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

[jira] [Commented] (AMBARI-17043) Fix description of SERVICE.ADD_DELETE_SERVICES permission

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-17043:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12808211/AMBARI-17043_trunk_01.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in 
ambari-server:

  org.apache.ambari.server.state.ServicePropertiesTest
  
org.apache.ambari.server.controller.internal.HostResourceProviderTest

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

This message is automatically generated.

> Fix description of SERVICE.ADD_DELETE_SERVICES permission
> -
>
> Key: AMBARI-17043
> URL: https://issues.apache.org/jira/browse/AMBARI-17043
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.3.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: rbac
> Fix For: 2.4.0
>
> Attachments: AMBARI-17043_branch-2.4_01.patch, 
> AMBARI-17043_trunk_01.patch
>
>
> The description of the SERVICE.ADD_DELETE_SERVICES permission currently reads
> {quote}
> Add Service to cluster
> {quote}
> This should be changed to
> {quote}
> Add/delete services
> {quote}



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

[jira] [Updated] (AMBARI-17070) Change HAWQ DFS Url from hawq_default to hawq_data

[Matt (JIRA)]

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

Matt updated AMBARI-17070:
--
Attachment: AMBARI-17070-trunk-orig.patch

> Change HAWQ DFS Url from hawq_default to hawq_data
> --
>
> Key: AMBARI-17070
> URL: https://issues.apache.org/jira/browse/AMBARI-17070
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server, ambari-web, stacks
>Reporter: Matt
>Assignee: Matt
>Priority: Trivial
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-17070-trunk-orig.patch
>
>
> Change HAWQ DFS Url from hawq_default to hawq_data



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