[jira] [Commented] (AMBARI-20368) HBase-client install fails when HDFS has not been installed

[zhangxiaolu (JIRA)]

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

zhangxiaolu commented on AMBARI-20368:
--

I run the test_hbase_master.py,and it's ok.

> HBase-client install fails when HDFS has not been installed
> ---
>
> Key: AMBARI-20368
> URL: https://issues.apache.org/jira/browse/AMBARI-20368
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: trunk, 2.4.0, 2.4.1, 2.5.0, 2.4.2
>Reporter: zhangxiaolu
>Assignee: zhangxiaolu
> Fix For: trunk
>
> Attachments: AMBARI-20368.patch, screenshot-1.png, screenshot-2.png
>
>
> the problem is that the installing of hbase-client is before hdfs-client, and 
> the hdfs-client installed failed because the hadoop-conf-dir didn't exist.
> so there are two ways to solve this problem.
> the first method is that create the hadoop-conf-dir in hbase.py
> the second method is that setting the orders in role_command_order.json.
> I think that we can take the first method.



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

[jira] [Updated] (AMBARI-20368) HBase-client install fails when HDFS has not been installed

[zhangxiaolu (JIRA)]

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

zhangxiaolu updated AMBARI-20368:
-
Attachment: screenshot-2.png

> HBase-client install fails when HDFS has not been installed
> ---
>
> Key: AMBARI-20368
> URL: https://issues.apache.org/jira/browse/AMBARI-20368
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: trunk, 2.4.0, 2.4.1, 2.5.0, 2.4.2
>Reporter: zhangxiaolu
>Assignee: zhangxiaolu
> Fix For: trunk
>
> Attachments: AMBARI-20368.patch, screenshot-1.png, screenshot-2.png
>
>
> the problem is that the installing of hbase-client is before hdfs-client, and 
> the hdfs-client installed failed because the hadoop-conf-dir didn't exist.
> so there are two ways to solve this problem.
> the first method is that create the hadoop-conf-dir in hbase.py
> the second method is that setting the orders in role_command_order.json.
> I think that we can take the first method.



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

[jira] [Commented] (AMBARI-20438) Duplicate only global notifications of origin alert group when duplicating alert group

[wangjianfei (JIRA)]

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

wangjianfei commented on AMBARI-20438:
--

[~jaimin]
{noformat}
  jaimin,
Hi,could you please help review the code on my review board? I'm not sure 
if this is a bug or it's originally designed as this.Thank you in advance.
{noformat}

> Duplicate only global notifications of origin alert group when duplicating 
> alert group
> --
>
> Key: AMBARI-20438
> URL: https://issues.apache.org/jira/browse/AMBARI-20438
> Project: Ambari
>  Issue Type: Bug
>Reporter: wangjianfei
> Fix For: trunk
>
> Attachments: AMBARI-20438.patch
>
>
> Problem:
> 　　When you duplicate alert group in the dialog of Manage Alert Groups,the new 
> copied alert group just shows the global notifications rather than all 
> notifications of the origin alert group.



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

[jira] [Commented] (AMBARI-20490) Fixes for Express Upgrade on large-scale clusters: batch execute-stage for hdp-select set all, alert for hdp-select versions, EU from HDP 2.2 to 2.5

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-20490:


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

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

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

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

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

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

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

This message is automatically generated.

> Fixes for Express Upgrade on large-scale clusters: batch execute-stage for 
> hdp-select set all, alert for hdp-select versions, EU from HDP 2.2 to 2.5
> 
>
> Key: AMBARI-20490
> URL: https://issues.apache.org/jira/browse/AMBARI-20490
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-20490.branch-2.4.patch, 
> AMBARI-20490.branch-2.5.patch, AMBARI-20490.trunk.patch
>
>
> On large-scale clusters over 1000 nodes, performance during Express Upgrade 
> can be very slow and it takes more time to fix potential errors.
> We can remedy these with the following fixes:
> * "hdp-select set all" is currently ran in the ClusterGroup with a single 
> stage instead of batching. This can cause Ambari Server to be the bottleneck 
> when processing 1000+ requests. Allow the execute-stage inside a ClusterGroup 
> to use batching.
> * If some hosts have symlinks or dirs that don't belong in /usr/hdp/ then it 
> will prevent the hosts from running "hdp-select versions". We can find these 
> problematic hosts with an alert.
> * There is currently no upgrade path from HDP 2.2 directly to 2.5. Doing a 
> 2-step upgrade is very time consuming (only for branch 2.4 since HDP 2.2 no 
> longer supported in Ambari 2.5).



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

[jira] [Updated] (AMBARI-20513) Storm alerts appear after disabling security [upgrade]

[Sviatoslav Tereshchenko (JIRA)]

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

Sviatoslav Tereshchenko updated AMBARI-20513:
-
Labels: upgrade  (was: )

> Storm alerts appear after disabling security [upgrade]
> --
>
> Key: AMBARI-20513
> URL: https://issues.apache.org/jira/browse/AMBARI-20513
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
> Environment: Centos 6,  ambari only upgrade 
>Reporter: Sviatoslav Tereshchenko
>  Labels: upgrade
> Fix For: 2.5.0
>
>
> 1)Deploy old version Cluster (with AD Security) 
> 2)Make ambari only upgrade
> 3) disable security
> 4) enable security (AD)
> 5) disable security
> *Actual result:* Storm alerts appear after disabling security



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

[jira] [Updated] (AMBARI-20514) Start services were aborted when try to disable/enable security after upgrade

[Sviatoslav Tereshchenko (JIRA)]

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

Sviatoslav Tereshchenko updated AMBARI-20514:
-
Labels: upgrade  (was: )

> Start services were aborted when try to disable/enable security after upgrade 
> --
>
> Key: AMBARI-20514
> URL: https://issues.apache.org/jira/browse/AMBARI-20514
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
> Environment: Centos 6, ambari only upgrade
>Reporter: Sviatoslav Tereshchenko
>  Labels: upgrade
> Fix For: 2.5.0
>
>
> 1)Deploy Cluster (with AD Security)
> 2)Make ambari only upgrade
> 3) disable security
> 4) enable security (AD)
> 5) disable security
> *Actual result:* Start services were aborted when try to disable/enable 
> security after upgrade



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

[jira] [Created] (AMBARI-20514) Start services were aborted when try to disable/enable security after upgrade

[Sviatoslav Tereshchenko (JIRA)]

Sviatoslav Tereshchenko created AMBARI-20514:


 Summary: Start services were aborted when try to disable/enable 
security after upgrade 
 Key: AMBARI-20514
 URL: https://issues.apache.org/jira/browse/AMBARI-20514
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.5.0
 Environment: Centos 6, ambari only upgrade
Reporter: Sviatoslav Tereshchenko
 Fix For: 2.5.0


1)Deploy Cluster (with AD Security)
2)Make ambari only upgrade
3) disable security
4) enable security (AD)
5) disable security

*Actual result:* Start services were aborted when try to disable/enable 
security after upgrade



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

[jira] [Updated] (AMBARI-20513) Storm alerts appear after disabling security [upgrade]

[Sviatoslav Tereshchenko (JIRA)]

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

Sviatoslav Tereshchenko updated AMBARI-20513:
-
Description: 
1)Deploy old version Cluster (with AD Security) 
2)Make ambari only upgrade
3) disable security
4) enable security (AD)
5) disable security

*Actual result:* Storm alerts appear after disabling security

  was:
1)Deploy old version Cluster (with AD Security) 
2)Make ambari only upgrade
3) disable security
4) enable security (AD)
5) disable security

*Actual result:* Storm alerts appear after disabling security*


> Storm alerts appear after disabling security [upgrade]
> --
>
> Key: AMBARI-20513
> URL: https://issues.apache.org/jira/browse/AMBARI-20513
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
> Environment: Centos 6,  ambari only upgrade 
>Reporter: Sviatoslav Tereshchenko
> Fix For: 2.5.0
>
>
> 1)Deploy old version Cluster (with AD Security) 
> 2)Make ambari only upgrade
> 3) disable security
> 4) enable security (AD)
> 5) disable security
> *Actual result:* Storm alerts appear after disabling security



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

[jira] [Created] (AMBARI-20513) Storm alerts appear after disabling security [upgrade]

[Sviatoslav Tereshchenko (JIRA)]

Sviatoslav Tereshchenko created AMBARI-20513:


 Summary: Storm alerts appear after disabling security [upgrade]
 Key: AMBARI-20513
 URL: https://issues.apache.org/jira/browse/AMBARI-20513
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.5.0
 Environment: Centos 6,  ambari only upgrade 
Reporter: Sviatoslav Tereshchenko
 Fix For: 2.5.0


1)Deploy old version Cluster (with AD Security) 
2)Make ambari only upgrade
3) disable security
4) enable security (AD)
5) disable security

*Actual result:* Storm alerts appear after disabling security*



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

[jira] [Commented] (AMBARI-20510) Oozie Database URL property was changed by itself

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20510:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7094 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7094/])
AMBARI-20510. Oozie Database URL property was changed by itself (hiveww: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a13e96e755f5daf692375b15bd32767eda987b6d])
* (add) ambari-web/test/mixins/common/loading_overlay_support_test.js
* (edit) ambari-web/app/controllers/main/service/info/configs.js
* (edit) ambari-web/app/styles/application.less
* (edit) ambari-web/app/mixins.js
* (edit) ambari-web/app/templates/common/configs/service_config_layout_tab.hbs
* (edit) ambari-web/app/styles/config_history_flow.less
* (edit) ambari-web/app/views/common/configs/service_config_layout_tab_view.js
* (edit) ambari-web/app/views/common/configs/config_category_container_view.js
* (add) ambari-web/app/mixins/common/loading_overlay_support.js
* (edit) ambari-web/app/assets/test/tests.js


> Oozie Database URL property was changed by itself
> -
>
> Key: AMBARI-20510
> URL: https://issues.apache.org/jira/browse/AMBARI-20510
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-20510.patch
>
>
> After investigation, I figured out, that in our tests when we trying to setup 
> config on Oozie tab application replaces the correct Oozie DB URL with the 
> wrong one.
> You can see this on video 1:07-1:11. 
> Looks like StackAdvisor response received twice.
> When we choose "Existing MySQL/MaridDB Database" Database URL property 
> changed according the value with "Oozie Server host", test changed it as 
> needed (according to pattern)
> OOZIE_DB_URL = "jdbc:mysql://" + 
> AmbariProperties.INSTALL_EXTERNAL_DB_HOST_NAME + "/" + "ooziedb";
> and immediately this property was changed to the old one
> go to HDFS configs
> in chrome dev console select Network, set throttling -> GPRS
> change "NameNode Java heap size"
> go to Advanced (config tab) and change "NameNode new generation size"
> once you will get response for recommendations, value of "NameNode new 
> generation size" will be changed to recommended one
> If you have bad internet connection you can make a stack of recommendation 
> requests, that will hang in pending state, and once resolved will apply 
> recommended values



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

[jira] [Updated] (AMBARI-20498) Ambari logo and title should not get hidden when user scrolls down the page

[Jaimin Jetly (JIRA)]

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

Jaimin Jetly updated AMBARI-20498:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Patch committed to ambari-rest-api-explorer branch

> Ambari logo and title should not get hidden when user scrolls down the page
> ---
>
> Key: AMBARI-20498
> URL: https://issues.apache.org/jira/browse/AMBARI-20498
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20498.patch
>
>
> As of now scrollbar is applied to the entire page.
> Rather iAmbari logo and title "Ambari REST API explorer" div should be 
> static. So when user scrolls down to see APIs, logo and title is still 
> visible on the top of the page



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

[jira] [Updated] (AMBARI-20510) Oozie Database URL property was changed by itself

[Antonenko Alexander (JIRA)]

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

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

committed to trunk

> Oozie Database URL property was changed by itself
> -
>
> Key: AMBARI-20510
> URL: https://issues.apache.org/jira/browse/AMBARI-20510
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-20510.patch
>
>
> After investigation, I figured out, that in our tests when we trying to setup 
> config on Oozie tab application replaces the correct Oozie DB URL with the 
> wrong one.
> You can see this on video 1:07-1:11. 
> Looks like StackAdvisor response received twice.
> When we choose "Existing MySQL/MaridDB Database" Database URL property 
> changed according the value with "Oozie Server host", test changed it as 
> needed (according to pattern)
> OOZIE_DB_URL = "jdbc:mysql://" + 
> AmbariProperties.INSTALL_EXTERNAL_DB_HOST_NAME + "/" + "ooziedb";
> and immediately this property was changed to the old one
> go to HDFS configs
> in chrome dev console select Network, set throttling -> GPRS
> change "NameNode Java heap size"
> go to Advanced (config tab) and change "NameNode new generation size"
> once you will get response for recommendations, value of "NameNode new 
> generation size" will be changed to recommended one
> If you have bad internet connection you can make a stack of recommendation 
> requests, that will hang in pending state, and once resolved will apply 
> recommended values



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

[jira] [Commented] (AMBARI-20498) Ambari logo and title should not get hidden when user scrolls down the page

[Jaimin Jetly (JIRA)]

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

Jaimin Jetly commented on AMBARI-20498:
---

+1 for the patch.

> Ambari logo and title should not get hidden when user scrolls down the page
> ---
>
> Key: AMBARI-20498
> URL: https://issues.apache.org/jira/browse/AMBARI-20498
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20498.patch
>
>
> As of now scrollbar is applied to the entire page.
> Rather iAmbari logo and title "Ambari REST API explorer" div should be 
> static. So when user scrolls down to see APIs, logo and title is still 
> visible on the top of the page



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

[jira] [Updated] (AMBARI-20498) Ambari logo and title should not get hidden when user scrolls down the page

[Jaimin Jetly (JIRA)]

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

Jaimin Jetly updated AMBARI-20498:
--
Status: Patch Available  (was: Open)

