[jira] [Updated] (AMBARI-20162) HiveView2.0: No notifications for successful query which yields no output.

2017-02-23 Thread Pallav Kulshreshtha (JIRA)

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

Pallav Kulshreshtha updated AMBARI-20162:
-
Attachment: AMBARI-20162-trunk.patch

> HiveView2.0: No notifications for successful query which yields no output.
> ---
>
> Key: AMBARI-20162
> URL: https://issues.apache.org/jira/browse/AMBARI-20162
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Pallav Kulshreshtha
>Assignee: Pallav Kulshreshtha
> Fix For: 2.5.0
>
> Attachments: AMBARI-20162-trunk.patch
>
>
> Hive view: No notifications for successfull query which yields no output..
> There is no notification in RESULTS as well as LOG tab.
> eg queries like
> create table:
> create table abc(x int, y int, z string)
> slect query on empty table:
> select * from test;
> queries got executed successfully with no notifications.
> It should give some info like succesfull query execution(OK) retrieve empty 
> set for select query on table(with no data)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-20109) HDP stack - enable shuffle connection keep-alive

2017-02-23 Thread Siddharth Seth (JIRA)

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

Siddharth Seth commented on AMBARI-20109:
-

[~swapanshridhar] - could you please revert the change. This was not ready to 
be committed. I had cancelled the patch.

> HDP stack - enable shuffle connection keep-alive
> 
>
> Key: AMBARI-20109
> URL: https://issues.apache.org/jira/browse/AMBARI-20109
> Project: Ambari
>  Issue Type: Task
>  Components: stacks
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Fix For: 2.5.0
>
> Attachments: AMBARI-20109.01.patch, AMBARI-20109.02.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20162) HiveView2.0: No notifications for successful query which yields no output.

2017-02-23 Thread Pallav Kulshreshtha (JIRA)

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

Pallav Kulshreshtha updated AMBARI-20162:
-
Attachment: (was: AMBARI-20162-trunk.patch)

> HiveView2.0: No notifications for successful query which yields no output.
> ---
>
> Key: AMBARI-20162
> URL: https://issues.apache.org/jira/browse/AMBARI-20162
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Pallav Kulshreshtha
>Assignee: Pallav Kulshreshtha
> Fix For: 2.5.0
>
>
> Hive view: No notifications for successfull query which yields no output..
> There is no notification in RESULTS as well as LOG tab.
> eg queries like
> create table:
> create table abc(x int, y int, z string)
> slect query on empty table:
> select * from test;
> queries got executed successfully with no notifications.
> It should give some info like succesfull query execution(OK) retrieve empty 
> set for select query on table(with no data)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20162) HiveView2.0: No notifications for successful query which yields no output.

2017-02-23 Thread Pallav Kulshreshtha (JIRA)

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

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

> HiveView2.0: No notifications for successful query which yields no output.
> ---
>
> Key: AMBARI-20162
> URL: https://issues.apache.org/jira/browse/AMBARI-20162
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Pallav Kulshreshtha
>Assignee: Pallav Kulshreshtha
> Fix For: 2.5.0
>
> Attachments: AMBARI-20162-trunk.patch
>
>
> Hive view: No notifications for successfull query which yields no output..
> There is no notification in RESULTS as well as LOG tab.
> eg queries like
> create table:
> create table abc(x int, y int, z string)
> slect query on empty table:
> select * from test;
> queries got executed successfully with no notifications.
> It should give some info like succesfull query execution(OK) retrieve empty 
> set for select query on table(with no data)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20162) HiveView2.0: No notifications for successful query which yields no output.

2017-02-23 Thread Pallav Kulshreshtha (JIRA)

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

Pallav Kulshreshtha updated AMBARI-20162:
-
Attachment: AMBARI-20162-trunk.patch

> HiveView2.0: No notifications for successful query which yields no output.
> ---
>
> Key: AMBARI-20162
> URL: https://issues.apache.org/jira/browse/AMBARI-20162
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Pallav Kulshreshtha
>Assignee: Pallav Kulshreshtha
> Fix For: 2.5.0
>
> Attachments: AMBARI-20162-trunk.patch
>
>
> Hive view: No notifications for successfull query which yields no output..
> There is no notification in RESULTS as well as LOG tab.
> eg queries like
> create table:
> create table abc(x int, y int, z string)
> slect query on empty table:
> select * from test;
> queries got executed successfully with no notifications.
> It should give some info like succesfull query execution(OK) retrieve empty 
> set for select query on table(with no data)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (AMBARI-20162) HiveView2.0: No notifications for successful query which yields no output.

2017-02-23 Thread Pallav Kulshreshtha (JIRA)
Pallav Kulshreshtha created AMBARI-20162:


 Summary: HiveView2.0: No notifications for successful query which 
yields no output.
 Key: AMBARI-20162
 URL: https://issues.apache.org/jira/browse/AMBARI-20162
 Project: Ambari
  Issue Type: Bug
  Components: ambari-views
Affects Versions: 2.5.0
Reporter: Pallav Kulshreshtha
Assignee: Pallav Kulshreshtha
 Fix For: 2.5.0


Hive view: No notifications for successfull query which yields no output..
There is no notification in RESULTS as well as LOG tab.
eg queries like
create table:
create table abc(x int, y int, z string)
slect query on empty table:
select * from test;
queries got executed successfully with no notifications.
It should give some info like succesfull query execution(OK) retrieve empty set 
for select query on table(with no data)




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (AMBARI-20161) Workflow Manager-mapred action contains duplicates in editor if user saves and reopen editor

2017-02-23 Thread Belliraj HB (JIRA)
Belliraj HB created AMBARI-20161:


 Summary: Workflow Manager-mapred action contains duplicates in 
editor if user saves and reopen editor
 Key: AMBARI-20161
 URL: https://issues.apache.org/jira/browse/AMBARI-20161
 Project: Ambari
  Issue Type: Bug
  Components: ambari-views
Affects Versions: 2.5.0
Reporter: Belliraj HB
Assignee: Padma Priya Nagaraj
Priority: Critical
 Fix For: 2.5.0


Open a Map-Red editor.
Fill in details and Save.
Reopen the editor. you will see the configuration in both general and advanced 
section.
Preview xml looks fine though.
Expected:
the configuration should be not duplicated.
Reported by ArtemErvits



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-20155) EU: Manual Step without any context after "All Service Checks" fail

2017-02-23 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on AMBARI-20155:


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

This message is automatically generated.

> EU: Manual Step without any context after "All Service Checks" fail
> ---
>
> Key: AMBARI-20155
> URL: https://issues.apache.org/jira/browse/AMBARI-20155
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20155_1.patch
>
>
> During EU from 2.5.3.0-2.6.0.0, a manual step popped up that didn't make 
> sense.
> It says "Manual steps required [] I have performed the manual steps above." 
> without telling the user what the manual steps are.
> The BE is not providing a message for display.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-20034) USER to GROUP mapping (hdfs_user -> hadoop_group) should be stack driven

2017-02-23 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on AMBARI-20034:


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

{color:red}-1 patch{color}.  The patch command could not apply the patch.

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

This message is automatically generated.

> USER to GROUP mapping (hdfs_user -> hadoop_group) should be stack driven
> 
>
> Key: AMBARI-20034
> URL: https://issues.apache.org/jira/browse/AMBARI-20034
> Project: Ambari
>  Issue Type: Bug
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
> Fix For: 2.5.0
>
> Attachments: AMBARI-20034_2.5.patch, AMBARI-20034.patch, 
> AMBARI-20034_trunk.patch
>
>
> There is a hard coded logic to creating the user-group mapping for services. 
> This presents an issue for custom services. Fix is to make it stack driven by 
> connecting user to its groups within the configuration/stack definition itself



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-20158) Host filter is missing for admin user after upgrading to ambari 2.4.2 or above

2017-02-23 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on AMBARI-20158:


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

This message is automatically generated.

> Host filter is missing for admin user after upgrading to ambari 2.4.2 or above
> --
>
> Key: AMBARI-20158
> URL: https://issues.apache.org/jira/browse/AMBARI-20158
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20158-fix1.patch, AMBARI-20158.patch
>
>
> *STR:*
> # Deploy ambari cluster and customize ambari behavior for "admin user" via 
> experimental page (For example: opsDuringUpgrade. Note this flag is most 
> frequently enabled by the customer for previous versions of ambari)
> # Upgrade ambari to 2.4.2 or above
> *Expected behavior:* Admin user should be able to use new combo box for 
> filtering hosts on Hosts page
> *Actual behavior:* new combobox is missing for "admin user" and there is no 
> way to filter hosts via ambari-web. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-20047) Repository config user needs to set customized service user in Ranger when service plugin is enabled

2017-02-23 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-20047:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1079 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1079/])
AMBARI-20047 Repository config user needs to set customized service user 
(mugdha: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e2c92d5f6b5d0ba8c7d749266fa7b44235f7810f])
* (edit) 
ambari-common/src/main/python/resource_management/libraries/functions/setup_ranger_plugin_xml.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/YARN/configuration/ranger-yarn-plugin-properties.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/ATLAS/configuration/ranger-atlas-plugin-properties.xml
* (edit) ambari-server/src/test/python/stacks/2.6/common/test_stack_advisor.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/HBASE/configuration/ranger-hbase-plugin-properties.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/ranger-hive-plugin-properties.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/HDFS/configuration/ranger-hdfs-plugin-properties.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/KAFKA/configuration/ranger-kafka-plugin-properties.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/stack_advisor.py


> Repository config user needs to set customized service user in Ranger when 
> service plugin is enabled
> 
>
> Key: AMBARI-20047
> URL: https://issues.apache.org/jira/browse/AMBARI-20047
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.5.0
>
> Attachments: AMBARI-20047.1.patch, AMBARI-20047.2_trunk.patch, 
> AMBARI-20047_branch_2.5.patch, AMBARI-20047.patch
>
>
> The property {{REPOSITORY_CONFIG_USERNAME}} in Advanced 
> ranger-*-plugin-properties is not updated to the custom user-name when 
> services are using custom users.
> This causes issues especially in cases of Test connection, and policy user 
> which is given default permissions in Ranger.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-20126) Add support for Spark2 upgrade from HDP-2.5

2017-02-23 Thread Dmytro Grinenko (JIRA)

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

Dmytro Grinenko commented on AMBARI-20126:
--

Tests not required as most changes done on XML structure, which r checked on 
general purpose by already written tests

> Add support for Spark2 upgrade from HDP-2.5
> ---
>
> Key: AMBARI-20126
> URL: https://issues.apache.org/jira/browse/AMBARI-20126
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Blocker
>  Labels: express_upgrade, rolling_upgrade
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-20126.patch, AMBARI-20126.patch.1
>
>
> Support of Spark2 service upgrade (both EU and EU) from HDP-2.5.x to 2.6 need 
> to be added



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-20047) Repository config user needs to set customized service user in Ranger when service plugin is enabled

2017-02-23 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-20047:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6837 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6837/])
AMBARI-20047 Repository config user needs to set customized service user 
(mugdha: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=14a99627bae2eeb108cfd1b45b953d3c667e8006])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/KAFKA/configuration/ranger-kafka-plugin-properties.xml
* (edit) ambari-server/src/test/python/stacks/2.6/common/test_stack_advisor.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/HBASE/configuration/ranger-hbase-plugin-properties.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/ranger-hive-plugin-properties.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/ATLAS/configuration/ranger-atlas-plugin-properties.xml
* (edit) 
ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/service_advisor.py
* (edit) 
ambari-common/src/main/python/resource_management/libraries/functions/setup_ranger_plugin_xml.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/YARN/configuration/ranger-yarn-plugin-properties.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/HDFS/configuration/ranger-hdfs-plugin-properties.xml
* (edit) 
ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/configuration/ranger-hdfs-plugin-properties.xml
* (edit) 
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/configuration/ranger-yarn-plugin-properties.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/stack_advisor.py
* (edit) 
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/service_advisor.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/3.0/properties/stack_features.json


> Repository config user needs to set customized service user in Ranger when 
> service plugin is enabled
> 
>
> Key: AMBARI-20047
> URL: https://issues.apache.org/jira/browse/AMBARI-20047
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.5.0
>
> Attachments: AMBARI-20047.1.patch, AMBARI-20047.2_trunk.patch, 
> AMBARI-20047_branch_2.5.patch, AMBARI-20047.patch
>
>
> The property {{REPOSITORY_CONFIG_USERNAME}} in Advanced 
> ranger-*-plugin-properties is not updated to the custom user-name when 
> services are using custom users.
> This causes issues especially in cases of Test connection, and policy user 
> which is given default permissions in Ranger.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-20116) Stack Recommendation for Atlas not working on change of Kafka broker port.

2017-02-23 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-20116:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6837 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6837/])
AMBARI-20116 Stack Recommendation for Atlas not working on change of (mugdha: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7d1e04b39709df51a94343b1ee699a4b002ac3d3])
* (edit) 
ambari-server/src/main/resources/common-services/ATLAS/0.7.0.2.5/configuration/application-properties.xml


> Stack Recommendation for Atlas not working on change of Kafka broker port.
> --
>
> Key: AMBARI-20116
> URL: https://issues.apache.org/jira/browse/AMBARI-20116
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.5.0
>
> Attachments: AMBARI-20116.patch
>
>
> When Kafka-broker port is changed, appropriate change should be made for 
> Atlas Kafla broker servers, this does not happen as stack-dependency for the 
> same is missing.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-20116) Stack Recommendation for Atlas not working on change of Kafka broker port.

2017-02-23 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-20116:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1078 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1078/])
AMBARI-20116 Stack Recommendation for Atlas not working on change of (mugdha: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7ee057287fad43b3269199310709dd7c6331a2e6])
* (edit) 
ambari-server/src/main/resources/common-services/ATLAS/0.7.0.2.5/configuration/application-properties.xml


> Stack Recommendation for Atlas not working on change of Kafka broker port.
> --
>
> Key: AMBARI-20116
> URL: https://issues.apache.org/jira/browse/AMBARI-20116
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.5.0
>
> Attachments: AMBARI-20116.patch
>
>
> When Kafka-broker port is changed, appropriate change should be made for 
> Atlas Kafla broker servers, this does not happen as stack-dependency for the 
> same is missing.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20116) Stack Recommendation for Atlas not working on change of Kafka broker port.

2017-02-23 Thread Vishal Suvagia (JIRA)

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

Vishal Suvagia updated AMBARI-20116:

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

Commited on 
[branch-2.5|https://github.com/apache/ambari/commit/7ee057287fad43b3269199310709dd7c6331a2e6]
 and 
[trunk|https://github.com/apache/ambari/commit/7d1e04b39709df51a94343b1ee699a4b002ac3d3]

> Stack Recommendation for Atlas not working on change of Kafka broker port.
> --
>
> Key: AMBARI-20116
> URL: https://issues.apache.org/jira/browse/AMBARI-20116
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.5.0
>
> Attachments: AMBARI-20116.patch
>
>
> When Kafka-broker port is changed, appropriate change should be made for 
> Atlas Kafla broker servers, this does not happen as stack-dependency for the 
> same is missing.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-19618) Make cohosted components configurable in metainfo.xml instead of hardcoding in UI

2017-02-23 Thread Yao Lei (JIRA)

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

Yao Lei updated AMBARI-19618:
-
Resolution: Duplicate
Status: Resolved  (was: Patch Available)

> Make cohosted components configurable in metainfo.xml instead of hardcoding 
> in UI
> -
>
> Key: AMBARI-19618
> URL: https://issues.apache.org/jira/browse/AMBARI-19618
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Yao Lei
> Fix For: trunk, 3.0.0
>
> Attachments: after_patched_hive1.png, after_patched_hive2.png, 
> after_patched_ranger1.png, after_patched_ranger2.png, 
> after_patched_ranger3.png, AMBARI-19618_1.patch, AMBARI-19618_2.patch, 
> AMBARI-19618_3.patch
>
>
> Cohosted components information now is hardcoded in 
> stack_service_component.js  as following:
> App.StackServiceComponent.coHost = {
>   'WEBHCAT_SERVER': 'HIVE_SERVER'
> };
> It's better to move them from javascript to metainfom.xml by adding tag 
> in stack like following:
> 
>   WEBHCAT_SERVER
>   WebHCat Server
>   MASTER
>   1
>   true
>   true
>   HIVE_SERVER
> 
> //https://issues.apache.org/jira/browse/AMBARI-19557
> //http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.5.3/bk_security/content/ch03s01s03s01.html
> 
>RANGER_USERSYNC
>Ranger Usersync
>MASTER
>1
>true
>RANGER_ADMIN
> 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20047) Repository config user needs to set customized service user in Ranger when service plugin is enabled

2017-02-23 Thread Vishal Suvagia (JIRA)

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

