[jira] [Commented] (AMBARI-18790) Implement lazy loading for Service configs Advanced tab

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18790:
-

ABORTED: Integrated in Jenkins build Ambari-trunk-Commit #5935 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5935/])
AMBARI-18790. Implement lazy loading for Service configs Advanced tab 
(akovalenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0c165e3368a9be1a4b023b129632bf4ba2b2b90e])
* (add) ambari-web/app/views/common/configs/config_category_container_view.js
* (edit) ambari-web/app/templates/common/configs/service_config.hbs
* (edit) 
ambari-web/test/views/common/configs/custom_category_views/notification_configs_view_test.js
* (edit) ambari-web/app/views/common/configs/service_configs_by_category_view.js
* (edit) ambari-web/app/views.js


> Implement lazy loading for Service configs Advanced tab
> ---
>
> Key: AMBARI-18790
> URL: https://issues.apache.org/jira/browse/AMBARI-18790
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-18790.patch
>
>
> We already have lazy loading for configs page in wizards. Let's implement the 
> same on service configs page.



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

[jira] [Updated] (AMBARI-18595) Icons don't display in Windows 10 Microsoft Edge or Internet Explorer 11

[Vivek Ratnavel Subramanian (JIRA)]

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

Vivek Ratnavel Subramanian updated AMBARI-18595:

Status: Patch Available  (was: Reopened)

> Icons don't display in Windows 10 Microsoft Edge or Internet Explorer 11
> 
>
> Key: AMBARI-18595
> URL: https://issues.apache.org/jira/browse/AMBARI-18595
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
> Environment: Microsoft Windows 10
>  - Microsoft Edge
>  - Microsoft Internet Explorer 11
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-18595.v0.patch, AMBARI-18595.v1.patch, 
> AMBARI-18595.v1Trunk.patch, Capture.PNG
>
>
> Icons do not display in any page as shown in the screen-shot attached.



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

[jira] [Updated] (AMBARI-18595) Icons don't display in Windows 10 Microsoft Edge or Internet Explorer 11

[Vivek Ratnavel Subramanian (JIRA)]

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

Vivek Ratnavel Subramanian updated AMBARI-18595:

Attachment: AMBARI-18595.v1.patch

> Icons don't display in Windows 10 Microsoft Edge or Internet Explorer 11
> 
>
> Key: AMBARI-18595
> URL: https://issues.apache.org/jira/browse/AMBARI-18595
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
> Environment: Microsoft Windows 10
>  - Microsoft Edge
>  - Microsoft Internet Explorer 11
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-18595.v0.patch, AMBARI-18595.v1.patch, Capture.PNG
>
>
> Icons do not display in any page as shown in the screen-shot attached.



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

[jira] [Updated] (AMBARI-18795) Ambari-server: Stack defintion to specify which services support credential store

[Nahappan Somasundaram (JIRA)]

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

Nahappan Somasundaram updated AMBARI-18795:
---
Status: Patch Available  (was: Open)

> Ambari-server: Stack defintion to specify which services support credential 
> store
> -
>
> Key: AMBARI-18795
> URL: https://issues.apache.org/jira/browse/AMBARI-18795
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb53454.patch
>
>
> Services must be tagged to indicate whether they support credential store 
> backed passwords. This also helps with backward compatibility.
> If services support credential store, they will also be able to read clear 
> text passwords. Services that do not support credential store will not be 
> able to decrypt the passwords in the configurations. 
> The server will send this information to the agent so that it can determine 
> whether it should store clear text passwords in the configuration files or 
> use JCEKS files.



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

[jira] [Updated] (AMBARI-18795) Ambari-server: Stack defintion to specify which services support credential store

[Nahappan Somasundaram (JIRA)]

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

Nahappan Somasundaram updated AMBARI-18795:
---
Attachment: rb53454.patch

> Ambari-server: Stack defintion to specify which services support credential 
> store
> -
>
> Key: AMBARI-18795
> URL: https://issues.apache.org/jira/browse/AMBARI-18795
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb53454.patch
>
>
> Services must be tagged to indicate whether they support credential store 
> backed passwords. This also helps with backward compatibility.
> If services support credential store, they will also be able to read clear 
> text passwords. Services that do not support credential store will not be 
> able to decrypt the passwords in the configurations. 
> The server will send this information to the agent so that it can determine 
> whether it should store clear text passwords in the configuration files or 
> use JCEKS files.



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

[jira] [Created] (AMBARI-18795) Ambari-server: Stack defintion to specify which services support credential store

[Nahappan Somasundaram (JIRA)]

Nahappan Somasundaram created AMBARI-18795:
--

 Summary: Ambari-server: Stack defintion to specify which services 
support credential store
 Key: AMBARI-18795
 URL: https://issues.apache.org/jira/browse/AMBARI-18795
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.4.2
Reporter: Nahappan Somasundaram
Assignee: Nahappan Somasundaram
 Fix For: 2.5.0


Services must be tagged to indicate whether they support credential store 
backed passwords. This also helps with backward compatibility.

If services support credential store, they will also be able to read clear text 
passwords. Services that do not support credential store will not be able to 
decrypt the passwords in the configurations. 

The server will send this information to the agent so that it can determine 
whether it should store clear text passwords in the configuration files or use 
JCEKS files.



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

[jira] [Updated] (AMBARI-18793) Ambari-server: Support stack inheritance for credential store information

[Nahappan Somasundaram (JIRA)]

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

Nahappan Somasundaram updated AMBARI-18793:
---
Attachment: rb53446.patch

> Ambari-server: Support stack inheritance for credential store information
> -
>
> Key: AMBARI-18793
> URL: https://issues.apache.org/jira/browse/AMBARI-18793
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb53446.patch
>
>
> If *credential-store* is not specified in the current stack definition, then 
> it must be inherited from the parent stack if specified.
> {quote}
> 
> true
> true
> 
> {quote}



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

[jira] [Updated] (AMBARI-18793) Ambari-server: Support stack inheritance for credential store information

[Nahappan Somasundaram (JIRA)]

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

Nahappan Somasundaram updated AMBARI-18793:
---
Status: Patch Available  (was: Open)

> Ambari-server: Support stack inheritance for credential store information
> -
>
> Key: AMBARI-18793
> URL: https://issues.apache.org/jira/browse/AMBARI-18793
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb53446.patch
>
>
> If *credential-store* is not specified in the current stack definition, then 
> it must be inherited from the parent stack if specified.
> {quote}
> 
> true
> true
> 
> {quote}



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

[jira] [Created] (AMBARI-18794) Remove PHD stack from Ambari source code

[Matt (JIRA)]

Matt created AMBARI-18794:
-

 Summary: Remove PHD stack from Ambari source code
 Key: AMBARI-18794
 URL: https://issues.apache.org/jira/browse/AMBARI-18794
 Project: Ambari
  Issue Type: Bug
  Components: stacks
Reporter: Matt
Assignee: Matt
Priority: Minor
 Fix For: trunk, 2.5.0, 2.4.2


PHD stack is no longer used. Hence it should be removed from Ambari 2.4+ 
branches.



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

[jira] [Created] (AMBARI-18793) Ambari-server: Support stack inheritance for credential store information

[Nahappan Somasundaram (JIRA)]

Nahappan Somasundaram created AMBARI-18793:
--

 Summary: Ambari-server: Support stack inheritance for credential 
store information
 Key: AMBARI-18793
 URL: https://issues.apache.org/jira/browse/AMBARI-18793
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.4.2
Reporter: Nahappan Somasundaram
Assignee: Nahappan Somasundaram
 Fix For: 2.5.0


If *credential-store* is not specified in the current stack definition, then it 
must be inherited from the parent stack if specified.

{quote}

true
true

{quote}



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

[jira] [Commented] (AMBARI-18778) Ambari-server: Blueprint enhancements to support enabling or disabling credential store

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18778:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5934 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5934/])
AMBARI-18778: Ambari-server: Blueprint enhancements to support enabling 
(nsomasundaram: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=988140979d64b9a1d38fc266ca58e509b4cbcfa1])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/topology/BlueprintImpl.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/topology/AmbariContextTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/topology/AmbariContext.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/topology/Setting.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/topology/Blueprint.java


> Ambari-server: Blueprint enhancements to support enabling or disabling 
> credential store 
> 
>
> Key: AMBARI-18778
> URL: https://issues.apache.org/jira/browse/AMBARI-18778
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb53412.patch
>
>
> When deploying a cluster using a blueprint, users must be able to specify 
> whether they want to enable the use of hadoop credential store for a service 
> if it supports it.
> { "settings" :
> {
>   "service_settings" : [
>   { "name" : "RANGER",
> "recovery_enabled" : "true",
> "credential_store_enabled" : "true"
>   },
>   { "name" : "HIVE",
> "recovery_enabled" : "true",
> "credential_store_enabled" : "false"
>   }
>   ]
> }
> }



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

[jira] [Updated] (AMBARI-18792) Update som configuration properties for hive interactive for the HDP 2.6 stack

[Siddharth Seth (JIRA)]

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

Siddharth Seth updated AMBARI-18792:

Status: Patch Available  (was: Open)

> Update som configuration properties for hive interactive for the HDP 2.6 stack
> --
>
> Key: AMBARI-18792
> URL: https://issues.apache.org/jira/browse/AMBARI-18792
> Project: Ambari
>  Issue Type: Task
>  Components: stacks
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Fix For: 2.5.0
>
> Attachments: AMBARI-18792.01.patch
>
>




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

[jira] [Commented] (AMBARI-18790) Implement lazy loading for Service configs Advanced tab

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko commented on AMBARI-18790:
--

committed to trunk

> Implement lazy loading for Service configs Advanced tab
> ---
>
> Key: AMBARI-18790
> URL: https://issues.apache.org/jira/browse/AMBARI-18790
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-18790.patch
>
>
> We already have lazy loading for configs page in wizards. Let's implement the 
> same on service configs page.



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

[jira] [Commented] (AMBARI-18790) Implement lazy loading for Service configs Advanced tab

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko commented on AMBARI-18790:
--

[~hadoopqa]:
{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12836904/AMBARI-18790.patch
  against trunk revision .

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

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

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

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

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

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

This message is automatically generated.


> Implement lazy loading for Service configs Advanced tab
> ---
>
> Key: AMBARI-18790
> URL: https://issues.apache.org/jira/browse/AMBARI-18790
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-18790.patch
>
>
> We already have lazy loading for configs page in wizards. Let's implement the 
> same on service configs page.



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

[jira] [Commented] (AMBARI-18666) Move HAWQ and PXF RCO from stacks to common-services

[Jonathan Hurley (JIRA)]

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

Jonathan Hurley commented on AMBARI-18666:
--

Perhaps the updated patch is what failed.  Or maybe something else changed in 
between the original patch and the updated one?

> Move HAWQ and PXF RCO from stacks to common-services
> 
>
> Key: AMBARI-18666
> URL: https://issues.apache.org/jira/browse/AMBARI-18666
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: trunk, 2.5.0, 2.4.2
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk, 2.5.0, 2.4.2
>
> Attachments: AMBARI-18666-trunk-orig.patch
>
>
> Move HAWQ and PXF RCO from stacks to common-services



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

[jira] [Commented] (AMBARI-18666) Move HAWQ and PXF RCO from stacks to common-services

[Matt (JIRA)]

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

Matt commented on AMBARI-18666:
---

[~jonathan.hurley]
Quite surprising that it passed Hadoop QA but failed on trunk-commit. Do you 
happen to know why the Hadoop QA behaves differently?

> Move HAWQ and PXF RCO from stacks to common-services
> 
>
> Key: AMBARI-18666
> URL: https://issues.apache.org/jira/browse/AMBARI-18666
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: trunk, 2.5.0, 2.4.2
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk, 2.5.0, 2.4.2
>
> Attachments: AMBARI-18666-trunk-orig.patch
>
>
> Move HAWQ and PXF RCO from stacks to common-services



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

[jira] [Updated] (AMBARI-18779) Fix the backend for HAWQ View BETA

[Matt (JIRA)]

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

Matt updated AMBARI-18779:
--
Attachment: AMBARI-18779-v2-orig.patch

> Fix the backend for HAWQ View BETA
> --
>
> Key: AMBARI-18779
> URL: https://issues.apache.org/jira/browse/AMBARI-18779
> Project: Ambari
>  Issue Type: Bug
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk, 2.5.0, 2.4.2
>
> Attachments: AMBARI-18779-trunk-orig.patch, 
> AMBARI-18779-v1-orig.patch, AMBARI-18779-v2-orig.patch
>
>
> Fix the backend for HAWQ View so that the backend is able to query from 
> pg_stat_activity table.



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

[jira] [Commented] (AMBARI-18774) Install Package for non-HDP stack fails with non-VDF repo version

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18774:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5933 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5933/])
AMBARI-18774: Install Package for non-HDP stack fails with non-VDF repo 
(jluniya: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2da6fa789f6ac64c4e699469bde1185bb2ab126d])
* (edit) ambari-server/src/main/java/org/apache/ambari/server/state/StackId.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/CompatibleRepositoryVersionResourceProviderTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProviderTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/RepositoryVersionEntity.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/RepositoryVersionDAOTest.java