> Ambari logo and title should not get hidden when user scrolls down the page
> ---
>
> Key: AMBARI-20498
> URL: https://issues.apache.org/jira/browse/AMBARI-20498
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20498.patch
>
>
> As of now scrollbar is applied to the entire page.
> Rather iAmbari logo and title "Ambari REST API explorer" div should be 
> static. So when user scrolls down to see APIs, logo and title is still 
> visible on the top of the page



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

[jira] [Updated] (AMBARI-20490) Fixes for Express Upgrade on large-scale clusters: batch execute-stage for hdp-select set all, alert for hdp-select versions, EU from HDP 2.2 to 2.5

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-20490:
-
Status: Patch Available  (was: Open)

> Fixes for Express Upgrade on large-scale clusters: batch execute-stage for 
> hdp-select set all, alert for hdp-select versions, EU from HDP 2.2 to 2.5
> 
>
> Key: AMBARI-20490
> URL: https://issues.apache.org/jira/browse/AMBARI-20490
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-20490.branch-2.4.patch, 
> AMBARI-20490.branch-2.5.patch, AMBARI-20490.trunk.patch
>
>
> On large-scale clusters over 1000 nodes, performance during Express Upgrade 
> can be very slow and it takes more time to fix potential errors.
> We can remedy these with the following fixes:
> * "hdp-select set all" is currently ran in the ClusterGroup with a single 
> stage instead of batching. This can cause Ambari Server to be the bottleneck 
> when processing 1000+ requests. Allow the execute-stage inside a ClusterGroup 
> to use batching.
> * If some hosts have symlinks or dirs that don't belong in /usr/hdp/ then it 
> will prevent the hosts from running "hdp-select versions". We can find these 
> problematic hosts with an alert.
> * There is currently no upgrade path from HDP 2.2 directly to 2.5. Doing a 
> 2-step upgrade is very time consuming (only for branch 2.4 since HDP 2.2 no 
> longer supported in Ambari 2.5).



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

[jira] [Updated] (AMBARI-20490) Fixes for Express Upgrade on large-scale clusters: batch execute-stage for hdp-select set all, alert for hdp-select versions, EU from HDP 2.2 to 2.5

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-20490:
-
Attachment: AMBARI-20490.trunk.patch

> Fixes for Express Upgrade on large-scale clusters: batch execute-stage for 
> hdp-select set all, alert for hdp-select versions, EU from HDP 2.2 to 2.5
> 
>
> Key: AMBARI-20490
> URL: https://issues.apache.org/jira/browse/AMBARI-20490
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-20490.branch-2.4.patch, 
> AMBARI-20490.branch-2.5.patch, AMBARI-20490.trunk.patch
>
>
> On large-scale clusters over 1000 nodes, performance during Express Upgrade 
> can be very slow and it takes more time to fix potential errors.
> We can remedy these with the following fixes:
> * "hdp-select set all" is currently ran in the ClusterGroup with a single 
> stage instead of batching. This can cause Ambari Server to be the bottleneck 
> when processing 1000+ requests. Allow the execute-stage inside a ClusterGroup 
> to use batching.
> * If some hosts have symlinks or dirs that don't belong in /usr/hdp/ then it 
> will prevent the hosts from running "hdp-select versions". We can find these 
> problematic hosts with an alert.
> * There is currently no upgrade path from HDP 2.2 directly to 2.5. Doing a 
> 2-step upgrade is very time consuming (only for branch 2.4 since HDP 2.2 no 
> longer supported in Ambari 2.5).



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

[jira] [Commented] (AMBARI-20495) Ambari REST API explorer should show ambari logo

[Jaimin Jetly (JIRA)]

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

Jaimin Jetly commented on AMBARI-20495:
---

+1 for the patch

> Ambari REST API explorer should show ambari logo
> 
>
> Key: AMBARI-20495
> URL: https://issues.apache.org/jira/browse/AMBARI-20495
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20495.patch
>
>
> clicking on the logo should route to ambari



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

[jira] [Updated] (AMBARI-20490) Fixes for Express Upgrade on large-scale clusters: batch execute-stage for hdp-select set all, alert for hdp-select versions, EU from HDP 2.2 to 2.5

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-20490:
-
Attachment: (was: AMBARI-20490.trunk.patch)

> Fixes for Express Upgrade on large-scale clusters: batch execute-stage for 
> hdp-select set all, alert for hdp-select versions, EU from HDP 2.2 to 2.5
> 
>
> Key: AMBARI-20490
> URL: https://issues.apache.org/jira/browse/AMBARI-20490
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-20490.branch-2.4.patch, 
> AMBARI-20490.branch-2.5.patch
>
>
> On large-scale clusters over 1000 nodes, performance during Express Upgrade 
> can be very slow and it takes more time to fix potential errors.
> We can remedy these with the following fixes:
> * "hdp-select set all" is currently ran in the ClusterGroup with a single 
> stage instead of batching. This can cause Ambari Server to be the bottleneck 
> when processing 1000+ requests. Allow the execute-stage inside a ClusterGroup 
> to use batching.
> * If some hosts have symlinks or dirs that don't belong in /usr/hdp/ then it 
> will prevent the hosts from running "hdp-select versions". We can find these 
> problematic hosts with an alert.
> * There is currently no upgrade path from HDP 2.2 directly to 2.5. Doing a 
> 2-step upgrade is very time consuming (only for branch 2.4 since HDP 2.2 no 
> longer supported in Ambari 2.5).



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

[jira] [Updated] (AMBARI-20495) Ambari REST API explorer should show ambari logo

[Jaimin Jetly (JIRA)]

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

Jaimin Jetly updated AMBARI-20495:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Patch committed to ambari-rest-api-explorer branch

> Ambari REST API explorer should show ambari logo
> 
>
> Key: AMBARI-20495
> URL: https://issues.apache.org/jira/browse/AMBARI-20495
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20495.patch
>
>
> clicking on the logo should route to ambari



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

[jira] [Updated] (AMBARI-20490) Fixes for Express Upgrade on large-scale clusters: batch execute-stage for hdp-select set all, alert for hdp-select versions, EU from HDP 2.2 to 2.5

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-20490:
-
Status: Open  (was: Patch Available)

> Fixes for Express Upgrade on large-scale clusters: batch execute-stage for 
> hdp-select set all, alert for hdp-select versions, EU from HDP 2.2 to 2.5
> 
>
> Key: AMBARI-20490
> URL: https://issues.apache.org/jira/browse/AMBARI-20490
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-20490.branch-2.4.patch, 
> AMBARI-20490.branch-2.5.patch
>
>
> On large-scale clusters over 1000 nodes, performance during Express Upgrade 
> can be very slow and it takes more time to fix potential errors.
> We can remedy these with the following fixes:
> * "hdp-select set all" is currently ran in the ClusterGroup with a single 
> stage instead of batching. This can cause Ambari Server to be the bottleneck 
> when processing 1000+ requests. Allow the execute-stage inside a ClusterGroup 
> to use batching.
> * If some hosts have symlinks or dirs that don't belong in /usr/hdp/ then it 
> will prevent the hosts from running "hdp-select versions". We can find these 
> problematic hosts with an alert.
> * There is currently no upgrade path from HDP 2.2 directly to 2.5. Doing a 
> 2-step upgrade is very time consuming (only for branch 2.4 since HDP 2.2 no 
> longer supported in Ambari 2.5).



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

[jira] [Updated] (AMBARI-20495) Ambari REST API explorer should show ambari logo

[Jaimin Jetly (JIRA)]

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

Jaimin Jetly updated AMBARI-20495:
--
Status: Patch Available  (was: Open)

> Ambari REST API explorer should show ambari logo
> 
>
> Key: AMBARI-20495
> URL: https://issues.apache.org/jira/browse/AMBARI-20495
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20495.patch
>
>
> clicking on the logo should route to ambari



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

[jira] [Commented] (AMBARI-20490) Fixes for Express Upgrade on large-scale clusters: batch execute-stage for hdp-select set all, alert for hdp-select versions, EU from HDP 2.2 to 2.5

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-20490:


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

This message is automatically generated.

> Fixes for Express Upgrade on large-scale clusters: batch execute-stage for 
> hdp-select set all, alert for hdp-select versions, EU from HDP 2.2 to 2.5
> 
>
> Key: AMBARI-20490
> URL: https://issues.apache.org/jira/browse/AMBARI-20490
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-20490.branch-2.4.patch, 
> AMBARI-20490.branch-2.5.patch, AMBARI-20490.trunk.patch
>
>
> On large-scale clusters over 1000 nodes, performance during Express Upgrade 
> can be very slow and it takes more time to fix potential errors.
> We can remedy these with the following fixes:
> * "hdp-select set all" is currently ran in the ClusterGroup with a single 
> stage instead of batching. This can cause Ambari Server to be the bottleneck 
> when processing 1000+ requests. Allow the execute-stage inside a ClusterGroup 
> to use batching.
> * If some hosts have symlinks or dirs that don't belong in /usr/hdp/ then it 
> will prevent the hosts from running "hdp-select versions". We can find these 
> problematic hosts with an alert.
> * There is currently no upgrade path from HDP 2.2 directly to 2.5. Doing a 
> 2-step upgrade is very time consuming (only for branch 2.4 since HDP 2.2 no 
> longer supported in Ambari 2.5).



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

[jira] [Commented] (AMBARI-20511) YARN Service Check failing due to incorrect jar name, Slider failing due to storm plugin conf not present at the moment

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20511:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7093 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7093/])
AMBARI-20511. YARN Service Check failing due to incorrect jar name, 
(afernandez: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4d0a5cf6591e5990183d9860a648267d84e87005])
* (edit) 
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/package/scripts/params_linux.py
* (edit) 
ambari-server/src/main/resources/common-services/SLIDER/0.91.0.3.0/package/scripts/slider.py


> YARN Service Check failing due to incorrect jar name, Slider failing due to 
> storm plugin conf not present at the moment
> ---
>
> Key: AMBARI-20511
> URL: https://issues.apache.org/jira/browse/AMBARI-20511
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-20511.patch
>
>
> YARN service check is failing on HDP 3.0 since Ambari is still looking for a 
> 2.* jar instead of 3.*
> {noformat}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/mapred_service_check.py",
>  line 172, in 
> MapReduce2ServiceCheck().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 314, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/mapred_service_check.py",
>  line 158, in service_check
> logoutput=True)
>   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/execute_hadoop.py",
>  line 44, in action_run
> environment = self.resource.environment,
>   File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
> line 155, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 160, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 124, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 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 'hadoop 
> --config /usr/hdp/current/hadoop-client/conf jar 
> /usr/hdp/current/hadoop-mapreduce-client/hadoop-mapreduce-examples-2.*.jar 
> wordcount /user/ambari-qa/mapredsmokeinput /user/ambari-qa/mapredsmokeoutput' 
> returned 255. JAR does not exist or is not a normal file: 
> /usr/hdp/3.0.0.0-154/hadoop-mapreduce/hadoop-mapreduce-examples-2.*.jar
> {noformat}
> Slider is failing because it currently does not have the Storm plugin, which 
> is expected this early in the release, so comment it out for now.
> {noformat}
> Traceback (most recent call last):
>   File "/usr/lib/python2.6/site-packages/resource_management/core/sudo.py", 
> line 72, in makedirs
> os.makedirs(path, mode)
>   File "/usr/lib64/python2.6/os.py", line 157, in makedirs
> mkdir(name, mode)
> OSError: [Errno 2] No such file or directory: 
> '/usr/hdp/current/storm-slider-client/conf'
> The above exception was the cause of the following exception:
> Traceback (most recent call last):
>   File 
> 

[jira] [Commented] (AMBARI-20512) While generating hash for ambari-server to fill agent cache, all the symlinks should be traversed too.

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-20512:


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

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

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

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

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

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

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

This message is automatically generated.

> While generating hash for ambari-server to fill agent cache, all the symlinks 
> should be traversed too.
> --
>
> Key: AMBARI-20512
> URL: https://issues.apache.org/jira/browse/AMBARI-20512
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
> Fix For: 2.5.0
>
> Attachments: AMBARI-20512.patch
>
>
> the archive.zip and .hash is not getting generated on the server side when 
> the package folder is under
> stacks///services//package
> instead of common-services///package
> On closer look, the issue was that when the directories are being traversed 
> to look for hooks and package folders that need to be hashed/archived for 
> having it in the agent cache, those directories that were symlinks were being 
> skipped.
> Fix is to include them.



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

[jira] [Commented] (AMBARI-19429) Create an ODPi stack definition

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19429:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12859659/hive.py
  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/11093//console

This message is automatically generated.

> Create an ODPi stack definition
> ---
>
> Key: AMBARI-19429
> URL: https://issues.apache.org/jira/browse/AMBARI-19429
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: 2.4.2
>Reporter: Roman Shaposhnik
>Assignee: Roman Shaposhnik
> Fix For: trunk
>
> Attachments: AMBARI-19429-mpack_trunk.patch, 
> AMBARI-19429_mpack_trunk_v2.patch, AMBARI-19429.patch2.gz, 
> AMBARI-19429.patch.gz, AMBARI-19429_trunk.patch, AMBARI-20512_trunk.patch, 
> ambari-agent.log, hive.py
>
>
> ODPi is a nonprofit organization committed to simplification & 
> standardization of the big data ecosystem with common reference 
> specifications and test suites. As part of its mission, ODPi has been 
> developing a series of specifications for how to integrate upstream Apache 
> projects into the coherent platform. Part of this standardization effort is 
> maintenance of the ODPi core stack definition which today includes:
>* Apache Zookeeper
>* Apache Hadoop
>* Apache Hive
> and has been maintained as a custom stack on ODPi side:
> 
> https://github.com/odpi/bigtop/tree/odpi-master/bigtop-packages/src/common/ambari/ODPi/1.0
> In conjunction with merge effort for Apache Bigtop BIGTOP-2666 I'd like to 
> propose that instead of migrating the stack definition to Bigtop, we should 
> actually migrate it to Ambari.



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