Vishal Suvagia updated AMBARI-20047:

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

Committed on 
[branch-2.5|https://github.com/apache/ambari/commit/e2c92d5f6b5d0ba8c7d749266fa7b44235f7810f]
 and 
[trunk|https://github.com/apache/ambari/commit/14a99627bae2eeb108cfd1b45b953d3c667e8006]

> Repository config user needs to set customized service user in Ranger when 
> service plugin is enabled
> 
>
> Key: AMBARI-20047
> URL: https://issues.apache.org/jira/browse/AMBARI-20047
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.5.0
>
> Attachments: AMBARI-20047.1.patch, AMBARI-20047.2_trunk.patch, 
> AMBARI-20047_branch_2.5.patch, AMBARI-20047.patch
>
>
> The property {{REPOSITORY_CONFIG_USERNAME}} in Advanced 
> ranger-*-plugin-properties is not updated to the custom user-name when 
> services are using custom users.
> This causes issues especially in cases of Test connection, and policy user 
> which is given default permissions in Ranger.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20158) Host filter is missing for admin user after upgrading to ambari 2.4.2 or above

2017-02-23 Thread Richard Zang (JIRA)

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

Richard Zang updated AMBARI-20158:
--
Attachment: AMBARI-20158-fix1.patch

> Host filter is missing for admin user after upgrading to ambari 2.4.2 or above
> --
>
> Key: AMBARI-20158
> URL: https://issues.apache.org/jira/browse/AMBARI-20158
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20158-fix1.patch, AMBARI-20158.patch
>
>
> *STR:*
> # Deploy ambari cluster and customize ambari behavior for "admin user" via 
> experimental page (For example: opsDuringUpgrade. Note this flag is most 
> frequently enabled by the customer for previous versions of ambari)
> # Upgrade ambari to 2.4.2 or above
> *Expected behavior:* Admin user should be able to use new combo box for 
> filtering hosts on Hosts page
> *Actual behavior:* new combobox is missing for "admin user" and there is no 
> way to filter hosts via ambari-web. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20158) Host filter is missing for admin user after upgrading to ambari 2.4.2 or above

2017-02-23 Thread Richard Zang (JIRA)

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

Richard Zang updated AMBARI-20158:
--
Status: Patch Available  (was: Reopened)

> Host filter is missing for admin user after upgrading to ambari 2.4.2 or above
> --
>
> Key: AMBARI-20158
> URL: https://issues.apache.org/jira/browse/AMBARI-20158
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20158-fix1.patch, AMBARI-20158.patch
>
>
> *STR:*
> # Deploy ambari cluster and customize ambari behavior for "admin user" via 
> experimental page (For example: opsDuringUpgrade. Note this flag is most 
> frequently enabled by the customer for previous versions of ambari)
> # Upgrade ambari to 2.4.2 or above
> *Expected behavior:* Admin user should be able to use new combo box for 
> filtering hosts on Hosts page
> *Actual behavior:* new combobox is missing for "admin user" and there is no 
> way to filter hosts via ambari-web. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-20150) Hive View 2.0 Tables tab does not open at all if Ranger policy does not include access to the 'admin' user

2017-02-23 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on AMBARI-20150:


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

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

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

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

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

{color:red}-1 core tests{color}.  The test build failed in 
contrib/views/hive20 

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

This message is automatically generated.

> Hive View 2.0 Tables tab does not open at all if Ranger policy does not 
> include access to the 'admin' user
> --
>
> Key: AMBARI-20150
> URL: https://issues.apache.org/jira/browse/AMBARI-20150
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.5.0
>
> Attachments: AMBARI-20150.2.branch-2.5.patch, 
> AMBARI-20150.branch-2.5.patch
>
>
> User should be given an appropriate error message while navigating to 
> 'Tables' tab upon opening 'Authorizations' tab of a specific table



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-20160) Side Nav: multiple fixes after integrated to trunk

2017-02-23 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-20160:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6836 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6836/])
AMBARI-20160.Side Nav: multiple fixes after integrated to trunk.(xiwang) 
(xiwang: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9c5f097a10c19e38fa4920067afb351449c1d5e4])
* (edit) ambari-web/app/templates/main/admin.hbs
* (edit) ambari-web/app/styles/application.less
* (edit) ambari-web/app/styles/theme/bootstrap-ambari.css
* (edit) ambari-web/app/styles/top-nav.less
* (edit) ambari-web/vendor/scripts/theme/bootstrap-ambari.js


> Side Nav: multiple fixes after integrated to trunk
> --
>
> Key: AMBARI-20160
> URL: https://issues.apache.org/jira/browse/AMBARI-20160
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 3.0.0
>
> Attachments: AMBARI-20160.patch
>
>
> Need to fix the following issues after integrated the Side Navi Bar and Top 
> Bar to trunk:
> 1. Service actions dropdown might positioned incorrectly sometimes.
> 2. If the scrollbar shows up, sometimes it is on top of the actions dropdown 
> menu.
> 3. Alerts Panel: change alert definition name into 14px in #333
> 4. Remove menu on Admin page, it is duplicated 
> 5. Alerts Panel: red alerts cnt circle should be able to display large 
> numbers. eg 99, 999,  .etc
> 6. FireFox issue: alert description not limited. should be limited to 3 lines



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20034) USER to GROUP mapping (hdfs_user -> hadoop_group) should be stack driven

2017-02-23 Thread Madhuvanthi Radhakrishnan (JIRA)

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

Madhuvanthi Radhakrishnan updated AMBARI-20034:
---
Attachment: AMBARI-20034_2.5.patch

> USER to GROUP mapping (hdfs_user -> hadoop_group) should be stack driven
> 
>
> Key: AMBARI-20034
> URL: https://issues.apache.org/jira/browse/AMBARI-20034
> Project: Ambari
>  Issue Type: Bug
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
> Fix For: 2.5.0
>
> Attachments: AMBARI-20034_2.5.patch, AMBARI-20034.patch, 
> AMBARI-20034_trunk.patch
>
>
> There is a hard coded logic to creating the user-group mapping for services. 
> This presents an issue for custom services. Fix is to make it stack driven by 
> connecting user to its groups within the configuration/stack definition itself



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20155) EU: Manual Step without any context after "All Service Checks" fail

2017-02-23 Thread Nate Cole (JIRA)

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

Nate Cole updated AMBARI-20155:
---
Status: Open  (was: Patch Available)

> EU: Manual Step without any context after "All Service Checks" fail
> ---
>
> Key: AMBARI-20155
> URL: https://issues.apache.org/jira/browse/AMBARI-20155
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20155_1.patch
>
>
> During EU from 2.5.3.0-2.6.0.0, a manual step popped up that didn't make 
> sense.
> It says "Manual steps required [] I have performed the manual steps above." 
> without telling the user what the manual steps are.
> The BE is not providing a message for display.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20155) EU: Manual Step without any context after "All Service Checks" fail

2017-02-23 Thread Nate Cole (JIRA)

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

Nate Cole updated AMBARI-20155:
---
Attachment: AMBARI-20155_1.patch

> EU: Manual Step without any context after "All Service Checks" fail
> ---
>
> Key: AMBARI-20155
> URL: https://issues.apache.org/jira/browse/AMBARI-20155
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20155_1.patch
>
>
> During EU from 2.5.3.0-2.6.0.0, a manual step popped up that didn't make 
> sense.
> It says "Manual steps required [] I have performed the manual steps above." 
> without telling the user what the manual steps are.
> The BE is not providing a message for display.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20155) EU: Manual Step without any context after "All Service Checks" fail

2017-02-23 Thread Nate Cole (JIRA)

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

Nate Cole updated AMBARI-20155:
---
Status: Patch Available  (was: Open)

Resubmit patch with test fixes

> EU: Manual Step without any context after "All Service Checks" fail
> ---
>
> Key: AMBARI-20155
> URL: https://issues.apache.org/jira/browse/AMBARI-20155
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20155_1.patch
>
>
> During EU from 2.5.3.0-2.6.0.0, a manual step popped up that didn't make 
> sense.
> It says "Manual steps required [] I have performed the manual steps above." 
> without telling the user what the manual steps are.
> The BE is not providing a message for display.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20155) EU: Manual Step without any context after "All Service Checks" fail

2017-02-23 Thread Nate Cole (JIRA)

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

Nate Cole updated AMBARI-20155:
---
Attachment: (was: AMBARI-20155.patch)

> EU: Manual Step without any context after "All Service Checks" fail
> ---
>
> Key: AMBARI-20155
> URL: https://issues.apache.org/jira/browse/AMBARI-20155
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20155_1.patch
>
>
> During EU from 2.5.3.0-2.6.0.0, a manual step popped up that didn't make 
> sense.
> It says "Manual steps required [] I have performed the manual steps above." 
> without telling the user what the manual steps are.
> The BE is not providing a message for display.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20034) USER to GROUP mapping (hdfs_user -> hadoop_group) should be stack driven

2017-02-23 Thread Madhuvanthi Radhakrishnan (JIRA)

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

Madhuvanthi Radhakrishnan updated AMBARI-20034:
---
Attachment: AMBARI-20034_trunk.patch

> USER to GROUP mapping (hdfs_user -> hadoop_group) should be stack driven
> 
>
> Key: AMBARI-20034
> URL: https://issues.apache.org/jira/browse/AMBARI-20034
> Project: Ambari
>  Issue Type: Bug
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
> Fix For: 2.5.0
>
> Attachments: AMBARI-20034.patch, AMBARI-20034_trunk.patch
>
>
> There is a hard coded logic to creating the user-group mapping for services. 
> This presents an issue for custom services. Fix is to make it stack driven by 
> connecting user to its groups within the configuration/stack definition itself



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-20155) EU: Manual Step without any context after "All Service Checks" fail

2017-02-23 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on AMBARI-20155:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12854290/AMBARI-20155.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.controller.internal.UpgradeResourceProviderTest
  
org.apache.ambari.server.api.services.KerberosServiceMetaInfoTest
  org.apache.ambari.server.state.stack.ConfigUpgradeValidityTest
  
org.apache.ambari.server.state.kerberos.KerberosDescriptorUpdateHelperTest
  org.apache.ambari.server.stack.StackManagerTest
  org.apache.ambari.server.api.services.AmbariMetaInfoTest

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

This message is automatically generated.

> EU: Manual Step without any context after "All Service Checks" fail
> ---
>
> Key: AMBARI-20155
> URL: https://issues.apache.org/jira/browse/AMBARI-20155
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20155.patch
>
>
> During EU from 2.5.3.0-2.6.0.0, a manual step popped up that didn't make 
> sense.
> It says "Manual steps required [] I have performed the manual steps above." 
> without telling the user what the manual steps are.
> The BE is not providing a message for display.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Reopened] (AMBARI-20158) Host filter is missing for admin user after upgrading to ambari 2.4.2 or above

2017-02-23 Thread Jaimin Jetly (JIRA)

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

Jaimin Jetly reopened AMBARI-20158:
---

As per the comment on the review board linked from this jira, the ticket is 
being re-opened

> Host filter is missing for admin user after upgrading to ambari 2.4.2 or above
> --
>
> Key: AMBARI-20158
> URL: https://issues.apache.org/jira/browse/AMBARI-20158
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20158.patch
>
>
> *STR:*
> # Deploy ambari cluster and customize ambari behavior for "admin user" via 
> experimental page (For example: opsDuringUpgrade. Note this flag is most 
> frequently enabled by the customer for previous versions of ambari)
> # Upgrade ambari to 2.4.2 or above
> *Expected behavior:* Admin user should be able to use new combo box for 
> filtering hosts on Hosts page
> *Actual behavior:* new combobox is missing for "admin user" and there is no 
> way to filter hosts via ambari-web. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20160) Side Nav: multiple fixes after integrated to trunk

2017-02-23 Thread Xi Wang (JIRA)

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

Xi Wang updated AMBARI-20160:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Side Nav: multiple fixes after integrated to trunk
> --
>
> Key: AMBARI-20160
> URL: https://issues.apache.org/jira/browse/AMBARI-20160
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 3.0.0
>
> Attachments: AMBARI-20160.patch
>
>
> Need to fix the following issues after integrated the Side Navi Bar and Top 
> Bar to trunk:
> 1. Service actions dropdown might positioned incorrectly sometimes.
> 2. If the scrollbar shows up, sometimes it is on top of the actions dropdown 
> menu.
> 3. Alerts Panel: change alert definition name into 14px in #333
> 4. Remove menu on Admin page, it is duplicated 
> 5. Alerts Panel: red alerts cnt circle should be able to display large 
> numbers. eg 99, 999,  .etc
> 6. FireFox issue: alert description not limited. should be limited to 3 lines



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-20160) Side Nav: multiple fixes after integrated to trunk

2017-02-23 Thread Xi Wang (JIRA)

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

Xi Wang commented on AMBARI-20160:
--

Committed to trunk

> Side Nav: multiple fixes after integrated to trunk
> --
>
> Key: AMBARI-20160
> URL: https://issues.apache.org/jira/browse/AMBARI-20160
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 3.0.0
>
> Attachments: AMBARI-20160.patch
>
>
> Need to fix the following issues after integrated the Side Navi Bar and Top 
> Bar to trunk:
> 1. Service actions dropdown might positioned incorrectly sometimes.
> 2. If the scrollbar shows up, sometimes it is on top of the actions dropdown 
> menu.
> 3. Alerts Panel: change alert definition name into 14px in #333
> 4. Remove menu on Admin page, it is duplicated 
> 5. Alerts Panel: red alerts cnt circle should be able to display large 
> numbers. eg 99, 999,  .etc
> 6. FireFox issue: alert description not limited. should be limited to 3 lines



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-20158) Host filter is missing for admin user after upgrading to ambari 2.4.2 or above

2017-02-23 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-20158:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1077 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1077/])
AMBARI-20158 - Host filter is missing for admin user after upgrading to (rzang: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7ce52f7035450d3cd72e35eaf5a158ae7f825c55])
* (edit) ambari-web/app/controllers/experimental.js
* (edit) ambari-web/app/templates/main/host/combo_search_box.hbs
* (edit) ambari-web/app/config.js


> Host filter is missing for admin user after upgrading to ambari 2.4.2 or above
> --
>
> Key: AMBARI-20158
> URL: https://issues.apache.org/jira/browse/AMBARI-20158
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20158.patch
>
>
> *STR:*
> # Deploy ambari cluster and customize ambari behavior for "admin user" via 
> experimental page (For example: opsDuringUpgrade. Note this flag is most 
> frequently enabled by the customer for previous versions of ambari)
> # Upgrade ambari to 2.4.2 or above
> *Expected behavior:* Admin user should be able to use new combo box for 
> filtering hosts on Hosts page
> *Actual behavior:* new combobox is missing for "admin user" and there is no 
> way to filter hosts via ambari-web. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-20159) Cluster deploy failed as install service failed with "Execution of 'zypper clean --all' returned 7. System management is locked by the application with pid ..."

2017-02-23 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-20159:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1077 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1077/])
AMBARI-20159. Cluster deploy failed as install service failed with 
(vbrodetskyi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1c44053d290346eafd24eae1ae28507252d2d327])
* (edit) 
ambari-common/src/main/python/resource_management/libraries/functions/__init__.py
* (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py
* (edit) ambari-agent/src/main/python/ambari_agent/PythonExecutor.py
* (add) 
ambari-common/src/main/python/resource_management/libraries/functions/log_process_information.py


> Cluster deploy failed as install service failed with "Execution of 'zypper 
> clean --all' returned 7. System management is locked by the application with 
> pid ..."
> 
>
> Key: AMBARI-20159
> URL: https://issues.apache.org/jira/browse/AMBARI-20159
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-20159.patch
>
>
> Cluster deploy failed as install Zookeeper server failed with 
> {code:java}
> "Traceback (most recent call last):   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL/scripts/hook.py",
>  line 37, in  BeforeInstallHook().execute()   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 313, in execute method(env)   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL/scripts/hook.py",
>  line 33, in hook install_repos()   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL/scripts/repo_initialization.py",
>  line 66, in install_repos _alter_repo("create", params.repo_info, 
> template)   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL/scripts/repo_initialization.py",
>  line 57, in _alter_repo components = ubuntu_components, # ubuntu 
> specific   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/libraries/providers/repository.py",
>  line 60, in action_create checked_call(self.update_cmd, sudo=True)   
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 72, in inner result = function(command, **kwargs)   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 102, in checked_call tries=tries, try_sleep=try_sleep, 
> timeout_kill_strategy=timeout_kill_strategy)   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 150, in _call_wrapper result = _call(command, **kwargs_copy)   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 303, in _call raise ExecutionFailed(err_msg, code, out, err) 
> resource_management.core.exceptions.ExecutionFailed: Execution of 'zypper 
> clean --all' returned 7. System management is locked by the application with 
> pid 14241 (/usr/bin/zypper)"
> {code}
> From agent logs:
> {code:java}
> INFO 2017-02-20 18:37:55,815 PythonExecutor.py:129 - Command 
> ['/usr/bin/python',
>  
> u'/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL/scripts/hook.py',
>  u'INSTALL',
>  '/var/lib/ambari-agent/data/command-652.json',
>  u'/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL',
>  '/var/lib/ambari-agent/data/structured-out-652.json',
>  'INFO',
>  '/var/lib/ambari-agent/tmp',
>  'PROTOCOL_TLSv1'] failed with exitcode=1
> INFO 2017-02-20 18:37:55,849 PythonExecutor.py:139 - Command 'export 
> COLUMNS= ; ps faux' returned 0. USER   PID %CPU %MEMVSZ   RSS TTY 
>  STAT START   TIME COMMAND
> root 2  0.0  0.0  0 0 ?S16:38   0:00 [kthreadd]
> root 3  0.0  0.0  0 0 ?S16:38   0:00  \_ 
> [ksoftirqd/0]
> root 5  0.0  0.0  0 0 ?S<   16:38   0:00  \_ 
> [kworker/0:0H]
> root 7  0.0  0.0  0 0 ?S16:38   0:06  \_ 
> 