> Install Package for non-HDP stack fails with non-VDF repo version
> -
>
> Key: AMBARI-18774
> URL: https://issues.apache.org/jira/browse/AMBARI-18774
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18774.2.patch, AMBARI-18774.patch
>
>
> Install Package fails when registering a new non-HDP version without using a 
> VDF. This is because the repo version is saved as display name (i.e. 
> "HDF-2.1.0.0-30" instead of "2.1.0.0-30"). If a new version is registered 
> using VDF, we dont run into this issue as the version is set correctly.
> {code}
> Ambari cannot install version HDF-2.1.0.0.  Version 2.0.1.0-12 is already 
> installed.
> {code}
> Fix:
> Remove HDP specific hardcodings from RepositoryVersionEntity.java



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

[jira] [Commented] (AMBARI-18746) Sqoop parameter hadoop_home is pointed to incorrect path in params_linux.py

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18746:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #261 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/261/])
AMBARI-18746: Sqoop parameter hadoop_home is pointed to incorrect path (dili: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=35adad6e6f387b25d577ce1ca30e57523bbd1b3e])
* (edit) 
ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/package/scripts/params_linux.py


> Sqoop parameter hadoop_home is pointed to incorrect path in params_linux.py
> ---
>
> Key: AMBARI-18746
> URL: https://issues.apache.org/jira/browse/AMBARI-18746
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0, 2.5.0
> Environment: Redhat 6.6, Sqoop 1.4.6+Hadoop 2.7.2
>Reporter: Ying Cao
>Assignee: Di Li
>Priority: Minor
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-18746-rebased.patch, AMBARI-18746.1.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> The parameter hadoop_home is pointed to hbase-client in params_linux.py, and 
> need to be updated.
> ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/package/scripts/params_linux.py
> # For stack versions supporting rolling upgrade
> if stack_version_formatted and 
> 
>   hadoop_home = format("{stack_root}/current/hbase-client")
> ...



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

[jira] [Commented] (AMBARI-18774) Install Package for non-HDP stack fails with non-VDF repo version

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18774:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #261 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/261/])
AMBARI-18774: Install Package for non-HDP stack fails with non-VDF repo 
(jluniya: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=298a50e91de43f4186d65b55e028e2a4b87f7f48])
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/RepositoryVersionDAOTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProviderTest.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/state/StackId.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/RepositoryVersionEntity.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/CompatibleRepositoryVersionResourceProviderTest.java


> Install Package for non-HDP stack fails with non-VDF repo version
> -
>
> Key: AMBARI-18774
> URL: https://issues.apache.org/jira/browse/AMBARI-18774
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18774.2.patch, AMBARI-18774.patch
>
>
> Install Package fails when registering a new non-HDP version without using a 
> VDF. This is because the repo version is saved as display name (i.e. 
> "HDF-2.1.0.0-30" instead of "2.1.0.0-30"). If a new version is registered 
> using VDF, we dont run into this issue as the version is set correctly.
> {code}
> Ambari cannot install version HDF-2.1.0.0.  Version 2.0.1.0-12 is already 
> installed.
> {code}
> Fix:
> Remove HDP specific hardcodings from RepositoryVersionEntity.java



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

[jira] [Commented] (AMBARI-17703) Hosts page: after component filter hosts have wrong list of components

[Kishor Ramakrishnan (JIRA)]

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

Kishor Ramakrishnan commented on AMBARI-17703:
--

Reproduced in today's 2.4.2 system test as well, while trying to search for 
History server.

> Hosts page: after component filter hosts have wrong list of components
> --
>
> Key: AMBARI-17703
> URL: https://issues.apache.org/jira/browse/AMBARI-17703
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.4.0
>
> Attachments: AMBARI-17703.patch
>
>
> Go to Hosts page, filter by component.
> Result: each host has only filtered component.
> Filtering by stack version produce the same behavior too. 
> Filtering by sub-resource should be carry out in two calls, as it was before 
> new filter were introduced.



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

[jira] [Commented] (AMBARI-18746) Sqoop parameter hadoop_home is pointed to incorrect path in params_linux.py

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18746:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5932 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5932/])
AMBARI-18746: Sqoop parameter hadoop_home is pointed to incorrect path (dili: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=574fd6435f1df87f632ea86287f26e8f1f7f1121])
* (edit) 
ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/package/scripts/params_linux.py


> Sqoop parameter hadoop_home is pointed to incorrect path in params_linux.py
> ---
>
> Key: AMBARI-18746
> URL: https://issues.apache.org/jira/browse/AMBARI-18746
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0, 2.5.0
> Environment: Redhat 6.6, Sqoop 1.4.6+Hadoop 2.7.2
>Reporter: Ying Cao
>Assignee: Di Li
>Priority: Minor
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-18746-rebased.patch, AMBARI-18746.1.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> The parameter hadoop_home is pointed to hbase-client in params_linux.py, and 
> need to be updated.
> ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/package/scripts/params_linux.py
> # For stack versions supporting rolling upgrade
> if stack_version_formatted and 
> 
>   hadoop_home = format("{stack_root}/current/hbase-client")
> ...



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

[jira] [Commented] (AMBARI-18774) Install Package for non-HDP stack fails with non-VDF repo version

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-18774:


Trunk
commit 2da6fa789f6ac64c4e699469bde1185bb2ab126d
Author: Jayush Luniya 
Date:   Thu Nov 3 13:17:44 2016 -0700

AMBARI-18774: Install Package for non-HDP stack fails with non-VDF repo 
version (jluniya)

Branch-2.5
commit 298a50e91de43f4186d65b55e028e2a4b87f7f48
Author: Jayush Luniya 
Date:   Thu Nov 3 13:17:44 2016 -0700

AMBARI-18774: Install Package for non-HDP stack fails with non-VDF repo 
version (jluniya)

Branch-2.4
commit 4692a16bc230f563211ec02b7326cf13cb519366
Author: Jayush Luniya 
Date:   Thu Nov 3 13:17:44 2016 -0700

AMBARI-18774: Install Package for non-HDP stack fails with non-VDF repo 
version (jluniya)


> Install Package for non-HDP stack fails with non-VDF repo version
> -
>
> Key: AMBARI-18774
> URL: https://issues.apache.org/jira/browse/AMBARI-18774
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18774.2.patch, AMBARI-18774.patch
>
>
> Install Package fails when registering a new non-HDP version without using a 
> VDF. This is because the repo version is saved as display name (i.e. 
> "HDF-2.1.0.0-30" instead of "2.1.0.0-30"). If a new version is registered 
> using VDF, we dont run into this issue as the version is set correctly.
> {code}
> Ambari cannot install version HDF-2.1.0.0.  Version 2.0.1.0-12 is already 
> installed.
> {code}
> Fix:
> Remove HDP specific hardcodings from RepositoryVersionEntity.java



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

[jira] [Updated] (AMBARI-18774) Install Package for non-HDP stack fails with non-VDF repo version

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-18774:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Install Package for non-HDP stack fails with non-VDF repo version
> -
>
> Key: AMBARI-18774
> URL: https://issues.apache.org/jira/browse/AMBARI-18774
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18774.2.patch, AMBARI-18774.patch
>
>
> Install Package fails when registering a new non-HDP version without using a 
> VDF. This is because the repo version is saved as display name (i.e. 
> "HDF-2.1.0.0-30" instead of "2.1.0.0-30"). If a new version is registered 
> using VDF, we dont run into this issue as the version is set correctly.
> {code}
> Ambari cannot install version HDF-2.1.0.0.  Version 2.0.1.0-12 is already 
> installed.
> {code}
> Fix:
> Remove HDP specific hardcodings from RepositoryVersionEntity.java



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

[jira] [Commented] (AMBARI-18746) Sqoop parameter hadoop_home is pointed to incorrect path in params_linux.py

[Di Li (JIRA)]

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

Di Li commented on AMBARI-18746:


Pushed to trunk and branch-2.5 respectively..
Trunk:
https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=commit;h=574fd6435f1df87f632ea86287f26e8f1f7f1121

branch-2.5:
https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=commit;h=35adad6e6f387b25d577ce1ca30e57523bbd1b3e


> Sqoop parameter hadoop_home is pointed to incorrect path in params_linux.py
> ---
>
> Key: AMBARI-18746
> URL: https://issues.apache.org/jira/browse/AMBARI-18746
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0, 2.5.0
> Environment: Redhat 6.6, Sqoop 1.4.6+Hadoop 2.7.2
>Reporter: Ying Cao
>Assignee: Di Li
>Priority: Minor
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-18746-rebased.patch, AMBARI-18746.1.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> The parameter hadoop_home is pointed to hbase-client in params_linux.py, and 
> need to be updated.
> ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/package/scripts/params_linux.py
> # For stack versions supporting rolling upgrade
> if stack_version_formatted and 
> 
>   hadoop_home = format("{stack_root}/current/hbase-client")
> ...



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

[jira] [Updated] (AMBARI-18774) Install Package for non-HDP stack fails with non-VDF repo version

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-18774:
---
Attachment: AMBARI-18774.2.patch

> Install Package for non-HDP stack fails with non-VDF repo version
> -
>
> Key: AMBARI-18774
> URL: https://issues.apache.org/jira/browse/AMBARI-18774
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18774.2.patch, AMBARI-18774.patch
>
>
> Install Package fails when registering a new non-HDP version without using a 
> VDF. This is because the repo version is saved as display name (i.e. 
> "HDF-2.1.0.0-30" instead of "2.1.0.0-30"). If a new version is registered 
> using VDF, we dont run into this issue as the version is set correctly.
> {code}
> Ambari cannot install version HDF-2.1.0.0.  Version 2.0.1.0-12 is already 
> installed.
> {code}
> Fix:
> Remove HDP specific hardcodings from RepositoryVersionEntity.java



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

[jira] [Updated] (AMBARI-18791) ADD configs for DRUID in KNOX service definitions

[Nishant Bangarwa (JIRA)]

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

Nishant Bangarwa updated AMBARI-18791:
--
Status: Patch Available  (was: Open)