[jira] [Updated] (AMBARI-20511) YARN Service Check failing due to incorrect jar name, Slider failing due to storm plugin conf not present at the moment

[Alejandro Fernandez (JIRA)]

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

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

Pushed to trunk, commit 4d0a5cf6591e5990183d9860a648267d84e87005

> YARN Service Check failing due to incorrect jar name, Slider failing due to 
> storm plugin conf not present at the moment
> ---
>
> Key: AMBARI-20511
> URL: https://issues.apache.org/jira/browse/AMBARI-20511
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-20511.patch
>
>
> YARN service check is failing on HDP 3.0 since Ambari is still looking for a 
> 2.* jar instead of 3.*
> {noformat}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/mapred_service_check.py",
>  line 172, in 
> MapReduce2ServiceCheck().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 314, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/mapred_service_check.py",
>  line 158, in service_check
> logoutput=True)
>   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/execute_hadoop.py",
>  line 44, in action_run
> environment = self.resource.environment,
>   File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
> line 155, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 160, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 124, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 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 'hadoop 
> --config /usr/hdp/current/hadoop-client/conf jar 
> /usr/hdp/current/hadoop-mapreduce-client/hadoop-mapreduce-examples-2.*.jar 
> wordcount /user/ambari-qa/mapredsmokeinput /user/ambari-qa/mapredsmokeoutput' 
> returned 255. JAR does not exist or is not a normal file: 
> /usr/hdp/3.0.0.0-154/hadoop-mapreduce/hadoop-mapreduce-examples-2.*.jar
> {noformat}
> Slider is failing because it currently does not have the Storm plugin, which 
> is expected this early in the release, so comment it out for now.
> {noformat}
> Traceback (most recent call last):
>   File "/usr/lib/python2.6/site-packages/resource_management/core/sudo.py", 
> line 72, in makedirs
> os.makedirs(path, mode)
>   File "/usr/lib64/python2.6/os.py", line 157, in makedirs
> mkdir(name, mode)
> OSError: [Errno 2] No such file or directory: 
> '/usr/hdp/current/storm-slider-client/conf'
> The above exception was the cause of the following exception:
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/SLIDER/0.91.0.3.0/package/scripts/slider_client.py",
>  line 71, in 
> SliderClient().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 314, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/SLIDER/0.91.0.3.0/package/scripts/slider_client.py",
>  line 55, in install
> self.configure(env)
>   File 
> 

[jira] [Resolved] (AMBARI-20486) Service check Hive failed with "unknown queue: hive"

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan resolved AMBARI-20486.

Resolution: Not A Problem

> Service check Hive failed with "unknown queue: hive"
> 
>
> Key: AMBARI-20486
> URL: https://issues.apache.org/jira/browse/AMBARI-20486
> Project: Ambari
>  Issue Type: Test
>  Components: ambari-admin
> Environment: ambari-server version: ambari-server-2.5.0.1-71.x86_64
> ambari-server --hash: c5f277b5299374a1db8bc215c2c3c78209786fa3
> HDP Stack: 2.3
> HDP Version: 2.3.6.0-3796
> 2.6.0.2-32
> Ambari DB: :MariaDB
> Oozie/Hive DB: MariaDB/MariaDB
> Security:yes
>Reporter: Denis Tarasyuk
>Priority: Blocker
>  Labels: system_test
> Fix For: 2.5.0
>
>
> STR:
> Deploy cluster HDP 2.3.6.0
> Enable NN HA
> Register and install HDP 2.6.0.2-32
> Perform RU
> Result: Service check Hive failed during RU



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

[jira] [Updated] (AMBARI-20486) Service check Hive failed with "unknown queue: hive"

[Denis Tarasyuk (JIRA)]

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

Denis Tarasyuk updated AMBARI-20486:

Issue Type: Test  (was: Bug)

> Service check Hive failed with "unknown queue: hive"
> 
>
> Key: AMBARI-20486
> URL: https://issues.apache.org/jira/browse/AMBARI-20486
> Project: Ambari
>  Issue Type: Test
>  Components: ambari-admin
> Environment: ambari-server version: ambari-server-2.5.0.1-71.x86_64
> ambari-server --hash: c5f277b5299374a1db8bc215c2c3c78209786fa3
> HDP Stack: 2.3
> HDP Version: 2.3.6.0-3796
> 2.6.0.2-32
> Ambari DB: :MariaDB
> Oozie/Hive DB: MariaDB/MariaDB
> Security:yes
>Reporter: Denis Tarasyuk
>Priority: Blocker
>  Labels: system_test
> Fix For: 2.5.0
>
>
> STR:
> Deploy cluster HDP 2.3.6.0
> Enable NN HA
> Register and install HDP 2.6.0.2-32
> Perform RU
> Result: Service check Hive failed during RU



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

[jira] [Assigned] (AMBARI-18212) Log entry missing in the preview log modal window

[Yusaku Sako (JIRA)]

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

Yusaku Sako reassigned AMBARI-18212:


Assignee: Dharmesh Makwana  (was: Yusaku Sako)

> Log entry missing in the preview log modal window
> -
>
> Key: AMBARI-18212
> URL: https://issues.apache.org/jira/browse/AMBARI-18212
> Project: Ambari
>  Issue Type: Bug
>  Components: logsearch
>Affects Versions: 2.4.0
>Reporter: Kishor Ramakrishnan
>Assignee: Dharmesh Makwana
> Fix For: 2.5.0
>
> Attachments: AMBARI-18212.patch
>
>




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

[jira] [Updated] (AMBARI-19429) Create an ODPi stack definition

[Madhuvanthi Radhakrishnan (JIRA)]

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

Madhuvanthi Radhakrishnan updated AMBARI-19429:
---
Attachment: hive.py

> Create an ODPi stack definition
> ---
>
> Key: AMBARI-19429
> URL: https://issues.apache.org/jira/browse/AMBARI-19429
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: 2.4.2
>Reporter: Roman Shaposhnik
>Assignee: Roman Shaposhnik
> Fix For: trunk
>
> Attachments: AMBARI-19429-mpack_trunk.patch, 
> AMBARI-19429_mpack_trunk_v2.patch, AMBARI-19429.patch2.gz, 
> AMBARI-19429.patch.gz, AMBARI-19429_trunk.patch, AMBARI-20512_trunk.patch, 
> ambari-agent.log, hive.py
>
>
> ODPi is a nonprofit organization committed to simplification & 
> standardization of the big data ecosystem with common reference 
> specifications and test suites. As part of its mission, ODPi has been 
> developing a series of specifications for how to integrate upstream Apache 
> projects into the coherent platform. Part of this standardization effort is 
> maintenance of the ODPi core stack definition which today includes:
>* Apache Zookeeper
>* Apache Hadoop
>* Apache Hive
> and has been maintained as a custom stack on ODPi side:
> 
> https://github.com/odpi/bigtop/tree/odpi-master/bigtop-packages/src/common/ambari/ODPi/1.0
> In conjunction with merge effort for Apache Bigtop BIGTOP-2666 I'd like to 
> propose that instead of migrating the stack definition to Bigtop, we should 
> actually migrate it to Ambari.



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

[jira] [Commented] (AMBARI-18650) Ambari should be able to manage passwords using a credential store

[Jonathan Maron (JIRA)]

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

Jonathan Maron commented on AMBARI-18650:
-

Thanks @sumitmohanty. When was that API introduced?  2.5?

> Ambari should be able to manage passwords using a credential store
> --
>
> Key: AMBARI-18650
> URL: https://issues.apache.org/jira/browse/AMBARI-18650
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Sumit Mohanty
> Fix For: 2.5.0
>
> Attachments: AmbariSupportforCredentialStore.pdf
>
>
> With Credential API many Hadoop components allow referring to password that 
> are encrypted and stored in a credential store.
> Example: SSL Passwords for HBase, Oozie, etc
> Ambari should support the use of hadoop credential store to manage such 
> passwords.



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

[jira] [Updated] (AMBARI-20133) Changes/Overwrites to Bundles and Coordinators Show as Workflow, Not able to select text from worflow 'Definition' tab

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-20133:
-
Reporter: Vivek Sharma  (was: venkat)

> Changes/Overwrites to Bundles and Coordinators Show as Workflow, Not able to 
> select text from worflow 'Definition' tab
> --
>
> Key: AMBARI-20133
> URL: https://issues.apache.org/jira/browse/AMBARI-20133
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Vivek Sharma
>Assignee: venkat
> Fix For: 2.5.0
>
> Attachments: AMBARI-20133.branch-2.5.patch
>
>
> When saving and/or overwriting coordinator or bundle files, UI appears to 
> have a typo. States that "Workflow" has been saved instead.
> Not able to select text from workflow 'Definition' tab.
> Dashboard - Select Workflow - Definition Tab - try selecting text. (browser: 
> chrome)



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

[jira] [Updated] (AMBARI-18212) Log entry missing in the preview log modal window

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-18212:
-
Reporter: Kishor Ramakrishnan  (was: Dharmesh Makwana)

> Log entry missing in the preview log modal window
> -
>
> Key: AMBARI-18212
> URL: https://issues.apache.org/jira/browse/AMBARI-18212
> Project: Ambari
>  Issue Type: Bug
>  Components: logsearch
>Affects Versions: 2.4.0
>Reporter: Kishor Ramakrishnan
>Assignee: Yusaku Sako
> Fix For: 2.5.0
>
> Attachments: AMBARI-18212.patch
>
>




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

[jira] [Updated] (AMBARI-19054) Grafana failed to start at deployment

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19054:
-
Reporter: Vivek Rathod  (was: Aravindan Vijayan)

> Grafana failed to start at deployment
> -
>
> Key: AMBARI-19054
> URL: https://issues.apache.org/jira/browse/AMBARI-19054
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19054.patch
>
>
> Grafana failed to start at deployment. No retries were given, but the live 
> cluster shows it is up
> {noformat}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
>  line 77, in 
> AmsGrafana().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 282, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
>  line 49, in start
> not_if = params.grafana_process_exists_cmd,
>   File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
> line 155, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 160, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 124, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 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 
> '/usr/sbin/ambari-metrics-grafana start' returned 1.  Hortonworks 
> #
> This is MOTD message, added for testing in qe infra
> {noformat}



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

[jira] [Updated] (AMBARI-19795) Ambari upgrade to not add ranger plugin configs under ranger plugin supported services

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19795:
-
Reporter: Sviatoslav Tereshchenko  (was: Mugdha Varadkar)

> Ambari upgrade to not add ranger plugin configs under ranger plugin supported 
> services
> --
>
> Key: AMBARI-19795
> URL: https://issues.apache.org/jira/browse/AMBARI-19795
> Project: Ambari
>  Issue Type: Bug
>Reporter: Sviatoslav Tereshchenko
>Assignee: Mugdha Varadkar
>Priority: Critical
> Attachments: AMBARI-19795.1.patch, AMBARI-19795.patch, 
> AMBARI-19795-trunk.1.patch
>
>
> Need to revert the changes done as a part of AMBARI-19044 for adding ranger 
> plugin configs during ambari upgrade.
> Need to add properties introduced for support cloud under stack 2.6 only.



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

[jira] [Updated] (AMBARI-19175) DB configs consistency check failed after disable kerberos or Ambari upgrade

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19175:
-
Reporter: Andrew Khalymon  (was: Dmitry Lysnichenko)

> DB configs consistency check failed after disable kerberos or Ambari upgrade
> 
>
> Key: AMBARI-19175
> URL: https://issues.apache.org/jira/browse/AMBARI-19175
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Andrew Khalymon
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.5.0
>
>
> DB configs consistency check failed after disable kerberos.
> Services start successful and service check passed.
> {noformat}Checking database
> DB configs consistency check failed. Run "ambari-server start 
> --skip-database-check" to skip.
> You may try --auto-fix-database flag to attempt to fix issues automatically.
> If you use this "--skip-database-check" option, do not make any changes to 
> your cluster topology or perform a cluster upgrade until you correct the 
> database consistency issues.
> See "/var/log/ambari-server/ambari-server-check-database.log" for more 
> details on the consistency issues.
> Ambari Server 'check-database' completed{noformat}
> =
> Also seen after Ambari upgrade. Below entry in 
> ambari-server-check-database.log might be the issue:
> {code}
> 2016-12-12 15:49:03,973 ERROR - Found configs that are not mapped to any 
> service!
> {code}



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

[jira] [Updated] (AMBARI-19456) RU: Falcon LR job failed (upgrade-downgrade)

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19456:
-
Reporter: Denis Tarasyuk  (was: Dmytro Grinenko)

> RU: Falcon LR job failed (upgrade-downgrade)
> 
>
> Key: AMBARI-19456
> URL: https://issues.apache.org/jira/browse/AMBARI-19456
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Denis Tarasyuk
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19456.patch
>
>
> {code}
> 2016-12-19 06:20:52,811|INFO|MainThread|machine.py:139 - run()|ERROR: Unable 
> to initialize Falcon Client object
> 2016-12-19 06:20:52,866|INFO|MainThread|ruUpgrade.py:67 - 
> reportProgress()|[FAILED][Falcon] Warning (ignoreError=True): Non-zero exit 
> code when running command admin -version as user falcon 
> {code}



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

[jira] [Updated] (AMBARI-19196) BG operations modal windows are too small to show the content (in certain scenarios) [Chrome]

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19196:
-
Reporter: Kishor Ramakrishnan  (was: Oleg Nechiporenko)