[jira] [Commented] (AMBARI-20109) HDP stack - enable shuffle connection keep-alive

2017-02-23 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-20109:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1077 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1077/])
AMBARI-20109. HDP stack - enable shuffle connection keep-alive. (sshridhar: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9dc9d8bce8d0e2f66f8a433ae542596b90cc13d6])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/TEZ/configuration/tez-site.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/tez-interactive-site.xml
* (add) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/YARN/configuration-mapred/mapred-site.xml


> HDP stack - enable shuffle connection keep-alive
> 
>
> Key: AMBARI-20109
> URL: https://issues.apache.org/jira/browse/AMBARI-20109
> Project: Ambari
>  Issue Type: Task
>  Components: stacks
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Fix For: 2.5.0
>
> Attachments: AMBARI-20109.01.patch, AMBARI-20109.02.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-20154) Package clean up

2017-02-23 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-20154:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6835 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6835/])
AMBARI-20154. Package clean up.(vbrodetskyi) (vbrodetskyi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7bbc678c566f2e72d6c43b7602dd7abd48aedecb])
* (edit) 
ambari-metrics/ambari-metrics-kafka-sink/src/main/assemblies/jar-with-common.xml
* (edit) 
ambari-metrics/ambari-metrics-timelineservice/src/main/assemblies/simulator.xml
* (edit) ambari-metrics/ambari-metrics-assembly/src/main/assembly/collector.xml
* (edit) ambari-metrics/ambari-metrics-assembly/src/main/assembly/sink.xml
* (edit) 
ambari-metrics/ambari-metrics-hadoop-sink/src/main/assemblies/jar-with-common.xml
* (edit) 
ambari-metrics/ambari-metrics-flume-sink/src/main/assemblies/jar-with-common.xml
* (edit) ambari-server/src/main/assemblies/server.xml


> Package clean up
> 
>
> Key: AMBARI-20154
> URL: https://issues.apache.org/jira/browse/AMBARI-20154
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics, ambari-server
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20154.patch
>
>
> Package clean up.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-20109) HDP stack - enable shuffle connection keep-alive

2017-02-23 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-20109:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6835 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6835/])
AMBARI-20109. HDP stack - enable shuffle connection keep-alive. (sshridhar: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=cce9489c2ed551940c70e9003fa421d4c9880e38])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/tez-interactive-site.xml
* (add) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/YARN/configuration-mapred/mapred-site.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/TEZ/configuration/tez-site.xml


> HDP stack - enable shuffle connection keep-alive
> 
>
> Key: AMBARI-20109
> URL: https://issues.apache.org/jira/browse/AMBARI-20109
> Project: Ambari
>  Issue Type: Task
>  Components: stacks
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Fix For: 2.5.0
>
> Attachments: AMBARI-20109.01.patch, AMBARI-20109.02.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-20159) Cluster deploy failed as install service failed with "Execution of 'zypper clean --all' returned 7. System management is locked by the application with pid ..."

2017-02-23 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-20159:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6835 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6835/])
AMBARI-20159. Cluster deploy failed as install service failed with 
(vbrodetskyi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ef355ae0d262dc16c8897d89110b3312653e0e68])
* (add) 
ambari-common/src/main/python/resource_management/libraries/functions/log_process_information.py
* (edit) ambari-agent/src/main/python/ambari_agent/PythonExecutor.py
* (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py
* (edit) 
ambari-common/src/main/python/resource_management/libraries/functions/__init__.py


> Cluster deploy failed as install service failed with "Execution of 'zypper 
> clean --all' returned 7. System management is locked by the application with 
> pid ..."
> 
>
> Key: AMBARI-20159
> URL: https://issues.apache.org/jira/browse/AMBARI-20159
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-20159.patch
>
>
> Cluster deploy failed as install Zookeeper server failed with 
> {code:java}
> "Traceback (most recent call last):   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL/scripts/hook.py",
>  line 37, in  BeforeInstallHook().execute()   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 313, in execute method(env)   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL/scripts/hook.py",
>  line 33, in hook install_repos()   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL/scripts/repo_initialization.py",
>  line 66, in install_repos _alter_repo("create", params.repo_info, 
> template)   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL/scripts/repo_initialization.py",
>  line 57, in _alter_repo components = ubuntu_components, # ubuntu 
> specific   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/libraries/providers/repository.py",
>  line 60, in action_create checked_call(self.update_cmd, sudo=True)   
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 72, in inner result = function(command, **kwargs)   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 102, in checked_call tries=tries, try_sleep=try_sleep, 
> timeout_kill_strategy=timeout_kill_strategy)   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 150, in _call_wrapper result = _call(command, **kwargs_copy)   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 303, in _call raise ExecutionFailed(err_msg, code, out, err) 
> resource_management.core.exceptions.ExecutionFailed: Execution of 'zypper 
> clean --all' returned 7. System management is locked by the application with 
> pid 14241 (/usr/bin/zypper)"
> {code}
> From agent logs:
> {code:java}
> INFO 2017-02-20 18:37:55,815 PythonExecutor.py:129 - Command 
> ['/usr/bin/python',
>  
> u'/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL/scripts/hook.py',
>  u'INSTALL',
>  '/var/lib/ambari-agent/data/command-652.json',
>  u'/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL',
>  '/var/lib/ambari-agent/data/structured-out-652.json',
>  'INFO',
>  '/var/lib/ambari-agent/tmp',
>  'PROTOCOL_TLSv1'] failed with exitcode=1
> INFO 2017-02-20 18:37:55,849 PythonExecutor.py:139 - Command 'export 
> COLUMNS= ; ps faux' returned 0. USER   PID %CPU %MEMVSZ   RSS TTY 
>  STAT START   TIME COMMAND
> root 2  0.0  0.0  0 0 ?S16:38   0:00 [kthreadd]
> root 3  0.0  0.0  0 0 ?S16:38   0:00  \_ 
> [ksoftirqd/0]
> root 5  0.0  0.0  0 0 ?S<   16:38   0:00  \_ 
> [kworker/0:0H]
> root 7  0.0  0.0  0 0 ?S16:38   0:06  \_ 
> 

[jira] [Commented] (AMBARI-20158) Host filter is missing for admin user after upgrading to ambari 2.4.2 or above

2017-02-23 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-20158:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6835 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6835/])
AMBARI-20158 - Host filter is missing for admin user after upgrading to (rzang: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3c939bd233439028e31e99daf0ed4141f81350af])
* (edit) ambari-web/app/config.js
* (edit) ambari-web/app/controllers/experimental.js
* (edit) ambari-web/app/templates/main/host/combo_search_box.hbs


> Host filter is missing for admin user after upgrading to ambari 2.4.2 or above
> --
>
> Key: AMBARI-20158
> URL: https://issues.apache.org/jira/browse/AMBARI-20158
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20158.patch
>
>
> *STR:*
> # Deploy ambari cluster and customize ambari behavior for "admin user" via 
> experimental page (For example: opsDuringUpgrade. Note this flag is most 
> frequently enabled by the customer for previous versions of ambari)
> # Upgrade ambari to 2.4.2 or above
> *Expected behavior:* Admin user should be able to use new combo box for 
> filtering hosts on Hosts page
> *Actual behavior:* new combobox is missing for "admin user" and there is no 
> way to filter hosts via ambari-web. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-20038) LogFeeder Simulator Enhancements for 3000-node cluster testing

2017-02-23 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-20038:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6835 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6835/])
AMBARI-20038 LogFeeder Simulator Enhancements for 3000-node cluster (mgergely: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=fc5cbc6e3c806a3e7193dff17093db8d1367fb74])
* (edit) 
ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/common/ConfigBlock.java
* (edit) 
ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/filter/Filter.java
* (edit) 
ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/LogFeeder.java
* (edit) 
ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/input/InputSimulate.java


> LogFeeder Simulator Enhancements for 3000-node cluster testing
> ---
>
> Key: AMBARI-20038
> URL: https://issues.apache.org/jira/browse/AMBARI-20038
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-logsearch
>Affects Versions: 2.5.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.5.0
>
> Attachments: AMBARI-20038.patch
>
>
> The number of simulators set via logfeeder.simulate.input_number should work 
> as imitating separate hosts, having separate queues pushing data from to the 
> solr.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-20109) HDP stack - enable shuffle connection keep-alive

2017-02-23 Thread Swapan Shridhar (JIRA)

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

Swapan Shridhar commented on AMBARI-20109:
--

Python UT passes.

commit


trunk:

{code}
commit cce9489c2ed551940c70e9003fa421d4c9880e38
Author: Swapan Shridhar 
Date:   Thu Feb 23 16:46:20 2017 -0800

AMBARI-20109. HDP stack - enable shuffle connection keep-alive. (Siddharth 
Seth via Swapan Shridhar).
{code}


branch-2.5:

{code}
commit 9dc9d8bce8d0e2f66f8a433ae542596b90cc13d6
Author: Swapan Shridhar 
Date:   Thu Feb 23 16:46:20 2017 -0800

AMBARI-20109. HDP stack - enable shuffle connection keep-alive. (Siddharth 
Seth via Swapan Shridhar).
{code}

> HDP stack - enable shuffle connection keep-alive
> 
>
> Key: AMBARI-20109
> URL: https://issues.apache.org/jira/browse/AMBARI-20109
> Project: Ambari
>  Issue Type: Task
>  Components: stacks
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Fix For: 2.5.0
>
> Attachments: AMBARI-20109.01.patch, AMBARI-20109.02.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Resolved] (AMBARI-20109) HDP stack - enable shuffle connection keep-alive

2017-02-23 Thread Swapan Shridhar (JIRA)

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

Swapan Shridhar resolved AMBARI-20109.
--
Resolution: Fixed

> HDP stack - enable shuffle connection keep-alive
> 
>
> Key: AMBARI-20109
> URL: https://issues.apache.org/jira/browse/AMBARI-20109
> Project: Ambari
>  Issue Type: Task
>  Components: stacks
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Fix For: 2.5.0
>
> Attachments: AMBARI-20109.01.patch, AMBARI-20109.02.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20160) Side Nav: multiple fixes after integrated to trunk

2017-02-23 Thread Xi Wang (JIRA)

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

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

> Side Nav: multiple fixes after integrated to trunk
> --
>
> Key: AMBARI-20160
> URL: https://issues.apache.org/jira/browse/AMBARI-20160
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 3.0.0
>
> Attachments: AMBARI-20160.patch
>
>
> Need to fix the following issues after integrated the Side Navi Bar and Top 
> Bar to trunk:
> 1. Service actions dropdown might positioned incorrectly sometimes.
> 2. If the scrollbar shows up, sometimes it is on top of the actions dropdown 
> menu.
> 3. Alerts Panel: change alert definition name into 14px in #333
> 4. Remove menu on Admin page, it is duplicated 
> 5. Alerts Panel: red alerts cnt circle should be able to display large 
> numbers. eg 99, 999,  .etc
> 6. FireFox issue: alert description not limited. should be limited to 3 lines



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-20154) Package clean up

2017-02-23 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on AMBARI-20154:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12854289/AMBARI-20154.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-metrics/ambari-metrics-flume-sink 
ambari-metrics/ambari-metrics-hadoop-sink 
ambari-metrics/ambari-metrics-kafka-sink 
ambari-metrics/ambari-metrics-timelineservice ambari-server.

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

This message is automatically generated.

> Package clean up
> 
>
> Key: AMBARI-20154
> URL: https://issues.apache.org/jira/browse/AMBARI-20154
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics, ambari-server
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20154.patch
>
>
> Package clean up.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20160) Side Nav: multiple fixes after integrated to trunk

2017-02-23 Thread Xi Wang (JIRA)

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

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

> Side Nav: multiple fixes after integrated to trunk
> --
>
> Key: AMBARI-20160
> URL: https://issues.apache.org/jira/browse/AMBARI-20160
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 3.0.0
>
> Attachments: AMBARI-20160.patch
>
>
> Need to fix the following issues after integrated the Side Navi Bar and Top 
> Bar to trunk:
> 1. Service actions dropdown might positioned incorrectly sometimes.
> 2. If the scrollbar shows up, sometimes it is on top of the actions dropdown 
> menu.
> 3. Alerts Panel: change alert definition name into 14px in #333
> 4. Remove menu on Admin page, it is duplicated 
> 5. Alerts Panel: red alerts cnt circle should be able to display large 
> numbers. eg 99, 999,  .etc
> 6. FireFox issue: alert description not limited. should be limited to 3 lines



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-20160) Side Nav: multiple fixes after integrated to trunk

2017-02-23 Thread Xi Wang (JIRA)

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

Xi Wang commented on AMBARI-20160:
--

20375 passing (37s)
  153 pending

> Side Nav: multiple fixes after integrated to trunk
> --
>
> Key: AMBARI-20160
> URL: https://issues.apache.org/jira/browse/AMBARI-20160
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 3.0.0
>
>
> Need to fix the following issues after integrated the Side Navi Bar and Top 
> Bar to trunk:
> 1. Service actions dropdown might positioned incorrectly sometimes.
> 2. If the scrollbar shows up, sometimes it is on top of the actions dropdown 
> menu.
> 3. Alerts Panel: change alert definition name into 14px in #333
> 4. Remove menu on Admin page, it is duplicated 
> 5. Alerts Panel: red alerts cnt circle should be able to display large 
> numbers. eg 99, 999,  .etc
> 6. FireFox issue: alert description not limited. should be limited to 3 lines



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-20154) Package clean up

2017-02-23 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-20154:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1076 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1076/])
AMBARI-20154. Package clean up.(vbrodetskyi) (vbrodetskyi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3779ac40c510d428779d5b8387ff98387b19bee4])
* (edit) ambari-metrics/ambari-metrics-assembly/src/main/assembly/sink.xml
* (edit) 
ambari-metrics/ambari-metrics-flume-sink/src/main/assemblies/jar-with-common.xml
* (edit) ambari-metrics/ambari-metrics-assembly/src/main/assembly/collector.xml
* (edit) 
ambari-metrics/ambari-metrics-hadoop-sink/src/main/assemblies/jar-with-common.xml
* (edit) 
ambari-metrics/ambari-metrics-timelineservice/src/main/assemblies/simulator.xml
* (edit) ambari-server/src/main/assemblies/server.xml
* (edit) 
ambari-metrics/ambari-metrics-kafka-sink/src/main/assemblies/jar-with-common.xml


> Package clean up
> 
>
> Key: AMBARI-20154
> URL: https://issues.apache.org/jira/browse/AMBARI-20154
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics, ambari-server
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20154.patch
>
>
> Package clean up.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-20159) Cluster deploy failed as install service failed with "Execution of 'zypper clean --all' returned 7. System management is locked by the application with pid ..."

2017-02-23 Thread Vitaly Brodetskyi (JIRA)

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

Vitaly Brodetskyi commented on AMBARI-20159:


Committed to trunk and branch-2.5