> ADD configs for DRUID in KNOX service definitions
> -
>
> Key: AMBARI-18791
> URL: https://issues.apache.org/jira/browse/AMBARI-18791
> Project: Ambari
>  Issue Type: Task
>Reporter: Nishant Bangarwa
> Attachments: ambari-18791.patch
>
>
> KNOX now supports proxying druid services -  
> https://issues.apache.org/jira/browse/KNOX-758
> Add configs for DRUID in KNOX service definitions. 



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

[jira] [Updated] (AMBARI-18791) ADD configs for DRUID in KNOX service definitions

[Nishant Bangarwa (JIRA)]

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

Nishant Bangarwa updated AMBARI-18791:
--
Attachment: ambari-18791.patch

> ADD configs for DRUID in KNOX service definitions
> -
>
> Key: AMBARI-18791
> URL: https://issues.apache.org/jira/browse/AMBARI-18791
> Project: Ambari
>  Issue Type: Task
>Reporter: Nishant Bangarwa
> Attachments: ambari-18791.patch
>
>
> KNOX now supports proxying druid services -  
> https://issues.apache.org/jira/browse/KNOX-758
> Add configs for DRUID in KNOX service definitions. 



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

[jira] [Updated] (AMBARI-18792) Update som configuration properties for hive interactive for the HDP 2.6 stack

[Siddharth Seth (JIRA)]

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

Siddharth Seth updated AMBARI-18792:

Attachment: AMBARI-18792.01.patch

Changes values for locality delay, fragment timeouts, and usage of grace hash 
joins.

cc [~sumitmohanty], [~swapanshridhar], [~gopalv]

> Update som configuration properties for hive interactive for the HDP 2.6 stack
> --
>
> Key: AMBARI-18792
> URL: https://issues.apache.org/jira/browse/AMBARI-18792
> Project: Ambari
>  Issue Type: Task
>  Components: stacks
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Fix For: 2.5.0
>
> Attachments: AMBARI-18792.01.patch
>
>




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

[jira] [Created] (AMBARI-18792) Update som configuration properties for hive interactive for the HDP 2.6 stack

[Siddharth Seth (JIRA)]

Siddharth Seth created AMBARI-18792:
---

 Summary: Update som configuration properties for hive interactive 
for the HDP 2.6 stack
 Key: AMBARI-18792
 URL: https://issues.apache.org/jira/browse/AMBARI-18792
 Project: Ambari
  Issue Type: Task
  Components: stacks
Reporter: Siddharth Seth
Assignee: Siddharth Seth
 Fix For: 2.5.0






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

[jira] [Commented] (AMBARI-18789) Change the Wording of the HiveServer2 Non-Rolling Warning

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18789:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5931 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5931/])
AMBARI-18789 - Change the Wording of the HiveServer2 Non-Rolling Warning 
(jhurley: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7394cef4bf0b949758d06470cefbf581a914967c])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/checks/CheckDescription.java


> Change the Wording of the HiveServer2 Non-Rolling Warning
> -
>
> Key: AMBARI-18789
> URL: https://issues.apache.org/jira/browse/AMBARI-18789
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: 2.5.0
>
> Attachments: AMBARI-18789.patch
>
>
> HiveServer2 is no longer rolling, even when choosing a rolling upgrade. The 
> warning message before upgrade might be a little misleading to users of the 
> Hive CLI. The new message should read:
> HiveServer2 Downtime
> HiveServer2 does not currently support rolling upgrades. HiveServer2 will be 
> upgraded, however existing queries which have been submitted will fail and 
> need to be resubmitted after HiveServer2 has been upgraded.



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

[jira] [Created] (AMBARI-18791) ADD configs for DRUID in KNOX service definitions

[Nishant Bangarwa (JIRA)]

Nishant Bangarwa created AMBARI-18791:
-

 Summary: ADD configs for DRUID in KNOX service definitions
 Key: AMBARI-18791
 URL: https://issues.apache.org/jira/browse/AMBARI-18791
 Project: Ambari
  Issue Type: Task
Reporter: Nishant Bangarwa


KNOX now supports proxying druid services -  
https://issues.apache.org/jira/browse/KNOX-758

Add configs for DRUID in KNOX service definitions. 



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

[jira] [Updated] (AMBARI-18779) Fix the backend for HAWQ View BETA

[Matt (JIRA)]

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

Matt updated AMBARI-18779:
--
Attachment: AMBARI-18779-v1-orig.patch

> Fix the backend for HAWQ View BETA
> --
>
> Key: AMBARI-18779
> URL: https://issues.apache.org/jira/browse/AMBARI-18779
> Project: Ambari
>  Issue Type: Bug
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk, 2.5.0, 2.4.2
>
> Attachments: AMBARI-18779-trunk-orig.patch, AMBARI-18779-v1-orig.patch
>
>
> Fix the backend for HAWQ View so that the backend is able to query from 
> pg_stat_activity table.



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

[jira] [Updated] (AMBARI-18580) Delete host throws 500 Error with unique constraint violation

[Myroslav Papirkovskyi (JIRA)]

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

Myroslav Papirkovskyi updated AMBARI-18580:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Pushed to branch-2.4

> Delete host throws 500 Error with unique constraint violation
> -
>
> Key: AMBARI-18580
> URL: https://issues.apache.org/jira/browse/AMBARI-18580
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18580.patch
>
>
> Delete host request fails for blueprint deployed clusters in case when 
> topology_host_request with empty hostname exists.



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

[jira] [Commented] (AMBARI-18788) Checkboxes for installed services aren't disabled in Add Service Wizard

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18788:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5930 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5930/])
AMBARI-18788 Checkboxes for installed services aren't disabled in Add 
(ababiichuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=35cb39682551f05d100fdf4975a61eaf5cc58340])
* (edit) ambari-web/app/mappers/stack_service_mapper.js
* (edit) ambari-web/app/models/stack_service.js
* (edit) ambari-web/test/models/stack_service_test.js


> Checkboxes for installed services aren't disabled in Add Service Wizard
> ---
>
> Key: AMBARI-18788
> URL: https://issues.apache.org/jira/browse/AMBARI-18788
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18788.patch
>
>
> On Choose Services step of Add Service Wizard, checkboxes for installed 
> services aren't disabled, so user is able to uncheck them by mistake.



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

[jira] [Commented] (AMBARI-18789) Change the Wording of the HiveServer2 Non-Rolling Warning

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18789:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #260 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/260/])
AMBARI-18789 - Change the Wording of the HiveServer2 Non-Rolling Warning 
(jhurley: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e65e9986d7b0fcba06c978b96a1e98d89207110d])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/checks/CheckDescription.java


> Change the Wording of the HiveServer2 Non-Rolling Warning
> -
>
> Key: AMBARI-18789
> URL: https://issues.apache.org/jira/browse/AMBARI-18789
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: 2.5.0
>
> Attachments: AMBARI-18789.patch
>
>
> HiveServer2 is no longer rolling, even when choosing a rolling upgrade. The 
> warning message before upgrade might be a little misleading to users of the 
> Hive CLI. The new message should read:
> HiveServer2 Downtime
> HiveServer2 does not currently support rolling upgrades. HiveServer2 will be 
> upgraded, however existing queries which have been submitted will fail and 
> need to be resubmitted after HiveServer2 has been upgraded.



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

[jira] [Commented] (AMBARI-18790) Implement lazy loading for Service configs Advanced tab

[Andrii Tkach (JIRA)]

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

Andrii Tkach commented on AMBARI-18790:
---

+1 for the patch

> Implement lazy loading for Service configs Advanced tab
> ---
>
> Key: AMBARI-18790
> URL: https://issues.apache.org/jira/browse/AMBARI-18790
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-18790.patch
>
>
> We already have lazy loading for configs page in wizards. Let's implement the 
> same on service configs page.



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

[jira] [Updated] (AMBARI-18790) Implement lazy loading for Service configs Advanced tab

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko updated AMBARI-18790:
-
Attachment: AMBARI-18790.patch

> Implement lazy loading for Service configs Advanced tab
> ---
>
> Key: AMBARI-18790
> URL: https://issues.apache.org/jira/browse/AMBARI-18790
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-18790.patch
>
>
> We already have lazy loading for configs page in wizards. Let's implement the 
> same on service configs page.



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

[jira] [Updated] (AMBARI-18790) Implement lazy loading for Service configs Advanced tab

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko updated AMBARI-18790:
-
Status: Patch Available  (was: Open)

> Implement lazy loading for Service configs Advanced tab
> ---
>
> Key: AMBARI-18790
> URL: https://issues.apache.org/jira/browse/AMBARI-18790
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-18790.patch
>
>
> We already have lazy loading for configs page in wizards. Let's implement the 
> same on service configs page.



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

[jira] [Created] (AMBARI-18790) Implement lazy loading for Service configs Advanced tab

[Aleksandr Kovalenko (JIRA)]

Aleksandr Kovalenko created AMBARI-18790:


 Summary: Implement lazy loading for Service configs Advanced tab
 Key: AMBARI-18790
 URL: https://issues.apache.org/jira/browse/AMBARI-18790
 Project: Ambari
  Issue Type: Task
  Components: ambari-web
Affects Versions: 3.0.0
Reporter: Aleksandr Kovalenko
Assignee: Aleksandr Kovalenko
Priority: Critical
 Fix For: 3.0.0


We already have lazy loading for configs page in wizards. Let's implement the 
same on service configs page.



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

[jira] [Updated] (AMBARI-18789) Change the Wording of the HiveServer2 Non-Rolling Warning

[Jonathan Hurley (JIRA)]

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

Jonathan Hurley updated AMBARI-18789:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Change the Wording of the HiveServer2 Non-Rolling Warning
> -
>
> Key: AMBARI-18789
> URL: https://issues.apache.org/jira/browse/AMBARI-18789
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: 2.5.0
>
> Attachments: AMBARI-18789.patch
>
>
> HiveServer2 is no longer rolling, even when choosing a rolling upgrade. The 
> warning message before upgrade might be a little misleading to users of the 
> Hive CLI. The new message should read:
> HiveServer2 Downtime
> HiveServer2 does not currently support rolling upgrades. HiveServer2 will be 
> upgraded, however existing queries which have been submitted will fail and 
> need to be resubmitted after HiveServer2 has been upgraded.



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

[jira] [Commented] (AMBARI-18765) Services with invalid themes hang the UI when you attempt to add them

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18765:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5929 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5929/])
AMBARI-18765 - Services with invalid themes hang the UI when you attempt 
(tthorpe: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2ebc6ed957c468ef5b2e966094ad41b09ceb1fc5])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/stack/ServiceModule.java
* (add) 
ambari-server/src/test/resources/extensions/EXT/0.1/services/OOZIE2/themes/working_theme.json
* (edit) 
ambari-server/src/test/resources/extensions/EXT/0.1/services/OOZIE2/metainfo.xml
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/stack/StackManagerExtensionTest.java
* (edit) 
ambari-server/src/test/resources/extensions/EXT/0.2/services/OOZIE2/metainfo.xml
* (add) 
ambari-server/src/test/resources/extensions/EXT/0.2/services/OOZIE2/themes/broken_theme.json


> Services with invalid themes hang the UI when you attempt to add them
> -
>
> Key: AMBARI-18765
> URL: https://issues.apache.org/jira/browse/AMBARI-18765
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0, 2.5.0
>Reporter: Tim Thorpe
>Assignee: Tim Thorpe
> Fix For: trunk, 2.5.0, 2.4.2
>
> Attachments: AMBARI-18765.patch
>
>
> For a given service if the theme.json file is not properly formatted, Ambari 
> server will still start 'successfully' but attempts to add that service to 
> the cluster will fail.
> The Ambari server start will log the theme error.  Although it neglects to 
> mention which theme file and service are in error.
> When you attempt to add the service, it will query for the service's themes:
> api/v1/stacks//versions//services?StackServices/service_name.in(HDFS,YARN,MAPREDUCE2,ZOOKEEPER,RANGER,RANGER_KMS,SLIDER)/ThemeInfo/default=true=themes/*
> This will return something like the following for the invalid theme:
>  "ThemeInfo" : {
>"default" : true,
>"file_name" : "theme_version_2.json",
>"service_name" : "RANGER_KMS",
>"stack_name" : "BigInsights",
>"stack_version" : "4.3",
>"theme_data" : null
>  }
> where the theme_data is null.



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