> BG operations modal windows are too small to show the content (in certain 
> scenarios) [Chrome]
> -
>
> Key: AMBARI-19196
> URL: https://issues.apache.org/jira/browse/AMBARI-19196
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Kishor Ramakrishnan
>Assignee: Oleg Nechiporenko
> Fix For: 2.5.0
>
> Attachments: AMBARI-19196_branch-2.5.patch, AMBARI-19196.patch
>
>
> 1. Login to Ambari
> 2. Click on BG operations.
> 3. Click on some action link which have relatively lesser content, e.g Hosts, 
> with only one host link.
> 4. Click on the link to get more details
> 5. Intermittently the details window also have the same dimension of the 
> previous window and as a result the user is not able to view the content
> BG operations modal window should be resizable as intermittently modal 
> windows are too small to view the content[Chrome].
> This behavior is observed when we navigate to the granular details and the 
> previous window was smaller size due to lesser content. Please see the 
> screenshots
>  Intermittently the details window also have the same dimension of the 
> previous window and as a result the user is not able to view the content



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

[jira] [Updated] (AMBARI-19197) Kerberos advanced tab. Page wasn't refreshed after save changes. Save button is disabled.

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19197:
-
Reporter: Andrew Khalymon  (was: Denys Buzhor)

> Kerberos advanced tab. Page wasn't refreshed after save changes. Save button 
> is disabled.
> -
>
> Key: AMBARI-19197
> URL: https://issues.apache.org/jira/browse/AMBARI-19197
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrew Khalymon
>Assignee: Denys Buzhor
> Fix For: 2.5.0
>
> Attachments: AMBARI-19197_branch_2.5.patch, AMBARI-19197.patch
>
>
> STR: 
> # change properties on kerb advanced tab
> # save and regenerate keytab
> # wait for complete
> # change properties on kerb advanced tab
> Result: 
> Save button is disabled.



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

[jira] [Updated] (AMBARI-19239) Logs modal window in Host Details> Logs Tab not displayed properly with hidden modal-footer

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19239:
-
Reporter: Kishor Ramakrishnan  (was: Antonenko Alexander)

> Logs modal window in Host Details> Logs Tab not displayed properly with 
> hidden modal-footer
> ---
>
> Key: AMBARI-19239
> URL: https://issues.apache.org/jira/browse/AMBARI-19239
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Kishor Ramakrishnan
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19239.patch
>
>
> Logs modal window in Host Details> Logs Tab not displayed properly with 
> hidden modal-footer.
> Chrome Version : 55.0



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

[jira] [Updated] (AMBARI-19010) Log Search external login credential let every user in

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19010:
-
Reporter: Kishor Ramakrishnan  (was: Olivér Szabó)

> Log Search external login credential let every user in
> --
>
> Key: AMBARI-19010
> URL: https://issues.apache.org/jira/browse/AMBARI-19010
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Kishor Ramakrishnan
>Assignee: Olivér Szabó
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19010.patch
>
>




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

[jira] [Updated] (AMBARI-19341) Not able to update the role for a given user

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19341:
-
Reporter: Supreeth Sharma  (was: Eugene Chekanskiy)

> Not able to update the role for a given user
> 
>
> Key: AMBARI-19341
> URL: https://issues.apache.org/jira/browse/AMBARI-19341
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: Oleg Nechiporenko
> Fix For: 2.5.0
>
> Attachments: AMBARI-19341.patch
>
>
> User is Not able to update the role for a given user.
> Steps to reproduce :
> 1) Go to manage ambari and select roles.
> 2) Select list views.
> 3) Try to update the role for user.
> The request DELET 
> /api/v1/clusters/cl1/privileges?PrivilegeInfo/privilege_id.in(2,12) is 
> failing with internal server error exception.
> From the initial analysis, privilege id 12 is the actual privilege and 2 is 
> the one granted for views user.



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

[jira] [Updated] (AMBARI-18255) Add unique constraint to host_version table

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-18255:
-
Reporter: Dhanya Balasundaran  (was: Nate Cole)

> Add unique constraint to host_version table
> ---
>
> Key: AMBARI-18255
> URL: https://issues.apache.org/jira/browse/AMBARI-18255
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Dhanya Balasundaran
>Assignee: Nate Cole
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18255.patch
>
>
> The software is allowing duplicate records into the {{host_version}} table.  
> This should be constrained in the db.



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

[jira] [Updated] (AMBARI-19304) Host logs should not be visible for cluster user and service operator users

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19304:
-
Reporter: Supreeth Sharma  (was: Antonenko Alexander)

> Host logs should not be visible for cluster user and service operator users
> ---
>
> Key: AMBARI-19304
> URL: https://issues.apache.org/jira/browse/AMBARI-19304
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19304.patch
>
>
> Host logs should not be visible for cluster user and service operator users 
> as they are not authorized to view these logs.
> Steps to reproduce :
> 1) Login as cluster user/ service operator.
> 2) From the background operation, select the host start/restart operation 
> (node manager start).
> 3) In the background operation details tab check that 'Host Logs' link is not 
> available for these two types of users.
> As of now this link is shown to the user. But when user clicks on it, he is 
> shown the blank page.



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

[jira] [Updated] (AMBARI-19291) User should be shown proper error message in file browser page

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19291:
-
Reporter: Supreeth Sharma  (was: M Madhan Mohan Reddy)

> User should be shown proper error message in file browser page
> --
>
> Key: AMBARI-19291
> URL: https://issues.apache.org/jira/browse/AMBARI-19291
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: M Madhan Mohan Reddy
>  Labels: WFD
> Fix For: 2.5.0
>
> Attachments: AMBARI-19291_trunk.patch
>
>
> User should be shown proper error message when user tries to navigate to a 
> hdfs folder and he doesn't have access on that folder.
> Steps to reproduce :
> 1) Try to import workflow from HDFS .
> 2) In the file browser, click on a folder on which user doesn't have 
> permission
> 3) Though api 
> /api/v1/views/Workflow%20Manager/versions/1.0.0/instances/WFD/resources/proxy/fileServices/fileops/listdir?path=%2Ftmp%2Fhive
>  fails with appropriate error, UI keeps on loading.
> UI should handle this error and show appropriate message to the user.



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

[jira] [Updated] (AMBARI-19473) Add Downgrade request validation to avoid accidental double-upgrades

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19473:
-
Reporter: Vivek Sharma  (was: Jonathan Hurley)

> Add Downgrade request validation to avoid accidental double-upgrades
> 
>
> Key: AMBARI-19473
> URL: https://issues.apache.org/jira/browse/AMBARI-19473
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vivek Sharma
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19473.patch
>
>
> There are currently several ways of starting upgrades / downgrades:
> - The use of a directive on the request
> {noformat}
> http://localhost:8080/api/v1/clusters/c1/upgrades?downgrade=true
> {noformat}
> - The POST body JSON
> {noformat}
> {
> "RequestInfo": {
>   "downgrade": "true"
>   },
> "Upgrade":{
>   "from_version": ...
>  }
> }
> {noformat}
> The directive is confusing and can allow multiple downgrades or upgrades to 
> be scheduled concurrently. It should be removed for consistency and the 
> {{Upgrade/direction}} property should replace it.



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

[jira] [Updated] (AMBARI-19032) HDFS Metric alerts turns to UNKNOWN state with error "'NoneType' object has no attribute 'split'"

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19032:
-
Reporter: Kishor Ramakrishnan  (was: Andrew Khalymon)

> HDFS Metric alerts turns to UNKNOWN state with error "'NoneType' object has 
> no attribute 'split'"
> -
>
> Key: AMBARI-19032
> URL: https://issues.apache.org/jira/browse/AMBARI-19032
> Project: Ambari
>  Issue Type: Bug
>  Components: alerts, ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Kishor Ramakrishnan
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19032_1.patch, AMBARI-19032_2.patch, 
> AMBARI-19032_branch2.5_additional.patch
>
>
> HDFS Metric alerts turns to UNKNOWN state with error "'NoneType' object has 
> no attribute 'split'".
> STR:
> Update the alert definition interval to 1 min, and thresholds to have minimum 
> values to trigger the Alert.



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

[jira] [Updated] (AMBARI-19435) NodeManager restart fails during HOU if it is on same host as RM

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19435:
-
Reporter: Vivek Sharma  (was: Jonathan Hurley)

> NodeManager restart fails during HOU if it is on same host as RM
> 
>
> Key: AMBARI-19435
> URL: https://issues.apache.org/jira/browse/AMBARI-19435
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vivek Sharma
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19435.patch
>
>
> *Steps*
> # Deploy HDP-2.5.0.0 cluster with Ambari-2.5.0.0 - 4 node cluster with 
> NodeManager installed on all hosts, NN HA is enabled, RM HA is not enabled
> # Register 2.5.3.0 version and install the bits
> # Start HOU using API and accept manual prompts to sys-prep the hosts. 
> Observe the wizard at restart task of host that runs RM and NM together
> *Result:*
> At the task to Restart Node Manager on the RM host, observed below failure:
> {code}
> 2016-12-20 18:32:39,446 - 
> File['/var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid'] {'action': 
> ['delete'], 'not_if': 'ambari-sudo.sh  -H -E test -f 
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh  -H -E 
> pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid'}
> 2016-12-20 18:32:39,459 - Execute['ulimit -c unlimited; export 
> HADOOP_LIBEXEC_DIR=/usr/hdp/2.5.3.0-37/hadoop/libexec && 
> /usr/hdp/current/hadoop-yarn-nodemanager/sbin/yarn-daemon.sh --config 
> /usr/hdp/2.5.3.0-37/hadoop/conf start nodemanager'] {'not_if': 
> 'ambari-sudo.sh  -H -E test -f 
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh  -H -E 
> pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid', 'user': 'yarn'}
> 2016-12-20 18:32:40,558 - Execute['ambari-sudo.sh  -H -E test -f 
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh  -H -E 
> pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid'] {'not_if': 
> 'ambari-sudo.sh  -H -E test -f 
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh  -H -E 
> pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid', 'tries': 5, 
> 'try_sleep': 1}
> 2016-12-20 18:32:40,576 - Skipping Execute['ambari-sudo.sh  -H -E test -f 
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh  -H -E 
> pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid'] due to not_if
> 2016-12-20 18:32:40,576 - Executing NodeManager Stack Upgrade post-restart
> 2016-12-20 18:32:40,578 - NodeManager executing "yarn node -list 
> -states=RUNNING" to verify the node has rejoined the cluster...
> 2016-12-20 18:32:40,578 - checked_call['yarn node -list -states=RUNNING'] 
> {'user': 'yarn'}
> Command failed after 1 tries
> {code}
> A retry of the failed task is successful. 
> The issue looks due to the fact that RM is still down while we try to start 
> NM on the host. While starting NM, we run below command to verify if NM has 
> come up
> {code}
> yarn node -list -states=RUNNING
> {code}
> The command fails since it tries to connect to RM, resulting in timeout
> As a possible fix, we may need to adjust the order in HOU upgrade pack so as 
> to start RM before NM in such cases.



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

[jira] [Updated] (AMBARI-19252) Incorrect Method types displayed in the description of created Alert notification

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19252:
-
Reporter: Kishor Ramakrishnan  (was: Kishore Rajasekar)

> Incorrect Method types displayed in the description of created Alert 
> notification
> -
>
> Key: AMBARI-19252
> URL: https://issues.apache.org/jira/browse/AMBARI-19252
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Kishor Ramakrishnan
>Assignee: Vivek Ratnavel Subramanian
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19252.v0.branch-2.5.patch, 
> AMBARI-19252.v0.trunk.patch
>
>
> Incorrect Method types displayed in the description of created Alert 
> notification.
> STR:
> 1. Create Alert Notifications with Methods "Custom SNMP" and "SNMP"
> 2. After creation, select the created "Custom SNMP" notification the method 
> type is displayed as "SNMP" in the UI
> 3. Select the created "SNMP" notification the method type is displayed as 
> "AMBARI_SNMP" in the UI



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

[jira] [Updated] (AMBARI-19252) Incorrect Method types displayed in the description of created Alert notification

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19252:
-
Reporter: Kishore Rajasekar  (was: Vivek Ratnavel Subramanian)

> Incorrect Method types displayed in the description of created Alert 
> notification
> -
>
> Key: AMBARI-19252
> URL: https://issues.apache.org/jira/browse/AMBARI-19252
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Kishore Rajasekar
>Assignee: Vivek Ratnavel Subramanian
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19252.v0.branch-2.5.patch, 
> AMBARI-19252.v0.trunk.patch
>
>
> Incorrect Method types displayed in the description of created Alert 
> notification.
> STR:
> 1. Create Alert Notifications with Methods "Custom SNMP" and "SNMP"
> 2. After creation, select the created "Custom SNMP" notification the method 
> type is displayed as "SNMP" in the UI
> 3. Select the created "SNMP" notification the method type is displayed as 
> "AMBARI_SNMP" in the UI



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

[jira] [Updated] (AMBARI-19602) Input logic tags are missing in the coordinator xml

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19602:
-
Reporter: Supreeth Sharma  (was: Padma Priya Nagaraj)

> Input logic tags are missing in the coordinator xml
> ---
>
> Key: AMBARI-19602
> URL: https://issues.apache.org/jira/browse/AMBARI-19602
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: Padma Priya Nagaraj
>  Labels: WFD
> Fix For: 2.5.0
>
> Attachments: AMBARI-19602_trunk.patch, coordinator.xml
>
>
> 'Input-logic' tags are missing in the coordinator xml.
> Steps to reproduce :
> 1) Import the attached xml.
> 2) Preview the xml.
> 3) Check that 'input-logic' tags which are available in original xml are 
> missing in the preview xml.



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

[jira] [Updated] (AMBARI-19284) Zeppelin Notebook start fails after reboot

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19284:
-
Reporter: Pradarttana  (was: Andrew Onischuk)