> Cluster deploy failed as install service failed with "Execution of 'zypper 
> clean --all' returned 7. System management is locked by the application with 
> pid ..."
> 
>
> Key: AMBARI-20159
> URL: https://issues.apache.org/jira/browse/AMBARI-20159
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-20159.patch
>
>
> Cluster deploy failed as install Zookeeper server failed with 
> {code:java}
> "Traceback (most recent call last):   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL/scripts/hook.py",
>  line 37, in  BeforeInstallHook().execute()   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 313, in execute method(env)   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL/scripts/hook.py",
>  line 33, in hook install_repos()   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL/scripts/repo_initialization.py",
>  line 66, in install_repos _alter_repo("create", params.repo_info, 
> template)   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL/scripts/repo_initialization.py",
>  line 57, in _alter_repo components = ubuntu_components, # ubuntu 
> specific   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/libraries/providers/repository.py",
>  line 60, in action_create checked_call(self.update_cmd, sudo=True)   
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 72, in inner result = function(command, **kwargs)   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 102, in checked_call tries=tries, try_sleep=try_sleep, 
> timeout_kill_strategy=timeout_kill_strategy)   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 150, in _call_wrapper result = _call(command, **kwargs_copy)   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 303, in _call raise ExecutionFailed(err_msg, code, out, err) 
> resource_management.core.exceptions.ExecutionFailed: Execution of 'zypper 
> clean --all' returned 7. System management is locked by the application with 
> pid 14241 (/usr/bin/zypper)"
> {code}
> From agent logs:
> {code:java}
> INFO 2017-02-20 18:37:55,815 PythonExecutor.py:129 - Command 
> ['/usr/bin/python',
>  
> u'/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL/scripts/hook.py',
>  u'INSTALL',
>  '/var/lib/ambari-agent/data/command-652.json',
>  u'/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL',
>  '/var/lib/ambari-agent/data/structured-out-652.json',
>  'INFO',
>  '/var/lib/ambari-agent/tmp',
>  'PROTOCOL_TLSv1'] failed with exitcode=1
> INFO 2017-02-20 18:37:55,849 PythonExecutor.py:139 - Command 'export 
> COLUMNS= ; ps faux' returned 0. USER   PID %CPU %MEMVSZ   RSS TTY 
>  STAT START   TIME COMMAND
> root 2  0.0  0.0  0 0 ?S16:38   0:00 [kthreadd]
> root 3  0.0  0.0  0 0 ?S16:38   0:00  \_ 
> [ksoftirqd/0]
> root 5  0.0  0.0  0 0 ?S<   16:38   0:00  \_ 
> [kworker/0:0H]
> root 7  0.0  0.0  0 0 ?S16:38   0:06  \_ 
> [rcu_sched]
> root 8  0.0  0.0  0 0 ?S16:38   0:00  \_ [rcu_bh]
> root 9  0.0  0.0  0 0 ?S16:38   0:00  \_ 
> [migration/0]
> root10  0.0  0.0  0 0 ?S16:38   0:00  \_ 
> [watchdog/0]
> root11  0.0  0.0  0 0 ?S16:38   0:00  \_ 
> [watchdog/1]
> root12  0.0  0.0  0 0 ?S16:38   0:00  \_ 
> [migration/1]
> root13  0.0  0.0  0 0 ?S16:38   0:00  \_ 
> [ksoftirqd/1]
> root15  0.0  0.0  0 0 ?S<   16:38   0:00  \_ 
> 

[jira] [Created] (AMBARI-20160) Side Nav: multiple fixes after integrated to trunk

2017-02-23 Thread Xi Wang (JIRA)
Xi Wang created AMBARI-20160:


 Summary: Side Nav: multiple fixes after integrated to trunk
 Key: AMBARI-20160
 URL: https://issues.apache.org/jira/browse/AMBARI-20160
 Project: Ambari
  Issue Type: Task
  Components: ambari-web
Affects Versions: 3.0.0
Reporter: Xi Wang
Assignee: Xi Wang


Need to fix the following issues after integrated the Side Navi Bar and Top Bar 
to trunk:
1. Service actions dropdown might positioned incorrectly sometimes.
2. If the scrollbar shows up, sometimes it is on top of the actions dropdown 
menu.
3. Alerts Panel: change alert definition name into 14px in #333
4. Remove menu on Admin page, it is duplicated 
5. Alerts Panel: red alerts cnt circle should be able to display large numbers. 
eg 99, 999,  .etc
6. FireFox issue: alert description not limited. should be limited to 3 lines




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20160) Side Nav: multiple fixes after integrated to trunk

2017-02-23 Thread Xi Wang (JIRA)

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

Xi Wang updated AMBARI-20160:
-
Fix Version/s: 3.0.0

> Side Nav: multiple fixes after integrated to trunk
> --
>
> Key: AMBARI-20160
> URL: https://issues.apache.org/jira/browse/AMBARI-20160
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 3.0.0
>
>
> Need to fix the following issues after integrated the Side Navi Bar and Top 
> Bar to trunk:
> 1. Service actions dropdown might positioned incorrectly sometimes.
> 2. If the scrollbar shows up, sometimes it is on top of the actions dropdown 
> menu.
> 3. Alerts Panel: change alert definition name into 14px in #333
> 4. Remove menu on Admin page, it is duplicated 
> 5. Alerts Panel: red alerts cnt circle should be able to display large 
> numbers. eg 99, 999,  .etc
> 6. FireFox issue: alert description not limited. should be limited to 3 lines



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20158) Host filter is missing for admin user after upgrading to ambari 2.4.2 or above

2017-02-23 Thread Richard Zang (JIRA)

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

Richard Zang updated AMBARI-20158:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to trunk and 2.5 7ce52f7035450d3cd72e35eaf5a158ae7f825c55

> Host filter is missing for admin user after upgrading to ambari 2.4.2 or above
> --
>
> Key: AMBARI-20158
> URL: https://issues.apache.org/jira/browse/AMBARI-20158
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20158.patch
>
>
> *STR:*
> # Deploy ambari cluster and customize ambari behavior for "admin user" via 
> experimental page (For example: opsDuringUpgrade. Note this flag is most 
> frequently enabled by the customer for previous versions of ambari)
> # Upgrade ambari to 2.4.2 or above
> *Expected behavior:* Admin user should be able to use new combo box for 
> filtering hosts on Hosts page
> *Actual behavior:* new combobox is missing for "admin user" and there is no 
> way to filter hosts via ambari-web. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-20154) Package clean up

2017-02-23 Thread Vitaly Brodetskyi (JIRA)

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

Vitaly Brodetskyi commented on AMBARI-20154:


Committed to trunk and branch-2.5

> Package clean up
> 
>
> Key: AMBARI-20154
> URL: https://issues.apache.org/jira/browse/AMBARI-20154
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics, ambari-server
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20154.patch
>
>
> Package clean up.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-20159) Cluster deploy failed as install service failed with "Execution of 'zypper clean --all' returned 7. System management is locked by the application with pid ..."

2017-02-23 Thread Sumit Mohanty (JIRA)

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

Sumit Mohanty commented on AMBARI-20159:


LGTM, +1

> Cluster deploy failed as install service failed with "Execution of 'zypper 
> clean --all' returned 7. System management is locked by the application with 
> pid ..."
> 
>
> Key: AMBARI-20159
> URL: https://issues.apache.org/jira/browse/AMBARI-20159
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-20159.patch
>
>
> Cluster deploy failed as install Zookeeper server failed with 
> {code:java}
> "Traceback (most recent call last):   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL/scripts/hook.py",
>  line 37, in  BeforeInstallHook().execute()   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 313, in execute method(env)   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL/scripts/hook.py",
>  line 33, in hook install_repos()   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL/scripts/repo_initialization.py",
>  line 66, in install_repos _alter_repo("create", params.repo_info, 
> template)   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL/scripts/repo_initialization.py",
>  line 57, in _alter_repo components = ubuntu_components, # ubuntu 
> specific   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/libraries/providers/repository.py",
>  line 60, in action_create checked_call(self.update_cmd, sudo=True)   
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 72, in inner result = function(command, **kwargs)   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 102, in checked_call tries=tries, try_sleep=try_sleep, 
> timeout_kill_strategy=timeout_kill_strategy)   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 150, in _call_wrapper result = _call(command, **kwargs_copy)   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 303, in _call raise ExecutionFailed(err_msg, code, out, err) 
> resource_management.core.exceptions.ExecutionFailed: Execution of 'zypper 
> clean --all' returned 7. System management is locked by the application with 
> pid 14241 (/usr/bin/zypper)"
> {code}
> From agent logs:
> {code:java}
> INFO 2017-02-20 18:37:55,815 PythonExecutor.py:129 - Command 
> ['/usr/bin/python',
>  
> u'/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL/scripts/hook.py',
>  u'INSTALL',
>  '/var/lib/ambari-agent/data/command-652.json',
>  u'/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL',
>  '/var/lib/ambari-agent/data/structured-out-652.json',
>  'INFO',
>  '/var/lib/ambari-agent/tmp',
>  'PROTOCOL_TLSv1'] failed with exitcode=1
> INFO 2017-02-20 18:37:55,849 PythonExecutor.py:139 - Command 'export 
> COLUMNS= ; ps faux' returned 0. USER   PID %CPU %MEMVSZ   RSS TTY 
>  STAT START   TIME COMMAND
> root 2  0.0  0.0  0 0 ?S16:38   0:00 [kthreadd]
> root 3  0.0  0.0  0 0 ?S16:38   0:00  \_ 
> [ksoftirqd/0]
> root 5  0.0  0.0  0 0 ?S<   16:38   0:00  \_ 
> [kworker/0:0H]
> root 7  0.0  0.0  0 0 ?S16:38   0:06  \_ 
> [rcu_sched]
> root 8  0.0  0.0  0 0 ?S16:38   0:00  \_ [rcu_bh]
> root 9  0.0  0.0  0 0 ?S16:38   0:00  \_ 
> [migration/0]
> root10  0.0  0.0  0 0 ?S16:38   0:00  \_ 
> [watchdog/0]
> root11  0.0  0.0  0 0 ?S16:38   0:00  \_ 
> [watchdog/1]
> root12  0.0  0.0  0 0 ?S16:38   0:00  \_ 
> [migration/1]
> root13  0.0  0.0  0 0 ?S16:38   0:00  \_ 
> [ksoftirqd/1]
> root15  0.0  0.0  0 0 ?S<   16:38   0:00  \_ 
> [kworker/1:0H]
> root17  0.0  

[jira] [Commented] (AMBARI-20151) add extra Tez logging configs for Hive

2017-02-23 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on AMBARI-20151:


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

{color:red}-1 patch{color}.  The patch command could not apply the patch.

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

This message is automatically generated.

> add extra Tez logging configs for Hive
> --
>
> Key: AMBARI-20151
> URL: https://issues.apache.org/jira/browse/AMBARI-20151
> Project: Ambari
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Fix For: 2.5.0
>
> Attachments: AMBARI-20151.01.patch, AMBARI-20151.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-17961) Create common-services/KAFKA/0.10.0 service definition

2017-02-23 Thread Madhuvanthi Radhakrishnan (JIRA)

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

Madhuvanthi Radhakrishnan updated AMBARI-17961:
---
Attachment: AMBARI-17961_2.5.patch

> Create common-services/KAFKA/0.10.0 service definition
> --
>
> Key: AMBARI-17961
> URL: https://issues.apache.org/jira/browse/AMBARI-17961
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: trunk
>
> Attachments: AMBARI-17961_2.5.patch, AMBARI-17961.patch
>
>
> As per RR: https://reviews.apache.org/r/50445/ comment. Need to create new 
> common version for KAFKA service



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-20034) USER to GROUP mapping (hdfs_user -> hadoop_group) should be stack driven

2017-02-23 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on AMBARI-20034:


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

{color:red}-1 patch{color}.  The patch command could not apply the patch.

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

This message is automatically generated.

> USER to GROUP mapping (hdfs_user -> hadoop_group) should be stack driven
> 
>
> Key: AMBARI-20034
> URL: https://issues.apache.org/jira/browse/AMBARI-20034
> Project: Ambari
>  Issue Type: Bug
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
> Fix For: 2.5.0
>
> Attachments: AMBARI-20034.patch
>
>
> There is a hard coded logic to creating the user-group mapping for services. 
> This presents an issue for custom services. Fix is to make it stack driven by 
> connecting user to its groups within the configuration/stack definition itself



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20158) Host filter is missing for admin user after upgrading to ambari 2.4.2 or above

2017-02-23 Thread Richard Zang (JIRA)

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

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

> Host filter is missing for admin user after upgrading to ambari 2.4.2 or above
> --
>
> Key: AMBARI-20158
> URL: https://issues.apache.org/jira/browse/AMBARI-20158
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20158.patch
>
>
> *STR:*
> # Deploy ambari cluster and customize ambari behavior for "admin user" via 
> experimental page (For example: opsDuringUpgrade. Note this flag is most 
> frequently enabled by the customer for previous versions of ambari)
> # Upgrade ambari to 2.4.2 or above
> *Expected behavior:* Admin user should be able to use new combo box for 
> filtering hosts on Hosts page
> *Actual behavior:* new combobox is missing for "admin user" and there is no 
> way to filter hosts via ambari-web. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20158) Host filter is missing for admin user after upgrading to ambari 2.4.2 or above

2017-02-23 Thread Richard Zang (JIRA)

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

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

> Host filter is missing for admin user after upgrading to ambari 2.4.2 or above
> --
>
> Key: AMBARI-20158
> URL: https://issues.apache.org/jira/browse/AMBARI-20158
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20158.patch
>
>
> *STR:*
> # Deploy ambari cluster and customize ambari behavior for "admin user" via 
> experimental page (For example: opsDuringUpgrade. Note this flag is most 
> frequently enabled by the customer for previous versions of ambari)
> # Upgrade ambari to 2.4.2 or above
> *Expected behavior:* Admin user should be able to use new combo box for 
> filtering hosts on Hosts page
> *Actual behavior:* new combobox is missing for "admin user" and there is no 
> way to filter hosts via ambari-web. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20159) Cluster deploy failed as install service failed with "Execution of 'zypper clean --all' returned 7. System management is locked by the application with pid ..."

2017-02-23 Thread Vitaly Brodetskyi (JIRA)

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

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

> Cluster deploy failed as install service failed with "Execution of 'zypper 
> clean --all' returned 7. System management is locked by the application with 
> pid ..."
> 
>
> Key: AMBARI-20159
> URL: https://issues.apache.org/jira/browse/AMBARI-20159
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-20159.patch
>
>
> Cluster deploy failed as install Zookeeper server failed with 
> {code:java}
> "Traceback (most recent call last):   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL/scripts/hook.py",
>  line 37, in  BeforeInstallHook().execute()   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 313, in execute method(env)   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL/scripts/hook.py",
>  line 33, in hook install_repos()   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL/scripts/repo_initialization.py",
>  line 66, in install_repos _alter_repo("create", params.repo_info, 
> template)   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL/scripts/repo_initialization.py",
>  line 57, in _alter_repo components = ubuntu_components, # ubuntu 
> specific   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/libraries/providers/repository.py",
>  line 60, in action_create checked_call(self.update_cmd, sudo=True)   
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 72, in inner result = function(command, **kwargs)   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 102, in checked_call tries=tries, try_sleep=try_sleep, 
> timeout_kill_strategy=timeout_kill_strategy)   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 150, in _call_wrapper result = _call(command, **kwargs_copy)   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 303, in _call raise ExecutionFailed(err_msg, code, out, err) 
> resource_management.core.exceptions.ExecutionFailed: Execution of 'zypper 
> clean --all' returned 7. System management is locked by the application with 
> pid 14241 (/usr/bin/zypper)"
> {code}
> From agent logs:
> {code:java}
> INFO 2017-02-20 18:37:55,815 PythonExecutor.py:129 - Command 
> ['/usr/bin/python',
>  
> u'/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL/scripts/hook.py',
>  u'INSTALL',
>  '/var/lib/ambari-agent/data/command-652.json',
>  u'/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL',
>  '/var/lib/ambari-agent/data/structured-out-652.json',
>  'INFO',
>  '/var/lib/ambari-agent/tmp',
>  'PROTOCOL_TLSv1'] failed with exitcode=1
> INFO 2017-02-20 18:37:55,849 PythonExecutor.py:139 - Command 'export 
> COLUMNS= ; ps faux' returned 0. USER   PID %CPU %MEMVSZ   RSS TTY 
>  STAT START   TIME COMMAND
> root 2  0.0  0.0  0 0 ?S16:38   0:00 [kthreadd]
> root 3  0.0  0.0  0 0 ?S16:38   0:00  \_ 
> [ksoftirqd/0]
> root 5  0.0  0.0  0 0 ?S<   16:38   0:00  \_ 
> [kworker/0:0H]
> root 7  0.0  0.0  0 0 ?S16:38   0:06  \_ 
> [rcu_sched]
> root 8  0.0  0.0  0 0 ?S16:38   0:00  \_ [rcu_bh]
> root 9  0.0  0.0  0 0 ?S16:38   0:00  \_ 
> [migration/0]
> root10  0.0  0.0  0 0 ?S16:38   0:00  \_ 
> [watchdog/0]
> root11  0.0  0.0  0 0 ?S16:38   0:00  \_ 
> [watchdog/1]
> root12  0.0  0.0  0 0 ?S16:38   0:00  \_ 
> [migration/1]
> root13  0.0  0.0  0 0 ?S16:38   0:00  \_ 
> [ksoftirqd/1]
> root15  0.0  0.0  0 0 ?S<   16:38   0:00  \_ 
> [kworker/1:0H]
> root17  0.0  0.0  