[jira] [Commented] (AMBARI-18788) Checkboxes for installed services aren't disabled in Add Service Wizard

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18788:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #259 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/259/])
AMBARI-18788 Checkboxes for installed services aren't disabled in Add 
(ababiichuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3f9d541d7604a79eddea383e887f9f84262f7a83])
* (edit) ambari-web/app/models/stack_service.js
* (edit) ambari-web/app/mappers/stack_service_mapper.js
* (edit) ambari-web/test/models/stack_service_test.js


> Checkboxes for installed services aren't disabled in Add Service Wizard
> ---
>
> Key: AMBARI-18788
> URL: https://issues.apache.org/jira/browse/AMBARI-18788
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18788.patch
>
>
> On Choose Services step of Add Service Wizard, checkboxes for installed 
> services aren't disabled, so user is able to uncheck them by mistake.



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

[jira] [Commented] (AMBARI-18765) Services with invalid themes hang the UI when you attempt to add them

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18765:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #259 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/259/])
AMBARI-18765 - Services with invalid themes hang the UI when you attempt 
(tthorpe: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5593a342d9289c0ac659235475fe78415fcbb87a])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/stack/ServiceModule.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/stack/StackManagerExtensionTest.java
* (edit) 
ambari-server/src/test/resources/extensions/EXT/0.1/services/OOZIE2/metainfo.xml
* (add) 
ambari-server/src/test/resources/extensions/EXT/0.1/services/OOZIE2/themes/working_theme.json
* (add) 
ambari-server/src/test/resources/extensions/EXT/0.2/services/OOZIE2/themes/broken_theme.json
* (edit) 
ambari-server/src/test/resources/extensions/EXT/0.2/services/OOZIE2/metainfo.xml


> Services with invalid themes hang the UI when you attempt to add them
> -
>
> Key: AMBARI-18765
> URL: https://issues.apache.org/jira/browse/AMBARI-18765
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0, 2.5.0
>Reporter: Tim Thorpe
>Assignee: Tim Thorpe
> Fix For: trunk, 2.5.0, 2.4.2
>
> Attachments: AMBARI-18765.patch
>
>
> For a given service if the theme.json file is not properly formatted, Ambari 
> server will still start 'successfully' but attempts to add that service to 
> the cluster will fail.
> The Ambari server start will log the theme error.  Although it neglects to 
> mention which theme file and service are in error.
> When you attempt to add the service, it will query for the service's themes:
> api/v1/stacks//versions//services?StackServices/service_name.in(HDFS,YARN,MAPREDUCE2,ZOOKEEPER,RANGER,RANGER_KMS,SLIDER)/ThemeInfo/default=true=themes/*
> This will return something like the following for the invalid theme:
>  "ThemeInfo" : {
>"default" : true,
>"file_name" : "theme_version_2.json",
>"service_name" : "RANGER_KMS",
>"stack_name" : "BigInsights",
>"stack_version" : "4.3",
>"theme_data" : null
>  }
> where the theme_data is null.



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

[jira] [Updated] (AMBARI-18580) Delete host throws 500 Error with unique constraint violation

[Myroslav Papirkovskyi (JIRA)]

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

Myroslav Papirkovskyi updated AMBARI-18580:
---
Attachment: AMBARI-18580.patch

> Delete host throws 500 Error with unique constraint violation
> -
>
> Key: AMBARI-18580
> URL: https://issues.apache.org/jira/browse/AMBARI-18580
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18580.patch
>
>
> Delete host request fails for blueprint deployed clusters in case when 
> topology_host_request with empty hostname exists.



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

[jira] [Updated] (AMBARI-18580) Delete host throws 500 Error with unique constraint violation

[Myroslav Papirkovskyi (JIRA)]

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

Myroslav Papirkovskyi updated AMBARI-18580:
---
Attachment: (was: AMBARI-18580.patch)

> Delete host throws 500 Error with unique constraint violation
> -
>
> Key: AMBARI-18580
> URL: https://issues.apache.org/jira/browse/AMBARI-18580
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18580.patch
>
>
> Delete host request fails for blueprint deployed clusters in case when 
> topology_host_request with empty hostname exists.



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

[jira] [Updated] (AMBARI-18789) Change the Wording of the HiveServer2 Non-Rolling Warning

[Jonathan Hurley (JIRA)]

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

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

> Change the Wording of the HiveServer2 Non-Rolling Warning
> -
>
> Key: AMBARI-18789
> URL: https://issues.apache.org/jira/browse/AMBARI-18789
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: 2.5.0
>
> Attachments: AMBARI-18789.patch
>
>
> HiveServer2 is no longer rolling, even when choosing a rolling upgrade. The 
> warning message before upgrade might be a little misleading to users of the 
> Hive CLI. The new message should read:
> HiveServer2 Downtime
> HiveServer2 does not currently support rolling upgrades. HiveServer2 will be 
> upgraded, however existing queries which have been submitted will fail and 
> need to be resubmitted after HiveServer2 has been upgraded.



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

[jira] [Updated] (AMBARI-18765) Services with invalid themes hang the UI when you attempt to add them

[Tim Thorpe (JIRA)]

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

Tim Thorpe updated AMBARI-18765:

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

> Services with invalid themes hang the UI when you attempt to add them
> -
>
> Key: AMBARI-18765
> URL: https://issues.apache.org/jira/browse/AMBARI-18765
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0, 2.5.0
>Reporter: Tim Thorpe
>Assignee: Tim Thorpe
> Fix For: trunk, 2.5.0, 2.4.2
>
> Attachments: AMBARI-18765.patch
>
>
> For a given service if the theme.json file is not properly formatted, Ambari 
> server will still start 'successfully' but attempts to add that service to 
> the cluster will fail.
> The Ambari server start will log the theme error.  Although it neglects to 
> mention which theme file and service are in error.
> When you attempt to add the service, it will query for the service's themes:
> api/v1/stacks//versions//services?StackServices/service_name.in(HDFS,YARN,MAPREDUCE2,ZOOKEEPER,RANGER,RANGER_KMS,SLIDER)/ThemeInfo/default=true=themes/*
> This will return something like the following for the invalid theme:
>  "ThemeInfo" : {
>"default" : true,
>"file_name" : "theme_version_2.json",
>"service_name" : "RANGER_KMS",
>"stack_name" : "BigInsights",
>"stack_version" : "4.3",
>"theme_data" : null
>  }
> where the theme_data is null.



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

[jira] [Created] (AMBARI-18789) Change the Wording of the HiveServer2 Non-Rolling Warning

[Jonathan Hurley (JIRA)]

Jonathan Hurley created AMBARI-18789:


 Summary: Change the Wording of the HiveServer2 Non-Rolling Warning
 Key: AMBARI-18789
 URL: https://issues.apache.org/jira/browse/AMBARI-18789
 Project: Ambari
  Issue Type: Task
  Components: ambari-server
Affects Versions: 2.5.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
 Fix For: 2.5.0


HiveServer2 is no longer rolling, even when choosing a rolling upgrade. The 
warning message before upgrade might be a little misleading to users of the 
Hive CLI. The new message should read:

HiveServer2 Downtime
HiveServer2 does not currently support rolling upgrades. HiveServer2 will be 
upgraded, however existing queries which have been submitted will fail and need 
to be resubmitted after HiveServer2 has been upgraded.



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

[jira] [Commented] (AMBARI-18788) Checkboxes for installed services aren't disabled in Add Service Wizard

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18788:


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

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

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

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

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

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

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

This message is automatically generated.

> Checkboxes for installed services aren't disabled in Add Service Wizard
> ---
>
> Key: AMBARI-18788
> URL: https://issues.apache.org/jira/browse/AMBARI-18788
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18788.patch
>
>
> On Choose Services step of Add Service Wizard, checkboxes for installed 
> services aren't disabled, so user is able to uncheck them by mistake.



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

[jira] [Commented] (AMBARI-18788) Checkboxes for installed services aren't disabled in Add Service Wizard

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk commented on AMBARI-18788:
---

Committed to branch-2.5 and trunk

> Checkboxes for installed services aren't disabled in Add Service Wizard
> ---
>
> Key: AMBARI-18788
> URL: https://issues.apache.org/jira/browse/AMBARI-18788
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18788.patch
>
>
> On Choose Services step of Add Service Wizard, checkboxes for installed 
> services aren't disabled, so user is able to uncheck them by mistake.



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

[jira] [Updated] (AMBARI-18778) Ambari-server: Blueprint enhancements to support enabling or disabling credential store

[Nahappan Somasundaram (JIRA)]

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

Nahappan Somasundaram updated AMBARI-18778:
---
Status: Patch Available  (was: Open)

> Ambari-server: Blueprint enhancements to support enabling or disabling 
> credential store 
> 
>
> Key: AMBARI-18778
> URL: https://issues.apache.org/jira/browse/AMBARI-18778
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb53412.patch
>
>
> When deploying a cluster using a blueprint, users must be able to specify 
> whether they want to enable the use of hadoop credential store for a service 
> if it supports it.
> { "settings" :
> {
>   "service_settings" : [
>   { "name" : "RANGER",
> "recovery_enabled" : "true",
> "credential_store_enabled" : "true"
>   },
>   { "name" : "HIVE",
> "recovery_enabled" : "true",
> "credential_store_enabled" : "false"
>   }
>   ]
> }
> }



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

[jira] [Updated] (AMBARI-18778) Ambari-server: Blueprint enhancements to support enabling or disabling credential store

[Nahappan Somasundaram (JIRA)]

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

Nahappan Somasundaram updated AMBARI-18778:
---
Attachment: rb53412.patch

> Ambari-server: Blueprint enhancements to support enabling or disabling 
> credential store 
> 
>
> Key: AMBARI-18778
> URL: https://issues.apache.org/jira/browse/AMBARI-18778
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb53412.patch
>
>
> When deploying a cluster using a blueprint, users must be able to specify 
> whether they want to enable the use of hadoop credential store for a service 
> if it supports it.
> { "settings" :
> {
>   "service_settings" : [
>   { "name" : "RANGER",
> "recovery_enabled" : "true",
> "credential_store_enabled" : "true"
>   },
>   { "name" : "HIVE",
> "recovery_enabled" : "true",
> "credential_store_enabled" : "false"
>   }
>   ]
> }
> }



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

[jira] [Updated] (AMBARI-18778) Ambari-server: Blueprint enhancements to support enabling or disabling credential store

[Nahappan Somasundaram (JIRA)]

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

Nahappan Somasundaram updated AMBARI-18778:
---
Attachment: (was: rb53412.patch)

> Ambari-server: Blueprint enhancements to support enabling or disabling 
> credential store 
> 
>
> Key: AMBARI-18778
> URL: https://issues.apache.org/jira/browse/AMBARI-18778
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb53412.patch
>
>
> When deploying a cluster using a blueprint, users must be able to specify 
> whether they want to enable the use of hadoop credential store for a service 
> if it supports it.
> { "settings" :
> {
>   "service_settings" : [
>   { "name" : "RANGER",
> "recovery_enabled" : "true",
> "credential_store_enabled" : "true"
>   },
>   { "name" : "HIVE",
> "recovery_enabled" : "true",
> "credential_store_enabled" : "false"
>   }
>   ]
> }
> }



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

[jira] [Updated] (AMBARI-18778) Ambari-server: Blueprint enhancements to support enabling or disabling credential store