> Zeppelin Notebook start fails after reboot
> --
>
> Key: AMBARI-19284
> URL: https://issues.apache.org/jira/browse/AMBARI-19284
> Project: Ambari
>  Issue Type: Bug
>Reporter: Pradarttana
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19284.patch
>
>
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py",
>  line 361, in 
> Master().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 287, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py",
>  line 191, in start
> + params.zeppelin_log_file, user=params.zeppelin_user)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 
> 155, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 160, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 124, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 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 
> '/usr/hdp/current/zeppelin-server/bin/zeppelin-daemon.sh restart >> 
> /grid/0/log/zeppelin/zeppelin-setup.log' returned 1.  Hortonworks 
> #
> This is MOTD message, added for testing in qe infra
> mkdir: cannot create directory `/var/run/zeppelin': Permission denied
> /usr/hdp/current/zeppelin-server/bin/zeppelin-daemon.sh: line 192: 
> /var/run/zeppelin/zeppelin-zeppelin-nat-d7-rrws-ambari-autostart-1-5.pid: No 
> such file or directory
> cat: 
> /var/run/zeppelin/zeppelin-zeppelin-nat-d7-rrws-ambari-autostart-1-5.pid: No 
> such file or directory
> 
> Explanation:  
> 1\. /var/run/zeppelin created only during install stage  
> 2\. Reboot pc. So that /var/run is cleaned.  
> 3\. Zeppelin fails to start because /var/run/zeppelin is absent



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

[jira] [Updated] (AMBARI-19711) Unable to register HDP version 2.6.0.0 on cluster with HDP 2.5.3.0

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19711:
-
Reporter: Denis Tarasyuk  (was: Andrii Tkach)

> Unable to register HDP version 2.6.0.0 on cluster with HDP 2.5.3.0
> --
>
> Key: AMBARI-19711
> URL: https://issues.apache.org/jira/browse/AMBARI-19711
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Denis Tarasyuk
>Assignee: Andrii Tkach
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19711.patch
>
>
> STR:
> # Deploy HDP 2.5.3.0-37 on Ambari 2.4.2.0
> # Enable NN HA
> # Enable security
> # Perform ambari upgade to 2.5.0.0-724 
> # Register HDP 2.6.0.p
> Result: Unable to register HDP version 2.6.0.0 on cluster with HDP 2.5.3.0



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

[jira] [Updated] (AMBARI-19560) Timezone for timestamps in Upgrade History not consistent with Background Operations

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19560:
-
Reporter: Vivek Sharma  (was: Oleg Nechiporenko)

> Timezone for timestamps in Upgrade History not consistent with Background 
> Operations  
> -
>
> Key: AMBARI-19560
> URL: https://issues.apache.org/jira/browse/AMBARI-19560
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Sharma
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19560_2.patch, AMBARI-19560_branch-2.5.patch, 
> AMBARI-19560.patch
>
>
> Looks like the timestamp in Upgrade History are shown as per current 
> machine's timezone; while the timestamp entries in Background Operations 
> Window is in GMT
> This causes confusion while trying to correlate events that happen after 
> upgrade, as my machine's timezone is GMT+5.30, so the post upgrade events 
> appear to show up few hours before the upgrade time reported in 'Upgrade 
> History'



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

[jira] [Assigned] (AMBARI-18212) Log entry missing in the preview log modal window

[Yusaku Sako (JIRA)]

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

Yusaku Sako reassigned AMBARI-18212:


Assignee: Yusaku Sako  (was: Dharmesh Makwana)

> Log entry missing in the preview log modal window
> -
>
> Key: AMBARI-18212
> URL: https://issues.apache.org/jira/browse/AMBARI-18212
> Project: Ambari
>  Issue Type: Bug
>  Components: logsearch
>Affects Versions: 2.4.0
>Reporter: Dharmesh Makwana
>Assignee: Yusaku Sako
> Fix For: 2.5.0
>
> Attachments: AMBARI-18212.patch
>
>




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

[jira] [Updated] (AMBARI-20042) HiveView2.0 : For large datasets, query results overlaps

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-20042:
-
Reporter: Anusha Bilgi  (was: DIPAYAN BHOWMICK)

> HiveView2.0 : For large datasets, query results overlaps
> 
>
> Key: AMBARI-20042
> URL: https://issues.apache.org/jira/browse/AMBARI-20042
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Anusha Bilgi
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.5.0
>
> Attachments: AMBARI-20042.branch-2.5.patch
>
>




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

[jira] [Updated] (AMBARI-19168) Pig and Hive UDF migration

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19168:
-
Reporter: Pradarttana  (was: Ishan Bhatt)

> Pig and Hive UDF migration
> --
>
> Key: AMBARI-19168
> URL: https://issues.apache.org/jira/browse/AMBARI-19168
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Pradarttana
>Assignee: Ishan Bhatt
> Fix For: 2.5.0
>
> Attachments: AMBARI-19168.patch
>
>
> Supports udf migration for both Pig and Hive between Hue to Ambari views
> Supports multiple user selection for all type of migrations
> Improvements on some features since the last version



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

[jira] [Updated] (AMBARI-17943) Hive View Upload table does not support line feed and carriage return in field delimiter

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-17943:
-
Reporter: Nitiraj Singh Rathore  (was: Anusha Bilgi)

> Hive View Upload table does not support line feed and carriage return in 
> field delimiter
> 
>
> Key: AMBARI-17943
> URL: https://issues.apache.org/jira/browse/AMBARI-17943
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Nitiraj Singh Rathore
>Assignee: Nitiraj Singh Rathore
> Fix For: 2.5.0
>
> Attachments: AMBARI-17943_branch-2.5_2.patch
>
>
> As row delimiter are set as endline and carriage return so they cannot be set 
> as column delimiter. 
> these options should be removed from dropdown in upload table.



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

[jira] [Updated] (AMBARI-18393) Hive Server Interactive (HSI) fails to start with 'Permission denied' for User Hive, if HSI starts before HS2.

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-18393:
-
Reporter: Sunitha  (was: Swapan Shridhar)

> Hive Server Interactive (HSI) fails to start with 'Permission denied' for 
> User Hive, if HSI starts before HS2.
> --
>
> Key: AMBARI-18393
> URL: https://issues.apache.org/jira/browse/AMBARI-18393
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Sunitha
>Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
> Attachments: AMBARI-18393.patch
>
>
> - Install Cluster using Blueprint including HiveServerInteractive
> - Start services fail at Hive interactive start, with below error:
> {code}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py",
>  line 535, in 
> HiveServerInteractive().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 280, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py",
>  line 115, in start
> self.setup_security()
>   File 
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py",
>  line 335, in setup_security
> Execute(slider_keytab_install_cmd, user=params.hive_user)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
> line 155, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 160, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 124, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 273, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 71, in inner
> result = function(command, **kwargs)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 93, in checked_call
> tries=tries, try_sleep=try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'slider install-keytab 
> --keytab /etc/security/keytabs/hive.llap.zk.sm.keytab --folder hive 
> --overwrite' returned 56. 2016-08-15 23:47:57,518 [main] INFO  
> tools.SliderUtils - JVM initialized into secure mode with kerberos realm 
> HWQE.HORTONWORKS.COM
> 2016-08-15 23:47:59,108 [main] INFO  impl.TimelineClientImpl - Timeline 
> service address: 
> http://nat-s11-4-lkws-stackdeploy-3.openstacklocal:8188/ws/v1/timeline/
> 2016-08-15 23:48:01,584 [main] WARN  shortcircuit.DomainSocketFactory - The 
> short-circuit local reads feature cannot be used because libhadoop cannot be 
> loaded.
> 2016-08-15 23:48:01,633 [main] INFO  client.RMProxy - Connecting to 
> ResourceManager at 
> nat-s11-4-lkws-stackdeploy-5.openstacklocal/172.22.71.181:8050
> 2016-08-15 23:48:01,983 [main] INFO  client.AHSProxy - Connecting to 
> Application History server at 
> nat-s11-4-lkws-stackdeploy-3.openstacklocal/172.22.71.168:10200
> 2016-08-15 23:48:03,297 [main] WARN  client.SliderClient - The 
> 'install-keytab' option has been deprecated.  Please use 'keytab --install'.
> 2016-08-15 23:48:03,440 [main] WARN  retry.RetryInvocationHandler - Exception 
> while invoking ClientNamenodeProtocolTranslatorPB.mkdirs over null. Not 
> retrying because try once and fail.
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.AccessControlException):
>  Permission denied: user=hive, access=WRITE, 
> inode="/user/hive/.slider/keytabs/hive":hdfs:hdfs:drwxr-xr-x
>   at 
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:319)
>   at 
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:292)
>   at 
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:213)
>   at 
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:190)
>   at 
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkPermission(FSDirectory.java:1827)
>   at 

[jira] [Updated] (AMBARI-18148) Kerberos UI labels should be specific to differentiate between SPARK and SPARK2 properties

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-18148:
-
Reporter: Kishor Ramakrishnan  (was: Andrii Babiichuk)

> Kerberos UI labels should be specific to differentiate between SPARK and 
> SPARK2 properties
> --
>
> Key: AMBARI-18148
> URL: https://issues.apache.org/jira/browse/AMBARI-18148
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Kishor Ramakrishnan
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18148.patch
>
>
> Kerberos UI labels should be specific to differentiate between SPARK and 
> SPARK2 properties. Currently the keytab and principal property labels for 
> SPARK and SPARK2 are the same and might confuse the admin user if both 
> services are present.



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

[jira] [Updated] (AMBARI-18989) Log level filter labels not getting updated with host name filter

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-18989:
-
Reporter: Kishor Ramakrishnan  (was: Olivér Szabó)

>  Log level filter labels not getting updated with host name filter
> --
>
> Key: AMBARI-18989
> URL: https://issues.apache.org/jira/browse/AMBARI-18989
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Kishor Ramakrishnan
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-18989.patch
>
>




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

[jira] [Updated] (AMBARI-18627) Add service wizard hung at Choose services page as no ClusterStackVersion is available with state=CURRENT

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-18627:
-
Reporter: Kishor Ramakrishnan  (was: Antonenko Alexander)

> Add service wizard hung at Choose services page as no ClusterStackVersion is 
> available with state=CURRENT
> -
>
> Key: AMBARI-18627
> URL: https://issues.apache.org/jira/browse/AMBARI-18627
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.2
>Reporter: Kishor Ramakrishnan
>Assignee: Antonenko Alexander
> Fix For: 2.4.2
>
> Attachments: AMBARI-18627.patch, AMBARI-18627.patch, 
> AMBARI-18627.patch
>
>
> Add service wizard hung at Choose services page as no ClusterStackVersion is 
> available with state=CURRENT



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

[jira] [Updated] (AMBARI-18260) Journal node restart failing on RU from HDP 2.4.x to 2.5 on Wire Encrypted cluster

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-18260:
-
Reporter: Shreya Bhat  (was: Andrew Onischuk)

> Journal node restart failing on RU from HDP 2.4.x to 2.5 on Wire Encrypted 
> cluster
> --
>
> Key: AMBARI-18260
> URL: https://issues.apache.org/jira/browse/AMBARI-18260
> Project: Ambari
>  Issue Type: Bug
>Reporter: Shreya Bhat
>Assignee: Andrew Onischuk
> Fix For: trunk
>
> Attachments: AMBARI-18260.patch
>
>
> Type of upgrade : RU  
> Upgrade from HDP (2.4.2.0) to 2.5 (on secure, Wire encrypted
> cluster)
> Journal node logs show :
> 
> 
> 
> org.apache.hadoop.hdfs.qjournal.protocol.JournalOutOfSyncException: Can't 
> write, no segment open
>   at 
> org.apache.hadoop.hdfs.qjournal.server.Journal.checkSync(Journal.java:484)
>   at 
> org.apache.hadoop.hdfs.qjournal.server.Journal.journal(Journal.java:353)
>   at 
> org.apache.hadoop.hdfs.qjournal.server.JournalNodeRpcServer.journal(JournalNodeRpcServer.java:152)
>   at 
> org.apache.hadoop.hdfs.qjournal.protocolPB.QJournalProtocolServerSideTranslatorPB.journal(QJournalProtocolServerSideTranslatorPB.java:158)
>   at 
> org.apache.hadoop.hdfs.qjournal.protocol.QJournalProtocolProtos$QJournalProtocolService$2.callBlockingMethod(QJournalProtocolProtos.java:25421)
>   at 
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:640)
>   at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:982)
>   at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2313)
>   at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2309)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:415)
>   at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1724)
>   at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2307)
> ç2016-08-25 07:19:47,651 INFO  namenode.FileJournalManager 
> (FileJournalManager.java:finalizeLogSegment(142)) - Finalizing edits file 
> /grid/0/hadoop/hdfs/journal/nameservice/current/edits_inprogress_0073697
>  -> 
> /grid/0/hadoop/hdfs/journal/nameservice/current/edits_0073697-0073698
> 
> Error at the exact RU task:
> 
> 
> 
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/journalnode.py",
>  line 198, in 
> JournalNode().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 280, in execute
> method(env)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 731, in restart
> self.post_upgrade_restart(env, upgrade_type=upgrade_type)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/journalnode.py",
>  line 75, in post_upgrade_restart
> journalnode_upgrade.post_upgrade_check()
>   File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/journalnode_upgrade.py",
>  line 64, in post_upgrade_check
> namenode_ha.is_encrypted(), params.security_enabled)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/utils.py",
>  line 306, in get_jmx_data
> data = urllib2.urlopen(nn_address).read()
>   File "/usr/lib64/python2.6/urllib2.py", line 126, in urlopen
> return _opener.open(url, data, timeout)
>   File "/usr/lib64/python2.6/urllib2.py", line 391, in open
> response = self._open(req, data)
>   File "/usr/lib64/python2.6/urllib2.py", line 409, in _open
> '_open', req)
>   File "/usr/lib64/python2.6/urllib2.py", line 369, in _call_chain
> result = func(*args)
>   File "/usr/lib64/python2.6/urllib2.py", line 1194, in https_open
> return self.do_open(httplib.HTTPSConnection, req)
>   File "/usr/lib64/python2.6/urllib2.py", line 1161, in do_open
> raise URLError(err)
> urllib2.URLError:  routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure>
> 
> Live cluster :  
> 
> Artifacts:  dgm10toerienoha-s11/test-logs/ambariru-dgm10toerie-sec-noha/ambaritestartifact
> s/artifacts/screenshots/com.hw.ambari.ui.tests.monitoring.admin_page.TestQuick
> RollingUpgradeApi/test060_StartPerformUpgrade/_24_22_9_0_One_step_of_upgrade_f
> ailed_after_retry_group_UpgradeGroup_completedtaskCount_4__name_CORE/>



--
This message was sent by Atlassian JIRA

[jira] [Updated] (AMBARI-20512) While generating hash for ambari-server to fill agent cache, all the symlinks should be traversed too.

[Madhuvanthi Radhakrishnan (JIRA)]

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

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

> While generating hash for ambari-server to fill agent cache, all the symlinks 
> should be traversed too.
> --
>
> Key: AMBARI-20512
> URL: https://issues.apache.org/jira/browse/AMBARI-20512
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
> Fix For: 2.5.0
>
> Attachments: AMBARI-20512.patch
>
>
> the archive.zip and .hash is not getting generated on the server side when 
> the package folder is under
> stacks///services//package
> instead of common-services///package
> On closer look, the issue was that when the directories are being traversed 
> to look for hooks and package folders that need to be hashed/archived for 
> having it in the agent cache, those directories that were symlinks were being 
> skipped.
> Fix is to include them.



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

[jira] [Updated] (AMBARI-18648) There were no labels on fields on step "Configure Kerberos" after clicking back

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-18648:
-
Reporter: Andrew Khalymon  (was: Antonenko Alexander)

> There were no labels on fields on step "Configure Kerberos" after clicking 
> back
> ---
>
> Key: AMBARI-18648
> URL: https://issues.apache.org/jira/browse/AMBARI-18648
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.2
>Reporter: Andrew Khalymon
>Assignee: Antonenko Alexander
>Priority: Blocker
> Fix For: 2.4.2
>
> Attachments: AMBARI-18648_2.4.patch, AMBARI-18648.patch
>
>
> STR: 
> #setup secure cluster
> #start enabling Kerberos
> #within "Install and test Kerberos client" step test got "Admin session 
> expiration error" window
> #click cancel on "Admin session expiration error" window
> #click back to step "Configure Kerberos"



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

[jira] [Updated] (AMBARI-20512) While generating hash for ambari-server to fill agent cache, all the symlinks should be traversed too.

[Madhuvanthi Radhakrishnan (JIRA)]

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

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

> While generating hash for ambari-server to fill agent cache, all the symlinks 
> should be traversed too.
> --
>
> Key: AMBARI-20512
> URL: https://issues.apache.org/jira/browse/AMBARI-20512
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
> Fix For: 2.5.0
>
> Attachments: AMBARI-20512.patch
>
>
> the archive.zip and .hash is not getting generated on the server side when 
> the package folder is under
> stacks///services//package
> instead of common-services///package
> On closer look, the issue was that when the directories are being traversed 
> to look for hooks and package folders that need to be hashed/archived for 
> having it in the agent cache, those directories that were symlinks were being 
> skipped.
> Fix is to include them.



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

[jira] [Updated] (AMBARI-18919) Oozie Server fails to start due to timeout

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-18919:
-
Reporter: Dhanya Balasundaran  (was: Andrew Onischuk)

> Oozie Server fails to start due to timeout
> --
>
> Key: AMBARI-18919
> URL: https://issues.apache.org/jira/browse/AMBARI-18919
> Project: Ambari
>  Issue Type: Bug
>Reporter: Dhanya Balasundaran
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-18919.patch
>
>
> Because of slow env every operation took so much time:
> 
> 
> untar - 1min
> sharelib create - 7min
> start oozie cmd - 1min
> shareliblist hive - 7 min (was waitting for Oozie to actually start)
> hdfs directories copy - 3min 
> 
> Looks like we have to increase timeout here, so Oozie start can succeed on
> slow envs



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

[jira] [Updated] (AMBARI-18997) ambari-server.pid might not be created on slow hardware

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-18997:
-
Reporter: Dhanya Balasundaran  (was: Dmytro Sen)

> ambari-server.pid might not be created on slow hardware
> ---
>
> Key: AMBARI-18997
> URL: https://issues.apache.org/jira/browse/AMBARI-18997
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Dhanya Balasundaran
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18997_6.patch, AMBARI-18997_7.patch
>
>
> ambari-server.pid file might not be created on slow hardware, but 
> "ambari-server start" exits with 0



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

[jira] [Updated] (AMBARI-18760) ambari-server.pid might not be created

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-18760:
-
Reporter: Dhanya Balasundaran  (was: Dmytro Sen)

> ambari-server.pid might not be created
> --
>
> Key: AMBARI-18760
> URL: https://issues.apache.org/jira/browse/AMBARI-18760
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Dhanya Balasundaran
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.4.2
>
> Attachments: AMBARI-18760_2.patch, AMBARI-18760.patch
>
>
> /var/run/ambari-server/ambari-server.pid might not be created, but IOError 
> not logged



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

[jira] [Updated] (AMBARI-18878) After entering wrong admin kdc credentials UI does not handle it and shows HTTP error 500 (intermittent)

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-18878:
-
Reporter: Andrew Khalymon  (was: Dmitry Lysnichenko)

> After entering wrong admin kdc credentials UI does not handle it and shows 
> HTTP error 500 (intermittent)
> 
>
> Key: AMBARI-18878
> URL: https://issues.apache.org/jira/browse/AMBARI-18878
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Andrew Khalymon
>Assignee: Dmitry Lysnichenko
> Fix For: 2.5.0
>
> Attachments: AMBARI-18878.patch
>
>
> STR:
> #setup unsecure cluster
> #start enabling Kerberos
> #enter wrong kdc credentials on "Configure Kerberos" page
> #click next
> expect: Error message "Failed to find a KDC for the specified realm - kadmin 
> Please enter admin principal and password."
> result: HTTP response 500



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

[jira] [Updated] (AMBARI-18728) During cluster install, Components get timed out icon while starting

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-18728:
-
Reporter: Vivek Rathod  (was: Andrew Onischuk)

> During cluster install, Components get timed out icon while starting
> 
>
> Key: AMBARI-18728
> URL: https://issues.apache.org/jira/browse/AMBARI-18728
> Project: Ambari
>  Issue Type: Bug
>Reporter: Vivek Rathod
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-18728.patch
>
>
> This was caused by a very tricky race-condition in the way python 
> multiprocessing.thread works resulting in deadlock in 
> ambari_agent.ActionQueue thread.
> The problem is the below flow:
> If this all these three get executed at the same time (a very rear occasion):
> 1. Process1 executes queue.get(False)
> 2. Process2 executes queue.put(largeObjectWhichTakesLongTimeToPut)
> 3. Someone kills Process2.
> This results in deadlock in process1 get. Which is caused by queue 
> locks/semaphores to being released during put of process2.
> I have wrote a script test_race_condition.py to emulate this behaviour and 
> indeed could reproduce this and test the fix for it.



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

[jira] [Updated] (AMBARI-20512) While generating hash for ambari-server to fill agent cache, all the symlinks should be traversed too.

[Madhuvanthi Radhakrishnan (JIRA)]

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

Madhuvanthi Radhakrishnan updated AMBARI-20512:
---
Description: 
the archive.zip and .hash is not getting generated on the server side when the 
package folder is under
stacks///services//package
instead of common-services///package
On closer look, the issue was that when the directories are being traversed to 
look for hooks and package folders that need to be hashed/archived for having 
it in the agent cache, those directories that were symlinks were being skipped.
Fix is to include them.

  was:
While testing a new management pack, it was found that when the component 
scripts come from the stack definition instead of the common-services, it was 
not getting copied over to the agent cache during install.
On closer look, the issue was that when the directories are being traversed to 
look for hooks and package folders that need to be hashed/archived for having 
it in the agent cache, those directories that were symlinks were being skipped.
Fix is to include them.


> While generating hash for ambari-server to fill agent cache, all the symlinks 
> should be traversed too.
> --
>
> Key: AMBARI-20512
> URL: https://issues.apache.org/jira/browse/AMBARI-20512
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
> Fix For: 2.5.0
>
>
> the archive.zip and .hash is not getting generated on the server side when 
> the package folder is under
> stacks///services//package
> instead of common-services///package
> On closer look, the issue was that when the directories are being traversed 
> to look for hooks and package folders that need to be hashed/archived for 
> having it in the agent cache, those directories that were symlinks were being 
> skipped.
> Fix is to include them.



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

[jira] [Updated] (AMBARI-18684) Webhcat server start failed during EU with BindException

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-18684:
-
Reporter: Vivek Sharma  (was: Vivek Rathod)

> Webhcat server start failed during EU with BindException
> 
>
> Key: AMBARI-18684
> URL: https://issues.apache.org/jira/browse/AMBARI-18684
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Vivek Sharma
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18684.patch
>
>
> WebHCat may fail to restart during an upgrade due to the following exception:
> {code}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/webhcat_server.py",
>  line 155, in 
> WebHCatServer().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 219, in execute
> method(env)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 530, in restart
> self.start(env, upgrade_type=upgrade_type)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/webhcat_server.py",
>  line 42, in start
> webhcat_service(action='start', upgrade_type=upgrade_type)
>   File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", 
> line 89, in thunk
> return fn(*args, **kwargs)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/webhcat_service.py",
>  line 54, in webhcat_service
> environment = environ)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
> line 154, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 160, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 124, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 238, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 70, in inner
> result = function(command, **kwargs)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 92, in checked_call
> tries=tries, try_sleep=try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 291, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'cd /var/run/webhcat ; 
> /usr/hdp/current/hive-webhcat/sbin/webhcat_server.sh start' returned 1. 
> {code}
> {noformat}
> WARN  | 17 Oct 2016 12:53:02,999 | 
> org.eclipse.jetty.util.component.AbstractLifeCycle | FAILED 
> org.eclipse.jetty.server.Server@19a639d8: java.net.BindException: Address 
> already in use
> java.net.BindException: Address already in use
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:444)
> at sun.nio.ch.Net.bind(Net.java:436)
> at 
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:214)
> {noformat}
> The problem seems to be caused by the failure of WebHCat to stop before being 
> upgraded. There was code added in AMBARI-12695 to address the issues with 
> WebHCat not stopping, however, it doesn't look correct.
> - Return Code 0 (prevents the kill -9 from running due to {{not_if}}
> -- 
> {code}
> ! (ls /var/run/webhcat/webhcat.pid >/dev/null 2>&1 && ps -p 
> `/var/lib/ambari-agent/ambari-sudo.sh su hcat -l -s /bin/bash -c 'cat 
> /var/run/webhcat/webhcat.pid'` >/dev/null 2>&1) || ( sleep 10 && ! (ls 
> /var/run/webhcat/webhcat.pid >/dev/null 2>&1 && ps -p `ambari-sudo.sh su hcat 
> -l -s /bin/bash -c 'cat /var/run/webhcat/webhcat.pid'` >/dev/null 2>&1) )
> {code}
> - Return Code 0 (prevents Fail from being raised)
> -- 
> {code}
> ! (ls /var/run/webhcat/webhcat.pid >/dev/null 2>&1 && ps -p 
> `/var/lib/ambari-agent/ambari-sudo.sh su hcat -l -s /bin/bash -c 'cat 
> /var/run/webhcat/webhcat.pid'` >/dev/null 2>&1)
> {code}



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