[jira] [Created] (AMBARI-20159) Cluster deploy failed as install service failed with "Execution of 'zypper clean --all' returned 7. System management is locked by the application with pid ..."

2017-02-23 Thread Vitaly Brodetskyi (JIRA)
Vitaly Brodetskyi created AMBARI-20159:
--

 Summary: Cluster deploy failed as install service failed with 
"Execution of 'zypper clean --all' returned 7. System management is locked by 
the application with pid ..."
 Key: AMBARI-20159
 URL: https://issues.apache.org/jira/browse/AMBARI-20159
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.5.0
Reporter: Vitaly Brodetskyi
Assignee: Vitaly Brodetskyi
Priority: Blocker
 Fix For: 2.5.0


Cluster deploy failed as install Zookeeper server failed with 
{code:java}
"Traceback (most recent call last):   File 
"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL/scripts/hook.py",
 line 37, in  BeforeInstallHook().execute()   File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
 line 313, in execute method(env)   File 
"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL/scripts/hook.py",
 line 33, in hook install_repos()   File 
"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL/scripts/repo_initialization.py",
 line 66, in install_repos _alter_repo("create", params.repo_info, 
template)   File 
"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL/scripts/repo_initialization.py",
 line 57, in _alter_repo components = ubuntu_components, # ubuntu specific  
 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/libraries/providers/repository.py",
 line 60, in action_create checked_call(self.update_cmd, sudo=True)   File 
"/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 72, 
in inner result = function(command, **kwargs)   File 
"/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 102, 
in checked_call tries=tries, try_sleep=try_sleep, 
timeout_kill_strategy=timeout_kill_strategy)   File 
"/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 150, 
in _call_wrapper result = _call(command, **kwargs_copy)   File 
"/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 303, 
in _call raise ExecutionFailed(err_msg, code, out, err) 
resource_management.core.exceptions.ExecutionFailed: Execution of 'zypper clean 
--all' returned 7. System management is locked by the application with pid 
14241 (/usr/bin/zypper)"
{code}


>From agent logs:

{code:java}
INFO 2017-02-20 18:37:55,815 PythonExecutor.py:129 - Command ['/usr/bin/python',
 
u'/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL/scripts/hook.py',
 u'INSTALL',
 '/var/lib/ambari-agent/data/command-652.json',
 u'/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL',
 '/var/lib/ambari-agent/data/structured-out-652.json',
 'INFO',
 '/var/lib/ambari-agent/tmp',
 'PROTOCOL_TLSv1'] failed with exitcode=1
INFO 2017-02-20 18:37:55,849 PythonExecutor.py:139 - Command 'export 
COLUMNS= ; ps faux' returned 0. USER   PID %CPU %MEMVSZ   RSS TTY   
   STAT START   TIME COMMAND
root 2  0.0  0.0  0 0 ?S16:38   0:00 [kthreadd]
root 3  0.0  0.0  0 0 ?S16:38   0:00  \_ 
[ksoftirqd/0]
root 5  0.0  0.0  0 0 ?S<   16:38   0:00  \_ 
[kworker/0:0H]
root 7  0.0  0.0  0 0 ?S16:38   0:06  \_ [rcu_sched]
root 8  0.0  0.0  0 0 ?S16:38   0:00  \_ [rcu_bh]
root 9  0.0  0.0  0 0 ?S16:38   0:00  \_ 
[migration/0]
root10  0.0  0.0  0 0 ?S16:38   0:00  \_ 
[watchdog/0]
root11  0.0  0.0  0 0 ?S16:38   0:00  \_ 
[watchdog/1]
root12  0.0  0.0  0 0 ?S16:38   0:00  \_ 
[migration/1]
root13  0.0  0.0  0 0 ?S16:38   0:00  \_ 
[ksoftirqd/1]
root15  0.0  0.0  0 0 ?S<   16:38   0:00  \_ 
[kworker/1:0H]
root17  0.0  0.0  0 0 ?S16:38   0:00  \_ [kdevtmpfs]
root18  0.0  0.0  0 0 ?S<   16:38   0:00  \_ [netns]
root19  0.0  0.0  0 0 ?S<   16:38   0:00  \_ [perf]
root20  0.0  0.0  0 0 ?S16:38   0:00  \_ 
[khungtaskd]
root21  0.0  0.0  0 0 ?S<   16:38   0:00  \_ [writeback]
root22  0.0  0.0  0 0 ?S16:38   0:00  \_ 
[kcompactd0]
root23  0.0  0.0  0 0 ?SN   16:38   

[jira] [Created] (AMBARI-20158) Host filter is missing for admin user after upgrading to ambari 2.4.2 or above

2017-02-23 Thread Richard Zang (JIRA)
Richard Zang created AMBARI-20158:
-

 Summary: Host filter is missing for admin user after upgrading to 
ambari 2.4.2 or above
 Key: AMBARI-20158
 URL: https://issues.apache.org/jira/browse/AMBARI-20158
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.5.0
Reporter: Richard Zang
Assignee: Richard Zang
Priority: Critical
 Fix For: 2.5.0


*STR:*
# Deploy ambari cluster and customize ambari behavior for "admin user" via 
experimental page (For example: opsDuringUpgrade. Note this flag is most 
frequently enabled by the customer for previous versions of ambari)
# Upgrade ambari to 2.4.2 or above

*Expected behavior:* Admin user should be able to use new combo box for 
filtering hosts on Hosts page
*Actual behavior:* new combobox is missing for "admin user" and there is no way 
to filter hosts via ambari-web. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20056) FIFO compaction resulting in too many store files on large cluster

2017-02-23 Thread Aravindan Vijayan (JIRA)

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

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

Pushed to branch-2.5 and trunk.

> FIFO compaction resulting in too many store files on large cluster
> --
>
> Key: AMBARI-20056
> URL: https://issues.apache.org/jira/browse/AMBARI-20056
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20056.patch
>
>
> Set Data Tiered compaction for all tables except METRIC_RECORD
> This will allow number of store files to go down over time.  On a 500 node 
> cluster AMS can become in-operational after creating 18K store files and no 
> compaction.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Assigned] (AMBARI-20157) Ambari sends SNMP notifications in incorrect order

2017-02-23 Thread amarnathreddy (JIRA)

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

amarnathreddy reassigned AMBARI-20157:
--

Assignee: amarnathreddy

> Ambari sends SNMP notifications in incorrect order
> --
>
> Key: AMBARI-20157
> URL: https://issues.apache.org/jira/browse/AMBARI-20157
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: amarnathreddy
>Assignee: amarnathreddy
>Priority: Minor
>
> Ambari sends notifications in wrong order. ideally first generated Alert 
> should be notified first.
> This issue is reproducible in straight steps. 
> 1. Have 4 to 5 alerts generated in short span of time.
> 2. when Ambari notifier thread queries Database with the query like "select * 
> from alert_notice where notify_state = 'PENDING'" 
> This query returns last one first.
> Ex: 
> 2066  51  4876PENDING a11bffc9-3eda-42a7-b8ef-3f197cddfa26
> 2065  51  4874PENDING 05e810cd-61a0-4d5c-9687-334aa71e0aaa
> 2064  51  4875PENDING b30999d3-0c78-46a3-aca4-f035743030b8
> 2063  51  4873PENDING 9508afee-48dd-4599-a901-8d64ee07b909
> 2062  51  4872PENDING 73d02181-138a-440e-8e8e-32f7ac5fbe2e
> 2061  51  4871PENDING 42a134f0-f979-4be3-a51d-a5f804a11c89
> So Notified threads loops that list and sends one by one.
> This needs to be fixed. either have to read " order by notification_id" so 
> that it gives correct order. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (AMBARI-20157) Ambari sends SNMP notifications in incorrect order

2017-02-23 Thread amarnathreddy (JIRA)
amarnathreddy created AMBARI-20157:
--

 Summary: Ambari sends SNMP notifications in incorrect order
 Key: AMBARI-20157
 URL: https://issues.apache.org/jira/browse/AMBARI-20157
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.4.2
Reporter: amarnathreddy
Priority: Minor


Ambari sends notifications in wrong order. ideally first generated Alert should 
be notified first.
This issue is reproducible in straight steps. 

1. Have 4 to 5 alerts generated in short span of time.

2. when Ambari notifier thread queries Database with the query like "select * 
from alert_notice where notify_state = 'PENDING'" 

This query returns last one first.

Ex: 
206651  4876PENDING a11bffc9-3eda-42a7-b8ef-3f197cddfa26
206551  4874PENDING 05e810cd-61a0-4d5c-9687-334aa71e0aaa
206451  4875PENDING b30999d3-0c78-46a3-aca4-f035743030b8
206351  4873PENDING 9508afee-48dd-4599-a901-8d64ee07b909
206251  4872PENDING 73d02181-138a-440e-8e8e-32f7ac5fbe2e
206151  4871PENDING 42a134f0-f979-4be3-a51d-a5f804a11c89

So Notified threads loops that list and sends one by one.

This needs to be fixed. either have to read " order by notification_id" so that 
it gives correct order. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-20056) FIFO compaction resulting in too many store files on large cluster

2017-02-23 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-20056:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1075 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1075/])
AMBARI-20056 : FIFO compaction resulting in too many store files on (avijayan: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=016c7ac48dff60e4506f038ca053cb73c8962337])
* (edit) 
ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/ITPhoenixHBaseAccessor.java
* (edit) 
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/PhoenixHBaseAccessor.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java
* (edit) 
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-site.xml
* (edit) 
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/HBaseTimelineMetricStore.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java
* (edit) 
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/TimelineMetricConfiguration.java


> FIFO compaction resulting in too many store files on large cluster
> --
>
> Key: AMBARI-20056
> URL: https://issues.apache.org/jira/browse/AMBARI-20056
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20056.patch
>
>
> Set Data Tiered compaction for all tables except METRIC_RECORD
> This will allow number of store files to go down over time.  On a 500 node 
> cluster AMS can become in-operational after creating 18K store files and no 
> compaction.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20034) USER to GROUP mapping (hdfs_user -> hadoop_group) should be stack driven

2017-02-23 Thread Madhuvanthi Radhakrishnan (JIRA)

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

Madhuvanthi Radhakrishnan updated AMBARI-20034:
---
Status: Patch Available  (was: Open)

> USER to GROUP mapping (hdfs_user -> hadoop_group) should be stack driven
> 
>
> Key: AMBARI-20034
> URL: https://issues.apache.org/jira/browse/AMBARI-20034
> Project: Ambari
>  Issue Type: Bug
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
> Fix For: 2.5.0
>
> Attachments: AMBARI-20034.patch
>
>
> There is a hard coded logic to creating the user-group mapping for services. 
> This presents an issue for custom services. Fix is to make it stack driven by 
> connecting user to its groups within the configuration/stack definition itself



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20034) USER to GROUP mapping (hdfs_user -> hadoop_group) should be stack driven

2017-02-23 Thread Madhuvanthi Radhakrishnan (JIRA)

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

Madhuvanthi Radhakrishnan updated AMBARI-20034:
---
Attachment: AMBARI-20034.patch

> USER to GROUP mapping (hdfs_user -> hadoop_group) should be stack driven
> 
>
> Key: AMBARI-20034
> URL: https://issues.apache.org/jira/browse/AMBARI-20034
> Project: Ambari
>  Issue Type: Bug
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
> Fix For: 2.5.0
>
> Attachments: AMBARI-20034.patch
>
>
> There is a hard coded logic to creating the user-group mapping for services. 
> This presents an issue for custom services. Fix is to make it stack driven by 
> connecting user to its groups within the configuration/stack definition itself



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20151) add extra Tez logging configs for Hive

2017-02-23 Thread Sergey Shelukhin (JIRA)

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

Sergey Shelukhin updated AMBARI-20151:
--
Attachment: AMBARI-20151.01.patch

I disagree with leaving TezMerger out, but whatever

> add extra Tez logging configs for Hive
> --
>
> Key: AMBARI-20151
> URL: https://issues.apache.org/jira/browse/AMBARI-20151
> Project: Ambari
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Fix For: 2.5.0
>
> Attachments: AMBARI-20151.01.patch, AMBARI-20151.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20156) HadoopTimelineMetricsSink breaks after Hadoop 3 alpha2

2017-02-23 Thread Wei-Chiu Chuang (JIRA)

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

Wei-Chiu Chuang updated AMBARI-20156:
-
Description: 
Because of an API change in Hadoop 3 alpha 2, HadoopTimelineMetricsSink will 
fail to load with the following error:

{noformat}
2017-02-22 15:05:45,577 ERROR namenode.NameNode (NameNode.java:main(1709)) - 
Failed to start namenode.
java.lang.AbstractMethodError: 
org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink.init(Lorg/apache/commons/configuration2/SubsetConfiguration;)V
   at 
org.apache.hadoop.metrics2.impl.MetricsConfig.getPlugin(MetricsConfig.java:208)
   at 
org.apache.hadoop.metrics2.impl.MetricsSystemImpl.newSink(MetricsSystemImpl.java:531)
   at 
org.apache.hadoop.metrics2.impl.MetricsSystemImpl.configureSinks(MetricsSystemImpl.java:503)
   at 
org.apache.hadoop.metrics2.impl.MetricsSystemImpl.configure(MetricsSystemImpl.java:479)
   at 
org.apache.hadoop.metrics2.impl.MetricsSystemImpl.start(MetricsSystemImpl.java:188)
   at 
org.apache.hadoop.metrics2.impl.MetricsSystemImpl.init(MetricsSystemImpl.java:163)
   at 
org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.init(DefaultMetricsSystem.java:62)
   at 
org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.initialize(DefaultMetricsSystem.java:58)
   at 
org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1635)
   at 
org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1704)
2017-02-22 15:05:45,578 INFO  util.ExitUtil (ExitUtil.java:terminate(124)) - 
Exiting with status 1
{noformat}

The Hadoop API MetricsPlugin.init() has a parameter that changed from 
org.apache.commons.configuration.SubsetConfiguration to 
org.apache.commons.configuration2.SubsetConfiguration.

See HADOOP-13660 for details of the API change.

Credit: the bug was found by Daniel Pol.

  was:
Because of an API change in Hadoop 3 alpha 2, HadoopTimelineMetricsSink will 
fail to load with the following error:

{noformat}
2017-02-22 15:05:45,577 ERROR namenode.NameNode (NameNode.java:main(1709)) - 
Failed to start namenode.
java.lang.AbstractMethodError: 
org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink.init(Lorg/apache/commons/configuration2/SubsetConfiguration;)V
   at 
org.apache.hadoop.metrics2.impl.MetricsConfig.getPlugin(MetricsConfig.java:208)
   at 
org.apache.hadoop.metrics2.impl.MetricsSystemImpl.newSink(MetricsSystemImpl.java:531)
   at 
org.apache.hadoop.metrics2.impl.MetricsSystemImpl.configureSinks(MetricsSystemImpl.java:503)
   at 
org.apache.hadoop.metrics2.impl.MetricsSystemImpl.configure(MetricsSystemImpl.java:479)
   at 
org.apache.hadoop.metrics2.impl.MetricsSystemImpl.start(MetricsSystemImpl.java:188)
   at 
org.apache.hadoop.metrics2.impl.MetricsSystemImpl.init(MetricsSystemImpl.java:163)
   at 
org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.init(DefaultMetricsSystem.java:62)
   at 
org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.initialize(DefaultMetricsSystem.java:58)
   at 
org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1635)
   at 
org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1704)
2017-02-22 15:05:45,578 INFO  util.ExitUtil (ExitUtil.java:terminate(124)) - 
Exiting with status 1
{noformat}

The Hadoop API MetricsPlugin.init() has a parameter that changed from 
org.apache.commons.configuration.SubsetConfiguration to 
org.apache.commons.configuration2.SubsetConfiguration.

Credit: the bug was found by Daniel Pol.