[Nahappan Somasundaram (JIRA)]

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

Nahappan Somasundaram updated AMBARI-18778:
---
Status: Open  (was: Patch Available)

> Ambari-server: Blueprint enhancements to support enabling or disabling 
> credential store 
> 
>
> Key: AMBARI-18778
> URL: https://issues.apache.org/jira/browse/AMBARI-18778
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb53412.patch
>
>
> When deploying a cluster using a blueprint, users must be able to specify 
> whether they want to enable the use of hadoop credential store for a service 
> if it supports it.
> { "settings" :
> {
>   "service_settings" : [
>   { "name" : "RANGER",
> "recovery_enabled" : "true",
> "credential_store_enabled" : "true"
>   },
>   { "name" : "HIVE",
> "recovery_enabled" : "true",
> "credential_store_enabled" : "false"
>   }
>   ]
> }
> }



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

[jira] [Commented] (AMBARI-18786) HDP Upgrade fails when the cluster size is large

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18786:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #258 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/258/])
AMBARI-18786. HDP Upgrade fails when the cluster size is large (dlysnichenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7d2b6bbc0a9fa3e7ee667be30b53b83d60f90a79])
* (edit) 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py


> HDP Upgrade fails when the cluster size is large
> 
>
> Key: AMBARI-18786
> URL: https://issues.apache.org/jira/browse/AMBARI-18786
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.5.0
>
> Attachments: AMBARI-18786.patch
>
>
> Starting from Ambari 2.4, when the cluster is large, HDP upgrade fails during 
> namenode restart.
> This is because, restart command waits for namenode to come out of safemode 
> and if the cluster size is large, namenode takes more time to leave safemode 
> but Ambari marks this action as failure as the namenode didn't leave safemode 
> within the configured timeout in Ambari scripts.
> {code}
> Traceback (most recent call last):
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
>  line 42, in get_value_from_jmx
> return data_dict["beans"][0][property]
> IndexError: list index out of range
> Traceback (most recent call last):
> File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
>  line 420, in 
> NameNode().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 720, in restart
> self.start(env, upgrade_type=upgrade_type)
> File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
>  line 101, in start
> upgrade_suspended=params.upgrade_suspended, env=env)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", 
> line 89, in thunk
> return fn(*args, **kwargs)
> File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py",
>  line 184, in namenode
> if is_this_namenode_active() is False:
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/decorator.py",
>  line 55, in wrapper
> return function(*args, **kwargs)
> File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py",
>  line 554, in is_this_namenode_active
> raise Fail(format("The NameNode {namenode_id} is not listed as Active or 
> Standby, waiting..."))
> resource_management.core.exceptions.Fail: The NameNode nn1 is not listed as 
> Active or Standby, waiting...
> {code}
> To resolve this, we increased the timeout for ambari
> 1. Increased the timeout in 
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py
>  from this;
> @retry(times=5, sleep_time=5, backoff_factor=2, err_class=Fail)
> to this;
> @retry(times=25, sleep_time=25, backoff_factor=2, err_class=Fail)
> 2. Restart Ambari server
> After this upgrade went through fine.
> I think its better to increase the timeout permanently so that we don't have 
> to deal with this issue again.



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

[jira] [Commented] (AMBARI-18786) HDP Upgrade fails when the cluster size is large

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18786:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5928 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5928/])
AMBARI-18786. HDP Upgrade fails when the cluster size is large (dlysnichenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ba5cbf428194733b93ff122dbe4b66706f75e676])
* (edit) 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py


> HDP Upgrade fails when the cluster size is large
> 
>
> Key: AMBARI-18786
> URL: https://issues.apache.org/jira/browse/AMBARI-18786
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.5.0
>
> Attachments: AMBARI-18786.patch
>
>
> Starting from Ambari 2.4, when the cluster is large, HDP upgrade fails during 
> namenode restart.
> This is because, restart command waits for namenode to come out of safemode 
> and if the cluster size is large, namenode takes more time to leave safemode 
> but Ambari marks this action as failure as the namenode didn't leave safemode 
> within the configured timeout in Ambari scripts.
> {code}
> Traceback (most recent call last):
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
>  line 42, in get_value_from_jmx
> return data_dict["beans"][0][property]
> IndexError: list index out of range
> Traceback (most recent call last):
> File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
>  line 420, in 
> NameNode().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 720, in restart
> self.start(env, upgrade_type=upgrade_type)
> File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
>  line 101, in start
> upgrade_suspended=params.upgrade_suspended, env=env)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", 
> line 89, in thunk
> return fn(*args, **kwargs)
> File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py",
>  line 184, in namenode
> if is_this_namenode_active() is False:
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/decorator.py",
>  line 55, in wrapper
> return function(*args, **kwargs)
> File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py",
>  line 554, in is_this_namenode_active
> raise Fail(format("The NameNode {namenode_id} is not listed as Active or 
> Standby, waiting..."))
> resource_management.core.exceptions.Fail: The NameNode nn1 is not listed as 
> Active or Standby, waiting...
> {code}
> To resolve this, we increased the timeout for ambari
> 1. Increased the timeout in 
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py
>  from this;
> @retry(times=5, sleep_time=5, backoff_factor=2, err_class=Fail)
> to this;
> @retry(times=25, sleep_time=25, backoff_factor=2, err_class=Fail)
> 2. Restart Ambari server
> After this upgrade went through fine.
> I think its better to increase the timeout permanently so that we don't have 
> to deal with this issue again.



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

[jira] [Commented] (AMBARI-18788) Checkboxes for installed services aren't disabled in Add Service Wizard

[Andrii Tkach (JIRA)]

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

Andrii Tkach commented on AMBARI-18788:
---

+1 for the patch

> Checkboxes for installed services aren't disabled in Add Service Wizard
> ---
>
> Key: AMBARI-18788
> URL: https://issues.apache.org/jira/browse/AMBARI-18788
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18788.patch
>
>
> On Choose Services step of Add Service Wizard, checkboxes for installed 
> services aren't disabled, so user is able to uncheck them by mistake.



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

[jira] [Updated] (AMBARI-18788) Checkboxes for installed services aren't disabled in Add Service Wizard

[Andrii Babiichuk (JIRA)]

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

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

> Checkboxes for installed services aren't disabled in Add Service Wizard
> ---
>
> Key: AMBARI-18788
> URL: https://issues.apache.org/jira/browse/AMBARI-18788
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18788.patch
>
>
> On Choose Services step of Add Service Wizard, checkboxes for installed 
> services aren't disabled, so user is able to uncheck them by mistake.



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

[jira] [Updated] (AMBARI-18788) Checkboxes for installed services aren't disabled in Add Service Wizard

[Andrii Babiichuk (JIRA)]

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

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

> Checkboxes for installed services aren't disabled in Add Service Wizard
> ---
>
> Key: AMBARI-18788
> URL: https://issues.apache.org/jira/browse/AMBARI-18788
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18788.patch
>
>
> On Choose Services step of Add Service Wizard, checkboxes for installed 
> services aren't disabled, so user is able to uncheck them by mistake.



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

[jira] [Created] (AMBARI-18788) Checkboxes for installed services aren't disabled in Add Service Wizard

[Andrii Babiichuk (JIRA)]

Andrii Babiichuk created AMBARI-18788:
-

 Summary: Checkboxes for installed services aren't disabled in Add 
Service Wizard
 Key: AMBARI-18788
 URL: https://issues.apache.org/jira/browse/AMBARI-18788
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.5.0
Reporter: Andrii Babiichuk
Assignee: Andrii Babiichuk
Priority: Critical
 Fix For: 2.5.0


On Choose Services step of Add Service Wizard, checkboxes for installed 
services aren't disabled, so user is able to uncheck them by mistake.



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

[jira] [Updated] (AMBARI-18787) Correct service Configs page styling

[Andrii Tkach (JIRA)]

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

Andrii Tkach updated AMBARI-18787:
--
Status: Patch Available  (was: Open)

> Correct service Configs page styling
> 
>
> Key: AMBARI-18787
> URL: https://issues.apache.org/jira/browse/AMBARI-18787
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-18787.patch
>
>
> # Fix padding in config version box
> # Fix version bar and version labels while comparing versions
> # JS error when switching to non-default config group



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

[jira] [Commented] (AMBARI-18787) Correct service Configs page styling

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko commented on AMBARI-18787:
--

+1 for the patch

> Correct service Configs page styling
> 
>
> Key: AMBARI-18787
> URL: https://issues.apache.org/jira/browse/AMBARI-18787
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-18787.patch
>
>
> # Fix padding in config version box
> # Fix version bar and version labels while comparing versions
> # JS error when switching to non-default config group



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

[jira] [Commented] (AMBARI-18787) Correct service Configs page styling

[Andrii Tkach (JIRA)]

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

Andrii Tkach commented on AMBARI-18787:
---

30324 tests complete (33 seconds)
  151 tests pending

> Correct service Configs page styling
> 
>
> Key: AMBARI-18787
> URL: https://issues.apache.org/jira/browse/AMBARI-18787
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-18787.patch
>
>
> # Fix padding in config version box
> # Fix version bar and version labels while comparing versions
> # JS error when switching to non-default config group



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

[jira] [Updated] (AMBARI-18787) Correct service Configs page styling

[Andrii Tkach (JIRA)]

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

Andrii Tkach updated AMBARI-18787:
--
Attachment: AMBARI-18787.patch

> Correct service Configs page styling
> 
>
> Key: AMBARI-18787
> URL: https://issues.apache.org/jira/browse/AMBARI-18787
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-18787.patch
>
>
> # Fix padding in config version box
> # Fix version bar and version labels while comparing versions
> # JS error when switching to non-default config group



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

[jira] [Created] (AMBARI-18787) Correct service Configs page styling

[Andrii Tkach (JIRA)]

Andrii Tkach created AMBARI-18787:
-

 Summary: Correct service Configs page styling
 Key: AMBARI-18787
 URL: https://issues.apache.org/jira/browse/AMBARI-18787
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 3.0.0
Reporter: Andrii Tkach
Assignee: Andrii Tkach
 Fix For: 3.0.0


# Fix padding in config version box
# Fix version bar and version labels while comparing versions
# JS error when switching to non-default config group



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

[jira] [Updated] (AMBARI-18680) Add orchestration for HOST_ORDERED upgrades

[Nate Cole (JIRA)]

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

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

> Add orchestration for HOST_ORDERED upgrades
> ---
>
> Key: AMBARI-18680
> URL: https://issues.apache.org/jira/browse/AMBARI-18680
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18680.patch
>
>
> Orchestration via UpgradeHelper need to orchestrate via HOSTS instead of the 
> UpgradePack services.  This will entail:
> * Refactor UpgradeHelper to choose orchestration model
> * Upgrade Pack changes are minimal, StageWrapper and Manual tasks are 
> generated in-code.
> * Determine service check changes (if any)
> * HostGrouping should use the following stages per-host:
> *# Stop command for each component
> *# Manual message to ask to proceed
> *# {{install_packages}} task - ONE per host.  The purpose is to make sure all 
> the symlink logic already in place is called correctly
> *# START commands for daemons, INSTALL commands for clients, just as a new 
> cluster would do.



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

[jira] [Updated] (AMBARI-18786) HDP Upgrade fails when the cluster size is large

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-18786:

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

Committed

To https://git-wip-us.apache.org/repos/asf/ambari.git
   819dbff..7d2b6bb  branch-2.5 -> branch-2.5
   43a181a..ba5cbf4  trunk -> trunk


> HDP Upgrade fails when the cluster size is large
> 
>
> Key: AMBARI-18786
> URL: https://issues.apache.org/jira/browse/AMBARI-18786
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.5.0
>
> Attachments: AMBARI-18786.patch
>
>
> Starting from Ambari 2.4, when the cluster is large, HDP upgrade fails during 
> namenode restart.
> This is because, restart command waits for namenode to come out of safemode 
> and if the cluster size is large, namenode takes more time to leave safemode 
> but Ambari marks this action as failure as the namenode didn't leave safemode 
> within the configured timeout in Ambari scripts.
> {code}
> Traceback (most recent call last):
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
>  line 42, in get_value_from_jmx
> return data_dict["beans"][0][property]
> IndexError: list index out of range
> Traceback (most recent call last):
> File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
>  line 420, in 
> NameNode().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 720, in restart
> self.start(env, upgrade_type=upgrade_type)
> File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
>  line 101, in start
> upgrade_suspended=params.upgrade_suspended, env=env)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", 
> line 89, in thunk
> return fn(*args, **kwargs)
> File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py",
>  line 184, in namenode
> if is_this_namenode_active() is False:
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/decorator.py",
>  line 55, in wrapper
> return function(*args, **kwargs)
> File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py",
>  line 554, in is_this_namenode_active
> raise Fail(format("The NameNode {namenode_id} is not listed as Active or 
> Standby, waiting..."))
> resource_management.core.exceptions.Fail: The NameNode nn1 is not listed as 
> Active or Standby, waiting...
> {code}
> To resolve this, we increased the timeout for ambari
> 1. Increased the timeout in 
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py
>  from this;
> @retry(times=5, sleep_time=5, backoff_factor=2, err_class=Fail)
> to this;
> @retry(times=25, sleep_time=25, backoff_factor=2, err_class=Fail)
> 2. Restart Ambari server
> After this upgrade went through fine.
> I think its better to increase the timeout permanently so that we don't have 
> to deal with this issue again.



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

[jira] [Updated] (AMBARI-18580) Delete host throws 500 Error with unique constraint violation

[Myroslav Papirkovskyi (JIRA)]

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

Myroslav Papirkovskyi updated AMBARI-18580:
---
Attachment: (was: AMBARI-18580.patch)

> Delete host throws 500 Error with unique constraint violation
> -
>
> Key: AMBARI-18580
> URL: https://issues.apache.org/jira/browse/AMBARI-18580
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18580.patch
>
>
> Delete host request fails for blueprint deployed clusters in case when 
> topology_host_request with empty hostname exists.



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

[jira] [Commented] (AMBARI-18782) Disable HDP-2.2 stack

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18782:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #257 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/257/])
AMBARI-18782. Disable HDP-2.2 stack (dgrinenko via dlysnichenko) (dlysnichenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=819dbff2fd3eee78e659b35992dd150cb2179234])
* (delete) 
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.3.xml
* (delete) 
ambari-server/src/main/resources/stacks/HDP/2.1/upgrades/nonrolling-upgrade-2.3.xml
* (delete) 
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.4.xml
* (delete) 
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/config-upgrade.xml
* (delete) 
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.4.xml
* (delete) 
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.3.xml
* (delete) 
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.2.xml
* (edit) ambari-server/src/main/resources/stacks/HDP/2.2/metainfo.xml
* (delete) 
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.2.xml


> Disable HDP-2.2 stack
> -
>
> Key: AMBARI-18782
> URL: https://issues.apache.org/jira/browse/AMBARI-18782
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Dmytro Grinenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-18782-trunk.patch, AMBARI-18782.patch
>
>
> We need to disable HDP-2.2 in the codebase and remove Upgrade Packs out of 
> the 2.2 directory.



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

[jira] [Updated] (AMBARI-18783) Incorrect behaviour of Copy/Open controls for task details

[Oleg Nechiporenko (JIRA)]

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

Oleg Nechiporenko updated AMBARI-18783:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Incorrect behaviour of Copy/Open controls for task details
> --
>
> Key: AMBARI-18783
> URL: https://issues.apache.org/jira/browse/AMBARI-18783
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-18783.patch
>
>
> Host progress popup (displayed on deploy steps of different wizards, in 
> background opertations view etc.) allows to open stderr and stdout of certain 
> task in new window. There are some issues with this feature.



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

[jira] [Commented] (AMBARI-18783) Incorrect behaviour of Copy/Open controls for task details

[Oleg Nechiporenko (JIRA)]

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

Oleg Nechiporenko commented on AMBARI-18783:


Build failed not because of this patch
{noformat}
[INFO] Ambari Web . SUCCESS [02:42 min]
[INFO] Ambari Server .. FAILURE [15:28 min]
{noformat}

> Incorrect behaviour of Copy/Open controls for task details
> --
>
> Key: AMBARI-18783
> URL: https://issues.apache.org/jira/browse/AMBARI-18783
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-18783.patch
>
>
> Host progress popup (displayed on deploy steps of different wizards, in 
> background opertations view etc.) allows to open stderr and stdout of certain 
> task in new window. There are some issues with this feature.



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

[jira] [Commented] (AMBARI-18782) Disable HDP-2.2 stack

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18782:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5927 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5927/])
AMBARI-18782. Disable HDP-2.2 stack (dgrinenko via dlysnichenko) (dlysnichenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=43a181ab35fb9f414b5b148aadf43b7199329953])
* (delete) 
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.4.xml
* (delete) 
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.2.xml
* (delete) 
ambari-server/src/main/resources/stacks/HDP/2.1/upgrades/nonrolling-upgrade-2.3.xml
* (delete) 
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/config-upgrade.xml
* (delete) 
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.3.xml
* (edit) ambari-server/src/main/resources/stacks/HDP/2.2/metainfo.xml
* (delete) 
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.2.xml