[jira] [Updated] (AMBARI-18684) Webhcat server start failed during EU with BindException

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-18684:
-
Reporter: Vivek Rathod  (was: Jonathan Hurley)

> Webhcat server start failed during EU with BindException
> 
>
> Key: AMBARI-18684
> URL: https://issues.apache.org/jira/browse/AMBARI-18684
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Vivek Rathod
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18684.patch
>
>
> WebHCat may fail to restart during an upgrade due to the following exception:
> {code}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/webhcat_server.py",
>  line 155, in 
> WebHCatServer().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 219, in execute
> method(env)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 530, in restart
> self.start(env, upgrade_type=upgrade_type)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/webhcat_server.py",
>  line 42, in start
> webhcat_service(action='start', upgrade_type=upgrade_type)
>   File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", 
> line 89, in thunk
> return fn(*args, **kwargs)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/webhcat_service.py",
>  line 54, in webhcat_service
> environment = environ)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
> line 154, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 160, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 124, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 238, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 70, in inner
> result = function(command, **kwargs)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 92, in checked_call
> tries=tries, try_sleep=try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 291, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'cd /var/run/webhcat ; 
> /usr/hdp/current/hive-webhcat/sbin/webhcat_server.sh start' returned 1. 
> {code}
> {noformat}
> WARN  | 17 Oct 2016 12:53:02,999 | 
> org.eclipse.jetty.util.component.AbstractLifeCycle | FAILED 
> org.eclipse.jetty.server.Server@19a639d8: java.net.BindException: Address 
> already in use
> java.net.BindException: Address already in use
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:444)
> at sun.nio.ch.Net.bind(Net.java:436)
> at 
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:214)
> {noformat}
> The problem seems to be caused by the failure of WebHCat to stop before being 
> upgraded. There was code added in AMBARI-12695 to address the issues with 
> WebHCat not stopping, however, it doesn't look correct.
> - Return Code 0 (prevents the kill -9 from running due to {{not_if}}
> -- 
> {code}
> ! (ls /var/run/webhcat/webhcat.pid >/dev/null 2>&1 && ps -p 
> `/var/lib/ambari-agent/ambari-sudo.sh su hcat -l -s /bin/bash -c 'cat 
> /var/run/webhcat/webhcat.pid'` >/dev/null 2>&1) || ( sleep 10 && ! (ls 
> /var/run/webhcat/webhcat.pid >/dev/null 2>&1 && ps -p `ambari-sudo.sh su hcat 
> -l -s /bin/bash -c 'cat /var/run/webhcat/webhcat.pid'` >/dev/null 2>&1) )
> {code}
> - Return Code 0 (prevents Fail from being raised)
> -- 
> {code}
> ! (ls /var/run/webhcat/webhcat.pid >/dev/null 2>&1 && ps -p 
> `/var/lib/ambari-agent/ambari-sudo.sh su hcat -l -s /bin/bash -c 'cat 
> /var/run/webhcat/webhcat.pid'` >/dev/null 2>&1)
> {code}



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

[jira] [Updated] (AMBARI-19051) Stage is sometimes marked as failed on command reschedule.

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19051:
-
Reporter: Pradarttana  (was: Myroslav Papirkovskyi)

> Stage is sometimes marked as failed on command reschedule.
> --
>
> Key: AMBARI-19051
> URL: https://issues.apache.org/jira/browse/AMBARI-19051
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Pradarttana
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19051.patch
>
>
> Sometimes when server processes command timeout and reschedules task for 
> agent execution, fail report is received from agent (after cancel command 
> processing) and whole stage/request gets marked as failed



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

[jira] [Updated] (AMBARI-19342) Race condition in agent on command reschedule

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19342:
-
Reporter: Pradarttana  (was: Myroslav Papirkovskyi)

> Race condition in agent on command reschedule
> -
>
> Key: AMBARI-19342
> URL: https://issues.apache.org/jira/browse/AMBARI-19342
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Pradarttana
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19342.patch
>
>
> Related to changes in AMBARI-19051. Task canceling and rescheduling should be 
> performed atomically to avoid unlucky context switch.



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

[jira] [Updated] (AMBARI-18780) Fix livy configuration upgrade from HDP 2.5 to HDP 2.6

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-18780:
-
Reporter: Vivek Sharma  (was: Jeff Zhang)

> Fix livy configuration upgrade from HDP 2.5 to HDP 2.6
> --
>
> Key: AMBARI-18780
> URL: https://issues.apache.org/jira/browse/AMBARI-18780
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Vivek Sharma
>Assignee: Jeff Zhang
> Fix For: 2.5.0
>
> Attachments: AMBARI-18780-1.patch
>
>
> Follow up work for upgrade fix of AMBARI-18758



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

[jira] [Updated] (AMBARI-18841) Grafana fails to start

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-18841:
-
Reporter: Dhanya Balasundaran  (was: Aravindan Vijayan)

> Grafana fails to start
> --
>
> Key: AMBARI-18841
> URL: https://issues.apache.org/jira/browse/AMBARI-18841
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.5.0
> Environment: Fresh install of 2.5.0 cluster.
>Reporter: Dhanya Balasundaran
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18841-2.patch, AMBARI-18841.patch
>
>
> Grafana fails to start with the below error
> {code}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
>  line 69, in 
> AmsGrafana().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 280, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
>  line 47, in start
> not_if = params.grafana_process_exists_cmd,
>   File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
> line 155, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 160, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 124, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 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 
> '/usr/sbin/ambari-metrics-grafana start' returned 1.  Hortonworks 
> #
> This is MOTD message, added for testing in qe infra
> Starting Ambari Metrics Grafana:  FAILED
> {code}



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

[jira] [Updated] (AMBARI-18908) Ambari Kerberos Identity not displayed in the Configured Identities page of Enable Kerberos Wizard

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-18908:
-
Reporter: Kishor Ramakrishnan  (was: Aleksandr Kovalenko)

> Ambari Kerberos Identity not displayed in the Configured Identities page of 
> Enable Kerberos Wizard
> --
>
> Key: AMBARI-18908
> URL: https://issues.apache.org/jira/browse/AMBARI-18908
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Kishor Ramakrishnan
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18908.patch
>
>
> Ambari Kerberos Identity not displayed in the Configured Identities page of 
> Enable Kerberos Wizard.



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

[jira] [Updated] (AMBARI-19049) Alerts Popup displays full error stacktrace instead of minimal content

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19049:
-
Reporter: Kishor Ramakrishnan  (was: Antonenko Alexander)

> Alerts Popup displays full error stacktrace instead of minimal content
> --
>
> Key: AMBARI-19049
> URL: https://issues.apache.org/jira/browse/AMBARI-19049
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Kishor Ramakrishnan
>Assignee: Antonenko Alexander
> Fix For: 2.5.0
>
> Attachments: AMBARI-19049.patch, AMBARI-19049_trunk.patch
>
>
> Alerts Popup displays full error stacktrace instead of minimal content
> STR:
> Navigate to any service page
> Click on Alerts button from top right corner of summary panel
> The complete error message should be displayed as a tooltip text or minimal 
> text should be displayed. But the complete stacktrace is displayed in the 
> popup window which makes the list of alerts look unorganized.



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

[jira] [Updated] (AMBARI-19043) CAPACITY-SCHEDULER & PIG View not loading for Ambari-2.5.0

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19043:
-
Reporter: Anusha Bilgi  (was: Akhil PB)

> CAPACITY-SCHEDULER & PIG View not loading for Ambari-2.5.0
> --
>
> Key: AMBARI-19043
> URL: https://issues.apache.org/jira/browse/AMBARI-19043
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Anusha Bilgi
>Assignee: Akhil PB
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19043.branch-2.5.patch, Capacity Scheduler View 
> Not Loading.png, Pig View Not Loading.png
>
>
> CAPACITY-SCHEDULER View not loading for Ambari-2.5.0 in the cluster: 
> http://172.27.29.71:8080/#/main/views/CAPACITY-SCHEDULER/1.0.0/NEW_INSTANCE
> Facing error while loading pig view in  live cluster: 
> http://172.27.23.128:8080/views/PIG/1.0.0/PIG/



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

[jira] [Updated] (AMBARI-19000) Ambari-server fails to restart with --debug if it is already running

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19000:
-
Reporter: Anusha Bilgi  (was: Andrew Onischuk)

> Ambari-server fails to restart with --debug if it is already running
> 
>
> Key: AMBARI-19000
> URL: https://issues.apache.org/jira/browse/AMBARI-19000
> Project: Ambari
>  Issue Type: Bug
>Reporter: Anusha Bilgi
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19000.patch
>
>
> Using python  /usr/bin/python
> Restarting ambari-server
> Ambari Server stopped
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Ambari database consistency check started...
> Server PID at: /var/run/ambari-server/ambari-server.pid
> Server out at: /var/log/ambari-server/ambari-server.out
> Server log at: /var/log/ambari-server/ambari-server.log
> Waiting for server start.
> DB configs consistency check: no errors and warnings were found.
> ERROR: Exiting with exit code -1. 
> REASON: Ambari Server java process died with exitcode 134. Check 
> /var/log/ambari-server/ambari-server.out for more information.



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

[jira] [Updated] (AMBARI-19030) Service Auto Start operations are permitted during Upgrade

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19030:
-
Reporter: Vivek Sharma  (was: Andrii Tkach)

> Service Auto Start operations are permitted during Upgrade
> --
>
> Key: AMBARI-19030
> URL: https://issues.apache.org/jira/browse/AMBARI-19030
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Sharma
>Assignee: Andrii Tkach
> Fix For: 2.5.0
>
> Attachments: AMBARI-19030_branch-2.5.patch, AMBARI-19030.patch, 
> Screen Shot 2016-11-29 at 4.24.52 PM.png
>
>
> Please see attached screenshots
> While an Express Upgrade is in progress, I am able to perform 'Service Auto 
> Start' operations like enable/disable auto start for a service component
> In-line with our standard mechanism of not allowing any operations during 
> upgrade (unless it is paused), it would be good to disable 'Service Auto 
> Start' during Upgrade - so as to not have any undesirable side-effects on the 
> system during an Upgrade



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

[jira] [Updated] (AMBARI-19118) Ranger Admin Start failed while enabling NameNode HA

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19118:
-
Reporter: Vivek Rathod  (was: Richard Zang)

> Ranger Admin Start failed while enabling NameNode HA
> 
>
> Key: AMBARI-19118
> URL: https://issues.apache.org/jira/browse/AMBARI-19118
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
>Assignee: Richard Zang
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19118.patch
>
>
> Ranger Admin Start failed while enabling NameNode HA. ZooKeeper needs to be 
> started before Ranger. Ambari infra also needs to be started before Ranger.



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

[jira] [Updated] (AMBARI-18988) [Intermittent]Ambari-server check-database command took longer (~3) minutes to complete

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-18988:
-
Reporter: Kishor Ramakrishnan  (was: Vitaly Brodetskyi)

> [Intermittent]Ambari-server check-database command took longer (~3) minutes 
> to complete
> ---
>
> Key: AMBARI-18988
> URL: https://issues.apache.org/jira/browse/AMBARI-18988
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Kishor Ramakrishnan
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18988.patch
>
>
> Ambari-server check-database command took longer (~3) minutes to complete 
> resulting in deploy test failures
> From ambari-server-check-database.log
> {noformat}
> 2016-11-23 02:09:54,281  INFO - *** Check 
> database started ***
> 2016-11-23 02:09:54,396  INFO - Checking for configs not mapped to any cluster
> 2016-11-23 02:09:55,543  INFO - Checking for configs selected more than once
> 2016-11-23 02:09:55,802  INFO - Checking for hosts without state
> 2016-11-23 02:09:55,804  INFO - Checking host component states count equals 
> host component desired states count
> 2016-11-23 02:09:55,808  INFO - Checking services and their configs
> 2016-11-23 02:12:58,491  INFO - Processing HDP-2.6 / MAHOUT
> 2016-11-23 02:12:58,491  INFO - Processing HDP-2.6 / SQOOP
> 2016-11-23 02:12:58,491  INFO - Processing HDP-2.6 / HDFS
> 2016-11-23 02:12:58,491  INFO - Processing HDP-2.6 / MAPREDUCE2
> 2016-11-23 02:12:58,491  INFO - Processing HDP-2.6 / OOZIE
> 2016-11-23 02:12:58,491  INFO - Processing HDP-2.6 / TEZ
> 2016-11-23 02:12:58,491  INFO - Processing HDP-2.6 / SPARK
> 2016-11-23 02:12:58,491  INFO - Processing HDP-2.6 / HBASE
> 2016-11-23 02:12:58,491  INFO - Processing HDP-2.6 / ZOOKEEPER
> 2016-11-23 02:12:58,491  INFO - Processing HDP-2.6 / KERBEROS
> 2016-11-23 02:12:58,491  INFO - Processing HDP-2.6 / YARN
> 2016-11-23 02:12:58,491  INFO - Processing HDP-2.6 / KNOX
> 2016-11-23 02:12:58,491  INFO - Processing HDP-2.6 / PIG
> 2016-11-23 02:12:58,491  INFO - Processing HDP-2.6 / ATLAS
> 2016-11-23 02:12:58,491  INFO - Processing HDP-2.6 / STORM
> 2016-11-23 02:12:58,491  INFO - Processing HDP-2.6 / HIVE
> 2016-11-23 02:12:58,492  INFO - Processing HDP-2.6 / SLIDER
> 2016-11-23 02:12:58,492  INFO - Processing HDP-2.6 / AMBARI_INFRA
> 2016-11-23 02:12:58,492  INFO - Processing HDP-2.6 / AMBARI_METRICS
> 2016-11-23 02:12:58,492  INFO - Processing HDP-2.6 / FLUME
> 2016-11-23 02:12:58,492  INFO - Processing HDP-2.6 / KAFKA
> 2016-11-23 02:12:58,492  INFO - Processing HDP-2.6 / LOGSEARCH
> 2016-11-23 02:12:58,492  INFO - Processing HDP-2.6 / FALCON
> 2016-11-23 02:12:58,492  INFO - Processing HDP-2.6 / SMARTSENSE
> 2016-11-23 02:12:58,546  INFO - *** Check 
> database completed ***
> {noformat}



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

[jira] [Updated] (AMBARI-19121) Add ability for users to provide mount exclusion list before cluster deployment

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19121:
-
Reporter: Vivek Sharma  (was: Dmytro Grinenko)

> Add ability for users to provide mount exclusion list before cluster 
> deployment
> ---
>
> Key: AMBARI-19121
> URL: https://issues.apache.org/jira/browse/AMBARI-19121
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: trunk, 2.5.0
>Reporter: Vivek Sharma
>Assignee: Dmytro Grinenko
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19121.patch, AMBARI-19121.patch.1
>
>
> Provide easy way for the user to add some mounts to the list of the filtered 
> for the Ambari.
> To do that, {{ignore_mount_points}} property need to be added to 
> ambari-agent.ini file. Property could be optional.



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

[jira] [Assigned] (AMBARI-19121) Add ability for users to provide mount exclusion list before cluster deployment

[Yusaku Sako (JIRA)]

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

Yusaku Sako reassigned AMBARI-19121:


Assignee: Dmytro Grinenko

> Add ability for users to provide mount exclusion list before cluster 
> deployment
> ---
>
> Key: AMBARI-19121
> URL: https://issues.apache.org/jira/browse/AMBARI-19121
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: trunk, 2.5.0
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19121.patch, AMBARI-19121.patch.1
>
>
> Provide easy way for the user to add some mounts to the list of the filtered 
> for the Ambari.
> To do that, {{ignore_mount_points}} property need to be added to 
> ambari-agent.ini file. Property could be optional.



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

[jira] [Updated] (AMBARI-19083) After ambari only upgrade Enable security(Configure Ambari Identity) was failed because could not run "ambari-sudo.sh"

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19083:
-
Reporter: Sviatoslav Tereshchenko  (was: Andrew Onischuk)

> After ambari only upgrade Enable security(Configure Ambari Identity) was 
> failed because could not run  "ambari-sudo.sh"
> ---
>
> Key: AMBARI-19083
> URL: https://issues.apache.org/jira/browse/AMBARI-19083
> Project: Ambari
>  Issue Type: Bug
>Reporter: Sviatoslav Tereshchenko
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19083.patch
>
>
> **STR:**  
> 1)Deploy cluster  
> 2)Make ambari only upgrade  
> 3)Enable security(MIT)
> **Actual result:** Enable security(Configure Ambari Identity) was failed 
> because could not run program "ambari-sudo.sh".



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