> HadoopTimelineMetricsSink breaks after Hadoop 3 alpha2
> --
>
> Key: AMBARI-20156
> URL: https://issues.apache.org/jira/browse/AMBARI-20156
> Project: Ambari
>  Issue Type: Bug
>  Components: metrics
>Reporter: Wei-Chiu Chuang
>
> Because of an API change in Hadoop 3 alpha 2, HadoopTimelineMetricsSink will 
> fail to load with the following error:
> {noformat}
> 2017-02-22 15:05:45,577 ERROR namenode.NameNode (NameNode.java:main(1709)) - 
> Failed to start namenode.
> java.lang.AbstractMethodError: 
> org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink.init(Lorg/apache/commons/configuration2/SubsetConfiguration;)V
>at 
> org.apache.hadoop.metrics2.impl.MetricsConfig.getPlugin(MetricsConfig.java:208)
>at 
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.newSink(MetricsSystemImpl.java:531)
>at 
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.configureSinks(MetricsSystemImpl.java:503)
>at 
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.configure(MetricsSystemImpl.java:479)
>at 
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.start(MetricsSystemImpl.java:188)
>at 
> 

[jira] [Commented] (AMBARI-15754) configs.sh expands ***** in config values to a local file list, causing broken config files

2017-02-23 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-15754:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1074 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1074/])
AMBARI-15754. configs.sh expands * in config values to a local file 
(smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a65bf361277a285292e08901ae4f5ecdafe9246e])
* (edit) ambari-server/src/main/resources/scripts/configs.sh


> configs.sh expands * in config values to a local file list, causing 
> broken config files
> ---
>
> Key: AMBARI-15754
> URL: https://issues.apache.org/jira/browse/AMBARI-15754
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.0.0, 2.0.1, 2.1.0, 2.3.0, 2.0.2, 2.1.1, 2.1.2, trunk, 
> 2.0.3, 2.2.0, 2.4.0, 2.2.1, 2.2.2, 2.4.1
>Reporter: Asger Askov Blekinge
>Assignee: Asger Askov Blekinge
>  Labels: easyfix, patch
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-15754-branch-2.5.patch, 
> AMBARI-15754_trunk_v3.patch, AMBARI-15754.v2.patch
>
>
> When you try to get the value of, say, pig-log4j like this, it outputs 
> correctly
> {code}
> curl -k -s -u $AMBARI_USER:$AMBARI_PASSWORD 
> "$AMBARI_HOST:$AMBARI_PORT/api/v1/clusters/$CLUSTER_NAME/configurations?type=pig-log4j=version1"
> {code}
> If you use configs.sh to do the same
> {code}
> configs.sh -u $AMBARI_USER -p $AMBARI_PASSWORD -port $AMBARI_PORT get 
> $AMBARI_HOST $CLUSTER_NAME pig-log4j
> {code}
> it will have replaced the * with the file list in the working directory
> So,
> {code}
>  "content" : "\n#\n#\n# Licensed to the Apache Software Foundation (ASF) 
> under one\n# or more contributor license agreements.  See the NOTICE file\n# 
> distributed with this work for additional information\n# regarding copyright 
> ownership.  The ASF licenses this file\n# to you under the Apache License, 
> Version 2.0 (the\n# \"License\"); you may not use this file except in 
> compliance\n# with the License.  You may obtain a copy of the License 
> at\n#\n#   http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required 
> by applicable law or agreed to in writing,\n# software distributed under the 
> License is distributed on an\n# \"AS IS\" BASIS, WITHOUT WARRANTIES OR 
> CONDITIONS OF ANY\n# KIND, either express or implied.  See the License for 
> the\n# specific language governing permissions and limitations\n# under the 
> License.\n#\n#\n#\n\n# * Set root logger level to DEBUG and its only 
> appender to A.\nlog4j.logger.org.apache.pig=info, A\n\n# * A is set to be 
> a ConsoleAppender.\nlog4j.appender.A=org.apache.log4j.ConsoleAppender\n# 
> * A uses 
> PatternLayout.\nlog4j.appender.A.layout=org.apache.log4j.PatternLayout\nlog4j.appender.A.layout.ConversionPattern=%-4r
>  [%t] %-5p %c %x - %m%n"
> {code}
> will be output as 
> {code}
> "content" : "\n#\n#\n# Licensed to the Apache Software Foundation (ASF) under 
> one\n# or more contributor license agreements. See the NOTICE file\n# 
> distributed with this work for additional information\n# regarding copyright 
> ownership. The ASF licenses this file\n# to you under the Apache License, 
> Version 2.0 (the\n# \"License\"); you may not use this file except in 
> compliance\n# with the License. You may obtain a copy of the License at\n#\n# 
> http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required by 
> applicable law or agreed to in writing,\n# software distributed under the 
> License is distributed on an\n# \"AS IS\" BASIS, WITHOUT WARRANTIES OR 
> CONDITIONS OF ANY\n# KIND, either express or implied. See the License for 
> the\n# specific language governing permissions and limitations\n# under the 
> License.\n#\n#\n#\n\n# bigr configs.sh gpfs mmls ssh symphony Set root logger 
> level to DEBUG and its only appender to A.\nlog4j.logger.org.apache.pig=info, 
> A\n\n# bigr configs.sh gpfs mmls ssh symphony A is set to be a 
> ConsoleAppender.\nlog4j.appender.A=org.apache.log4j.ConsoleAppender\n# bigr 
> configs.sh gpfs mmls ssh symphony A uses 
> PatternLayout.\nlog4j.appender.A.layout=org.apache.log4j.PatternLayout\nlog4j.appender.A.layout.ConversionPattern=%-4r
>  [%t] %-5p %c %x - %m%n"
> {code}
> As you can see, there are no * string in the output any longer, but 
> instead it has been replaced with "bigr configs.sh gpfs mmls ssh symphony" 
> which happened to be the local files in my working dir. 
> It all comes from this line in configs.sh, line 241-247
> {code}
> if [ "$propertiesStarted" -gt "0" ]; then
>   if [ -z $FILENAME ]; then
> echo $line
>   else
> echo $line >> $FILENAME
>   fi
> fi

[jira] [Created] (AMBARI-20156) HadoopTimelineMetricsSink breaks after Hadoop 3 alpha2

2017-02-23 Thread Wei-Chiu Chuang (JIRA)
Wei-Chiu Chuang created AMBARI-20156:


 Summary: HadoopTimelineMetricsSink breaks after Hadoop 3 alpha2
 Key: AMBARI-20156
 URL: https://issues.apache.org/jira/browse/AMBARI-20156
 Project: Ambari
  Issue Type: Bug
  Components: metrics
Reporter: Wei-Chiu Chuang


Because of an API change in Hadoop 3 alpha 2, HadoopTimelineMetricsSink will 
fail to load with the following error:

{noformat}
2017-02-22 15:05:45,577 ERROR namenode.NameNode (NameNode.java:main(1709)) - 
Failed to start namenode.
java.lang.AbstractMethodError: 
org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink.init(Lorg/apache/commons/configuration2/SubsetConfiguration;)V
   at 
org.apache.hadoop.metrics2.impl.MetricsConfig.getPlugin(MetricsConfig.java:208)
   at 
org.apache.hadoop.metrics2.impl.MetricsSystemImpl.newSink(MetricsSystemImpl.java:531)
   at 
org.apache.hadoop.metrics2.impl.MetricsSystemImpl.configureSinks(MetricsSystemImpl.java:503)
   at 
org.apache.hadoop.metrics2.impl.MetricsSystemImpl.configure(MetricsSystemImpl.java:479)
   at 
org.apache.hadoop.metrics2.impl.MetricsSystemImpl.start(MetricsSystemImpl.java:188)
   at 
org.apache.hadoop.metrics2.impl.MetricsSystemImpl.init(MetricsSystemImpl.java:163)
   at 
org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.init(DefaultMetricsSystem.java:62)
   at 
org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.initialize(DefaultMetricsSystem.java:58)
   at 
org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1635)
   at 
org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1704)
2017-02-22 15:05:45,578 INFO  util.ExitUtil (ExitUtil.java:terminate(124)) - 
Exiting with status 1
{noformat}

The Hadoop API MetricsPlugin.init() has a parameter that changed from 
org.apache.commons.configuration.SubsetConfiguration to 
org.apache.commons.configuration2.SubsetConfiguration.

Credit: the bug was found by Daniel Pol.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-15754) configs.sh expands ***** in config values to a local file list, causing broken config files

2017-02-23 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-15754:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6833 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6833/])
AMBARI-15754. Retain the deprecation warning from 2.5.0 (Asger Askov (smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=fc37b7376bc65de3aec93accd0a57cf7807ef98f])
* (edit) ambari-server/src/main/resources/scripts/configs.sh


> configs.sh expands * in config values to a local file list, causing 
> broken config files
> ---
>
> Key: AMBARI-15754
> URL: https://issues.apache.org/jira/browse/AMBARI-15754
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.0.0, 2.0.1, 2.1.0, 2.3.0, 2.0.2, 2.1.1, 2.1.2, trunk, 
> 2.0.3, 2.2.0, 2.4.0, 2.2.1, 2.2.2, 2.4.1
>Reporter: Asger Askov Blekinge
>Assignee: Asger Askov Blekinge
>  Labels: easyfix, patch
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-15754-branch-2.5.patch, 
> AMBARI-15754_trunk_v3.patch, AMBARI-15754.v2.patch
>
>
> When you try to get the value of, say, pig-log4j like this, it outputs 
> correctly
> {code}
> curl -k -s -u $AMBARI_USER:$AMBARI_PASSWORD 
> "$AMBARI_HOST:$AMBARI_PORT/api/v1/clusters/$CLUSTER_NAME/configurations?type=pig-log4j=version1"
> {code}
> If you use configs.sh to do the same
> {code}
> configs.sh -u $AMBARI_USER -p $AMBARI_PASSWORD -port $AMBARI_PORT get 
> $AMBARI_HOST $CLUSTER_NAME pig-log4j
> {code}
> it will have replaced the * with the file list in the working directory
> So,
> {code}
>  "content" : "\n#\n#\n# Licensed to the Apache Software Foundation (ASF) 
> under one\n# or more contributor license agreements.  See the NOTICE file\n# 
> distributed with this work for additional information\n# regarding copyright 
> ownership.  The ASF licenses this file\n# to you under the Apache License, 
> Version 2.0 (the\n# \"License\"); you may not use this file except in 
> compliance\n# with the License.  You may obtain a copy of the License 
> at\n#\n#   http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required 
> by applicable law or agreed to in writing,\n# software distributed under the 
> License is distributed on an\n# \"AS IS\" BASIS, WITHOUT WARRANTIES OR 
> CONDITIONS OF ANY\n# KIND, either express or implied.  See the License for 
> the\n# specific language governing permissions and limitations\n# under the 
> License.\n#\n#\n#\n\n# * Set root logger level to DEBUG and its only 
> appender to A.\nlog4j.logger.org.apache.pig=info, A\n\n# * A is set to be 
> a ConsoleAppender.\nlog4j.appender.A=org.apache.log4j.ConsoleAppender\n# 
> * A uses 
> PatternLayout.\nlog4j.appender.A.layout=org.apache.log4j.PatternLayout\nlog4j.appender.A.layout.ConversionPattern=%-4r
>  [%t] %-5p %c %x - %m%n"
> {code}
> will be output as 
> {code}
> "content" : "\n#\n#\n# Licensed to the Apache Software Foundation (ASF) under 
> one\n# or more contributor license agreements. See the NOTICE file\n# 
> distributed with this work for additional information\n# regarding copyright 
> ownership. The ASF licenses this file\n# to you under the Apache License, 
> Version 2.0 (the\n# \"License\"); you may not use this file except in 
> compliance\n# with the License. You may obtain a copy of the License at\n#\n# 
> http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required by 
> applicable law or agreed to in writing,\n# software distributed under the 
> License is distributed on an\n# \"AS IS\" BASIS, WITHOUT WARRANTIES OR 
> CONDITIONS OF ANY\n# KIND, either express or implied. See the License for 
> the\n# specific language governing permissions and limitations\n# under the 
> License.\n#\n#\n#\n\n# bigr configs.sh gpfs mmls ssh symphony Set root logger 
> level to DEBUG and its only appender to A.\nlog4j.logger.org.apache.pig=info, 
> A\n\n# bigr configs.sh gpfs mmls ssh symphony A is set to be a 
> ConsoleAppender.\nlog4j.appender.A=org.apache.log4j.ConsoleAppender\n# bigr 
> configs.sh gpfs mmls ssh symphony A uses 
> PatternLayout.\nlog4j.appender.A.layout=org.apache.log4j.PatternLayout\nlog4j.appender.A.layout.ConversionPattern=%-4r
>  [%t] %-5p %c %x - %m%n"
> {code}
> As you can see, there are no * string in the output any longer, but 
> instead it has been replaced with "bigr configs.sh gpfs mmls ssh symphony" 
> which happened to be the local files in my working dir. 
> It all comes from this line in configs.sh, line 241-247
> {code}
> if [ "$propertiesStarted" -gt "0" ]; then
>   if [ -z $FILENAME ]; then
> echo $line
>   else
> echo $line >> $FILENAME
>   fi
> fi

[jira] [Commented] (AMBARI-20151) add extra Tez logging configs for Hive

2017-02-23 Thread Siddharth Seth (JIRA)

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

Siddharth Seth commented on AMBARI-20151:
-

We need to leave out TezMerger for now, and add it in when it has a custom 
logger.

> add extra Tez logging configs for Hive
> --
>
> Key: AMBARI-20151
> URL: https://issues.apache.org/jira/browse/AMBARI-20151
> Project: Ambari
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Fix For: 2.5.0
>
> Attachments: AMBARI-20151.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-20154) Package clean up

2017-02-23 Thread Robert Levas (JIRA)

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

Robert Levas commented on AMBARI-20154:
---

+1 for [^AMBARI-20154.patch].  This appears good to me. 


> Package clean up
> 
>
> Key: AMBARI-20154
> URL: https://issues.apache.org/jira/browse/AMBARI-20154
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics, ambari-server
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20154.patch
>
>
> Package clean up.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20151) add extra Tez logging configs for Hive

2017-02-23 Thread Sumit Mohanty (JIRA)

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

Sumit Mohanty updated AMBARI-20151:
---
Fix Version/s: 2.5.0

> add extra Tez logging configs for Hive
> --
>
> Key: AMBARI-20151
> URL: https://issues.apache.org/jira/browse/AMBARI-20151
> Project: Ambari
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Fix For: 2.5.0
>
> Attachments: AMBARI-20151.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-15754) configs.sh expands ***** in config values to a local file list, causing broken config files

2017-02-23 Thread Sumit Mohanty (JIRA)

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

Sumit Mohanty updated AMBARI-15754:
---
Fix Version/s: 2.5.0