> Disable HDP-2.2 stack
> -
>
> Key: AMBARI-18782
> URL: https://issues.apache.org/jira/browse/AMBARI-18782
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Dmytro Grinenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-18782-trunk.patch, AMBARI-18782.patch
>
>
> We need to disable HDP-2.2 in the codebase and remove Upgrade Packs out of 
> the 2.2 directory.



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

[jira] [Updated] (AMBARI-18786) HDP Upgrade fails when the cluster size is large

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-18786:

Fix Version/s: 2.5.0

> HDP Upgrade fails when the cluster size is large
> 
>
> Key: AMBARI-18786
> URL: https://issues.apache.org/jira/browse/AMBARI-18786
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.5.0
>
> Attachments: AMBARI-18786.patch
>
>
> Starting from Ambari 2.4, when the cluster is large, HDP upgrade fails during 
> namenode restart.
> This is because, restart command waits for namenode to come out of safemode 
> and if the cluster size is large, namenode takes more time to leave safemode 
> but Ambari marks this action as failure as the namenode didn't leave safemode 
> within the configured timeout in Ambari scripts.
> {code}
> Traceback (most recent call last):
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
>  line 42, in get_value_from_jmx
> return data_dict["beans"][0][property]
> IndexError: list index out of range
> Traceback (most recent call last):
> File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
>  line 420, in 
> NameNode().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 720, in restart
> self.start(env, upgrade_type=upgrade_type)
> File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
>  line 101, in start
> upgrade_suspended=params.upgrade_suspended, env=env)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", 
> line 89, in thunk
> return fn(*args, **kwargs)
> File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py",
>  line 184, in namenode
> if is_this_namenode_active() is False:
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/decorator.py",
>  line 55, in wrapper
> return function(*args, **kwargs)
> File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py",
>  line 554, in is_this_namenode_active
> raise Fail(format("The NameNode {namenode_id} is not listed as Active or 
> Standby, waiting..."))
> resource_management.core.exceptions.Fail: The NameNode nn1 is not listed as 
> Active or Standby, waiting...
> {code}
> To resolve this, we increased the timeout for ambari
> 1. Increased the timeout in 
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py
>  from this;
> @retry(times=5, sleep_time=5, backoff_factor=2, err_class=Fail)
> to this;
> @retry(times=25, sleep_time=25, backoff_factor=2, err_class=Fail)
> 2. Restart Ambari server
> After this upgrade went through fine.
> I think its better to increase the timeout permanently so that we don't have 
> to deal with this issue again.



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

[jira] [Created] (AMBARI-18786) HDP Upgrade fails when the cluster size is large

[Dmitry Lysnichenko (JIRA)]

Dmitry Lysnichenko created AMBARI-18786:
---

 Summary: HDP Upgrade fails when the cluster size is large
 Key: AMBARI-18786
 URL: https://issues.apache.org/jira/browse/AMBARI-18786
 Project: Ambari
  Issue Type: Bug
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
 Attachments: AMBARI-18786.patch


Starting from Ambari 2.4, when the cluster is large, HDP upgrade fails during 
namenode restart.

This is because, restart command waits for namenode to come out of safemode and 
if the cluster size is large, namenode takes more time to leave safemode but 
Ambari marks this action as failure as the namenode didn't leave safemode 
within the configured timeout in Ambari scripts.


{code}

Traceback (most recent call last):
File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
 line 42, in get_value_from_jmx
return data_dict["beans"][0][property]
IndexError: list index out of range
Traceback (most recent call last):
File 
"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
 line 420, in 
NameNode().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 720, in restart
self.start(env, upgrade_type=upgrade_type)
File 
"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
 line 101, in start
upgrade_suspended=params.upgrade_suspended, env=env)
File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", line 
89, in thunk
return fn(*args, **kwargs)
File 
"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py",
 line 184, in namenode
if is_this_namenode_active() is False:
File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/decorator.py",
 line 55, in wrapper
return function(*args, **kwargs)
File 
"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py",
 line 554, in is_this_namenode_active
raise Fail(format("The NameNode {namenode_id} is not listed as Active or 
Standby, waiting..."))
resource_management.core.exceptions.Fail: The NameNode nn1 is not listed as 
Active or Standby, waiting...
{code}

To resolve this, we increased the timeout for ambari

1. Increased the timeout in 
/var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py
 from this;
@retry(times=5, sleep_time=5, backoff_factor=2, err_class=Fail)
to this;
@retry(times=25, sleep_time=25, backoff_factor=2, err_class=Fail)

2. Restart Ambari server

After this upgrade went through fine.

I think its better to increase the timeout permanently so that we don't have to 
deal with this issue again.





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

[jira] [Updated] (AMBARI-18786) HDP Upgrade fails when the cluster size is large

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-18786:

Attachment: AMBARI-18786.patch

> HDP Upgrade fails when the cluster size is large
> 
>
> Key: AMBARI-18786
> URL: https://issues.apache.org/jira/browse/AMBARI-18786
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Attachments: AMBARI-18786.patch
>
>
> Starting from Ambari 2.4, when the cluster is large, HDP upgrade fails during 
> namenode restart.
> This is because, restart command waits for namenode to come out of safemode 
> and if the cluster size is large, namenode takes more time to leave safemode 
> but Ambari marks this action as failure as the namenode didn't leave safemode 
> within the configured timeout in Ambari scripts.
> {code}
> Traceback (most recent call last):
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
>  line 42, in get_value_from_jmx
> return data_dict["beans"][0][property]
> IndexError: list index out of range
> Traceback (most recent call last):
> File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
>  line 420, in 
> NameNode().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 720, in restart
> self.start(env, upgrade_type=upgrade_type)
> File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
>  line 101, in start
> upgrade_suspended=params.upgrade_suspended, env=env)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", 
> line 89, in thunk
> return fn(*args, **kwargs)
> File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py",
>  line 184, in namenode
> if is_this_namenode_active() is False:
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/decorator.py",
>  line 55, in wrapper
> return function(*args, **kwargs)
> File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py",
>  line 554, in is_this_namenode_active
> raise Fail(format("The NameNode {namenode_id} is not listed as Active or 
> Standby, waiting..."))
> resource_management.core.exceptions.Fail: The NameNode nn1 is not listed as 
> Active or Standby, waiting...
> {code}
> To resolve this, we increased the timeout for ambari
> 1. Increased the timeout in 
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py
>  from this;
> @retry(times=5, sleep_time=5, backoff_factor=2, err_class=Fail)
> to this;
> @retry(times=25, sleep_time=25, backoff_factor=2, err_class=Fail)
> 2. Restart Ambari server
> After this upgrade went through fine.
> I think its better to increase the timeout permanently so that we don't have 
> to deal with this issue again.



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

[jira] [Updated] (AMBARI-18786) HDP Upgrade fails when the cluster size is large

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-18786:

Component/s: ambari-server

> HDP Upgrade fails when the cluster size is large
> 
>
> Key: AMBARI-18786
> URL: https://issues.apache.org/jira/browse/AMBARI-18786
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Attachments: AMBARI-18786.patch
>
>
> Starting from Ambari 2.4, when the cluster is large, HDP upgrade fails during 
> namenode restart.
> This is because, restart command waits for namenode to come out of safemode 
> and if the cluster size is large, namenode takes more time to leave safemode 
> but Ambari marks this action as failure as the namenode didn't leave safemode 
> within the configured timeout in Ambari scripts.
> {code}
> Traceback (most recent call last):
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
>  line 42, in get_value_from_jmx
> return data_dict["beans"][0][property]
> IndexError: list index out of range
> Traceback (most recent call last):
> File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
>  line 420, in 
> NameNode().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 720, in restart
> self.start(env, upgrade_type=upgrade_type)
> File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
>  line 101, in start
> upgrade_suspended=params.upgrade_suspended, env=env)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", 
> line 89, in thunk
> return fn(*args, **kwargs)
> File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py",
>  line 184, in namenode
> if is_this_namenode_active() is False:
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/decorator.py",
>  line 55, in wrapper
> return function(*args, **kwargs)
> File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py",
>  line 554, in is_this_namenode_active
> raise Fail(format("The NameNode {namenode_id} is not listed as Active or 
> Standby, waiting..."))
> resource_management.core.exceptions.Fail: The NameNode nn1 is not listed as 
> Active or Standby, waiting...
> {code}
> To resolve this, we increased the timeout for ambari
> 1. Increased the timeout in 
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py
>  from this;
> @retry(times=5, sleep_time=5, backoff_factor=2, err_class=Fail)
> to this;
> @retry(times=25, sleep_time=25, backoff_factor=2, err_class=Fail)
> 2. Restart Ambari server
> After this upgrade went through fine.
> I think its better to increase the timeout permanently so that we don't have 
> to deal with this issue again.



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

[jira] [Created] (AMBARI-18785) HDP Upgrade fails when the cluster size is large

[Dmitry Lysnichenko (JIRA)]

Dmitry Lysnichenko created AMBARI-18785:
---

 Summary: HDP Upgrade fails when the cluster size is large
 Key: AMBARI-18785
 URL: https://issues.apache.org/jira/browse/AMBARI-18785
 Project: Ambari
  Issue Type: Bug
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko



Starting from Ambari 2.4, when the cluster is large, HDP upgrade fails during 
namenode restart.

This is because, restart command waits for namenode to come out of safemode and 
if the cluster size is large, namenode takes more time to leave safemode but 
Ambari marks this action as failure as the namenode didn't leave safemode 
within the configured timeout in Ambari scripts.


{code}

Traceback (most recent call last):
File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
 line 42, in get_value_from_jmx
return data_dict["beans"][0][property]
IndexError: list index out of range
Traceback (most recent call last):
File 
"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
 line 420, in 
NameNode().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 720, in restart
self.start(env, upgrade_type=upgrade_type)
File 
"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
 line 101, in start
upgrade_suspended=params.upgrade_suspended, env=env)
File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", line 
89, in thunk
return fn(*args, **kwargs)
File 
"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py",
 line 184, in namenode
if is_this_namenode_active() is False:
File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/decorator.py",
 line 55, in wrapper
return function(*args, **kwargs)
File 
"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py",
 line 554, in is_this_namenode_active
raise Fail(format("The NameNode {namenode_id} is not listed as Active or 
Standby, waiting..."))
resource_management.core.exceptions.Fail: The NameNode nn1 is not listed as 
Active or Standby, waiting...
{code}

To resolve this, we increased the timeout for ambari

1. Increased the timeout in 
/var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py
 from this;
@retry(times=5, sleep_time=5, backoff_factor=2, err_class=Fail)
to this;
@retry(times=25, sleep_time=25, backoff_factor=2, err_class=Fail)

2. Restart Ambari server

After this upgrade went through fine.

I think its better to increase the timeout permanently so that we don't have to 
deal with this issue again.





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

[jira] [Updated] (AMBARI-18786) HDP Upgrade fails when the cluster size is large

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-18786:

Status: Patch Available  (was: Open)

> HDP Upgrade fails when the cluster size is large
> 
>
> Key: AMBARI-18786
> URL: https://issues.apache.org/jira/browse/AMBARI-18786
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Attachments: AMBARI-18786.patch
>
>
> Starting from Ambari 2.4, when the cluster is large, HDP upgrade fails during 
> namenode restart.
> This is because, restart command waits for namenode to come out of safemode 
> and if the cluster size is large, namenode takes more time to leave safemode 
> but Ambari marks this action as failure as the namenode didn't leave safemode 
> within the configured timeout in Ambari scripts.
> {code}
> Traceback (most recent call last):
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
>  line 42, in get_value_from_jmx
> return data_dict["beans"][0][property]
> IndexError: list index out of range
> Traceback (most recent call last):
> File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
>  line 420, in 
> NameNode().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 720, in restart
> self.start(env, upgrade_type=upgrade_type)
> File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
>  line 101, in start
> upgrade_suspended=params.upgrade_suspended, env=env)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", 
> line 89, in thunk
> return fn(*args, **kwargs)
> File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py",
>  line 184, in namenode
> if is_this_namenode_active() is False:
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/decorator.py",
>  line 55, in wrapper
> return function(*args, **kwargs)
> File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py",
>  line 554, in is_this_namenode_active
> raise Fail(format("The NameNode {namenode_id} is not listed as Active or 
> Standby, waiting..."))
> resource_management.core.exceptions.Fail: The NameNode nn1 is not listed as 
> Active or Standby, waiting...
> {code}
> To resolve this, we increased the timeout for ambari
> 1. Increased the timeout in 
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py
>  from this;
> @retry(times=5, sleep_time=5, backoff_factor=2, err_class=Fail)
> to this;
> @retry(times=25, sleep_time=25, backoff_factor=2, err_class=Fail)
> 2. Restart Ambari server
> After this upgrade went through fine.
> I think its better to increase the timeout permanently so that we don't have 
> to deal with this issue again.



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

[jira] [Updated] (AMBARI-18782) Disable HDP-2.2 stack

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-18782:

Resolution: Fixed
  Assignee: Dmitry Lysnichenko
Status: Resolved  (was: Patch Available)

Committed

To https://git-wip-us.apache.org/repos/asf/ambari.git
   775d4bd..819dbff  branch-2.5 -> branch-2.5
   e719ea4..43a181a  trunk -> trunk


> Disable HDP-2.2 stack
> -
>
> Key: AMBARI-18782
> URL: https://issues.apache.org/jira/browse/AMBARI-18782
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Dmytro Grinenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-18782-trunk.patch, AMBARI-18782.patch
>
>
> We need to disable HDP-2.2 in the codebase and remove Upgrade Packs out of 
> the 2.2 directory.



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

[jira] [Commented] (AMBARI-18784) Some static attributes of config properties are lost after return to Customize Services step of Add Service Wizard

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18784:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5926 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5926/])
AMBARI-18784 Some static attributes of config properties are lost after 
(ababiichuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=753b8d5a0fe4866cc3350fdcfdf9509a5a3fbf59])
* (edit) ambari-web/app/controllers/wizard.js
* (edit) ambari-web/app/controllers/wizard/step7_controller.js
* (edit) ambari-web/test/controllers/wizard_test.js
* (edit) ambari-web/app/utils/config.js


> Some static attributes of config properties are lost after return to 
> Customize Services step of Add Service Wizard
> --
>
> Key: AMBARI-18784
> URL: https://issues.apache.org/jira/browse/AMBARI-18784
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.2
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18784-branch-2.4.patch, 
> AMBARI-18784-branch-2.5.patch, AMBARI-18784-trunk.patch
>
>
> *STR*
> # Complete Customize Services step of Add Service Wizard.
> # Refresh page.
> # Go back to Customize Services.
> *Result*
> Static attributes like isUserProperty, isRequiredByAgent are not restored.



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

[jira] [Commented] (AMBARI-18783) Incorrect behaviour of Copy/Open controls for task details

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18783:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5926 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5926/])
AMBARI-18783. Incorrect behaviour of Copy/Open controls for task details 
(onechiporenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e719ea44d190cba118934e8f993cff8a8b8119cb])
* (edit) ambari-web/app/templates/common/modal_popups/logs_popup.hbs
* (edit) ambari-web/app/templates/main/admin/stack_upgrade/versions.hbs
* (edit) ambari-web/app/styles/application.less
* (edit) ambari-web/app/views.js
* (edit) ambari-web/app/views/common/modal_popups/log_tail_popup.js
* (edit) ambari-web/app/templates/main/admin/stack_upgrade/upgrade_task.hbs
* (edit) ambari-web/app/styles/log_file_search.less
* (edit) ambari-web/app/templates/wizard/step9/step9HostTasksLogPopup.hbs
* (add) ambari-web/app/views/common/not-scrollable-textarea.js
* (edit) ambari-web/app/templates/common/host_progress_popup.hbs
* (edit) ambari-web/app/templates/main/host/logs.hbs
* (edit) ambari-web/app/templates/common/log_file_search.hbs
* (edit) ambari-web/app/templates/common/modal_popups/log_tail_popup.hbs
* (edit) ambari-web/app/views/wizard/step9/hostLogPopupBody_view.js
* (edit) ambari-web/test/views/common/host_progress_popup_body_view_test.js
* (edit) 
ambari-web/app/templates/main/admin/stack_upgrade/upgrade_configs_merge_table.hbs
* (edit) ambari-web/app/styles/modal_popups.less
* (edit) ambari-web/app/views/common/host_progress_popup_body_view.js


> Incorrect behaviour of Copy/Open controls for task details
> --
>
> Key: AMBARI-18783
> URL: https://issues.apache.org/jira/browse/AMBARI-18783
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-18783.patch
>
>
> Host progress popup (displayed on deploy steps of different wizards, in 
> background opertations view etc.) allows to open stderr and stdout of certain 
> task in new window. There are some issues with this feature.



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

[jira] [Commented] (AMBARI-18784) Some static attributes of config properties are lost after return to Customize Services step of Add Service Wizard

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18784:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #256 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/256/])
AMBARI-18784 Some static attributes of config properties are lost after 
(ababiichuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=775d4bd8501eb426a9892f302bb8c6f84775532b])
* (edit) ambari-web/app/controllers/wizard.js
* (edit) ambari-web/app/utils/config.js
* (edit) ambari-web/test/controllers/wizard_test.js
* (edit) ambari-web/app/controllers/wizard/step7_controller.js