[jira] [Updated] (AMBARI-19110) "Cluster Load" widget in ambari-dashboard, download as CSV is not working

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19110:
-
Reporter: Pradarttana  (was: Antonenko Alexander)

> "Cluster Load" widget in ambari-dashboard, download as CSV is not working
> -
>
> Key: AMBARI-19110
> URL: https://issues.apache.org/jira/browse/AMBARI-19110
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Pradarttana
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19110.patch
>
>
> *Steps to Reporduce:-*
> 1. Log In to Ambari
> 2. Open DashBoard.
> 3. Download CSV file by clicking on Save icon in extreme right corner.



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

[jira] [Updated] (AMBARI-19086) LDAP sync creates groups with "Local" type

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19086:
-
Reporter: Dhanya Balasundaran  (was: Doroszlai, Attila)

> LDAP sync creates groups with "Local" type
> --
>
> Key: AMBARI-19086
> URL: https://issues.apache.org/jira/browse/AMBARI-19086
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Dhanya Balasundaran
>Assignee: Doroszlai, Attila
> Fix For: 2.5.0
>
> Attachments: AMBARI-19086.patch
>
>
> STR:
> {noformat}
> ambari-server setup-ldap
> ambari-server restart
> ambari-server sync-ldap --all
> {noformat}
> Result: users synced from LDAP are created with type LDAP, but groups are 
> created with type LOCAL:
> {noformat}
> ambari=> select group_id, group_name, group_type, ldap_group from groups 
> order by group_name;
>  group_id |group_name | group_type | ldap_group
> --+---++
>59 | accumulo  | LOCAL  |  1
> 2 | ambari| LOCAL  |  0
>72 | ambari-server | LOCAL  |  1
>81 | ams   | LOCAL  |  1
>60 | atlas | LOCAL  |  1
> ...
> {noformat}



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