> configs.sh expands * in config values to a local file list, causing 
> broken config files
> ---
>
> Key: AMBARI-15754
> URL: https://issues.apache.org/jira/browse/AMBARI-15754
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.0.0, 2.0.1, 2.1.0, 2.3.0, 2.0.2, 2.1.1, 2.1.2, trunk, 
> 2.0.3, 2.2.0, 2.4.0, 2.2.1, 2.2.2, 2.4.1
>Reporter: Asger Askov Blekinge
>Assignee: Asger Askov Blekinge
>  Labels: easyfix, patch
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-15754-branch-2.5.patch, 
> AMBARI-15754_trunk_v3.patch, AMBARI-15754.v2.patch
>
>
> When you try to get the value of, say, pig-log4j like this, it outputs 
> correctly
> {code}
> curl -k -s -u $AMBARI_USER:$AMBARI_PASSWORD 
> "$AMBARI_HOST:$AMBARI_PORT/api/v1/clusters/$CLUSTER_NAME/configurations?type=pig-log4j=version1"
> {code}
> If you use configs.sh to do the same
> {code}
> configs.sh -u $AMBARI_USER -p $AMBARI_PASSWORD -port $AMBARI_PORT get 
> $AMBARI_HOST $CLUSTER_NAME pig-log4j
> {code}
> it will have replaced the * with the file list in the working directory
> So,
> {code}
>  "content" : "\n#\n#\n# Licensed to the Apache Software Foundation (ASF) 
> under one\n# or more contributor license agreements.  See the NOTICE file\n# 
> distributed with this work for additional information\n# regarding copyright 
> ownership.  The ASF licenses this file\n# to you under the Apache License, 
> Version 2.0 (the\n# \"License\"); you may not use this file except in 
> compliance\n# with the License.  You may obtain a copy of the License 
> at\n#\n#   http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required 
> by applicable law or agreed to in writing,\n# software distributed under the 
> License is distributed on an\n# \"AS IS\" BASIS, WITHOUT WARRANTIES OR 
> CONDITIONS OF ANY\n# KIND, either express or implied.  See the License for 
> the\n# specific language governing permissions and limitations\n# under the 
> License.\n#\n#\n#\n\n# * Set root logger level to DEBUG and its only 
> appender to A.\nlog4j.logger.org.apache.pig=info, A\n\n# * A is set to be 
> a ConsoleAppender.\nlog4j.appender.A=org.apache.log4j.ConsoleAppender\n# 
> * A uses 
> PatternLayout.\nlog4j.appender.A.layout=org.apache.log4j.PatternLayout\nlog4j.appender.A.layout.ConversionPattern=%-4r
>  [%t] %-5p %c %x - %m%n"
> {code}
> will be output as 
> {code}
> "content" : "\n#\n#\n# Licensed to the Apache Software Foundation (ASF) under 
> one\n# or more contributor license agreements. See the NOTICE file\n# 
> distributed with this work for additional information\n# regarding copyright 
> ownership. The ASF licenses this file\n# to you under the Apache License, 
> Version 2.0 (the\n# \"License\"); you may not use this file except in 
> compliance\n# with the License. You may obtain a copy of the License at\n#\n# 
> http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required by 
> applicable law or agreed to in writing,\n# software distributed under the 
> License is distributed on an\n# \"AS IS\" BASIS, WITHOUT WARRANTIES OR 
> CONDITIONS OF ANY\n# KIND, either express or implied. See the License for 
> the\n# specific language governing permissions and limitations\n# under the 
> License.\n#\n#\n#\n\n# bigr configs.sh gpfs mmls ssh symphony Set root logger 
> level to DEBUG and its only appender to A.\nlog4j.logger.org.apache.pig=info, 
> A\n\n# bigr configs.sh gpfs mmls ssh symphony A is set to be a 
> ConsoleAppender.\nlog4j.appender.A=org.apache.log4j.ConsoleAppender\n# bigr 
> configs.sh gpfs mmls ssh symphony A uses 
> PatternLayout.\nlog4j.appender.A.layout=org.apache.log4j.PatternLayout\nlog4j.appender.A.layout.ConversionPattern=%-4r
>  [%t] %-5p %c %x - %m%n"
> {code}
> As you can see, there are no * string in the output any longer, but 
> instead it has been replaced with "bigr configs.sh gpfs mmls ssh symphony" 
> which happened to be the local files in my working dir. 
> It all comes from this line in configs.sh, line 241-247
> {code}
> if [ "$propertiesStarted" -gt "0" ]; then
>   if [ -z $FILENAME ]; then
> echo $line
>   else
> echo $line >> $FILENAME
>   fi
> fi
> {code}
> where the echo do not quote the $line to output



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-15754) configs.sh expands ***** in config values to a local file list, causing broken config files

2017-02-23 Thread Sumit Mohanty (JIRA)

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

Sumit Mohanty commented on AMBARI-15754:


2.5 patch and trunk addendum LGTM, +1

> configs.sh expands * in config values to a local file list, causing 
> broken config files
> ---
>
> Key: AMBARI-15754
> URL: https://issues.apache.org/jira/browse/AMBARI-15754
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.0.0, 2.0.1, 2.1.0, 2.3.0, 2.0.2, 2.1.1, 2.1.2, trunk, 
> 2.0.3, 2.2.0, 2.4.0, 2.2.1, 2.2.2, 2.4.1
>Reporter: Asger Askov Blekinge
>Assignee: Asger Askov Blekinge
>  Labels: easyfix, patch
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-15754-branch-2.5.patch, 
> AMBARI-15754_trunk_v3.patch, AMBARI-15754.v2.patch
>
>
> When you try to get the value of, say, pig-log4j like this, it outputs 
> correctly
> {code}
> curl -k -s -u $AMBARI_USER:$AMBARI_PASSWORD 
> "$AMBARI_HOST:$AMBARI_PORT/api/v1/clusters/$CLUSTER_NAME/configurations?type=pig-log4j=version1"
> {code}
> If you use configs.sh to do the same
> {code}
> configs.sh -u $AMBARI_USER -p $AMBARI_PASSWORD -port $AMBARI_PORT get 
> $AMBARI_HOST $CLUSTER_NAME pig-log4j
> {code}
> it will have replaced the * with the file list in the working directory
> So,
> {code}
>  "content" : "\n#\n#\n# Licensed to the Apache Software Foundation (ASF) 
> under one\n# or more contributor license agreements.  See the NOTICE file\n# 
> distributed with this work for additional information\n# regarding copyright 
> ownership.  The ASF licenses this file\n# to you under the Apache License, 
> Version 2.0 (the\n# \"License\"); you may not use this file except in 
> compliance\n# with the License.  You may obtain a copy of the License 
> at\n#\n#   http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required 
> by applicable law or agreed to in writing,\n# software distributed under the 
> License is distributed on an\n# \"AS IS\" BASIS, WITHOUT WARRANTIES OR 
> CONDITIONS OF ANY\n# KIND, either express or implied.  See the License for 
> the\n# specific language governing permissions and limitations\n# under the 
> License.\n#\n#\n#\n\n# * Set root logger level to DEBUG and its only 
> appender to A.\nlog4j.logger.org.apache.pig=info, A\n\n# * A is set to be 
> a ConsoleAppender.\nlog4j.appender.A=org.apache.log4j.ConsoleAppender\n# 
> * A uses 
> PatternLayout.\nlog4j.appender.A.layout=org.apache.log4j.PatternLayout\nlog4j.appender.A.layout.ConversionPattern=%-4r
>  [%t] %-5p %c %x - %m%n"
> {code}
> will be output as 
> {code}
> "content" : "\n#\n#\n# Licensed to the Apache Software Foundation (ASF) under 
> one\n# or more contributor license agreements. See the NOTICE file\n# 
> distributed with this work for additional information\n# regarding copyright 
> ownership. The ASF licenses this file\n# to you under the Apache License, 
> Version 2.0 (the\n# \"License\"); you may not use this file except in 
> compliance\n# with the License. You may obtain a copy of the License at\n#\n# 
> http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required by 
> applicable law or agreed to in writing,\n# software distributed under the 
> License is distributed on an\n# \"AS IS\" BASIS, WITHOUT WARRANTIES OR 
> CONDITIONS OF ANY\n# KIND, either express or implied. See the License for 
> the\n# specific language governing permissions and limitations\n# under the 
> License.\n#\n#\n#\n\n# bigr configs.sh gpfs mmls ssh symphony Set root logger 
> level to DEBUG and its only appender to A.\nlog4j.logger.org.apache.pig=info, 
> A\n\n# bigr configs.sh gpfs mmls ssh symphony A is set to be a 
> ConsoleAppender.\nlog4j.appender.A=org.apache.log4j.ConsoleAppender\n# bigr 
> configs.sh gpfs mmls ssh symphony A uses 
> PatternLayout.\nlog4j.appender.A.layout=org.apache.log4j.PatternLayout\nlog4j.appender.A.layout.ConversionPattern=%-4r
>  [%t] %-5p %c %x - %m%n"
> {code}
> As you can see, there are no * string in the output any longer, but 
> instead it has been replaced with "bigr configs.sh gpfs mmls ssh symphony" 
> which happened to be the local files in my working dir. 
> It all comes from this line in configs.sh, line 241-247
> {code}
> if [ "$propertiesStarted" -gt "0" ]; then
>   if [ -z $FILENAME ]; then
> echo $line
>   else
> echo $line >> $FILENAME
>   fi
> fi
> {code}
> where the echo do not quote the $line to output



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-15754) configs.sh expands ***** in config values to a local file list, causing broken config files

2017-02-23 Thread Madhuvanthi Radhakrishnan (JIRA)

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

Madhuvanthi Radhakrishnan updated AMBARI-15754:
---
Attachment: AMBARI-15754-branch-2.5.patch
AMBARI-15754_trunk_v3.patch

> configs.sh expands * in config values to a local file list, causing 
> broken config files
> ---
>
> Key: AMBARI-15754
> URL: https://issues.apache.org/jira/browse/AMBARI-15754
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.0.0, 2.0.1, 2.1.0, 2.3.0, 2.0.2, 2.1.1, 2.1.2, trunk, 
> 2.0.3, 2.2.0, 2.4.0, 2.2.1, 2.2.2, 2.4.1
>Reporter: Asger Askov Blekinge
>Assignee: Asger Askov Blekinge
>  Labels: easyfix, patch
> Fix For: trunk
>
> Attachments: AMBARI-15754-branch-2.5.patch, 
> AMBARI-15754_trunk_v3.patch, AMBARI-15754.v2.patch
>
>
> When you try to get the value of, say, pig-log4j like this, it outputs 
> correctly
> {code}
> curl -k -s -u $AMBARI_USER:$AMBARI_PASSWORD 
> "$AMBARI_HOST:$AMBARI_PORT/api/v1/clusters/$CLUSTER_NAME/configurations?type=pig-log4j=version1"
> {code}
> If you use configs.sh to do the same
> {code}
> configs.sh -u $AMBARI_USER -p $AMBARI_PASSWORD -port $AMBARI_PORT get 
> $AMBARI_HOST $CLUSTER_NAME pig-log4j
> {code}
> it will have replaced the * with the file list in the working directory
> So,
> {code}
>  "content" : "\n#\n#\n# Licensed to the Apache Software Foundation (ASF) 
> under one\n# or more contributor license agreements.  See the NOTICE file\n# 
> distributed with this work for additional information\n# regarding copyright 
> ownership.  The ASF licenses this file\n# to you under the Apache License, 
> Version 2.0 (the\n# \"License\"); you may not use this file except in 
> compliance\n# with the License.  You may obtain a copy of the License 
> at\n#\n#   http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required 
> by applicable law or agreed to in writing,\n# software distributed under the 
> License is distributed on an\n# \"AS IS\" BASIS, WITHOUT WARRANTIES OR 
> CONDITIONS OF ANY\n# KIND, either express or implied.  See the License for 
> the\n# specific language governing permissions and limitations\n# under the 
> License.\n#\n#\n#\n\n# * Set root logger level to DEBUG and its only 
> appender to A.\nlog4j.logger.org.apache.pig=info, A\n\n# * A is set to be 
> a ConsoleAppender.\nlog4j.appender.A=org.apache.log4j.ConsoleAppender\n# 
> * A uses 
> PatternLayout.\nlog4j.appender.A.layout=org.apache.log4j.PatternLayout\nlog4j.appender.A.layout.ConversionPattern=%-4r
>  [%t] %-5p %c %x - %m%n"
> {code}
> will be output as 
> {code}
> "content" : "\n#\n#\n# Licensed to the Apache Software Foundation (ASF) under 
> one\n# or more contributor license agreements. See the NOTICE file\n# 
> distributed with this work for additional information\n# regarding copyright 
> ownership. The ASF licenses this file\n# to you under the Apache License, 
> Version 2.0 (the\n# \"License\"); you may not use this file except in 
> compliance\n# with the License. You may obtain a copy of the License at\n#\n# 
> http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required by 
> applicable law or agreed to in writing,\n# software distributed under the 
> License is distributed on an\n# \"AS IS\" BASIS, WITHOUT WARRANTIES OR 
> CONDITIONS OF ANY\n# KIND, either express or implied. See the License for 
> the\n# specific language governing permissions and limitations\n# under the 
> License.\n#\n#\n#\n\n# bigr configs.sh gpfs mmls ssh symphony Set root logger 
> level to DEBUG and its only appender to A.\nlog4j.logger.org.apache.pig=info, 
> A\n\n# bigr configs.sh gpfs mmls ssh symphony A is set to be a 
> ConsoleAppender.\nlog4j.appender.A=org.apache.log4j.ConsoleAppender\n# bigr 
> configs.sh gpfs mmls ssh symphony A uses 
> PatternLayout.\nlog4j.appender.A.layout=org.apache.log4j.PatternLayout\nlog4j.appender.A.layout.ConversionPattern=%-4r
>  [%t] %-5p %c %x - %m%n"
> {code}
> As you can see, there are no * string in the output any longer, but 
> instead it has been replaced with "bigr configs.sh gpfs mmls ssh symphony" 
> which happened to be the local files in my working dir. 
> It all comes from this line in configs.sh, line 241-247
> {code}
> if [ "$propertiesStarted" -gt "0" ]; then
>   if [ -z $FILENAME ]; then
> echo $line
>   else
> echo $line >> $FILENAME
>   fi
> fi
> {code}
> where the echo do not quote the $line to output



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Resolved] (AMBARI-20153) Fix AMBARI-15754 in Ambari 2.5, potentially modifying configs.sh

2017-02-23 Thread Madhuvanthi Radhakrishnan (JIRA)

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

Madhuvanthi Radhakrishnan resolved AMBARI-20153.

Resolution: Duplicate

> Fix AMBARI-15754 in Ambari 2.5, potentially modifying configs.sh
> 
>
> Key: AMBARI-20153
> URL: https://issues.apache.org/jira/browse/AMBARI-20153
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
>
> Fix for maintaining * characters in configs.sh get commands was made in 
> AMBARI-15754. Creating a patch for 2.5 branch in this jira.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20155) EU: Manual Step without any context after "All Service Checks" fail

2017-02-23 Thread Nate Cole (JIRA)

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

Nate Cole updated AMBARI-20155:
---
Status: Patch Available  (was: Open)

> EU: Manual Step without any context after "All Service Checks" fail
> ---
>
> Key: AMBARI-20155
> URL: https://issues.apache.org/jira/browse/AMBARI-20155
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20155.patch
>
>
> During EU from 2.5.3.0-2.6.0.0, a manual step popped up that didn't make 
> sense.
> It says "Manual steps required [] I have performed the manual steps above." 
> without telling the user what the manual steps are.
> The BE is not providing a message for display.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20155) EU: Manual Step without any context after "All Service Checks" fail

2017-02-23 Thread Nate Cole (JIRA)

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

Nate Cole updated AMBARI-20155:
---
Attachment: AMBARI-20155.patch

> EU: Manual Step without any context after "All Service Checks" fail
> ---
>
> Key: AMBARI-20155
> URL: https://issues.apache.org/jira/browse/AMBARI-20155
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20155.patch
>
>
> During EU from 2.5.3.0-2.6.0.0, a manual step popped up that didn't make 
> sense.
> It says "Manual steps required [] I have performed the manual steps above." 
> without telling the user what the manual steps are.
> The BE is not providing a message for display.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-20154) Package clean up

2017-02-23 Thread Siddharth Wagle (JIRA)

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

Siddharth Wagle commented on AMBARI-20154:
--

+1 LGTM

> Package clean up
> 
>
> Key: AMBARI-20154
> URL: https://issues.apache.org/jira/browse/AMBARI-20154
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics, ambari-server
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20154.patch
>
>
> Package clean up.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (AMBARI-20155) EU: Manual Step without any context after "All Service Checks" fail

2017-02-23 Thread Nate Cole (JIRA)
Nate Cole created AMBARI-20155:
--

 Summary: EU: Manual Step without any context after "All Service 
Checks" fail
 Key: AMBARI-20155
 URL: https://issues.apache.org/jira/browse/AMBARI-20155
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Reporter: Nate Cole
Assignee: Nate Cole
Priority: Critical
 Fix For: 2.5.0


During EU from 2.5.3.0-2.6.0.0, a manual step popped up that didn't make sense.
It says "Manual steps required [] I have performed the manual steps above." 
without telling the user what the manual steps are.

The BE is not providing a message for display.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20154) Package clean up

2017-02-23 Thread Vitaly Brodetskyi (JIRA)

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

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

> Package clean up
> 
>
> Key: AMBARI-20154
> URL: https://issues.apache.org/jira/browse/AMBARI-20154
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics, ambari-server
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20154.patch
>
>
> Package clean up.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20154) Package clean up

2017-02-23 Thread Vitaly Brodetskyi (JIRA)

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

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

> Package clean up
> 
>
> Key: AMBARI-20154
> URL: https://issues.apache.org/jira/browse/AMBARI-20154
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics, ambari-server
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20154.patch
>
>
> Package clean up.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (AMBARI-20154) Package clean up

2017-02-23 Thread Vitaly Brodetskyi (JIRA)
Vitaly Brodetskyi created AMBARI-20154:
--

 Summary: Package clean up
 Key: AMBARI-20154
 URL: https://issues.apache.org/jira/browse/AMBARI-20154
 Project: Ambari
  Issue Type: Bug
  Components: ambari-metrics, ambari-server
Affects Versions: 2.5.0
Reporter: Vitaly Brodetskyi
Assignee: Vitaly Brodetskyi
Priority: Critical
 Fix For: 2.5.0


Package clean up.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20150) Hive View 2.0 Tables tab does not open at all if Ranger policy does not include access to the 'admin' user

2017-02-23 Thread DIPAYAN BHOWMICK (JIRA)

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

DIPAYAN BHOWMICK updated AMBARI-20150:
--
Attachment: AMBARI-20150.2.branch-2.5.patch