> Some static attributes of config properties are lost after return to 
> Customize Services step of Add Service Wizard
> --
>
> Key: AMBARI-18784
> URL: https://issues.apache.org/jira/browse/AMBARI-18784
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.2
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18784-branch-2.4.patch, 
> AMBARI-18784-branch-2.5.patch, AMBARI-18784-trunk.patch
>
>
> *STR*
> # Complete Customize Services step of Add Service Wizard.
> # Refresh page.
> # Go back to Customize Services.
> *Result*
> Static attributes like isUserProperty, isRequiredByAgent are not restored.



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

[jira] [Updated] (AMBARI-18782) Disable HDP-2.2 stack

[Dmytro Grinenko (JIRA)]

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

Dmytro Grinenko updated AMBARI-18782:
-
Fix Version/s: 2.5.0

> Disable HDP-2.2 stack
> -
>
> Key: AMBARI-18782
> URL: https://issues.apache.org/jira/browse/AMBARI-18782
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-18782-trunk.patch, AMBARI-18782.patch
>
>
> We need to disable HDP-2.2 in the codebase and remove Upgrade Packs out of 
> the 2.2 directory.



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

[jira] [Updated] (AMBARI-18782) Disable HDP-2.2 stack

[Dmytro Grinenko (JIRA)]

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