[jira] [Updated] (AMBARI-19162) LogSearch - use fully qualified hostname instead of localhost for spnego.host

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19162:
-
Reporter: Sviatoslav Tereshchenko  (was: Olivér Szabó)

> LogSearch - use fully qualified hostname instead of localhost for spnego.host
> -
>
> Key: AMBARI-19162
> URL: https://issues.apache.org/jira/browse/AMBARI-19162
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, ambari-server
>Affects Versions: 2.4.0
>Reporter: Sviatoslav Tereshchenko
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-19162.patch
>
>




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

[jira] [Updated] (AMBARI-19148) Wrong filter groups names "Missing translation" on "Upgrade history" tab of Stack and Versions

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19148:
-
Reporter: Denis Tarasyuk  (was: Andrii Tkach)

> Wrong filter groups names "Missing translation" on "Upgrade history" tab of 
> Stack and Versions
> --
>
> Key: AMBARI-19148
> URL: https://issues.apache.org/jira/browse/AMBARI-19148
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Denis Tarasyuk
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19148.patch, Wrong filter groups name.png
>
>
> STR:
> # Deploy HDP 2.3 on Ambari 2.5.0.0-425
> # Enable NN HA
> # Register and install HDP 2.5.3.0
> # Perform RU to the new HDP version.
> # Open "Upgrade history" tab of Stack and Versions
> # Open Filters
> Result: There are not "Failed Upgrade" and "Failed Downgrade" in filters.
> Screenshot is attached.



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

[jira] [Updated] (AMBARI-19061) Ambari-server restart command not working. if any parameters are changed and reset to default.

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19061:
-
Reporter: Pradarttana  (was: Andrew Onischuk)

> Ambari-server restart command not working. if any parameters are changed and 
> reset to default. 
> ---
>
> Key: AMBARI-19061
> URL: https://issues.apache.org/jira/browse/AMBARI-19061
> Project: Ambari
>  Issue Type: Bug
>Reporter: Pradarttana
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19061.patch
>
>
> **Steps to reproduce:**  
> 1\. Change any of the parameters that hamper the ambari-server to restart
> successfully.(password.dat file)  
> 2\. Restart ambari-server, ambari-server restart will fail saying (This is
> expected as we have changed the parameter.)
> 
> 
> 
> Unable to determine server PID. Retrying...
> DB configs consistency check: no errors and warnings were found.
> ERROR: Exiting with exit code -1. 
> 
> 3\. Now set the Parameter to its actual value.  
> 4.Restart ambari-server, ambari-server restart will fail saying
> 
> 
> 
> Using python  /usr/bin/python
> Restarting ambari-server
> WARNING: '' is incorrect PID value. 
> /var/run/ambari-server/ambari-server.pid is corrupt. Removing
> Ambari Server 'restart' completed with warnings.
> 
> 5.If you Restart the Ambari server again. It gets restarted successfully.



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

[jira] [Updated] (AMBARI-19032) HDFS Metric alerts turns to UNKNOWN state with error "'NoneType' object has no attribute 'split'"

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19032:
-
Reporter: Andrew Khalymon  (was: Dmytro Sen)

> HDFS Metric alerts turns to UNKNOWN state with error "'NoneType' object has 
> no attribute 'split'"
> -
>
> Key: AMBARI-19032
> URL: https://issues.apache.org/jira/browse/AMBARI-19032
> Project: Ambari
>  Issue Type: Bug
>  Components: alerts, ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Andrew Khalymon
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19032_1.patch, AMBARI-19032_2.patch, 
> AMBARI-19032_branch2.5_additional.patch
>
>
> HDFS Metric alerts turns to UNKNOWN state with error "'NoneType' object has 
> no attribute 'split'".
> STR:
> Update the alert definition interval to 1 min, and thresholds to have minimum 
> values to trigger the Alert.



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

[jira] [Updated] (AMBARI-19139) UI: Quick Link from Falcon has not correct name (Now: Falcon Dashboard), but before was 'Falcon Web UI'

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19139:
-
Reporter: Sviatoslav Tereshchenko  (was: Antonenko Alexander)

> UI: Quick Link from Falcon has not correct name (Now: Falcon Dashboard), but 
> before was 'Falcon Web UI'
> ---
>
> Key: AMBARI-19139
> URL: https://issues.apache.org/jira/browse/AMBARI-19139
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Sviatoslav Tereshchenko
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19139.patch
>
>
> STR:
> 1)Deploy cluster
> 2)Check Quick Links from Falcon
> *Actual result:* UI: Quick Link from Falcon has not correct name (Now: Falcon 
> Dashboard), but before was Falcon Web UI



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

[jira] [Updated] (AMBARI-19221) Preview xml feature is not functional across different tabs

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19221:
-
Reporter: Supreeth Sharma  (was: Padma Priya Nagaraj)

> Preview xml feature is not functional across different tabs
> ---
>
> Key: AMBARI-19221
> URL: https://issues.apache.org/jira/browse/AMBARI-19221
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: Padma Priya Nagaraj
>  Labels: WFD
> Fix For: 2.5.0
>
> Attachments: AMBARI-19221_trunk.patch
>
>
> Preview xml feature is not functional across different tabs.UI hangs when 
> user tries to view preview workflow from two different tabs.
> Steps to reproduce :
> 1) Create a workflow and check preview is happening correctly.
> 2) Open new tab and create another workflow
> 3) UI hangs when user tries to preview.



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

[jira] [Updated] (AMBARI-19194) Deployed Views Throw Exceptions On Ambari Server Startup

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19194:
-
Reporter: Andrew Khalymon  (was: Anusha Bilgi)

> Deployed Views Throw Exceptions On Ambari Server Startup
> 
>
> Key: AMBARI-19194
> URL: https://issues.apache.org/jira/browse/AMBARI-19194
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Andrew Khalymon
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19194.patch
>
>
> - Install an HDP 2.5 cluster with HDFS, YARN, MapR, and ZK
> -- Relevant views, like Capacity Scheduler, should be instantiated at this 
> point
> - Restart Ambari Server
> {noformat}
> 12 Dec 2016 02:37:47,067  INFO [main] ViewRegistry:1796 - setting up logging 
> for view CAPACITY-SCHEDULER{1.0.0} as per property file view.log4j.properties
> 12 Dec 2016 02:37:47,112  INFO [main] ViewRegistry:1860 - Auto creating 
> instance of view CAPACITY-SCHEDULER for cluster cl1.
> 12 Dec 2016 02:37:47,165 ERROR [main] AmbariJpaLocalTxnInterceptor:180 - 
> [DETAILED ERROR] Rollback reason: 
> 12 Dec 2016 02:37:47,166 ERROR [main] AmbariJpaLocalTxnInterceptor:188 - 
> [DETAILED ERROR] Internal exception (1) : 
> 12 Dec 2016 02:37:47,167 ERROR [main] ViewRegistry:1867 - Can't auto create 
> instance of view CAPACITY-SCHEDULER for cluster cl1.  Caught exception 
> :Exception [EclipseLink-4002] (Eclipse Persistence Services - 
> 2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
> 12 Dec 2016 02:37:47,168  INFO [main] ViewRegistry:1738 - View deployed: 
> CAPACITY-SCHEDULER{1.0.0}.
> 12 Dec 2016 02:37:47,176  INFO [main] ViewRegistry:1705 - Reading view 
> archive /var/lib/ambari-server/resources/views/files-2.5.0.0.453.jar.
> 12 Dec 2016 02:37:47,227  INFO [main] ViewRegistry:1796 - setting up logging 
> for view FILES{1.0.0} as per property file view.log4j.properties
> 12 Dec 2016 02:37:47,277  INFO [main] ViewRegistry:1860 - Auto creating 
> instance of view FILES for cluster cl1.
> 12 Dec 2016 02:37:47,285 ERROR [main] AmbariJpaLocalTxnInterceptor:180 - 
> [DETAILED ERROR] Rollback reason: 
> 12 Dec 2016 02:37:47,286 ERROR [main] AmbariJpaLocalTxnInterceptor:188 - 
> [DETAILED ERROR] Internal exception (1) : 
> 12 Dec 2016 02:37:47,287 ERROR [main] ViewRegistry:1867 - Can't auto create 
> instance of view FILES for cluster cl1.  Caught exception :Exception 
> [EclipseLink-4002] (Eclipse Persistence Services - 2.6.2.v20151217-774c696): 
> org.eclipse.persistence.exceptions.DatabaseException
> {noformat}
> and 
> {noformat}
> 12 Dec 2016 17:49:57,423 ERROR [main] AmbariJpaLocalTxnInterceptor:180 - 
> [DETAILED ERROR] Rollback reason: 
> Local Exception Stack: 
> Exception [EclipseLink-4002] (Eclipse Persistence Services - 
> 2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: 
> com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: 
> Column 'resource_id' cannot be null
> Error Code: 1048
> {noformat}
> This seems to be due to how view syncing works with in-memory (not persisted) 
> entities. Because the {{ViewInstanceEntity}} is constructed in memory (and 
> not retrieve from the DB), it's incomplete and cannot be used for things like 
> retrieving associated entities from.



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

[jira] [Updated] (AMBARI-19220) Fix version of HDFS and YARN used by HDP 3.0

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19220:
-
Reporter: Denis Tarasyuk  (was: Alejandro Fernandez)

> Fix version of HDFS and YARN used by HDP 3.0
> 
>
> Key: AMBARI-19220
> URL: https://issues.apache.org/jira/browse/AMBARI-19220
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Denis Tarasyuk
>Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
> Attachments: AMBARI-19220.patch
>
>
> HDP 3.0 is set to use HDFS and YARN from the versions in common services.
> HDFS will use 3.0.0.3.0
> YARN will ise 3.0.0.3.0
> Right now there's a bug in that the metainfo.xml file for the new YARN in 
> common services has its version set to 2.1.0.2.0, which is obviously 
> incorrect and causes older stack versions to inherit newer properties.



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

[jira] [Updated] (AMBARI-19205) Technical Preview services should not be enabled by default

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19205:
-
Reporter: Andrew Khalymon  (was: Sumit Mohanty)

> Technical Preview services should not be enabled by default
> ---
>
> Key: AMBARI-19205
> URL: https://issues.apache.org/jira/browse/AMBARI-19205
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Andrew Khalymon
>Assignee: Sumit Mohanty
> Fix For: 2.5.0
>
> Attachments: AMBARI-19205.patch, Screen Shot 2016-12-14 at 12.53.23 
> PM.png
>
>
> Technical Preview services should not be enabled by default. Use the 
> "selection" tag to set the services as TECH_PREVIEW.



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

[jira] [Updated] (AMBARI-19306) User is not able to validate/submit the workflow after browsing workflow path

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19306:
-
Reporter: Supreeth Sharma  (was: M Madhan Mohan Reddy)

> User is not able to validate/submit the workflow after browsing workflow path
> -
>
> Key: AMBARI-19306
> URL: https://issues.apache.org/jira/browse/AMBARI-19306
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: M Madhan Mohan Reddy
>Priority: Critical
>  Labels: WFD
> Fix For: 2.5.0
>
> Attachments: AMBARI-19306_trunk.patch
>
>
> User is not able to validate/submit the workflow after browsing workflow path.
> Steps to reproduce :
> 1) Import the workflow. (attaching the workflow)
> 2) Click on submit.
> 3) Browse the 'workflow path' using file browser.
> 4) After selecting the workflow path, UI scrolling is not functional and 
> footer elements become non accessible.



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