> Hive View 2.0 Tables tab does not open at all if Ranger policy does not 
> include access to the 'admin' user
> --
>
> Key: AMBARI-20150
> URL: https://issues.apache.org/jira/browse/AMBARI-20150
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.5.0
>
> Attachments: AMBARI-20150.2.branch-2.5.patch, 
> AMBARI-20150.branch-2.5.patch
>
>
> User should be given an appropriate error message while navigating to 
> 'Tables' tab upon opening 'Authorizations' tab of a specific table



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20152) Use storm user principal instead of nimbus user principal for ranger audit

2017-02-23 Thread JIRA

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

Olivér Szabó updated AMBARI-20152:
--
Summary: Use storm user principal instead of nimbus user principal for 
ranger audit  (was: Use storm user instead of nimbus user for ranger audit)

> Use storm user principal instead of nimbus user principal for ranger audit
> --
>
> Key: AMBARI-20152
> URL: https://issues.apache.org/jira/browse/AMBARI-20152
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20147) Not able to delete custom property

2017-02-23 Thread Yusaku Sako (JIRA)

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

Yusaku Sako updated AMBARI-20147:
-
Fix Version/s: 2.5.0

> Not able to delete custom property
> --
>
> Key: AMBARI-20147
> URL: https://issues.apache.org/jira/browse/AMBARI-20147
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: amarnathreddy
>Priority: Critical
> Fix For: 2.5.0
>
>
> Steps to reproduce the issue:
> 1. Under Hive service , Create a custom Group called "hive-group1"
> 2. Add a property say "hive.mv.files.thread"
> 3. save the configurations
> 4. Again go to hive configurations, select hive-group1 group and then try to 
> delete the configuration by clicking "-" , it does nothing - in console fails 
> with JS error as
> Uncaught TypeError: Cannot read property 'without' of null
> at Class.removeOverride (app.js:185869)
> at handler (vendor.js:21227)
> at HTMLAnchorElement. (vendor.js:13019)
> at HTMLDivElement.dispatch (vendor.js:126)
> at HTMLDivElement.i (vendor.js:126)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Assigned] (AMBARI-20147) Not able to delete custom property

2017-02-23 Thread Yusaku Sako (JIRA)

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

Yusaku Sako reassigned AMBARI-20147:


Assignee: Oleg Nechiporenko

> Not able to delete custom property
> --
>
> Key: AMBARI-20147
> URL: https://issues.apache.org/jira/browse/AMBARI-20147
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: amarnathreddy
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.5.0
>
>
> Steps to reproduce the issue:
> 1. Under Hive service , Create a custom Group called "hive-group1"
> 2. Add a property say "hive.mv.files.thread"
> 3. save the configurations
> 4. Again go to hive configurations, select hive-group1 group and then try to 
> delete the configuration by clicking "-" , it does nothing - in console fails 
> with JS error as
> Uncaught TypeError: Cannot read property 'without' of null
> at Class.removeOverride (app.js:185869)
> at handler (vendor.js:21227)
> at HTMLAnchorElement. (vendor.js:13019)
> at HTMLDivElement.dispatch (vendor.js:126)
> at HTMLDivElement.i (vendor.js:126)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (AMBARI-20153) Fix AMBARI-15754 in Ambari 2.5, potentially modifying configs.sh

2017-02-23 Thread Madhuvanthi Radhakrishnan (JIRA)
Madhuvanthi Radhakrishnan created AMBARI-20153:
--

 Summary: Fix AMBARI-15754 in Ambari 2.5, potentially modifying 
configs.sh
 Key: AMBARI-20153
 URL: https://issues.apache.org/jira/browse/AMBARI-20153
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.5.0
Reporter: Madhuvanthi Radhakrishnan
Assignee: Madhuvanthi Radhakrishnan


Fix for maintaining * characters in configs.sh get commands was made in 
AMBARI-15754. Creating a patch for 2.5 branch in this jira.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20151) add extra Tez logging configs for Hive

2017-02-23 Thread Sergey Shelukhin (JIRA)

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

Sergey Shelukhin updated AMBARI-20151:
--
Status: Patch Available  (was: Open)

> add extra Tez logging configs for Hive
> --
>
> Key: AMBARI-20151
> URL: https://issues.apache.org/jira/browse/AMBARI-20151
> Project: Ambari
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Attachments: AMBARI-20151.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20151) add extra Tez logging configs for Hive

2017-02-23 Thread Sergey Shelukhin (JIRA)

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

Sergey Shelukhin updated AMBARI-20151:
--
Attachment: AMBARI-20151.patch

Based in HIVE-16015
We will later also change TezMerger cc [~sseth]

[~swapanshridhar] can you take a look?

> add extra Tez logging configs for Hive
> --
>
> Key: AMBARI-20151
> URL: https://issues.apache.org/jira/browse/AMBARI-20151
> Project: Ambari
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Attachments: AMBARI-20151.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (AMBARI-20152) Use storm user instead of nimbus user for ranger audit

2017-02-23 Thread JIRA
Olivér Szabó created AMBARI-20152:
-

 Summary: Use storm user instead of nimbus user for ranger audit
 Key: AMBARI-20152
 URL: https://issues.apache.org/jira/browse/AMBARI-20152
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.5.0
Reporter: Olivér Szabó
Assignee: Olivér Szabó
 Fix For: 2.5.0






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (AMBARI-20151) add extra Tez logging configs for Hive

2017-02-23 Thread Sergey Shelukhin (JIRA)
Sergey Shelukhin created AMBARI-20151:
-

 Summary: add extra Tez logging configs for Hive
 Key: AMBARI-20151
 URL: https://issues.apache.org/jira/browse/AMBARI-20151
 Project: Ambari
  Issue Type: Bug
Reporter: Sergey Shelukhin
Assignee: Sergey Shelukhin






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20150) Hive View 2.0 Tables tab does not open at all if Ranger policy does not include access to the 'admin' user

2017-02-23 Thread DIPAYAN BHOWMICK (JIRA)

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

DIPAYAN BHOWMICK updated AMBARI-20150:
--
Status: Patch Available  (was: Open)

> Hive View 2.0 Tables tab does not open at all if Ranger policy does not 
> include access to the 'admin' user
> --
>
> Key: AMBARI-20150
> URL: https://issues.apache.org/jira/browse/AMBARI-20150
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.5.0
>
> Attachments: AMBARI-20150.branch-2.5.patch
>
>
> User should be given an appropriate error message while navigating to 
> 'Tables' tab upon opening 'Authorizations' tab of a specific table



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20150) Hive View 2.0 Tables tab does not open at all if Ranger policy does not include access to the 'admin' user

2017-02-23 Thread DIPAYAN BHOWMICK (JIRA)

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

DIPAYAN BHOWMICK updated AMBARI-20150:
--
Attachment: AMBARI-20150.branch-2.5.patch

> Hive View 2.0 Tables tab does not open at all if Ranger policy does not 
> include access to the 'admin' user
> --
>
> Key: AMBARI-20150
> URL: https://issues.apache.org/jira/browse/AMBARI-20150
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.5.0
>
> Attachments: AMBARI-20150.branch-2.5.patch
>
>
> User should be given an appropriate error message while navigating to 
> 'Tables' tab upon opening 'Authorizations' tab of a specific table



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (AMBARI-20150) Hive View 2.0 Tables tab does not open at all if Ranger policy does not include access to the 'admin' user

2017-02-23 Thread DIPAYAN BHOWMICK (JIRA)
DIPAYAN BHOWMICK created AMBARI-20150:
-

 Summary: Hive View 2.0 Tables tab does not open at all if Ranger 
policy does not include access to the 'admin' user
 Key: AMBARI-20150
 URL: https://issues.apache.org/jira/browse/AMBARI-20150
 Project: Ambari
  Issue Type: Bug
  Components: ambari-views
Affects Versions: 2.5.0
Reporter: DIPAYAN BHOWMICK
Assignee: DIPAYAN BHOWMICK
 Fix For: 2.5.0


User should be given an appropriate error message while navigating to 'Tables' 
tab upon opening 'Authorizations' tab of a specific table



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AMBARI-20148) "Set Version on All Hosts" Fails For Hosts Without Any Stack Components

2017-02-23 Thread Jonathan Hurley (JIRA)

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

Jonathan Hurley updated AMBARI-20148:
-
Status: Patch Available  (was: Open)

> "Set Version on All Hosts" Fails For Hosts Without Any Stack Components
> ---
>
> Key: AMBARI-20148
> URL: https://issues.apache.org/jira/browse/AMBARI-20148
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20148.patch
>
>
> During EU of HDP from 2.5.3.0 to 2.6.0.0, "Set Version on All Hosts" step 
> failed for all hosts which don't have "versionable" components on them.
> *stdout*
> {noformat}
> * 2017-02-21 23:55:38,889 - Task. Type: EXECUTE, Script: 
> scripts/ru_set_all.py - Function: actionexecute
> * 2017-02-21 23:55:39,048 - call[('/usr/bin/yum', 'clean', 'all')] {'sudo': 
> True}
> * 2017-02-21 23:55:39,328 - call returned (0, 'Loaded plugins: fastestmirror, 
> security\nCleaning repos: HDP-2.5 HDP-UTILS-1.1.0.21 ambari-2.5.0.0 base 
> extras updates\nCleaning up Everything\nCleaning up list of fastest mirrors')
> * 2017-02-21 23:55:39,329 - call[('ambari-python-wrap', 
> '/usr/bin/hdp-select', 'set', 'all', '2.6.0.0-517')] {'sudo': True}
> * 2017-02-21 23:55:39,356 - call returned (1, 'ERROR: Invalid version 
> 2.6.0.0-517\n\nValid choices:')
> * Traceback (most recent call last):
> *   File "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_set_all.py", 
> line 189, in 
> * UpgradeSetAll().execute()
> *   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 313, in execute
> * method(env)
> *   File "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_set_all.py", 
> line 65, in actionexecute
> * raise Exception("Command '{0}' exit code is nonzero".format(cmd))
> * Exception: Command '('ambari-python-wrap', '/usr/bin/hdp-select', 'set', 
> 'all', '2.6.0.0-517')' exit code is nonzero
> * Command failed after 1 tries
> {noformat}
> *stderr*
> {noformat}
> * Traceback (most recent call last):
> *   File 
> "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_execute_tasks.py", 
> line 156, in 
> * ExecuteUpgradeTasks().execute()
> *   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 313, in execute
> * method(env)
> *   File 
> "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_execute_tasks.py", 
> line 153, in actionexecute
> * shell.checked_call(task.command, logoutput=True, quiet=True)
> *   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 72, in inner
> * result = function(command, **kwargs)
> *   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 102, in checked_call
> * tries=tries, try_sleep=try_sleep, 
> timeout_kill_strategy=timeout_kill_strategy)
> *   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 150, in _call_wrapper
> * result = _call(command, **kwargs_copy)
> *   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 303, in _call
> * raise ExecutionFailed(err_msg, code, out, err)
> * resource_management.core.exceptions.ExecutionFailed: Execution of 'source 
> /var/lib/ambari-agent/ambari-env.sh ; /usr/bin/ambari-python-wrap 
> /var/lib/ambari-agent/cache/custom_actions/scripts/ru_set_all.py 
> actionexecute /var/lib/ambari-agent/data/command-71697.json 
> /var/lib/ambari-agent/cache/custom_actions 
> /var/lib/ambari-agent/data/structured-out-71697.json INFO 
> /var/lib/ambari-agent/tmp' returned 1. 2017-02-21 23:55:39,048 - 
> call[('/usr/bin/yum', 'clean', 'all')] {'sudo': True}
> * 2017-02-21 23:55:39,328 - call returned (0, 'Loaded plugins: fastestmirror, 
> security\nCleaning repos: HDP-2.5 HDP-UTILS-1.1.0.21 ambari-2.5.0.0 base 
> extras updates\nCleaning up Everything\nCleaning up list of fastest mirrors')
> * 2017-02-21 23:55:39,329 - call[('ambari-python-wrap', 
> '/usr/bin/hdp-select', 'set', 'all', '2.6.0.0-517')] {'sudo': True}
> * 2017-02-21 23:55:39,356 - call returned (1, 'ERROR: Invalid version 
> 2.6.0.0-517\n\nValid choices:')
> * Traceback (most recent call last):
> *   File "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_set_all.py", 
> line 189, in 
> * UpgradeSetAll().execute()
> *   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 313, in execute
> * method(env)
> *   File "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_set_all.py", 
> line 65, in actionexecute
> * raise Exception("Command '{0}' exit code is 

[jira] [Updated] (AMBARI-20148) "Set Version on All Hosts" Fails For Hosts Without Any Stack Components

2017-02-23 Thread Jonathan Hurley (JIRA)

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

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

> "Set Version on All Hosts" Fails For Hosts Without Any Stack Components
> ---
>
> Key: AMBARI-20148
> URL: https://issues.apache.org/jira/browse/AMBARI-20148
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20148.patch
>
>
> During EU of HDP from 2.5.3.0 to 2.6.0.0, "Set Version on All Hosts" step 
> failed for all hosts which don't have "versionable" components on them.
> *stdout*
> {noformat}
> * 2017-02-21 23:55:38,889 - Task. Type: EXECUTE, Script: 
> scripts/ru_set_all.py - Function: actionexecute
> * 2017-02-21 23:55:39,048 - call[('/usr/bin/yum', 'clean', 'all')] {'sudo': 
> True}
> * 2017-02-21 23:55:39,328 - call returned (0, 'Loaded plugins: fastestmirror, 
> security\nCleaning repos: HDP-2.5 HDP-UTILS-1.1.0.21 ambari-2.5.0.0 base 
> extras updates\nCleaning up Everything\nCleaning up list of fastest mirrors')
> * 2017-02-21 23:55:39,329 - call[('ambari-python-wrap', 
> '/usr/bin/hdp-select', 'set', 'all', '2.6.0.0-517')] {'sudo': True}
> * 2017-02-21 23:55:39,356 - call returned (1, 'ERROR: Invalid version 
> 2.6.0.0-517\n\nValid choices:')
> * Traceback (most recent call last):
> *   File "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_set_all.py", 
> line 189, in 
> * UpgradeSetAll().execute()
> *   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 313, in execute
> * method(env)
> *   File "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_set_all.py", 
> line 65, in actionexecute
> * raise Exception("Command '{0}' exit code is nonzero".format(cmd))
> * Exception: Command '('ambari-python-wrap', '/usr/bin/hdp-select', 'set', 
> 'all', '2.6.0.0-517')' exit code is nonzero
> * Command failed after 1 tries
> {noformat}
> *stderr*
> {noformat}
> * Traceback (most recent call last):
> *   File 
> "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_execute_tasks.py", 
> line 156, in 
> * ExecuteUpgradeTasks().execute()
> *   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 313, in execute
> * method(env)
> *   File 
> "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_execute_tasks.py", 
> line 153, in actionexecute
> * shell.checked_call(task.command, logoutput=True, quiet=True)
> *   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 72, in inner
> * result = function(command, **kwargs)
> *   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 102, in checked_call
> * tries=tries, try_sleep=try_sleep, 
> timeout_kill_strategy=timeout_kill_strategy)
> *   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 150, in _call_wrapper
> * result = _call(command, **kwargs_copy)
> *   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 303, in _call
> * raise ExecutionFailed(err_msg, code, out, err)
> * resource_management.core.exceptions.ExecutionFailed: Execution of 'source 
> /var/lib/ambari-agent/ambari-env.sh ; /usr/bin/ambari-python-wrap 
> /var/lib/ambari-agent/cache/custom_actions/scripts/ru_set_all.py 
> actionexecute /var/lib/ambari-agent/data/command-71697.json 
> /var/lib/ambari-agent/cache/custom_actions 
> /var/lib/ambari-agent/data/structured-out-71697.json INFO 
> /var/lib/ambari-agent/tmp' returned 1. 2017-02-21 23:55:39,048 - 
> call[('/usr/bin/yum', 'clean', 'all')] {'sudo': True}
> * 2017-02-21 23:55:39,328 - call returned (0, 'Loaded plugins: fastestmirror, 
> security\nCleaning repos: HDP-2.5 HDP-UTILS-1.1.0.21 ambari-2.5.0.0 base 
> extras updates\nCleaning up Everything\nCleaning up list of fastest mirrors')
> * 2017-02-21 23:55:39,329 - call[('ambari-python-wrap', 
> '/usr/bin/hdp-select', 'set', 'all', '2.6.0.0-517')] {'sudo': True}
> * 2017-02-21 23:55:39,356 - call returned (1, 'ERROR: Invalid version 
> 2.6.0.0-517\n\nValid choices:')
> * Traceback (most recent call last):
> *   File "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_set_all.py", 
> line 189, in 
> * UpgradeSetAll().execute()
> *   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 313, in execute
> * method(env)
> *   File "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_set_all.py", 
> line 65, in actionexecute
> * raise Exception("Command '{0}' exit code is 

  1   2   3   >