Dmytro Grinenko updated AMBARI-18782:
-
Attachment: AMBARI-18782-trunk.patch

> Disable HDP-2.2 stack
> -
>
> Key: AMBARI-18782
> URL: https://issues.apache.org/jira/browse/AMBARI-18782
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18782-trunk.patch, AMBARI-18782.patch
>
>
> We need to disable HDP-2.2 in the codebase and remove Upgrade Packs out of 
> the 2.2 directory.



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

[jira] [Commented] (AMBARI-18783) Incorrect behaviour of Copy/Open controls for task details

[Oleg Nechiporenko (JIRA)]

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

Oleg Nechiporenko commented on AMBARI-18783:


Committed to trunk

> Incorrect behaviour of Copy/Open controls for task details
> --
>
> Key: AMBARI-18783
> URL: https://issues.apache.org/jira/browse/AMBARI-18783
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-18783.patch
>
>
> Host progress popup (displayed on deploy steps of different wizards, in 
> background opertations view etc.) allows to open stderr and stdout of certain 
> task in new window. There are some issues with this feature.



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

[jira] [Commented] (AMBARI-18784) Some static attributes of config properties are lost after return to Customize Services step of Add Service Wizard

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk commented on AMBARI-18784:
---

Committed to branch-2.4, branch-2.5 and trunk

> Some static attributes of config properties are lost after return to 
> Customize Services step of Add Service Wizard
> --
>
> Key: AMBARI-18784
> URL: https://issues.apache.org/jira/browse/AMBARI-18784
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.2
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18784-branch-2.4.patch, 
> AMBARI-18784-branch-2.5.patch, AMBARI-18784-trunk.patch
>
>
> *STR*
> # Complete Customize Services step of Add Service Wizard.
> # Refresh page.
> # Go back to Customize Services.
> *Result*
> Static attributes like isUserProperty, isRequiredByAgent are not restored.



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

[jira] [Commented] (AMBARI-18783) Incorrect behaviour of Copy/Open controls for task details

[Oleg Nechiporenko (JIRA)]

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

Oleg Nechiporenko commented on AMBARI-18783:


https://builds.apache.org/job/Ambari-trunk-test-patch/9116/console
{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12836781/AMBARI-18783.patch
  against trunk revision .

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

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

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

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

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


> Incorrect behaviour of Copy/Open controls for task details
> --
>
> Key: AMBARI-18783
> URL: https://issues.apache.org/jira/browse/AMBARI-18783
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-18783.patch
>
>
> Host progress popup (displayed on deploy steps of different wizards, in 
> background opertations view etc.) allows to open stderr and stdout of certain 
> task in new window. There are some issues with this feature.



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

[jira] [Commented] (AMBARI-18784) Some static attributes of config properties are lost after return to Customize Services step of Add Service Wizard

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk commented on AMBARI-18784:
---

  30324 tests complete (31 seconds)
  151 tests pending


Ambari-trunk-test-patch job passed: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9117/


> Some static attributes of config properties are lost after return to 
> Customize Services step of Add Service Wizard
> --
>
> Key: AMBARI-18784
> URL: https://issues.apache.org/jira/browse/AMBARI-18784
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.2
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18784-branch-2.4.patch, 
> AMBARI-18784-branch-2.5.patch, AMBARI-18784-trunk.patch
>
>
> *STR*
> # Complete Customize Services step of Add Service Wizard.
> # Refresh page.
> # Go back to Customize Services.
> *Result*
> Static attributes like isUserProperty, isRequiredByAgent are not restored.



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

[jira] [Updated] (AMBARI-18580) Delete host throws 500 Error with unique constraint violation

[Myroslav Papirkovskyi (JIRA)]

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

Myroslav Papirkovskyi updated AMBARI-18580:
---
Status: Patch Available  (was: Open)

> Delete host throws 500 Error with unique constraint violation
> -
>
> Key: AMBARI-18580
> URL: https://issues.apache.org/jira/browse/AMBARI-18580
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18580.patch
>
>
> Delete host request fails for blueprint deployed clusters in case when 
> topology_host_request with empty hostname exists.



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

[jira] [Updated] (AMBARI-18784) Some static attributes of config properties are lost after return to Customize Services step of Add Service Wizard

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk updated AMBARI-18784:
--
Attachment: AMBARI-18784-trunk.patch

> Some static attributes of config properties are lost after return to 
> Customize Services step of Add Service Wizard
> --
>
> Key: AMBARI-18784
> URL: https://issues.apache.org/jira/browse/AMBARI-18784
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.2
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18784-branch-2.4.patch, 
> AMBARI-18784-branch-2.5.patch, AMBARI-18784-trunk.patch
>
>
> *STR*
> # Complete Customize Services step of Add Service Wizard.
> # Refresh page.
> # Go back to Customize Services.
> *Result*
> Static attributes like isUserProperty, isRequiredByAgent are not restored.



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

[jira] [Updated] (AMBARI-18784) Some static attributes of config properties are lost after return to Customize Services step of Add Service Wizard

[Andrii Babiichuk (JIRA)]

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

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

> Some static attributes of config properties are lost after return to 
> Customize Services step of Add Service Wizard
> --
>
> Key: AMBARI-18784
> URL: https://issues.apache.org/jira/browse/AMBARI-18784
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.2
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18784-branch-2.4.patch, 
> AMBARI-18784-branch-2.5.patch, AMBARI-18784-trunk.patch
>
>
> *STR*
> # Complete Customize Services step of Add Service Wizard.
> # Refresh page.
> # Go back to Customize Services.
> *Result*
> Static attributes like isUserProperty, isRequiredByAgent are not restored.



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

[jira] [Updated] (AMBARI-18784) Some static attributes of config properties are lost after return to Customize Services step of Add Service Wizard

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk updated AMBARI-18784:
--
Attachment: AMBARI-18784-branch-2.5.patch
AMBARI-18784-branch-2.4.patch

> Some static attributes of config properties are lost after return to 
> Customize Services step of Add Service Wizard
> --
>
> Key: AMBARI-18784
> URL: https://issues.apache.org/jira/browse/AMBARI-18784
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.2
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18784-branch-2.4.patch, 
> AMBARI-18784-branch-2.5.patch, AMBARI-18784-trunk.patch
>
>
> *STR*
> # Complete Customize Services step of Add Service Wizard.
> # Refresh page.
> # Go back to Customize Services.
> *Result*
> Static attributes like isUserProperty, isRequiredByAgent are not restored.



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

[jira] [Created] (AMBARI-18784) Some static attributes of config properties are lost after return to Customize Services step of Add Service Wizard

[Andrii Babiichuk (JIRA)]

Andrii Babiichuk created AMBARI-18784:
-

 Summary: Some static attributes of config properties are lost 
after return to Customize Services step of Add Service Wizard
 Key: AMBARI-18784
 URL: https://issues.apache.org/jira/browse/AMBARI-18784
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.4.2
Reporter: Andrii Babiichuk
Assignee: Andrii Babiichuk
Priority: Critical
 Fix For: 2.4.2


*STR*
# Complete Customize Services step of Add Service Wizard.
# Refresh page.
# Go back to Customize Services.

*Result*
Static attributes like isUserProperty, isRequiredByAgent are not restored.



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

[jira] [Commented] (AMBARI-18783) Incorrect behaviour of Copy/Open controls for task details

[Andrii Tkach (JIRA)]

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

Andrii Tkach commented on AMBARI-18783:
---

+1 for the patch

> Incorrect behaviour of Copy/Open controls for task details
> --
>
> Key: AMBARI-18783
> URL: https://issues.apache.org/jira/browse/AMBARI-18783
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-18783.patch
>
>
> Host progress popup (displayed on deploy steps of different wizards, in 
> background opertations view etc.) allows to open stderr and stdout of certain 
> task in new window. There are some issues with this feature.



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

[jira] [Updated] (AMBARI-18772) Bg Ops popup is not shown

[Oleg Nechiporenko (JIRA)]

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

Oleg Nechiporenko updated AMBARI-18772:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Bg Ops popup is not shown
> -
>
> Key: AMBARI-18772
> URL: https://issues.apache.org/jira/browse/AMBARI-18772
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-18772.patch
>
>
> *STR*:
> * Open Bg Ops modal
> * Press "Esc"
> * Open Bg Ops again
> *AR* Modal-backdrop is shown and modal-container is NOT shown
> *ER* Modal-backdrop and modal-container are shown



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

[jira] [Updated] (AMBARI-18783) Incorrect behaviour of Copy/Open controls for task details

[Oleg Nechiporenko (JIRA)]

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

Oleg Nechiporenko updated AMBARI-18783:
---
Status: Patch Available  (was: Open)

Patch added

> Incorrect behaviour of Copy/Open controls for task details
> --
>
> Key: AMBARI-18783
> URL: https://issues.apache.org/jira/browse/AMBARI-18783
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-18783.patch
>
>
> Host progress popup (displayed on deploy steps of different wizards, in 
> background opertations view etc.) allows to open stderr and stdout of certain 
> task in new window. There are some issues with this feature.



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

[jira] [Commented] (AMBARI-18783) Incorrect behaviour of Copy/Open controls for task details

[Oleg Nechiporenko (JIRA)]

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

Oleg Nechiporenko commented on AMBARI-18783:


  30323 tests complete (34 seconds)
  151 tests pending


> Incorrect behaviour of Copy/Open controls for task details
> --
>
> Key: AMBARI-18783
> URL: https://issues.apache.org/jira/browse/AMBARI-18783
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-18783.patch
>
>
> Host progress popup (displayed on deploy steps of different wizards, in 
> background opertations view etc.) allows to open stderr and stdout of certain 
> task in new window. There are some issues with this feature.



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

[jira] [Updated] (AMBARI-18783) Incorrect behaviour of Copy/Open controls for task details

[Oleg Nechiporenko (JIRA)]

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

Oleg Nechiporenko updated AMBARI-18783:
---
Attachment: AMBARI-18783.patch

> Incorrect behaviour of Copy/Open controls for task details
> --
>
> Key: AMBARI-18783
> URL: https://issues.apache.org/jira/browse/AMBARI-18783
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-18783.patch
>
>
> Host progress popup (displayed on deploy steps of different wizards, in 
> background opertations view etc.) allows to open stderr and stdout of certain 
> task in new window. There are some issues with this feature.



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

[jira] [Created] (AMBARI-18783) Incorrect behaviour of Copy/Open controls for task details

[Oleg Nechiporenko (JIRA)]

Oleg Nechiporenko created AMBARI-18783:
--

 Summary: Incorrect behaviour of Copy/Open controls for task details
 Key: AMBARI-18783
 URL: https://issues.apache.org/jira/browse/AMBARI-18783
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.2.0
Reporter: Oleg Nechiporenko
Assignee: Oleg Nechiporenko
 Fix For: 3.0.0


Host progress popup (displayed on deploy steps of different wizards, in 
background opertations view etc.) allows to open stderr and stdout of certain 
task in new window. There are some issues with this feature.



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