[jira] [Created] (AMBARI-14916) Issues with Login Message dialog

[Antonenko Alexander (JIRA)]

Antonenko Alexander created AMBARI-14916:


 Summary: Issues with Login Message dialog
 Key: AMBARI-14916
 URL: https://issues.apache.org/jira/browse/AMBARI-14916
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.4.0
Reporter: Antonenko Alexander
Assignee: Antonenko Alexander
 Fix For: 2.4.0


Using trunk build




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

[jira] [Updated] (AMBARI-14918) enabling ranger caused proxy settings for user hive in hdfs to get updated

[Dmytro Sen (JIRA)]

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

Dmytro Sen updated AMBARI-14918:

Attachment: AMBARI-14918-trunk.patch

> enabling ranger caused proxy settings for user hive in hdfs to get updated
> --
>
> Key: AMBARI-14918
> URL: https://issues.apache.org/jira/browse/AMBARI-14918
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.2.1
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.2.2
>
> Attachments: AMBARI-14918-trunk.patch
>
>
> On a running cluster i added service Ranger. After ranger was installed proxy 
> settings for user hive got updated to values that were not correct.
> Compare configs v23 (before installing ranger) and v24 and you will see that 
> proxy hosts for user hive changed to only have 1 node where as i am running 
> multiple nodes for hive services.
> I was never alerted that these configs were being changed when ranger was 
> installed. We have to be very careful when we automatically update settings 
> related to proxy



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

Review Request 43186: enabling ranger caused proxy settings for user hive in hdfs to get updated

[Dmytro Sen]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43186/
---

Review request for Ambari, Andrew Onischuk, Myroslav Papirkovskyy, and Vitalyi 
Brodetskyi.


Bugs: AMBARI-14918
https://issues.apache.org/jira/browse/AMBARI-14918


Repository: ambari


Description
---

On a running cluster i added service Ranger. After ranger was installed proxy 
settings for user hive got updated to values that were not correct.
Compare configs v23 (before installing ranger) and v24 and you will see that 
proxy hosts for user hive changed to only have 1 node where as i am running 
multiple nodes for hive services.
I was never alerted that these configs were being changed when ranger was 
installed. We have to be very careful when we automatically update settings 
related to proxy


Diffs
-

  ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py 
9a21b71 
  ambari-server/src/test/python/stacks/2.0.6/common/test_stack_advisor.py 
a584a48 

Diff: https://reviews.apache.org/r/43186/diff/


Testing
---

unit tests passed


Thanks,

Dmytro Sen

[jira] [Updated] (AMBARI-14915) Ambari Server should not use /tmp for extraction

[Myroslav Papirkovskyy (JIRA)]

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

Myroslav Papirkovskyy updated AMBARI-14915:
---
Attachment: (was: AMBARI-14915.patch)

> Ambari Server should not use /tmp for extraction
> 
>
> Key: AMBARI-14915
> URL: https://issues.apache.org/jira/browse/AMBARI-14915
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Myroslav Papirkovskyy
>Assignee: Myroslav Papirkovskyy
>Priority: Critical
> Fix For: 2.2.2
>
>
> For example, Ambari Server extracts web assets (like views) to /tmp.
> /tmp should not be used as user systems sometimes have daemons that come 
> along and wipe tmp periodically. Therefore, use of /tmp can cause sporadic 
> problems in user environments.
> We might need to be sure Ambari Server jetty is started to use server.tmp.dir 
> from ambari.properties, so that jetty does not use /tmp.



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

[jira] [Updated] (AMBARI-14915) Ambari Server should not use /tmp for extraction

[Myroslav Papirkovskyy (JIRA)]

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

Myroslav Papirkovskyy updated AMBARI-14915:
---
Attachment: AMBARI-14915-trunk.patch
AMBARI-14915-branch-2.2.patch

> Ambari Server should not use /tmp for extraction
> 
>
> Key: AMBARI-14915
> URL: https://issues.apache.org/jira/browse/AMBARI-14915
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Myroslav Papirkovskyy
>Assignee: Myroslav Papirkovskyy
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14915-branch-2.2.patch, AMBARI-14915-trunk.patch
>
>
> For example, Ambari Server extracts web assets (like views) to /tmp.
> /tmp should not be used as user systems sometimes have daemons that come 
> along and wipe tmp periodically. Therefore, use of /tmp can cause sporadic 
> problems in user environments.
> We might need to be sure Ambari Server jetty is started to use server.tmp.dir 
> from ambari.properties, so that jetty does not use /tmp.



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

[jira] [Resolved] (AMBARI-14915) Ambari Server should not use /tmp for extraction

[Myroslav Papirkovskyy (JIRA)]

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

Myroslav Papirkovskyy resolved AMBARI-14915.

Resolution: Fixed

Pushed to trunk and branch-2.2

> Ambari Server should not use /tmp for extraction
> 
>
> Key: AMBARI-14915
> URL: https://issues.apache.org/jira/browse/AMBARI-14915
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Myroslav Papirkovskyy
>Assignee: Myroslav Papirkovskyy
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14915-branch-2.2.patch, AMBARI-14915-trunk.patch
>
>
> For example, Ambari Server extracts web assets (like views) to /tmp.
> /tmp should not be used as user systems sometimes have daemons that come 
> along and wipe tmp periodically. Therefore, use of /tmp can cause sporadic 
> problems in user environments.
> We might need to be sure Ambari Server jetty is started to use server.tmp.dir 
> from ambari.properties, so that jetty does not use /tmp.



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

[jira] [Updated] (AMBARI-14919) [Ambari tarballs] Create script to install ambari tar.gz into custom root

[Andrew Onischuk (JIRA)]

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

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

> [Ambari tarballs] Create script to install ambari tar.gz into custom root
> -
>
> Key: AMBARI-14919
> URL: https://issues.apache.org/jira/browse/AMBARI-14919
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-14919.patch
>
>
> This should include:
>   * downloading post (pre) install (remove scripts) along with script for 
> execution
>   * supporting custom root for these scripts
>   * the script extraction routine itself



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

[jira] [Created] (AMBARI-14919) [Ambari tarballs] Create script to install ambari tar.gz into custom root

[Andrew Onischuk (JIRA)]

Andrew Onischuk created AMBARI-14919:


 Summary: [Ambari tarballs] Create script to install ambari tar.gz 
into custom root
 Key: AMBARI-14919
 URL: https://issues.apache.org/jira/browse/AMBARI-14919
 Project: Ambari
  Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
 Fix For: 2.4.0
 Attachments: AMBARI-14919.patch

This should include:

  * downloading post (pre) install (remove scripts) along with script for 
execution
  * supporting custom root for these scripts
  * the script extraction routine itself





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

[jira] [Commented] (AMBARI-14916) Issues with Login Message dialog

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko commented on AMBARI-14916:
--

+1 for the patch

> Issues with Login Message dialog
> 
>
> Key: AMBARI-14916
> URL: https://issues.apache.org/jira/browse/AMBARI-14916
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-14916.patch
>
>
> Using trunk build



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

[jira] [Updated] (AMBARI-14915) Ambari Server should not use /tmp for extraction

[Myroslav Papirkovskyy (JIRA)]

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

Myroslav Papirkovskyy updated AMBARI-14915:
---
Attachment: AMBARI-14915.patch

> Ambari Server should not use /tmp for extraction
> 
>
> Key: AMBARI-14915
> URL: https://issues.apache.org/jira/browse/AMBARI-14915
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Myroslav Papirkovskyy
>Assignee: Myroslav Papirkovskyy
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14915.patch
>
>
> For example, Ambari Server extracts web assets (like views) to /tmp.
> /tmp should not be used as user systems sometimes have daemons that come 
> along and wipe tmp periodically. Therefore, use of /tmp can cause sporadic 
> problems in user environments.
> We might need to be sure Ambari Server jetty is started to use server.tmp.dir 
> from ambari.properties, so that jetty does not use /tmp.



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

Re: Review Request 43186: enabling ranger caused proxy settings for user hive in hdfs to get updated

[Andrew Onischuk]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43186/#review117798
---


Ship it!




Ship It!

- Andrew Onischuk


On Feb. 4, 2016, 11:59 a.m., Dmytro Sen wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43186/
> ---
> 
> (Updated Feb. 4, 2016, 11:59 a.m.)
> 
> 
> Review request for Ambari, Andrew Onischuk, Myroslav Papirkovskyy, and 
> Vitalyi Brodetskyi.
> 
> 
> Bugs: AMBARI-14918
> https://issues.apache.org/jira/browse/AMBARI-14918
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> On a running cluster i added service Ranger. After ranger was installed proxy 
> settings for user hive got updated to values that were not correct.
> Compare configs v23 (before installing ranger) and v24 and you will see that 
> proxy hosts for user hive changed to only have 1 node where as i am running 
> multiple nodes for hive services.
> I was never alerted that these configs were being changed when ranger was 
> installed. We have to be very careful when we automatically update settings 
> related to proxy
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py 
> 9a21b71 
>   ambari-server/src/test/python/stacks/2.0.6/common/test_stack_advisor.py 
> a584a48 
> 
> Diff: https://reviews.apache.org/r/43186/diff/
> 
> 
> Testing
> ---
> 
> unit tests passed
> 
> 
> Thanks,
> 
> Dmytro Sen
> 
>

Re: Review Request 43187: [Ambari tarballs] Create script to install ambari tar.gz into custom root

[Myroslav Papirkovskyy]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43187/#review117799
---


Ship it!




Ship It!

- Myroslav Papirkovskyy


On Лют. 4, 2016, 2:01 після полудня, Andrew Onischuk wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43187/
> ---
> 
> (Updated Лют. 4, 2016, 2:01 після полудня)
> 
> 
> Review request for Ambari and Myroslav Papirkovskyy.
> 
> 
> Bugs: AMBARI-14919
> https://issues.apache.org/jira/browse/AMBARI-14919
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> This should include:
> 
>   * downloading post (pre) install (remove scripts) along with script for 
> execution
>   * supporting custom root for these scripts
>   * the script extraction routine itself
> 
> 
> Diffs
> -
> 
>   ambari-agent/pom.xml 918065f 
>   ambari-common/src/main/repo/install_ambari_tarball.py PRE-CREATION 
>   ambari-server/conf/unix/install-helper.sh c7d05b4 
>   ambari-server/pom.xml c601baa 
>   ambari-server/src/main/package/deb/control/postinst e8d12c3 
>   ambari-server/src/main/package/deb/control/preinst 7bf7365 
>   ambari-server/src/main/package/deb/control/prerm 98e3be5 
> 
> Diff: https://reviews.apache.org/r/43187/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Andrew Onischuk
> 
>

[jira] [Commented] (AMBARI-14917) Edit WEB Alert issues

[Oleg Nechiporenko (JIRA)]

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

Oleg Nechiporenko commented on AMBARI-14917:


  24145 tests complete (24 seconds)
  156 tests pending


> Edit WEB Alert issues
> -
>
> Key: AMBARI-14917
> URL: https://issues.apache.org/jira/browse/AMBARI-14917
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14917.patch, web-alert-edit.pptx
>
>
> See attached.



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

[jira] [Updated] (AMBARI-14917) Edit WEB Alert issues

[Oleg Nechiporenko (JIRA)]

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

Oleg Nechiporenko updated AMBARI-14917:
---
Attachment: AMBARI-14917_branch-2.2.patch

> Edit WEB Alert issues
> -
>
> Key: AMBARI-14917
> URL: https://issues.apache.org/jira/browse/AMBARI-14917
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14917.patch, AMBARI-14917_branch-2.2.patch, 
> web-alert-edit.pptx
>
>
> See attached.



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

[jira] [Commented] (AMBARI-14917) Edit WEB Alert issues

[Oleg Nechiporenko (JIRA)]

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

Oleg Nechiporenko commented on AMBARI-14917:


2.2:
  10364 tests complete (12 seconds)
  121 tests pending


> Edit WEB Alert issues
> -
>
> Key: AMBARI-14917
> URL: https://issues.apache.org/jira/browse/AMBARI-14917
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14917.patch, AMBARI-14917_branch-2.2.patch, 
> web-alert-edit.pptx
>
>
> See attached.



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

[jira] [Commented] (AMBARI-14917) Edit WEB Alert issues

[Oleg Nechiporenko (JIRA)]

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

Oleg Nechiporenko commented on AMBARI-14917:


Patches for trunk and 2.2 are added.

> Edit WEB Alert issues
> -
>
> Key: AMBARI-14917
> URL: https://issues.apache.org/jira/browse/AMBARI-14917
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14917.patch, AMBARI-14917_branch-2.2.patch, 
> web-alert-edit.pptx
>
>
> See attached.



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

[jira] [Updated] (AMBARI-14901) NPE when configuring Kerberos at provisioning secure cluster with Blueprint

[Sandor Magyari (JIRA)]

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

Sandor Magyari updated AMBARI-14901:

Attachment: AMBARI-14901_branch-2.2.patch

> NPE when configuring Kerberos at provisioning secure cluster with Blueprint
> ---
>
> Key: AMBARI-14901
> URL: https://issues.apache.org/jira/browse/AMBARI-14901
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.1
>Reporter: Sandor Magyari
>Assignee: Sandor Magyari
> Fix For: 2.2.2
>
> Attachments: AMBARI-14901.patch, AMBARI-14901_branch-2.2.patch
>
>
> Provision a cluster with blueprint and enable kerberos with it. 
> config_recommendation_strategy is ONLY_STACK_DEFAULTS_APPLY. The cluster 
> installation will fail.
> java.lang.NullPointerException
> at 
> org.apache.ambari.server.topology.ClusterConfigurationRequest.configureKerberos(ClusterConfigurationRequest.java:151)
> at 
> org.apache.ambari.server.topology.ClusterConfigurationRequest.process(ClusterConfigurationRequest.java:103)
> at 
> org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:764)
> at 
> org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:738)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Suspicious code snippet:
> {code:java}
> Map propertyMap = updatedConfigs.get(configType);
> Map clusterConfigProperties = 
> existingConfigurations.get(configType);
> Map stackDefaultConfigProperties = 
> stackDefaultProps.get(configType);
> for (String property : propertyMap.keySet()) {
>   if (clusterConfigProperties == null || 
> !clusterConfigProperties.containsKey(property)
> || (clusterConfigProperties.get(property) == null && 
> stackDefaultConfigProperties.get(property) == null)
> || (clusterConfigProperties.get(property) != null && 
> clusterConfigProperties.get(property).equals(stackDefaultConfigProperties.get(property
> {code}



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

[jira] [Commented] (AMBARI-14916) Issues with Login Message dialog

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-14916:


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

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

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

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

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

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

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

This message is automatically generated.

> Issues with Login Message dialog
> 
>
> Key: AMBARI-14916
> URL: https://issues.apache.org/jira/browse/AMBARI-14916
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-14916.patch
>
>
> Using trunk build



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

Review Request 43187: [Ambari tarballs] Create script to install ambari tar.gz into custom root

[Andrew Onischuk]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43187/
---

Review request for Ambari and Myroslav Papirkovskyy.


Bugs: AMBARI-14919
https://issues.apache.org/jira/browse/AMBARI-14919


Repository: ambari


Description
---

This should include:

  * downloading post (pre) install (remove scripts) along with script for 
execution
  * supporting custom root for these scripts
  * the script extraction routine itself


Diffs
-

  ambari-agent/pom.xml 918065f 
  ambari-common/src/main/repo/install_ambari_tarball.py PRE-CREATION 
  ambari-server/conf/unix/install-helper.sh c7d05b4 
  ambari-server/pom.xml c601baa 
  ambari-server/src/main/package/deb/control/postinst e8d12c3 
  ambari-server/src/main/package/deb/control/preinst 7bf7365 
  ambari-server/src/main/package/deb/control/prerm 98e3be5 

Diff: https://reviews.apache.org/r/43187/diff/


Testing
---

mvn clean test


Thanks,

Andrew Onischuk

[jira] [Updated] (AMBARI-14917) Edit WEB Alert issues

[Oleg Nechiporenko (JIRA)]

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

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

> Edit WEB Alert issues
> -
>
> Key: AMBARI-14917
> URL: https://issues.apache.org/jira/browse/AMBARI-14917
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14917.patch, web-alert-edit.pptx
>
>
> See attached.



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

[jira] [Commented] (AMBARI-14917) Edit WEB Alert issues

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk commented on AMBARI-14917:
---

+1 for the patch

> Edit WEB Alert issues
> -
>
> Key: AMBARI-14917
> URL: https://issues.apache.org/jira/browse/AMBARI-14917
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14917.patch, AMBARI-14917_branch-2.2.patch, 
> web-alert-edit.pptx
>
>
> See attached.



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

[jira] [Updated] (AMBARI-14917) Edit WEB Alert issues

[Oleg Nechiporenko (JIRA)]

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

Oleg Nechiporenko updated AMBARI-14917:
---
Description: See attached.

> Edit WEB Alert issues
> -
>
> Key: AMBARI-14917
> URL: https://issues.apache.org/jira/browse/AMBARI-14917
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: web-alert-edit.pptx
>
>
> See attached.



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

[jira] [Created] (AMBARI-14917) Edit WEB Alert issues

[Oleg Nechiporenko (JIRA)]

Oleg Nechiporenko created AMBARI-14917:
--

 Summary: Edit WEB Alert issues
 Key: AMBARI-14917
 URL: https://issues.apache.org/jira/browse/AMBARI-14917
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.2.2
Reporter: Oleg Nechiporenko
Assignee: Oleg Nechiporenko
Priority: Critical
 Fix For: 2.2.2
 Attachments: web-alert-edit.pptx





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

[jira] [Updated] (AMBARI-14917) Edit WEB Alert issues

[Oleg Nechiporenko (JIRA)]

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

Oleg Nechiporenko updated AMBARI-14917:
---
Attachment: web-alert-edit.pptx

> Edit WEB Alert issues
> -
>
> Key: AMBARI-14917
> URL: https://issues.apache.org/jira/browse/AMBARI-14917
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: web-alert-edit.pptx
>
>
> See attached.



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

[jira] [Created] (AMBARI-14915) Ambari Server should not use /tmp for extraction

[Myroslav Papirkovskyy (JIRA)]

Myroslav Papirkovskyy created AMBARI-14915:
--

 Summary: Ambari Server should not use /tmp for extraction
 Key: AMBARI-14915
 URL: https://issues.apache.org/jira/browse/AMBARI-14915
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.2.0
Reporter: Myroslav Papirkovskyy
Assignee: Myroslav Papirkovskyy
Priority: Critical
 Fix For: 2.2.2


For example, Ambari Server extracts web assets (like views) to /tmp.

/tmp should not be used as user systems sometimes have daemons that come along 
and wipe tmp periodically. Therefore, use of /tmp can cause sporadic problems 
in user environments.

We might need to be sure Ambari Server jetty is started to use server.tmp.dir 
from ambari.properties, so that jetty does not use /tmp.



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

[jira] [Updated] (AMBARI-14916) Issues with Login Message dialog

[Antonenko Alexander (JIRA)]

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

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

> Issues with Login Message dialog
> 
>
> Key: AMBARI-14916
> URL: https://issues.apache.org/jira/browse/AMBARI-14916
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-14916.patch
>
>
> Using trunk build



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

[jira] [Created] (AMBARI-14918) enabling ranger caused proxy settings for user hive in hdfs to get updated

[Dmytro Sen (JIRA)]

Dmytro Sen created AMBARI-14918:
---

 Summary: enabling ranger caused proxy settings for user hive in 
hdfs to get updated
 Key: AMBARI-14918
 URL: https://issues.apache.org/jira/browse/AMBARI-14918
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.2.1
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Priority: Blocker
 Fix For: 2.2.2


On a running cluster i added service Ranger. After ranger was installed proxy 
settings for user hive got updated to values that were not correct.
Compare configs v23 (before installing ranger) and v24 and you will see that 
proxy hosts for user hive changed to only have 1 node where as i am running 
multiple nodes for hive services.
I was never alerted that these configs were being changed when ranger was 
installed. We have to be very careful when we automatically update settings 
related to proxy



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

[jira] [Commented] (AMBARI-14893) Add Grafana-based Ambari Metrics Dashboard Builder

[Yusaku Sako (JIRA)]

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

Yusaku Sako commented on AMBARI-14893:
--

Committed the pom.xml fix to trunk and branch-2.2 (verified that 
apache-rat:check passes locally).

> Add Grafana-based Ambari Metrics Dashboard Builder
> --
>
> Key: AMBARI-14893
> URL: https://issues.apache.org/jira/browse/AMBARI-14893
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-metrics
>Affects Versions: 2.2.2
>Reporter: Yusaku Sako
>Assignee: Prajwal Rao
> Fix For: 2.2.2
>
> Attachments: AMBARI-14893.patch, screenshots.tar.gz
>
>
> This is a Grafana datasource that allows visualization of metrics stored in 
> Ambari Metrics Collector.



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

RU: HiveServer2 port conflict when RU 2.2 to 2.3 then to 2.4 ?

[Di Li]

Hello folks,

When rolling upgrade HDP 2.2 to 2.3, HiveServer2 port is changed from 1 to 
10010. The same port change logic is in upgrade-2.4.xml as well. 

But wouldn't this make no difference if I rolling upgrade a 2.3 cluster that 
was originally rolling upgrade from an HDP 2.2 cluster , where the port had 
already been changed to 10010? It'd be like changing the port from 10010 (on 
HDP 2.3) to 10010 (on HDP 2.4), right ?

How does Ambari  handle Hive Server 2 port value change in  this continuously 
upgrade case?


Thank you.

Di Li

Re: RU: HiveServer2 port conflict when RU 2.2 to 2.3 then to 2.4 ?

[Alejandro Fernandez]

That's a good observation. I think it should have logic to always swap.
If hive.server2.transport.mode is set to "binary", then swap
hive.server2.thrift.port between 10,000 and 10,010
If hive.server2.transport.mode is set to "http", then swap
hive.server2.http.port between 10,001 and 10,011


Thanks,
Alejandro

On 2/4/16, 1:10 PM, "Di Li"  wrote:

>Hello folks,
>
>When rolling upgrade HDP 2.2 to 2.3, HiveServer2 port is changed from
>1 to 10010. The same port change logic is in upgrade-2.4.xml as well.
>
>But wouldn't this make no difference if I rolling upgrade a 2.3 cluster
>that was originally rolling upgrade from an HDP 2.2 cluster , where the
>port had already been changed to 10010? It'd be like changing the port
>from 10010 (on HDP 2.3) to 10010 (on HDP 2.4), right ?
>
>How does Ambari  handle Hive Server 2 port value change in  this
>continuously upgrade case?
>
>
>Thank you.
>
>Di Li

Re: Review Request 43125: AMBARI-14892 : Add Grafana as a component to AMS

[Aravindan Vijayan]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43125/
---

(Updated Feb. 4, 2016, 9:35 p.m.)


Review request for Ambari, Dmytro Sen, Sumit Mohanty, Sid Wagle, and Yusaku 
Sako.


Changes
---

Fix issues in package installation.


Bugs: AMBARI-14892
https://issues.apache.org/jira/browse/AMBARI-14892


Repository: ambari


Description
---

Add a MASTER component called Grafana to AMS service.

Include install and start/stop/status scripts for the grafana server.

Config Management for Ambari Metrics - Grafana also part of this patch.


Diffs (updated)
-

  ambari-metrics/ambari-metrics-grafana/conf/unix/ambari-metrics-grafana 
1de5401 
  ambari-metrics/ambari-metrics-grafana/conf/unix/ams-grafana-env.sh 20986cb 
  ambari-metrics/ambari-metrics-grafana/conf/unix/ams-grafana.ini e42a92f 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-grafana-env.xml
 PRE-CREATION 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-grafana-ini.xml
 PRE-CREATION 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/metainfo.xml
 48469df 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py
 8fdf4ba 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py
 cf498ec 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py
 PRE-CREATION 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_monitor.py
 a1d6a1d 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py
 a1de919 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/status.py
 59466ad 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/status_params.py
 d446baa 
  ambari-server/src/main/resources/stacks/HDP/2.0.6/role_command_order.json 
a480e2a 

Diff: https://reviews.apache.org/r/43125/diff/


Testing
---

Manual testing done by installing ambari-metrics-grafana rpm on a host and 
testing the patch.


Thanks,

Aravindan Vijayan

Re: Review Request 43154: AMBARI-14766: Selecting ALL groups does not work under Manage Alert Notifications

[Keta Patel]

> On Feb. 4, 2016, 7:26 p.m., Jonathan Hurley wrote:
> > Ship It!

Thank you Jonathan!
Could you help me with committing the patch please?


- Keta


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43154/#review117867
---


On Feb. 4, 2016, 5:49 p.m., Keta Patel wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43154/
> ---
> 
> (Updated Feb. 4, 2016, 5:49 p.m.)
> 
> 
> Review request for Ambari, Alexandr Antonenko, Di Li, Jonathan Hurley, and 
> Oleg Nechiporenko.
> 
> 
> Bugs: AMBARI-14766
> https://issues.apache.org/jira/browse/AMBARI-14766
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Selecting "ALL" groups does not work under Manage Alert Notifications.
> 
> Reproduction Steps:-
> 1. Go to Alerts Tab in Ambari GUI
> 2. Actions --> Manage Notifications
> 3. Create New Alert Notification (Click the custom radio button for groups 
> and select couple of options eg HDFS, PIG)
> 4. Save it.
> 5. Edit the newly created Alert notification by clicking on the All radio 
> button. Everything gets selected.
> 6. Save it
> 
> Expected results:
> On Saving the Alert notification, the dialog box "Manage Alert Notification" 
> should show Groups as ALL ( or Show all the values eg HDFS, PIG, MR2). 
> Basically all the values should be selected.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertTargetResourceProvider.java
>  d28987d 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AlertTargetResourceProviderTest.java
>  f80b6f7 
>   
> ambari-web/app/controllers/main/alerts/manage_alert_notifications_controller.js
>  38e4e75 
> 
> Diff: https://reviews.apache.org/r/43154/diff/
> 
> 
> Testing
> ---
> 
> FIX:
> 
> The UI did not show "All" even after selecting "ALL" for Groups in the Edit 
> Alert Target pop-up because the property "selectedAlertGroup" was not set to 
> true even after the selection. This is fixed in the 
> "manageAlertGroupsController" in ambari-web.
> 
> However, this only resolved the UI issue. The alert notifications were still 
> not sent for all services after this change. This was because there was no 
> corresponding update made in the server code for this "ALL" Groups selection 
> for a Target. The DB has a table for AlertTarget (alert_target) and 
> AlertGroup (alert_group). There is a many-to-many mapping between these 2 
> tables, which is tracked in the combination table alert_group_target. 
> 1. This combination table was not getting updated for the "ALL" Groups 
> selection. 
> 2. Also, the Target was not updated as global in the DB. 
> 
> The "updateAlertTargets()" in "AlertTargetResourceProvider" is updated with 
> the fix for both these issues.
> The global property in Target is set if the ALL selection is made.
> And, if the Target is global, all the groups in the DB are upadted with the 
> current Target in the alert_group_target table.
> 
> 
> TESTS:
> ==
> 2 test cases are added to test for Custom and All Group selections.
> In case of Custom, the request to the REST API has group IDs passed and the 
> global paramter is false.
> The Target after this update must have global as false and should be mapped 
> to only the selected groups passed in the request.
> 
> In case of All, the request to the REST API does not have group IDs passed 
> and the global paramter is true.
> The Target after this update must contain global as true and should be mapped 
> to all the groups in the DB.
> 
> 
> Thanks,
> 
> Keta Patel
> 
>

[jira] [Commented] (AMBARI-14834) Register Version: make the 'Repositories' category editable and addable

[Xi Wang (JIRA)]

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

Xi Wang commented on AMBARI-14834:
--

Unit tests ran locally.
Executed 61 of 61 SUCCESS (0.232 secs / 0.476 secs)

> Register Version: make the 'Repositories' category editable and addable
> ---
>
> Key: AMBARI-14834
> URL: https://issues.apache.org/jira/browse/AMBARI-14834
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Xi Wang
>Assignee: Xi Wang
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-14834.patch, AMBARI-14834.patch, Screen Shot 
> 2016-01-27 at 4.08.17 PM.png
>
>
> This one is the third part to implement" Manage Ambari > Register Version" 
> page. 
> Should implement:
> 1. Display all the repo urls loaded from version definition file.
> 2. Each of the urls should be editable.
> 3. Add ability to add new OS (new repo urls for new OS).
> 4. Validate urls, avoid redundant OS, at least one OS .etc



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

[jira] [Commented] (AMBARI-14913) Show HAWQ default_segment_num parameter in General section

[Matt (JIRA)]

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

Matt commented on AMBARI-14913:
---

The failure is unrelated to this patch.
The build failed because of ambari-metrics-grafana

[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Ambari Main ... SUCCESS [  4.512 s]
[INFO] Apache Ambari Project POM . SUCCESS [  0.245 s]
[INFO] Ambari Web  SUCCESS [ 49.720 s]
[INFO] Ambari Views .. SUCCESS [  3.402 s]
[INFO] Ambari Admin View . SUCCESS [01:43 min]
[INFO] ambari-metrics  SUCCESS [  0.068 s]
[INFO] Ambari Metrics Common . SUCCESS [  0.946 s]
[INFO] Ambari Metrics Hadoop Sink  SUCCESS [  0.976 s]
[INFO] Ambari Metrics Flume Sink . SUCCESS [  0.745 s]
[INFO] Ambari Metrics Kafka Sink . SUCCESS [  0.749 s]
[INFO] Ambari Metrics Storm Sink . SUCCESS [  2.693 s]
[INFO] Ambari Metrics Collector .. SUCCESS [ 18.285 s]
[INFO] Ambari Metrics Monitor  SUCCESS [  2.703 s]
[INFO] Ambari Metrics Grafana  FAILURE [  5.463 s]
[INFO] Ambari Metrics Assembly ... SKIPPED
[INFO] Ambari Server . SKIPPED
[INFO] Ambari Functional Tests ... SKIPPED
[INFO] Ambari Agent .. SKIPPED
[INFO] Ambari Client . SKIPPED
[INFO] Ambari Python Client .. SKIPPED
[INFO] Ambari Groovy Client .. SKIPPED
[INFO] Ambari Shell .. SKIPPED
[INFO] Ambari Python Shell ... SKIPPED
[INFO] Ambari Groovy Shell ... SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 03:16 min
[INFO] Finished at: 2016-02-04T21:16:33+00:00
[INFO] Final Memory: 67M/438M
[INFO] 

> Show HAWQ default_segment_num parameter in General section
> --
>
> Key: AMBARI-14913
> URL: https://issues.apache.org/jira/browse/AMBARI-14913
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Reporter: Matt
>Assignee: Matt
>Priority: Trivial
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-14913-branch-2.2.patch, AMBARI-14913-trunk.patch
>
>
> Given the importance of the parameter and likelihood of tuning it 
> occasionally, HAWQ default_segment_num parameter should be displayed in 
> General section.



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

[jira] [Commented] (AMBARI-14797) Register Version: display loaded version definition info in different categories and Save them

[Xi Wang (JIRA)]

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

Xi Wang commented on AMBARI-14797:
--

Unit tests ran locally.
Executed 61 of 61 SUCCESS (0.232 secs / 0.476 secs)

> Register Version: display loaded version definition info in different 
> categories and Save them
> --
>
> Key: AMBARI-14797
> URL: https://issues.apache.org/jira/browse/AMBARI-14797
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Xi Wang
>Assignee: Xi Wang
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-14797.patch, AMBARI-14797.patch, register version 
> -1.png, register version -2.png
>
>
> Belongs to UI work of Patch Upgrade ( Provide ability to apply single patches 
> on top of RU release).
> This one is the second part to implement" Manage Ambari > Register Version" 
> page.
> 1. Should generate the UI template for all three categories, then show loaded 
> version definition info in three different categories as:
>  
> Just show what loaded for this one, will file another ticket to make 
> 'Repositories' category more functional.
> 2. Click on "Save" button on the bottom of this page, will PUT the 
> information to server side.



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

[jira] [Commented] (AMBARI-14837) Versions: display all versions as tabs on left side, version details on selecting

[Xi Wang (JIRA)]

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

Xi Wang commented on AMBARI-14837:
--

Unit tests ran locally.
Executed 61 of 61 SUCCESS (0.232 secs / 0.476 secs)

> Versions: display all versions as tabs on left side, version details on 
> selecting
> -
>
> Key: AMBARI-14837
> URL: https://issues.apache.org/jira/browse/AMBARI-14837
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Xi Wang
>Assignee: Xi Wang
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-14837.patch, AMBARI-14837.patch, 
> AMBARI-14837.patch, Screen Shot 2016-01-29 at 5.59.13 PM.png, Screen Shot 
> 2016-01-29 at 5.59.28 PM.png, Screen Shot 2016-02-01 at 11.33.35 AM.png
>
>
> This one is to implement" Manage Ambari > Versions" page. 
> 1. All versions show be displayed as tabs on the left side,  each patch 
> version should be a child of its parent stack version.
> 2. On selecting a version (either patch version or original stack version), 
> all the version definition info show up on the right side.
> This look should be the same as register version page. "Details" and 
> "Contents" are un-editable, "Repos" is editable and addable.
> 3. Add a mark/icon to the patch versions to differentiate them from original 
> stack versions. 
> Related API:
> {code}
> GET /api/v1/stacks/HDP/versions/2.3/repository_versions
> PUT /api/v1/stacks/HDP/versions/2.3/repository_versions   // for editing repo 
> urls
> {code}



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

[jira] [Commented] (AMBARI-14925) Make AMS Grafana component available as a DEB package

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14925:
-

FAILURE: Integrated in Ambari-branch-2.2 #291 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/291/])
AMBARI-14925 Make AMS Grafana component available as a DEB package (dsen: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a9e2d18712eba6090f6175780d7a295da4b54a7d])
* ambari-metrics/ambari-metrics-assembly/pom.xml


> Make AMS Grafana component available as a DEB package
> -
>
> Key: AMBARI-14925
> URL: https://issues.apache.org/jira/browse/AMBARI-14925
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-metrics
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14925-trunk.patch
>
>
> Make AMS Grafana component available as a DEB package



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

[jira] [Commented] (AMBARI-14893) Add Grafana-based Ambari Metrics Dashboard Builder

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14893:
-

FAILURE: Integrated in Ambari-branch-2.2 #291 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/291/])
AMBARI-14893. Add Grafana-based Ambari Metrics Dashboard Builder. (yusaku: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=df7ba1b1bf06ad21f321722f6055e39b35e98e40])
* ambari-metrics/ambari-metrics-grafana/ambari-metrics/plugin.json
* 
ambari-metrics/ambari-metrics-grafana/ambari-metrics/partials/query.options.html
* ambari-metrics/pom.xml
* ambari-metrics/ambari-metrics-grafana/ambari-metrics/partials/config.html
* ambari-metrics/ambari-metrics-grafana/ambari-metrics/datasource.js
* ambari-metrics/ambari-metrics-grafana/README.md
* ambari-metrics/ambari-metrics-grafana/ambari-metrics/queryCtrl.js
* 
ambari-metrics/ambari-metrics-grafana/ambari-metrics/partials/query.editor.html
* ambari-metrics/ambari-metrics-grafana/ambari-metrics/directives.js
AMBARI-14893. Add Grafana-based Ambari Metrics Dashboard Builder. (yusaku: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3e1e4f86e16f4bf4dc43cb2ae2012a9ac5464055])
* ambari-metrics/ambari-metrics-grafana/screenshots/5-dashboard-graph-menu.png
* ambari-metrics/ambari-metrics-grafana/screenshots/9-choose-metric.png
* ambari-metrics/ambari-metrics-grafana/screenshots/15-change-units.png
* ambari-metrics/ambari-metrics-grafana/screenshots/18-override-time.png
* ambari-metrics/ambari-metrics-grafana/screenshots/13-save-dashboard.png
* ambari-metrics/ambari-metrics-grafana/screenshots/2-datasource-details.png
* ambari-metrics/ambari-metrics-grafana/screenshots/16-display-style-graph-1.png
* ambari-metrics/ambari-metrics-grafana/screenshots/4-dashboard-dropdown.png
* ambari-metrics/ambari-metrics-grafana/screenshots/12-change-panel-title.png
* ambari-metrics/ambari-metrics-grafana/screenshots/3-test-datasource.png
* ambari-metrics/ambari-metrics-grafana/screenshots/19-edit-graph.png
* ambari-metrics/ambari-metrics-grafana/screenshots/full-dashboard.png
* ambari-metrics/ambari-metrics-grafana/screenshots/10-choose-hostname.png
* ambari-metrics/ambari-metrics-grafana/screenshots/add-dashboard.png
* ambari-metrics/ambari-metrics-grafana/screenshots/14-change-timerange.png
* ambari-metrics/ambari-metrics-grafana/screenshots/8-choose-component.png
* 
ambari-metrics/ambari-metrics-grafana/screenshots/11-choose-agg-rate-precision.png
* 
ambari-metrics/ambari-metrics-grafana/screenshots/17-series-specific-override.png
* ambari-metrics/ambari-metrics-grafana/screenshots/1-add-datasource.png
* ambari-metrics/ambari-metrics-grafana/screenshots/7-choose-datasource.png
* ambari-metrics/ambari-metrics-grafana/screenshots/6-graph-panels.png


> Add Grafana-based Ambari Metrics Dashboard Builder
> --
>
> Key: AMBARI-14893
> URL: https://issues.apache.org/jira/browse/AMBARI-14893
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-metrics
>Affects Versions: 2.2.2
>Reporter: Yusaku Sako
>Assignee: Prajwal Rao
> Fix For: 2.2.2
>
> Attachments: AMBARI-14893.patch, screenshots.tar.gz
>
>
> This is a Grafana datasource that allows visualization of metrics stored in 
> Ambari Metrics Collector.



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

[jira] [Created] (AMBARI-14931) HAWQ service checks failing for single node clusters

[Newton Alex (JIRA)]

Newton Alex created AMBARI-14931:


 Summary: HAWQ service checks failing for single node clusters
 Key: AMBARI-14931
 URL: https://issues.apache.org/jira/browse/AMBARI-14931
 Project: Ambari
  Issue Type: Bug
  Components: stacks
Reporter: Newton Alex
Assignee: Newton Alex


Here is the log:

```
2016-02-04 19:01:30,163 - SQL command executed failed: export PGPORT=10432 && 
source /usr/local/hawq/greenplum_path.sh && psql -d template1 -c \\\"DROP  
TABLE IF EXISTS ambari_hawq_test;\\\"
Returncode: 127
Stdout: 
Stderr: psql: warning: extra command-line argument "IF" ignored
psql: warning: extra command-line argument "EXISTS" ignored
psql: warning: extra command-line argument "ambari_hawq_test" ignored
psql: FATAL:  no pg_hba.conf entry for host "[local]", user "TABLE", database 
"template1", SSL off
-bash: ": command not found

2016-02-04 19:01:30,164 - SERVICE CHECK FAILED: HAWQ was not able to write and 
query from a table
2016-02-04 19:01:30,229 - SQL command executed failed: export PGPORT=10432 && 
source /usr/local/hawq/greenplum_path.sh && psql -d template1 -c \\\"DROP  
TABLE IF EXISTS ambari_hawq_test;\\\"
Returncode: 127
Stdout: 
Stderr: psql: warning: extra command-line argument "IF" ignored
psql: warning: extra command-line argument "EXISTS" ignored
psql: warning: extra command-line argument "ambari_hawq_test" ignored
psql: FATAL:  no pg_hba.conf entry for host "[local]", user "TABLE", database 
"template1", SSL off
-bash: ": command not found

Traceback (most recent call last):
  File 
"/var/lib/ambari-agent/cache/common-services/HAWQ/2.0.0/package/scripts/service_check.py",
 line 170, in 
HAWQServiceCheck().execute()
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
 line 238, in execute
method(env)
  File 
"/var/lib/ambari-agent/cache/common-services/HAWQ/2.0.0/package/scripts/service_check.py",
 line 48, in service_check
self.check_hawq()
  File 
"/var/lib/ambari-agent/cache/common-services/HAWQ/2.0.0/package/scripts/service_check.py",
 line 99, in check_hawq
self.drop_table(table)
  File 
"/var/lib/ambari-agent/cache/common-services/HAWQ/2.0.0/package/scripts/service_check.py",
 line 131, in drop_table
exec_psql_cmd(sql_cmd, self.active_master_host, self.active_master_port)
  File 
"/var/lib/ambari-agent/cache/common-services/HAWQ/2.0.0/package/scripts/utils.py",
 line 106, in exec_psql_cmd
raise Fail("SQL command executed failed.")
resource_management.core.exceptions.Fail: SQL command executed failed.
```




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

[jira] [Commented] (AMBARI-14913) Show HAWQ default_segment_num parameter in General section

[jun aoki (JIRA)]

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

jun aoki commented on AMBARI-14913:
---

+1

> Show HAWQ default_segment_num parameter in General section
> --
>
> Key: AMBARI-14913
> URL: https://issues.apache.org/jira/browse/AMBARI-14913
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Reporter: Matt
>Assignee: Matt
>Priority: Trivial
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-14913-branch-2.2.patch, AMBARI-14913-trunk.patch
>
>
> Given the importance of the parameter and likelihood of tuning it 
> occasionally, HAWQ default_segment_num parameter should be displayed in 
> General section.



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

[jira] [Commented] (AMBARI-14931) HAWQ service checks failing for single node clusters

[Newton Alex (JIRA)]

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

Newton Alex commented on AMBARI-14931:
--

The same patch applies to both trunk and branch-2.2

> HAWQ service checks failing for single node clusters
> 
>
> Key: AMBARI-14931
> URL: https://issues.apache.org/jira/browse/AMBARI-14931
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Reporter: Newton Alex
>Assignee: Newton Alex
> Attachments: AMBARI-14931.patch
>
>
> Here is the log:
> ```
> 2016-02-04 19:01:30,163 - SQL command executed failed: export PGPORT=10432 && 
> source /usr/local/hawq/greenplum_path.sh && psql -d template1 -c \\\"DROP  
> TABLE IF EXISTS ambari_hawq_test;\\\"
> Returncode: 127
> Stdout: 
> Stderr: psql: warning: extra command-line argument "IF" ignored
> psql: warning: extra command-line argument "EXISTS" ignored
> psql: warning: extra command-line argument "ambari_hawq_test" ignored
> psql: FATAL:  no pg_hba.conf entry for host "[local]", user "TABLE", database 
> "template1", SSL off
> -bash: ": command not found
> 2016-02-04 19:01:30,164 - SERVICE CHECK FAILED: HAWQ was not able to write 
> and query from a table
> 2016-02-04 19:01:30,229 - SQL command executed failed: export PGPORT=10432 && 
> source /usr/local/hawq/greenplum_path.sh && psql -d template1 -c \\\"DROP  
> TABLE IF EXISTS ambari_hawq_test;\\\"
> Returncode: 127
> Stdout: 
> Stderr: psql: warning: extra command-line argument "IF" ignored
> psql: warning: extra command-line argument "EXISTS" ignored
> psql: warning: extra command-line argument "ambari_hawq_test" ignored
> psql: FATAL:  no pg_hba.conf entry for host "[local]", user "TABLE", database 
> "template1", SSL off
> -bash: ": command not found
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/HAWQ/2.0.0/package/scripts/service_check.py",
>  line 170, in 
> HAWQServiceCheck().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 238, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HAWQ/2.0.0/package/scripts/service_check.py",
>  line 48, in service_check
> self.check_hawq()
>   File 
> "/var/lib/ambari-agent/cache/common-services/HAWQ/2.0.0/package/scripts/service_check.py",
>  line 99, in check_hawq
> self.drop_table(table)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HAWQ/2.0.0/package/scripts/service_check.py",
>  line 131, in drop_table
> exec_psql_cmd(sql_cmd, self.active_master_host, self.active_master_port)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HAWQ/2.0.0/package/scripts/utils.py",
>  line 106, in exec_psql_cmd
> raise Fail("SQL command executed failed.")
> resource_management.core.exceptions.Fail: SQL command executed failed.
> ```



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

[jira] [Commented] (AMBARI-14931) HAWQ service checks failing for single node clusters

[Newton Alex (JIRA)]

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

Newton Alex commented on AMBARI-14931:
--

No new unit tests added as this was just a bug fix to existing functionality.

> HAWQ service checks failing for single node clusters
> 
>
> Key: AMBARI-14931
> URL: https://issues.apache.org/jira/browse/AMBARI-14931
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Reporter: Newton Alex
>Assignee: Newton Alex
> Attachments: AMBARI-14931.patch
>
>
> Here is the log:
> ```
> 2016-02-04 19:01:30,163 - SQL command executed failed: export PGPORT=10432 && 
> source /usr/local/hawq/greenplum_path.sh && psql -d template1 -c \\\"DROP  
> TABLE IF EXISTS ambari_hawq_test;\\\"
> Returncode: 127
> Stdout: 
> Stderr: psql: warning: extra command-line argument "IF" ignored
> psql: warning: extra command-line argument "EXISTS" ignored
> psql: warning: extra command-line argument "ambari_hawq_test" ignored
> psql: FATAL:  no pg_hba.conf entry for host "[local]", user "TABLE", database 
> "template1", SSL off
> -bash: ": command not found
> 2016-02-04 19:01:30,164 - SERVICE CHECK FAILED: HAWQ was not able to write 
> and query from a table
> 2016-02-04 19:01:30,229 - SQL command executed failed: export PGPORT=10432 && 
> source /usr/local/hawq/greenplum_path.sh && psql -d template1 -c \\\"DROP  
> TABLE IF EXISTS ambari_hawq_test;\\\"
> Returncode: 127
> Stdout: 
> Stderr: psql: warning: extra command-line argument "IF" ignored
> psql: warning: extra command-line argument "EXISTS" ignored
> psql: warning: extra command-line argument "ambari_hawq_test" ignored
> psql: FATAL:  no pg_hba.conf entry for host "[local]", user "TABLE", database 
> "template1", SSL off
> -bash: ": command not found
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/HAWQ/2.0.0/package/scripts/service_check.py",
>  line 170, in 
> HAWQServiceCheck().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 238, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HAWQ/2.0.0/package/scripts/service_check.py",
>  line 48, in service_check
> self.check_hawq()
>   File 
> "/var/lib/ambari-agent/cache/common-services/HAWQ/2.0.0/package/scripts/service_check.py",
>  line 99, in check_hawq
> self.drop_table(table)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HAWQ/2.0.0/package/scripts/service_check.py",
>  line 131, in drop_table
> exec_psql_cmd(sql_cmd, self.active_master_host, self.active_master_port)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HAWQ/2.0.0/package/scripts/utils.py",
>  line 106, in exec_psql_cmd
> raise Fail("SQL command executed failed.")
> resource_management.core.exceptions.Fail: SQL command executed failed.
> ```



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

Re: Review Request 43125: AMBARI-14892 : Add Grafana as a component to AMS

[Aravindan Vijayan]

> On Feb. 4, 2016, 10:24 p.m., Sid Wagle wrote:
> > ambari-metrics/ambari-metrics-grafana/conf/unix/ams-grafana.ini, line 151
> > 
> >
> > Ambari sounds better.

Will customize Grafana for AMS and Ambari through a follow up patch.


- Aravindan


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43125/#review117892
---


On Feb. 4, 2016, 9:35 p.m., Aravindan Vijayan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43125/
> ---
> 
> (Updated Feb. 4, 2016, 9:35 p.m.)
> 
> 
> Review request for Ambari, Dmytro Sen, Sumit Mohanty, Sid Wagle, and Yusaku 
> Sako.
> 
> 
> Bugs: AMBARI-14892
> https://issues.apache.org/jira/browse/AMBARI-14892
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Add a MASTER component called Grafana to AMS service.
> 
> Include install and start/stop/status scripts for the grafana server.
> 
> Config Management for Ambari Metrics - Grafana also part of this patch.
> 
> 
> Diffs
> -
> 
>   ambari-metrics/ambari-metrics-grafana/conf/unix/ambari-metrics-grafana 
> 1de5401 
>   ambari-metrics/ambari-metrics-grafana/conf/unix/ams-grafana-env.sh 20986cb 
>   ambari-metrics/ambari-metrics-grafana/conf/unix/ams-grafana.ini e42a92f 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-grafana-env.xml
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-grafana-ini.xml
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/metainfo.xml
>  48469df 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py
>  8fdf4ba 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py
>  cf498ec 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_monitor.py
>  a1d6a1d 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py
>  a1de919 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/status.py
>  59466ad 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/status_params.py
>  d446baa 
>   ambari-server/src/main/resources/stacks/HDP/2.0.6/role_command_order.json 
> a480e2a 
> 
> Diff: https://reviews.apache.org/r/43125/diff/
> 
> 
> Testing
> ---
> 
> Manual testing done by installing ambari-metrics-grafana rpm on a host and 
> testing the patch.
> 
> 
> Thanks,
> 
> Aravindan Vijayan
> 
>

[jira] [Updated] (AMBARI-14931) HAWQ service checks failing for single node clusters

[Newton Alex (JIRA)]

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

Newton Alex updated AMBARI-14931:
-
Attachment: AMBARI-14931.patch

> HAWQ service checks failing for single node clusters
> 
>
> Key: AMBARI-14931
> URL: https://issues.apache.org/jira/browse/AMBARI-14931
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Reporter: Newton Alex
>Assignee: Newton Alex
> Attachments: AMBARI-14931.patch
>
>
> Here is the log:
> ```
> 2016-02-04 19:01:30,163 - SQL command executed failed: export PGPORT=10432 && 
> source /usr/local/hawq/greenplum_path.sh && psql -d template1 -c \\\"DROP  
> TABLE IF EXISTS ambari_hawq_test;\\\"
> Returncode: 127
> Stdout: 
> Stderr: psql: warning: extra command-line argument "IF" ignored
> psql: warning: extra command-line argument "EXISTS" ignored
> psql: warning: extra command-line argument "ambari_hawq_test" ignored
> psql: FATAL:  no pg_hba.conf entry for host "[local]", user "TABLE", database 
> "template1", SSL off
> -bash: ": command not found
> 2016-02-04 19:01:30,164 - SERVICE CHECK FAILED: HAWQ was not able to write 
> and query from a table
> 2016-02-04 19:01:30,229 - SQL command executed failed: export PGPORT=10432 && 
> source /usr/local/hawq/greenplum_path.sh && psql -d template1 -c \\\"DROP  
> TABLE IF EXISTS ambari_hawq_test;\\\"
> Returncode: 127
> Stdout: 
> Stderr: psql: warning: extra command-line argument "IF" ignored
> psql: warning: extra command-line argument "EXISTS" ignored
> psql: warning: extra command-line argument "ambari_hawq_test" ignored
> psql: FATAL:  no pg_hba.conf entry for host "[local]", user "TABLE", database 
> "template1", SSL off
> -bash: ": command not found
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/HAWQ/2.0.0/package/scripts/service_check.py",
>  line 170, in 
> HAWQServiceCheck().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 238, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HAWQ/2.0.0/package/scripts/service_check.py",
>  line 48, in service_check
> self.check_hawq()
>   File 
> "/var/lib/ambari-agent/cache/common-services/HAWQ/2.0.0/package/scripts/service_check.py",
>  line 99, in check_hawq
> self.drop_table(table)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HAWQ/2.0.0/package/scripts/service_check.py",
>  line 131, in drop_table
> exec_psql_cmd(sql_cmd, self.active_master_host, self.active_master_port)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HAWQ/2.0.0/package/scripts/utils.py",
>  line 106, in exec_psql_cmd
> raise Fail("SQL command executed failed.")
> resource_management.core.exceptions.Fail: SQL command executed failed.
> ```



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

[jira] [Commented] (AMBARI-14927) Log Search: Add Host Components Logs tab to Host Details page

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-14927:


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

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

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

This message is automatically generated.

> Log Search: Add Host Components Logs tab to Host Details page
> -
>
> Key: AMBARI-14927
> URL: https://issues.apache.org/jira/browse/AMBARI-14927
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-14927.patch
>
>
> - Add Tab "Logs" to Host Details
> - Create filter by Service, Component, Extension
> - Create table to display result
> - Pagination for results.



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

Re: RU: HiveServer2 port conflict when RU 2.2 to 2.3 then to 2.4 ?

[Jonathan Hurley]

Yes. Most Ambari administrators actually change this back to 1 after the 
upgrade since they have hard coded scripts which they want to use. We've 
discussed adding the ability for a while now to increase by a value instead of 
setting the port directly. It's just never been prioritized. 

> On Feb 4, 2016, at 4:44 PM, Di Li  wrote:
> 
> Hello folks,
> 
> Thanks for the reply.  I was thinking of more like automatically increasing 
> (for RU) or decreasing (for rolling downgrade) like by 10 against the base 
> port ( aka whatever port value a customer may specify during the cluster 
> installation time, may not be the default 1 though).
> 
> For example, if the customer set HiveServer2 port to 3, then I guess the 
> upgrade logic would ideally be able to change it to 30010 for RU (like 
> port_value + 10)  and set that back to 3 (like port_value - 10) for 
> downgrade.
> 
> 
> From: Alejandro Fernandez 
> To: "dev@ambari.apache.org" ; Di Li 
> ; Nate Cole ; Jonathan Hurley 
>  
> Sent: Thursday, February 4, 2016 4:22 PM
> Subject: Re: RU: HiveServer2 port conflict when RU 2.2 to 2.3 then to 2.4 ?
> 
> That's a good observation. I think it should have logic to always swap.
> If hive.server2.transport.mode is set to "binary", then swap
> hive.server2.thrift.port between 10,000 and 10,010
> If hive.server2.transport.mode is set to "http", then swap
> hive.server2.http.portbetween 10,001 and 10,011
> 
> 
> Thanks,
> Alejandro
> 
> On 2/4/16, 1:10 PM, "Di Li"  wrote:
> 
>> Hello folks,
>> 
>> When rolling upgrade HDP 2.2 to 2.3, HiveServer2 port is changed from
>> 1 to 10010. The same port change logic is in upgrade-2.4.xml as well.
>> 
>> But wouldn't this make no difference if I rolling upgrade a 2.3 cluster
>> that was originally rolling upgrade from an HDP 2.2 cluster , where the
>> port had already been changed to 10010? It'd be like changing the port
>> from 10010 (on HDP 2.3) to 10010 (on HDP 2.4), right ?
>> 
>> How does Ambari  handle Hive Server 2 port value change in  this
>> continuously upgrade case?
>> 
>> 
>> Thank you.
>> 
>> Di Li
> 
> 

[jira] [Commented] (AMBARI-14893) Add Grafana-based Ambari Metrics Dashboard Builder

[Yusaku Sako (JIRA)]

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

Yusaku Sako commented on AMBARI-14893:
--

Looks like the rat check failed because AMBARI-14902 added a pom.xml file and 
is overriding the rules to ignore json files.


> Add Grafana-based Ambari Metrics Dashboard Builder
> --
>
> Key: AMBARI-14893
> URL: https://issues.apache.org/jira/browse/AMBARI-14893
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-metrics
>Affects Versions: 2.2.2
>Reporter: Yusaku Sako
>Assignee: Prajwal Rao
> Fix For: 2.2.2
>
> Attachments: AMBARI-14893.patch, screenshots.tar.gz
>
>
> This is a Grafana datasource that allows visualization of metrics stored in 
> Ambari Metrics Collector.



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

Re: Review Request 43174: HAWQ hdfs-client.xml should be updated when NN HA in enabled

[Lav Jain]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43174/#review117898
---


Ship it!




Ship It!

- Lav Jain


On Feb. 4, 2016, 3:17 a.m., Matt wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43174/
> ---
> 
> (Updated Feb. 4, 2016, 3:17 a.m.)
> 
> 
> Review request for Ambari, Alexander Denissov, Alejandro Fernandez, bhuvnesh 
> chaudhary, Goutam Tadi, Jaimin Jetly, jun aoki, Lav Jain, Newton Alex, and 
> Oleksandr Diachenko.
> 
> 
> Bugs: AMBARI-14910
> https://issues.apache.org/jira/browse/AMBARI-14910
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Scenario:
> - Install Ambari
> - Install a cluster with HDFS and HAWQ
> - Enable NN HA
> 
> After enabling NN HA, HAWQ's hdfs-client.xml is not populated with the HA 
> related parameters.
> 
> Ensure that HAWQ works after NN HA enabled on a cluster with HAWQ.
> 
> 
> Diffs
> -
> 
>   
> ambari-web/app/controllers/main/admin/highAvailability/nameNode/rollback_controller.js
>  aa3d3b0 
>   
> ambari-web/app/controllers/main/admin/highAvailability/nameNode/step3_controller.js
>  b420687 
>   
> ambari-web/app/controllers/main/admin/highAvailability/nameNode/step9_controller.js
>  7745c6b 
>   ambari-web/app/data/HDP2/ha_properties.js 8b2960d 
>   
> ambari-web/test/controllers/main/admin/highAvailability/nameNode/step3_controller_test.js
>  938b2c9 
> 
> Diff: https://reviews.apache.org/r/43174/diff/
> 
> 
> Testing
> ---
> 
> Manually tested.
> 
> Unit tests updated.
> 
> Unit Tests passed:
>   24160 tests complete (20 seconds)
>   156 tests pending
> 
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 52.595 s
> [INFO] Finished at: 2016-02-03T19:15:21-08:00
> [INFO] Final Memory: 12M/310M
> [INFO] 
> 
> 
> 
> Thanks,
> 
> Matt
> 
>

[jira] [Commented] (AMBARI-14786) Localhost configuration value for multiple host properties does not work properly

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14786:
-

FAILURE: Integrated in Ambari-branch-2.2 #291 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/291/])
AMBARI-14786. Localhost configuration value for multiple host properties 
(rnettleton: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=79681f8fb21a32c9ab2338e74a90f1a718e37ac0])
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java


> Localhost configuration value for multiple host properties does not work 
> properly
> -
>
> Key: AMBARI-14786
> URL: https://issues.apache.org/jira/browse/AMBARI-14786
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Daniel Gergely
>Assignee: Daniel Gergely
> Fix For: 2.4.0, 2.2.2
>
> Attachments: AMBARI-14786.patch, AMBARI-14786_branch-2.2.2.patch
>
>
> If the configuration value for a multiple host property is "localhost" AND 
> the corresponding component can be found in a single hostgroup, then it is 
> resolved to only one host from that hostgroup, instead of a list of them.
> Example:
> "hbase.zookeeper.quorum": "localhost"
> Zookeeper Server is assigned to a hostgroup that have 3 hosts (hostA, hostB, 
> hostC). Then after a Blueprint import, the value is incorrectly set:
> "hbase.zookeeper.quorum": "hostA"
> Correct value would be:
> "hbase.zookeeper.quorum": "hostA,hostB,hostC"



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

[jira] [Commented] (AMBARI-14833) Add role command order Start/Stop dependency between Metrics Collector and Zookeeper Server

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14833:
-

FAILURE: Integrated in Ambari-branch-2.2 #291 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/291/])
AMBARI-14833 : Add role command order Start/Stop dependency between (avijayan: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=db898020a11ca80e6f3c9b5de86e5683203fbb52])
* ambari-server/src/main/resources/stacks/HDP/2.0.6/role_command_order.json


> Add role command order Start/Stop dependency between Metrics Collector and 
> Zookeeper Server
> ---
>
> Key: AMBARI-14833
> URL: https://issues.apache.org/jira/browse/AMBARI-14833
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.2.1
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14833.patch
>
>
> AMS in distributed mode uses cluster zookeeper by default. Introducing the 
> following 2 dependency in the role command order for Start All & Stop All 
> makes sure AMS HBase is started and stopped cleanly.
> METRICS_COLLECTOR-START depends on ZOOKEEPER_SERVER-START
> ZOOKEEPER_SERVER-STOP depends on METRICS_COLLECTOR-STOP



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

[jira] [Commented] (AMBARI-14929) Enable security wizard hangs

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14929:
-

FAILURE: Integrated in Ambari-branch-2.2 #291 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/291/])
AMBARI-14929. Enable security wizard hangs (srimanth) (sgunturi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=49c03e04dbd74aa15b16280ac25aefeb3f686387])
* ambari-web/app/controllers/wizard/step7_controller.js


> Enable security wizard hangs 
> -
>
> Key: AMBARI-14929
> URL: https://issues.apache.org/jira/browse/AMBARI-14929
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.1
>Reporter: Srimanth Gunturi
>Assignee: Srimanth Gunturi
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-14929.patch, Screen Shot 2016-02-04 at 10.22.58 
> AM.png, Screen Shot 2016-02-04 at 10.23.27 AM.png
>
>
> Enabling security wizard hangs in the _Configure Kerberos_ page with below 
> error in the Javascript console.
> {noformat}
> Uncaught TypeError: Cannot convert undefined or null to object
> App.WizardStep7Controller.Em.Controller.extend.applyServicesConfigs @ 
> app.js:38205
> App.KerberosWizardStep2Controller.App.WizardStep7Controller.extend.loadStep @ 
> app.js:9420
> newFunc @ vendor.js:2627
> (anonymous function) @ app.js:174969
> invoke @ vendor.js:5055
> invokeNextTimers @ vendor.js:5552
> app.js:54881 
> App.serviceMetricsMapper execution time: 86.719ms
> {noformat}
> See attached screenshots.



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

[jira] [Commented] (AMBARI-14907) Metrics not displayed for "Last 1 year" period.

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14907:
-

FAILURE: Integrated in Ambari-branch-2.2 #291 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/291/])
AMBARI-14907 : Metrics not displayed for 'Last 1 year' period. (avijayan: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=dc4c1cfbd92b06c4ed0976b80e33ad5b189784d9])
* 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog222.java
* 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog222Test.java
* 
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-site.xml


> Metrics not displayed for "Last 1 year" period.
> ---
>
> Key: AMBARI-14907
> URL: https://issues.apache.org/jira/browse/AMBARI-14907
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.2.1
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>  Labels: ambari-metrics
> Fix For: 2.2.2
>
> Attachments: AMBARI-14907.patch
>
>
> PROBLEM
> Metrics not displayed for Last 1 year period interval on Ambari.
> BUG
> The daily aggregator discards the last timestamp because it is fractionally 
> more in the past than the cutOff time. We use 1*DAY as current cutoff. This 
> can cause checkpoints to be dropped intermittently.
> FIX
> Change cutOff multiplier for daily aggregators from 1 to 2.



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

[jira] [Commented] (AMBARI-14913) Show HAWQ default_segment_num parameter in General section

[jun aoki (JIRA)]

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

jun aoki commented on AMBARI-14913:
---

Committed to branch-2.2
305a85fb54902e294495f4d600685bff9d902c9b
Committed to trunk
3d7643b41c214dfc2bca4af2ab5dc37f27b8e652

> Show HAWQ default_segment_num parameter in General section
> --
>
> Key: AMBARI-14913
> URL: https://issues.apache.org/jira/browse/AMBARI-14913
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Reporter: Matt
>Assignee: Matt
>Priority: Trivial
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-14913-branch-2.2.patch, AMBARI-14913-trunk.patch
>
>
> Given the importance of the parameter and likelihood of tuning it 
> occasionally, HAWQ default_segment_num parameter should be displayed in 
> General section.



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

Review Request 43226: HAWQ service failure on single node clusters

[Newton Alex]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43226/
---

Review request for Ambari.


Bugs: AMBARI-14931
https://issues.apache.org/jira/browse/AMBARI-14931


Repository: ambari


Description
---

Fix for HAWQ service failure on single node clusters


Diffs
-

  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/utils.py
 e607a28 

Diff: https://reviews.apache.org/r/43226/diff/


Testing
---

Manual testing done

Single Node:
```
2016-02-04 20:24:22,716 - Validating data inserted, finding sum of all the 
inserted entries. Expected output: 55
2016-02-04 20:24:22,716 - Command executed: su - gpadmin -c "export 
PGPORT=10432 && source /usr/local/hawq/greenplum_path.sh && psql -t -d 
template1 -c \"SELECT sum(col1) FROM ambari_hawq_test;\""
2016-02-04 20:24:23,481 - Output:
  55


2016-02-04 20:24:23,482 - Dropping ambari_hawq_test table if exists
2016-02-04 20:24:23,482 - Command executed: su - gpadmin -c "export 
PGPORT=10432 && source /usr/local/hawq/greenplum_path.sh && psql -d template1 
-c \"DROP  TABLE IF EXISTS ambari_hawq_test;\""
2016-02-04 20:24:23,697 - Output:
DROP TABLE

2016-02-04 20:24:23,698 - PXF not installed. Skipping HAWQ-PXF checks...
2016-02-04 20:24:23,698 - Service check completed successfully
```


Multi Node:
```
2016-02-04 22:42:33,348 - Validating data inserted, finding sum of all the 
inserted entries. Expected output: 55
2016-02-04 22:42:33,349 - Command executed: su - gpadmin -c 'ssh -o 
StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null 
c6410.ambari.apache.org "export PGPORT=5432 && source 
/usr/local/hawq/greenplum_path.sh && psql -t -d template1 -c \"SELECT sum(col1) 
FROM ambari_hawq_test;\" " '
2016-02-04 22:42:33,904 - Output:
  55


2016-02-04 22:42:33,904 - Dropping ambari_hawq_test table if exists
2016-02-04 22:42:33,905 - Command executed: su - gpadmin -c 'ssh -o 
StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null 
c6410.ambari.apache.org "export PGPORT=5432 && source 
/usr/local/hawq/greenplum_path.sh && psql -d template1 -c \"DROP  TABLE IF 
EXISTS ambari_hawq_test;\" " '
2016-02-04 22:42:34,131 - Output:
DROP TABLE

2016-02-04 22:42:34,131 - PXF not installed. Skipping HAWQ-PXF checks...
2016-02-04 22:42:34,132 - Service check completed successfully
```


Thanks,

Newton Alex

Re: Review Request 43226: HAWQ service failure on single node clusters

[Matt]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43226/#review117903
---


Ship it!




Ship It!

- Matt


On Feb. 4, 2016, 3:08 p.m., Newton Alex wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43226/
> ---
> 
> (Updated Feb. 4, 2016, 3:08 p.m.)
> 
> 
> Review request for Ambari.
> 
> 
> Bugs: AMBARI-14931
> https://issues.apache.org/jira/browse/AMBARI-14931
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Fix for HAWQ service failure on single node clusters
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/utils.py
>  e607a28 
> 
> Diff: https://reviews.apache.org/r/43226/diff/
> 
> 
> Testing
> ---
> 
> Manual testing done
> 
> Single Node:
> ```
> 2016-02-04 20:24:22,716 - Validating data inserted, finding sum of all the 
> inserted entries. Expected output: 55
> 2016-02-04 20:24:22,716 - Command executed: su - gpadmin -c "export 
> PGPORT=10432 && source /usr/local/hawq/greenplum_path.sh && psql -t -d 
> template1 -c \"SELECT sum(col1) FROM ambari_hawq_test;\""
> 2016-02-04 20:24:23,481 - Output:
>   55
> 
> 
> 2016-02-04 20:24:23,482 - Dropping ambari_hawq_test table if exists
> 2016-02-04 20:24:23,482 - Command executed: su - gpadmin -c "export 
> PGPORT=10432 && source /usr/local/hawq/greenplum_path.sh && psql -d template1 
> -c \"DROP  TABLE IF EXISTS ambari_hawq_test;\""
> 2016-02-04 20:24:23,697 - Output:
> DROP TABLE
> 
> 2016-02-04 20:24:23,698 - PXF not installed. Skipping HAWQ-PXF checks...
> 2016-02-04 20:24:23,698 - Service check completed successfully
> ```
> 
> 
> Multi Node:
> ```
> 2016-02-04 22:42:33,348 - Validating data inserted, finding sum of all the 
> inserted entries. Expected output: 55
> 2016-02-04 22:42:33,349 - Command executed: su - gpadmin -c 'ssh -o 
> StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null 
> c6410.ambari.apache.org "export PGPORT=5432 && source 
> /usr/local/hawq/greenplum_path.sh && psql -t -d template1 -c \"SELECT 
> sum(col1) FROM ambari_hawq_test;\" " '
> 2016-02-04 22:42:33,904 - Output:
>   55
> 
> 
> 2016-02-04 22:42:33,904 - Dropping ambari_hawq_test table if exists
> 2016-02-04 22:42:33,905 - Command executed: su - gpadmin -c 'ssh -o 
> StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null 
> c6410.ambari.apache.org "export PGPORT=5432 && source 
> /usr/local/hawq/greenplum_path.sh && psql -d template1 -c \"DROP  TABLE IF 
> EXISTS ambari_hawq_test;\" " '
> 2016-02-04 22:42:34,131 - Output:
> DROP TABLE
> 
> 2016-02-04 22:42:34,131 - PXF not installed. Skipping HAWQ-PXF checks...
> 2016-02-04 22:42:34,132 - Service check completed successfully
> ```
> 
> 
> Thanks,
> 
> Newton Alex
> 
>

Re: Review Request 43154: AMBARI-14766: Selecting ALL groups does not work under Manage Alert Notifications

[Jonathan Hurley]

> On Feb. 4, 2016, 2:26 p.m., Jonathan Hurley wrote:
> > Ship It!
> 
> Keta Patel wrote:
> Thank you Jonathan!
> Could you help me with committing the patch please?

I can - but you should really get another +1 on it first. Let's see if anyone 
else reviews it.


- Jonathan


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43154/#review117867
---


On Feb. 4, 2016, 12:49 p.m., Keta Patel wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43154/
> ---
> 
> (Updated Feb. 4, 2016, 12:49 p.m.)
> 
> 
> Review request for Ambari, Alexandr Antonenko, Di Li, Jonathan Hurley, and 
> Oleg Nechiporenko.
> 
> 
> Bugs: AMBARI-14766
> https://issues.apache.org/jira/browse/AMBARI-14766
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Selecting "ALL" groups does not work under Manage Alert Notifications.
> 
> Reproduction Steps:-
> 1. Go to Alerts Tab in Ambari GUI
> 2. Actions --> Manage Notifications
> 3. Create New Alert Notification (Click the custom radio button for groups 
> and select couple of options eg HDFS, PIG)
> 4. Save it.
> 5. Edit the newly created Alert notification by clicking on the All radio 
> button. Everything gets selected.
> 6. Save it
> 
> Expected results:
> On Saving the Alert notification, the dialog box "Manage Alert Notification" 
> should show Groups as ALL ( or Show all the values eg HDFS, PIG, MR2). 
> Basically all the values should be selected.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertTargetResourceProvider.java
>  d28987d 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AlertTargetResourceProviderTest.java
>  f80b6f7 
>   
> ambari-web/app/controllers/main/alerts/manage_alert_notifications_controller.js
>  38e4e75 
> 
> Diff: https://reviews.apache.org/r/43154/diff/
> 
> 
> Testing
> ---
> 
> FIX:
> 
> The UI did not show "All" even after selecting "ALL" for Groups in the Edit 
> Alert Target pop-up because the property "selectedAlertGroup" was not set to 
> true even after the selection. This is fixed in the 
> "manageAlertGroupsController" in ambari-web.
> 
> However, this only resolved the UI issue. The alert notifications were still 
> not sent for all services after this change. This was because there was no 
> corresponding update made in the server code for this "ALL" Groups selection 
> for a Target. The DB has a table for AlertTarget (alert_target) and 
> AlertGroup (alert_group). There is a many-to-many mapping between these 2 
> tables, which is tracked in the combination table alert_group_target. 
> 1. This combination table was not getting updated for the "ALL" Groups 
> selection. 
> 2. Also, the Target was not updated as global in the DB. 
> 
> The "updateAlertTargets()" in "AlertTargetResourceProvider" is updated with 
> the fix for both these issues.
> The global property in Target is set if the ALL selection is made.
> And, if the Target is global, all the groups in the DB are upadted with the 
> current Target in the alert_group_target table.
> 
> 
> TESTS:
> ==
> 2 test cases are added to test for Custom and All Group selections.
> In case of Custom, the request to the REST API has group IDs passed and the 
> global paramter is false.
> The Target after this update must have global as false and should be mapped 
> to only the selected groups passed in the request.
> 
> In case of All, the request to the REST API does not have group IDs passed 
> and the global paramter is true.
> The Target after this update must contain global as true and should be mapped 
> to all the groups in the DB.
> 
> 
> Thanks,
> 
> Keta Patel
> 
>

[jira] [Commented] (AMBARI-14913) Show HAWQ default_segment_num parameter in General section

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-14913:


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

{color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

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

This message is automatically generated.

> Show HAWQ default_segment_num parameter in General section
> --
>
> Key: AMBARI-14913
> URL: https://issues.apache.org/jira/browse/AMBARI-14913
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Reporter: Matt
>Assignee: Matt
>Priority: Trivial
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-14913-branch-2.2.patch, AMBARI-14913-trunk.patch
>
>
> Given the importance of the parameter and likelihood of tuning it 
> occasionally, HAWQ default_segment_num parameter should be displayed in 
> General section.



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

Re: RU: HiveServer2 port conflict when RU 2.2 to 2.3 then to 2.4 ?

[Di Li]

Hello folks,
 
Thanks for the reply.  I was thinking of more like automatically increasing 
(for RU) or decreasing (for rolling downgrade) like by 10 against the base port 
( aka whatever port value a customer may specify during the cluster 
installation time, may not be the default 1 though).

For example, if the customer set HiveServer2 port to 3, then I guess the 
upgrade logic would ideally be able to change it to 30010 for RU (like 
port_value + 10)  and set that back to 3 (like port_value - 10) for 
downgrade.


 From: Alejandro Fernandez 
 To: "dev@ambari.apache.org" ; Di Li 
; Nate Cole ; Jonathan Hurley 
 
 Sent: Thursday, February 4, 2016 4:22 PM
 Subject: Re: RU: HiveServer2 port conflict when RU 2.2 to 2.3 then to 2.4 ?
   
That's a good observation. I think it should have logic to always swap.
If hive.server2.transport.mode is set to "binary", then swap
hive.server2.thrift.port between 10,000 and 10,010
If hive.server2.transport.mode is set to "http", then swap
hive.server2.http.port    between 10,001 and 10,011


Thanks,
Alejandro

On 2/4/16, 1:10 PM, "Di Li"  wrote:

>Hello folks,
>
>When rolling upgrade HDP 2.2 to 2.3, HiveServer2 port is changed from
>1 to 10010. The same port change logic is in upgrade-2.4.xml as well.
>
>But wouldn't this make no difference if I rolling upgrade a 2.3 cluster
>that was originally rolling upgrade from an HDP 2.2 cluster , where the
>port had already been changed to 10010? It'd be like changing the port
>from 10010 (on HDP 2.3) to 10010 (on HDP 2.4), right ?
>
>How does Ambari  handle Hive Server 2 port value change in  this
>continuously upgrade case?
>
>
>Thank you.
>
>Di Li


  

Re: Review Request 43125: AMBARI-14892 : Add Grafana as a component to AMS

[Sid Wagle]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43125/#review117892
---



Can you please add some unit tests. Changes look good.


ambari-metrics/ambari-metrics-grafana/conf/unix/ambari-metrics-grafana (line 21)


.pid ?



ambari-metrics/ambari-metrics-grafana/conf/unix/ams-grafana.ini (line 151)


Ambari sounds better.



ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py
 (line 66)


Is this required? This component does not support kerberization.


- Sid Wagle


On Feb. 4, 2016, 9:35 p.m., Aravindan Vijayan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43125/
> ---
> 
> (Updated Feb. 4, 2016, 9:35 p.m.)
> 
> 
> Review request for Ambari, Dmytro Sen, Sumit Mohanty, Sid Wagle, and Yusaku 
> Sako.
> 
> 
> Bugs: AMBARI-14892
> https://issues.apache.org/jira/browse/AMBARI-14892
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Add a MASTER component called Grafana to AMS service.
> 
> Include install and start/stop/status scripts for the grafana server.
> 
> Config Management for Ambari Metrics - Grafana also part of this patch.
> 
> 
> Diffs
> -
> 
>   ambari-metrics/ambari-metrics-grafana/conf/unix/ambari-metrics-grafana 
> 1de5401 
>   ambari-metrics/ambari-metrics-grafana/conf/unix/ams-grafana-env.sh 20986cb 
>   ambari-metrics/ambari-metrics-grafana/conf/unix/ams-grafana.ini e42a92f 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-grafana-env.xml
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-grafana-ini.xml
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/metainfo.xml
>  48469df 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py
>  8fdf4ba 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py
>  cf498ec 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_monitor.py
>  a1d6a1d 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py
>  a1de919 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/status.py
>  59466ad 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/status_params.py
>  d446baa 
>   ambari-server/src/main/resources/stacks/HDP/2.0.6/role_command_order.json 
> a480e2a 
> 
> Diff: https://reviews.apache.org/r/43125/diff/
> 
> 
> Testing
> ---
> 
> Manual testing done by installing ambari-metrics-grafana rpm on a host and 
> testing the patch.
> 
> 
> Thanks,
> 
> Aravindan Vijayan
> 
>

[jira] [Commented] (AMBARI-14905) Add API directive to force toggling Kerberos if the cluster's security type has not changed

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14905:
-

FAILURE: Integrated in Ambari-trunk-Commit #4277 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4277/])
AMBARI-14905. Add API directive to force toggling Kerberos if the (rlevas: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=eb3f995965b2749910ceae9e5cc8f8bc043e6862])
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariManagementControllerImplTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelperImpl.java
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/KerberosHelperTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/api/resources/ClusterResourceDefinition.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelper.java


> Add API directive to force toggling Kerberos if the cluster's security type 
> has not changed
> ---
>
> Key: AMBARI-14905
> URL: https://issues.apache.org/jira/browse/AMBARI-14905
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: kerberos, rest_api
> Fix For: 2.2.2
>
> Attachments: AMBARI-14905_branch-2.2_01.patch, 
> AMBARI-14905_branch-2.2_02.patch, AMBARI-14905_branch-2.2_03.patch, 
> AMBARI-14905_trunk_01.patch, AMBARI-14905_trunk_02.patch, 
> AMBARI-14905_trunk_03.patch
>
>
> Add an API directive to force toggling Kerberos if the cluster's security 
> type has not changed.  
> This is useful for _retry_ attempts to enable or disable Kerberos when the 
> workflow progressed far enough to store the _new_ security type.  
> Trying to enable Kerberos when the cluster's security type is already set to 
> {{KERBEROS}} will result in a successful response from the Ambari server but 
> no actions will be performed.  Same for attempting to disable Kerberos when 
> the cluster's security type is already set to {{NONE}}.  
> By forcing the operation using the {{force_toggle_kerberos=true}} directive, 
> the security type check is avoided, thus allowing the _retry_ operation to 
> proceed. 
> Example: 
> {code}
> PUT /api/v1/clusters/CLUSTER_NAME?force_toggle_kerberos=true
> {
>   "Clusters" : {
> "security_type" : "KERBEROS"
> }
> }
> {code}



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

[jira] [Commented] (AMBARI-14929) Enable security wizard hangs

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14929:
-

FAILURE: Integrated in Ambari-trunk-Commit #4277 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4277/])
AMBARI-14929. Enable security wizard hangs (srimanth) (sgunturi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ab06c68acafd9e31a24e6b136f5772fdbf25655c])
* ambari-web/app/controllers/wizard/step7_controller.js


> Enable security wizard hangs 
> -
>
> Key: AMBARI-14929
> URL: https://issues.apache.org/jira/browse/AMBARI-14929
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.1
>Reporter: Srimanth Gunturi
>Assignee: Srimanth Gunturi
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-14929.patch, Screen Shot 2016-02-04 at 10.22.58 
> AM.png, Screen Shot 2016-02-04 at 10.23.27 AM.png
>
>
> Enabling security wizard hangs in the _Configure Kerberos_ page with below 
> error in the Javascript console.
> {noformat}
> Uncaught TypeError: Cannot convert undefined or null to object
> App.WizardStep7Controller.Em.Controller.extend.applyServicesConfigs @ 
> app.js:38205
> App.KerberosWizardStep2Controller.App.WizardStep7Controller.extend.loadStep @ 
> app.js:9420
> newFunc @ vendor.js:2627
> (anonymous function) @ app.js:174969
> invoke @ vendor.js:5055
> invokeNextTimers @ vendor.js:5552
> app.js:54881 
> App.serviceMetricsMapper execution time: 86.719ms
> {noformat}
> See attached screenshots.



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

[jira] [Commented] (AMBARI-14910) HAWQ hdfs-client.xml should be updated when NN HA in enabled

[jun aoki (JIRA)]

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

jun aoki commented on AMBARI-14910:
---

[~jluniya][~jaimin][~aantonenko][~akovalenko], I see some contributions from 
you guys to the files for this patch.
I believe it is pretty specific to HAWQ but wanted to touch based with you if 
you have anything to say.
Will wait for a few hours (the patches were submitted yesterday) before I go 
ahead and commit. let us know.

> HAWQ hdfs-client.xml should be updated when NN HA in enabled
> 
>
> Key: AMBARI-14910
> URL: https://issues.apache.org/jira/browse/AMBARI-14910
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-web
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-14910-branch-2.2.patch, AMBARI-14910-trunk.patch
>
>
> Scenario:
> - Install Ambari
> - Install a cluster with HDFS and HAWQ
> - Enable NN HA
> After enabling NN HA, HAWQ's hdfs-client.xml is not populated with the HA 
> related parameters.
> Ensure that HAWQ works after NN HA enabled on a cluster with HAWQ.



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

[jira] [Updated] (AMBARI-14917) Edit WEB Alert issues

[Oleg Nechiporenko (JIRA)]

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

Oleg Nechiporenko updated AMBARI-14917:
---
Attachment: (was: AMBARI-14917.patch)

> Edit WEB Alert issues
> -
>
> Key: AMBARI-14917
> URL: https://issues.apache.org/jira/browse/AMBARI-14917
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14917_branch-2.2.patch, web-alert-edit.pptx
>
>
> See attached.



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

[jira] [Updated] (AMBARI-14917) Edit WEB Alert issues

[Oleg Nechiporenko (JIRA)]

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

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

> Edit WEB Alert issues
> -
>
> Key: AMBARI-14917
> URL: https://issues.apache.org/jira/browse/AMBARI-14917
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14917.patch, AMBARI-14917_branch-2.2.patch, 
> web-alert-edit.pptx
>
>
> See attached.



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

[jira] [Commented] (AMBARI-14925) Make AMS Grafana component available as a DEB package

[Dmytro Sen (JIRA)]

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

Dmytro Sen commented on AMBARI-14925:
-

the failure is not related to this issue
Failed unit test
{code}
org.apache.ambari.server.upgrade.UpgradeCatalog222Test.testExecuteDMLUpdates
{code}

> Make AMS Grafana component available as a DEB package
> -
>
> Key: AMBARI-14925
> URL: https://issues.apache.org/jira/browse/AMBARI-14925
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-metrics
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14925-trunk.patch
>
>
> Make AMS Grafana component available as a DEB package



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

[jira] [Updated] (AMBARI-14933) ranger audit db password is required even when audit to db is off

[Andrii Babiichuk (JIRA)]

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

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

> ranger audit db password is required even when audit to db is off
> -
>
> Key: AMBARI-14933
> URL: https://issues.apache.org/jira/browse/AMBARI-14933
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, ambari-web
>Affects Versions: 2.2.1
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 2.2.2
>
> Attachments: AMBARI-14933.patch
>
>
> Install ranger service after cluster is up and in customize ranger configs 
> user is asked to provide password for ranger audit to db even though audit to 
> DB is turned off.
> If the feature is turned off we should hide password for db.



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

[jira] [Created] (AMBARI-14933) ranger audit db password is required even when audit to db is off

[Andrii Babiichuk (JIRA)]

Andrii Babiichuk created AMBARI-14933:
-

 Summary: ranger audit db password is required even when audit to 
db is off
 Key: AMBARI-14933
 URL: https://issues.apache.org/jira/browse/AMBARI-14933
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server, ambari-web
Affects Versions: 2.2.1
Reporter: Andrii Babiichuk
Assignee: Andrii Babiichuk
 Fix For: 2.2.2


Install ranger service after cluster is up and in customize ranger configs user 
is asked to provide password for ranger audit to db even though audit to DB is 
turned off.
If the feature is turned off we should hide password for db.



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

Re: Review Request 42572: Ambari server throws error when unused configs are present in blueprint

[Sebastian Toader]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/42572/#review117985
---


Ship it!




Ship It!

- Sebastian Toader


On Feb. 5, 2016, 1:51 a.m., Oliver Szabo wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/42572/
> ---
> 
> (Updated Feb. 5, 2016, 1:51 a.m.)
> 
> 
> Review request for Ambari, Laszlo Puskas, Robert Nettleton, Sandor Magyari, 
> Sumit Mohanty, and Sebastian Toader.
> 
> 
> Bugs: AMBARI-14745
> https://issues.apache.org/jira/browse/AMBARI-14745
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> In case of a blueprint contains unused config types -> updaters can apply on 
> the unused properties. In same cases this can cause exceptions. E.g.: single 
> host updater on a property -> no host found for a service.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/topology/ClusterConfigurationRequest.java
>  464aee7 
>   
> ambari-server/src/main/java/org/apache/ambari/server/topology/Configuration.java
>  108ff74 
>   
> ambari-server/src/test/java/org/apache/ambari/server/topology/ClusterConfigurationRequestTest.java
>  5967a64 
>   
> ambari-server/src/test/java/org/apache/ambari/server/topology/ClusterInstallWithoutStartTest.java
>  dd66b1b 
>   
> ambari-server/src/test/java/org/apache/ambari/server/topology/ConfigurationTest.java
>  e971e03 
>   
> ambari-server/src/test/java/org/apache/ambari/server/topology/TopologyManagerTest.java
>  7810f92 
> 
> Diff: https://reviews.apache.org/r/42572/diff/
> 
> 
> Testing
> ---
> 
> Unit testing is in progress.
> FT: blueprints with unused config types.
> 
> 
> Thanks,
> 
> Oliver Szabo
> 
>

[jira] [Updated] (AMBARI-14745) Ambari server throws error when unused configs are present in blueprint

[JIRA]

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

Olivér Szabó updated AMBARI-14745:
--
Attachment: AMBARI-14745.patch

> Ambari server throws error when unused configs are present in blueprint
> ---
>
> Key: AMBARI-14745
> URL: https://issues.apache.org/jira/browse/AMBARI-14745
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14745.patch, AMBARI-14745_branch-2.2.patch
>
>
> When trying to create unsecure cluster, ambari server throws error when 
> Ranger configs are present in the blueprint.
> Error Message seen:
> “ [pool-6-thread-1] ERROR org.apache.ambari.server.topology.TopologyManager - 
> TopologyManager.ConfigureClusterTask: An exception occurred while attempting 
> to process cluster configs and set on cluster: 
> java.lang.IllegalArgumentException: Unable to update configuration property 
> 'policymgr_external_url' with topology information. Component 'RANGER_ADMIN' 
> is mapped to an invalid number of hosts '0'.
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$SingleHostTopologyUpdater.updateForClusterCreate(BlueprintConfigurationProcessor.java:1270)



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

[jira] [Updated] (AMBARI-14914) Update Spark to 1.6.1 in HDP 2.5

[Jeff Zhang (JIRA)]

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

Jeff Zhang updated AMBARI-14914:

Summary: Update Spark to 1.6.1 in HDP 2.5  (was: Update Spark to 1.6.1 in 
HDP 2.4)

> Update Spark to 1.6.1 in HDP 2.5
> 
>
> Key: AMBARI-14914
> URL: https://issues.apache.org/jira/browse/AMBARI-14914
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Reporter: Jeff Zhang
>Assignee: Jeff Zhang
>Priority: Minor
>




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

[jira] [Updated] (AMBARI-14932) "download zip" does not work

[Keta Patel (JIRA)]

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

Keta Patel updated AMBARI-14932:

Attachment: screenshot.tiff

> "download zip"  does not work
> -
>
> Key: AMBARI-14932
> URL: https://issues.apache.org/jira/browse/AMBARI-14932
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views, contrib
>Affects Versions: trunk
>Reporter: Keta Patel
>Assignee: Keta Patel
> Attachments: screenshot.tiff
>
>
> Steps to Reproduce:
> 1. go to "View" - "FILES" - " Create Instance"
> 2. go to hdfs file view
> 3. click "download zip" icon
> The click doesn't download any file. The REST call returns 200 OK status.



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

[jira] [Commented] (AMBARI-14902) Make AMS Grafana component available as a repo package

[jun aoki (JIRA)]

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

jun aoki commented on AMBARI-14902:
---

They used to be populated 
ambari-metrics/ambari-metrics-assembly/target/rpm/ambari-metrics-collector/RPMS/x86_64/ambari-metrics-collector-*rpm
and
ambari-metrics/ambari-metrics-assembly/target/rpm/ambari-metrics-hadoop-sink/RPMS/x86_64/ambari-metrics-hadoop-sink-*rpm

The sink seems to find here
ambari-metrics/ambari-metrics-hadoop-sink/target/
but I can not find the collector.rpm. which is still required by 
https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/metainfo.xml#L72

> Make AMS Grafana component available as a repo package
> --
>
> Key: AMBARI-14902
> URL: https://issues.apache.org/jira/browse/AMBARI-14902
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-metrics
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14902-trunk-2.patch
>
>
> Grafana 2.6.0 to be installed as an AMS component. We need this to be a part 
> of the Ambari repo so that Ambari can install it with AMS.



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

[jira] [Commented] (AMBARI-14884) Hawq standby host config should be removed on single node cluster during initial cluster installation

[bhuvnesh chaudhary (JIRA)]

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

bhuvnesh chaudhary commented on AMBARI-14884:
-

Thanks [~srimanth.gunturi] for the update and catch. My bad, i should have 
tested it with security enabled as well.

> Hawq standby host config should be removed on single node cluster during 
> initial cluster installation
> -
>
> Key: AMBARI-14884
> URL: https://issues.apache.org/jira/browse/AMBARI-14884
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: bhuvnesh chaudhary
>Assignee: bhuvnesh chaudhary
>Priority: Trivial
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-14884-1.patch, AMBARI-14884-branch-2.2.patch, 
> AMBARI-14884.patch
>
>
> Hawq standby host config should be removed on single node cluster during 
> initial cluster installation.
> Currently, it works only if the cluster is installed and Hawq is added later, 
> but during initial single node installation of cluster with Hawq, it does not.



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

[jira] [Commented] (AMBARI-14933) ranger audit db password is required even when audit to db is off

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-14933:


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

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

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

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

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

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

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

This message is automatically generated.

> ranger audit db password is required even when audit to db is off
> -
>
> Key: AMBARI-14933
> URL: https://issues.apache.org/jira/browse/AMBARI-14933
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, ambari-web
>Affects Versions: 2.2.1
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 2.2.2
>
> Attachments: AMBARI-14933.patch
>
>
> Install ranger service after cluster is up and in customize ranger configs 
> user is asked to provide password for ranger audit to db even though audit to 
> DB is turned off.
> If the feature is turned off we should hide password for db.



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

[jira] [Updated] (AMBARI-14892) Add Grafana as a component to AMS

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan updated AMBARI-14892:
---
Attachment: AMBARI-14892-trunk.patch

> Add Grafana as a component to AMS
> -
>
> Key: AMBARI-14892
> URL: https://issues.apache.org/jira/browse/AMBARI-14892
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-metrics
>Affects Versions: 2.2.1
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14892-trunk.patch, AMBARI-14892.patch
>
>
> Add a MASTER component called Grafana to AMS service.
> Include install and start/stop script for the grafana server



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

[jira] [Commented] (AMBARI-14917) Edit WEB Alert issues

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-14917:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12786430/AMBARI-14917.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 2 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/5218//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/5218//console

This message is automatically generated.

> Edit WEB Alert issues
> -
>
> Key: AMBARI-14917
> URL: https://issues.apache.org/jira/browse/AMBARI-14917
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14917.patch, AMBARI-14917_branch-2.2.patch, 
> web-alert-edit.pptx
>
>
> See attached.



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

[jira] [Updated] (AMBARI-14885) After exporting blueprint from existing cluster knox_master_secret is exported

[Tuong Truong (JIRA)]

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

Tuong Truong updated AMBARI-14885:
--
Assignee: Amruta Borkar

> After exporting blueprint from existing cluster knox_master_secret is exported
> --
>
> Key: AMBARI-14885
> URL: https://issues.apache.org/jira/browse/AMBARI-14885
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, blueprints
>Affects Versions: 2.2.0
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
>
> After exporting blueprint from existing cluster knox_master_secret is also 
> exported
> Due to this property, the same blueprint file cannot be used to create 
> another cluster, this property need to be removed to create a cluster from 
> the file.
> User needs to remove the property in order to use the blueprint.
> Error shown:
> {
>   "status" : 400,
>   "message" : "Blueprint configuration validation failed: Secret references 
> are not allowed in blueprints, replace following properties with real 
> passwords:\n  Config:knox-env Property:knox_master_secret\n"
> }



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

[jira] [Assigned] (AMBARI-14701) assign_master_components.js breaks next step in certain case

[Matt (JIRA)]

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

Matt reassigned AMBARI-14701:
-

Assignee: Matt  (was: jun aoki)

> assign_master_components.js breaks next step in certain case
> 
>
> Key: AMBARI-14701
> URL: https://issues.apache.org/jira/browse/AMBARI-14701
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Reporter: jun aoki
>Assignee: Matt
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> We have a custom wizard with AssignMasterComponents mixin and 
> useServerValidation is set true.
> Select Host page shows a confirmation when there is a validation error 
> validated on the server side, which is good.
> However, if you cancel the confirmation, you can no longer go to Next page by 
> clicking Next button.



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

Re: Review Request 43154: AMBARI-14766: Selecting ALL groups does not work under Manage Alert Notifications

[Keta Patel]

> On Feb. 4, 2016, 7:26 p.m., Jonathan Hurley wrote:
> > Ship It!
> 
> Keta Patel wrote:
> Thank you Jonathan!
> Could you help me with committing the patch please?
> 
> Jonathan Hurley wrote:
> I can - but you should really get another +1 on it first. Let's see if 
> anyone else reviews it.

Ok, thank you


- Keta


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43154/#review117867
---


On Feb. 4, 2016, 5:49 p.m., Keta Patel wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43154/
> ---
> 
> (Updated Feb. 4, 2016, 5:49 p.m.)
> 
> 
> Review request for Ambari, Alexandr Antonenko, Di Li, Jonathan Hurley, and 
> Oleg Nechiporenko.
> 
> 
> Bugs: AMBARI-14766
> https://issues.apache.org/jira/browse/AMBARI-14766
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Selecting "ALL" groups does not work under Manage Alert Notifications.
> 
> Reproduction Steps:-
> 1. Go to Alerts Tab in Ambari GUI
> 2. Actions --> Manage Notifications
> 3. Create New Alert Notification (Click the custom radio button for groups 
> and select couple of options eg HDFS, PIG)
> 4. Save it.
> 5. Edit the newly created Alert notification by clicking on the All radio 
> button. Everything gets selected.
> 6. Save it
> 
> Expected results:
> On Saving the Alert notification, the dialog box "Manage Alert Notification" 
> should show Groups as ALL ( or Show all the values eg HDFS, PIG, MR2). 
> Basically all the values should be selected.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertTargetResourceProvider.java
>  d28987d 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AlertTargetResourceProviderTest.java
>  f80b6f7 
>   
> ambari-web/app/controllers/main/alerts/manage_alert_notifications_controller.js
>  38e4e75 
> 
> Diff: https://reviews.apache.org/r/43154/diff/
> 
> 
> Testing
> ---
> 
> FIX:
> 
> The UI did not show "All" even after selecting "ALL" for Groups in the Edit 
> Alert Target pop-up because the property "selectedAlertGroup" was not set to 
> true even after the selection. This is fixed in the 
> "manageAlertGroupsController" in ambari-web.
> 
> However, this only resolved the UI issue. The alert notifications were still 
> not sent for all services after this change. This was because there was no 
> corresponding update made in the server code for this "ALL" Groups selection 
> for a Target. The DB has a table for AlertTarget (alert_target) and 
> AlertGroup (alert_group). There is a many-to-many mapping between these 2 
> tables, which is tracked in the combination table alert_group_target. 
> 1. This combination table was not getting updated for the "ALL" Groups 
> selection. 
> 2. Also, the Target was not updated as global in the DB. 
> 
> The "updateAlertTargets()" in "AlertTargetResourceProvider" is updated with 
> the fix for both these issues.
> The global property in Target is set if the ALL selection is made.
> And, if the Target is global, all the groups in the DB are upadted with the 
> current Target in the alert_group_target table.
> 
> 
> TESTS:
> ==
> 2 test cases are added to test for Custom and All Group selections.
> In case of Custom, the request to the REST API has group IDs passed and the 
> global paramter is false.
> The Target after this update must have global as false and should be mapped 
> to only the selected groups passed in the request.
> 
> In case of All, the request to the REST API does not have group IDs passed 
> and the global paramter is true.
> The Target after this update must contain global as true and should be mapped 
> to all the groups in the DB.
> 
> 
> Thanks,
> 
> Keta Patel
> 
>

Re: Review Request 43226: HAWQ service failure on single node clusters

[Lav Jain]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43226/#review117909
---


Ship it!




Ship It!

- Lav Jain


On Feb. 4, 2016, 11:08 p.m., Newton Alex wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43226/
> ---
> 
> (Updated Feb. 4, 2016, 11:08 p.m.)
> 
> 
> Review request for Ambari.
> 
> 
> Bugs: AMBARI-14931
> https://issues.apache.org/jira/browse/AMBARI-14931
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Fix for HAWQ service failure on single node clusters
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/utils.py
>  e607a28 
> 
> Diff: https://reviews.apache.org/r/43226/diff/
> 
> 
> Testing
> ---
> 
> Manual testing done
> 
> Single Node:
> ```
> 2016-02-04 20:24:22,716 - Validating data inserted, finding sum of all the 
> inserted entries. Expected output: 55
> 2016-02-04 20:24:22,716 - Command executed: su - gpadmin -c "export 
> PGPORT=10432 && source /usr/local/hawq/greenplum_path.sh && psql -t -d 
> template1 -c \"SELECT sum(col1) FROM ambari_hawq_test;\""
> 2016-02-04 20:24:23,481 - Output:
>   55
> 
> 
> 2016-02-04 20:24:23,482 - Dropping ambari_hawq_test table if exists
> 2016-02-04 20:24:23,482 - Command executed: su - gpadmin -c "export 
> PGPORT=10432 && source /usr/local/hawq/greenplum_path.sh && psql -d template1 
> -c \"DROP  TABLE IF EXISTS ambari_hawq_test;\""
> 2016-02-04 20:24:23,697 - Output:
> DROP TABLE
> 
> 2016-02-04 20:24:23,698 - PXF not installed. Skipping HAWQ-PXF checks...
> 2016-02-04 20:24:23,698 - Service check completed successfully
> ```
> 
> 
> Multi Node:
> ```
> 2016-02-04 22:42:33,348 - Validating data inserted, finding sum of all the 
> inserted entries. Expected output: 55
> 2016-02-04 22:42:33,349 - Command executed: su - gpadmin -c 'ssh -o 
> StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null 
> c6410.ambari.apache.org "export PGPORT=5432 && source 
> /usr/local/hawq/greenplum_path.sh && psql -t -d template1 -c \"SELECT 
> sum(col1) FROM ambari_hawq_test;\" " '
> 2016-02-04 22:42:33,904 - Output:
>   55
> 
> 
> 2016-02-04 22:42:33,904 - Dropping ambari_hawq_test table if exists
> 2016-02-04 22:42:33,905 - Command executed: su - gpadmin -c 'ssh -o 
> StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null 
> c6410.ambari.apache.org "export PGPORT=5432 && source 
> /usr/local/hawq/greenplum_path.sh && psql -d template1 -c \"DROP  TABLE IF 
> EXISTS ambari_hawq_test;\" " '
> 2016-02-04 22:42:34,131 - Output:
> DROP TABLE
> 
> 2016-02-04 22:42:34,131 - PXF not installed. Skipping HAWQ-PXF checks...
> 2016-02-04 22:42:34,132 - Service check completed successfully
> ```
> 
> 
> Thanks,
> 
> Newton Alex
> 
>

Re: Review Request 43125: AMBARI-14892 : Add Grafana as a component to AMS

[Aravindan Vijayan]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43125/
---

(Updated Feb. 4, 2016, 11:54 p.m.)


Review request for Ambari, Dmytro Sen, Sumit Mohanty, Sid Wagle, and Yusaku 
Sako.


Changes
---

Addressed review comments. 

Added python unit tests for Grafana.

Fixed an issue in Collector while requested for precision data.


Bugs: AMBARI-14892
https://issues.apache.org/jira/browse/AMBARI-14892


Repository: ambari


Description
---

Add a MASTER component called Grafana to AMS service.

Include install and start/stop/status scripts for the grafana server.

Config Management for Ambari Metrics - Grafana also part of this patch.


Diffs (updated)
-

  ambari-metrics/ambari-metrics-grafana/conf/unix/ambari-metrics-grafana 
1de5401 
  ambari-metrics/ambari-metrics-grafana/conf/unix/ams-grafana-env.sh 20986cb 
  ambari-metrics/ambari-metrics-grafana/conf/unix/ams-grafana.ini e42a92f 
  
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/PhoenixHBaseAccessor.java
 5067454 
  
ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/AbstractMiniHBaseClusterTest.java
 8cbc56b 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-grafana-env.xml
 PRE-CREATION 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-grafana-ini.xml
 PRE-CREATION 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/metainfo.xml
 48469df 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py
 8fdf4ba 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py
 cf498ec 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py
 PRE-CREATION 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_monitor.py
 a1d6a1d 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py
 a1de919 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/status.py
 59466ad 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/status_params.py
 d446baa 
  ambari-server/src/main/resources/stacks/HDP/2.0.6/role_command_order.json 
a480e2a 
  
ambari-server/src/test/python/stacks/2.0.6/AMBARI_METRICS/test_metrics_grafana.py
 PRE-CREATION 
  ambari-server/src/test/python/stacks/2.0.6/configs/default.json f421aec 

Diff: https://reviews.apache.org/r/43125/diff/


Testing
---

Manual testing done by installing ambari-metrics-grafana rpm on a host and 
testing the patch.


Thanks,

Aravindan Vijayan

[jira] [Updated] (AMBARI-14932) "download zip" does not work

[Keta Patel (JIRA)]

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

Keta Patel updated AMBARI-14932:

Attachment: adapter.tiff
DownloadService.tiff
file_1.tiff
file_2.tiff

> "download zip"  does not work
> -
>
> Key: AMBARI-14932
> URL: https://issues.apache.org/jira/browse/AMBARI-14932
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views, contrib
>Affects Versions: trunk
>Reporter: Keta Patel
>Assignee: Keta Patel
> Attachments: DownloadService.tiff, adapter.tiff, file_1.tiff, 
> file_2.tiff, screenshot.tiff
>
>
> Steps to Reproduce:
> 1. go to "View" - "FILES" - " Create Instance"
> 2. go to hdfs file view
> 3. click "download zip" icon
> The click doesn't download any file. The REST call returns 200 OK status.



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

[jira] [Commented] (AMBARI-14905) Add API directive to force toggling Kerberos if the cluster's security type has not changed

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14905:
-

ABORTED: Integrated in Ambari-branch-2.2 #292 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/292/])
AMBARI-14905. Add API directive to force toggling Kerberos if the (rlevas: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=feca33de8217b61e0c4d7a77dbfb1955ca971edb])
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelperImpl.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/KerberosHelperTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariManagementControllerImplTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/api/resources/ClusterResourceDefinition.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelper.java


> Add API directive to force toggling Kerberos if the cluster's security type 
> has not changed
> ---
>
> Key: AMBARI-14905
> URL: https://issues.apache.org/jira/browse/AMBARI-14905
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: kerberos, rest_api
> Fix For: 2.2.2
>
> Attachments: AMBARI-14905_branch-2.2_01.patch, 
> AMBARI-14905_branch-2.2_02.patch, AMBARI-14905_branch-2.2_03.patch, 
> AMBARI-14905_trunk_01.patch, AMBARI-14905_trunk_02.patch, 
> AMBARI-14905_trunk_03.patch
>
>
> Add an API directive to force toggling Kerberos if the cluster's security 
> type has not changed.  
> This is useful for _retry_ attempts to enable or disable Kerberos when the 
> workflow progressed far enough to store the _new_ security type.  
> Trying to enable Kerberos when the cluster's security type is already set to 
> {{KERBEROS}} will result in a successful response from the Ambari server but 
> no actions will be performed.  Same for attempting to disable Kerberos when 
> the cluster's security type is already set to {{NONE}}.  
> By forcing the operation using the {{force_toggle_kerberos=true}} directive, 
> the security type check is avoided, thus allowing the _retry_ operation to 
> proceed. 
> Example: 
> {code}
> PUT /api/v1/clusters/CLUSTER_NAME?force_toggle_kerberos=true
> {
>   "Clusters" : {
> "security_type" : "KERBEROS"
> }
> }
> {code}



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

[jira] [Commented] (AMBARI-14893) Add Grafana-based Ambari Metrics Dashboard Builder

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14893:
-

ABORTED: Integrated in Ambari-branch-2.2 #292 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/292/])
AMBARI-14893. Add Grafana-based Ambari Metrics Dashboard Builder. (yusaku: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4a739b2d33aa04d36e0e7632191ef3428c7fa04d])
* ambari-metrics/ambari-metrics-grafana/pom.xml


> Add Grafana-based Ambari Metrics Dashboard Builder
> --
>
> Key: AMBARI-14893
> URL: https://issues.apache.org/jira/browse/AMBARI-14893
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-metrics
>Affects Versions: 2.2.2
>Reporter: Yusaku Sako
>Assignee: Prajwal Rao
> Fix For: 2.2.2
>
> Attachments: AMBARI-14893.patch, screenshots.tar.gz
>
>
> This is a Grafana datasource that allows visualization of metrics stored in 
> Ambari Metrics Collector.



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

Re: Review Request 43125: AMBARI-14892 : Add Grafana as a component to AMS

[Sid Wagle]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43125/#review117931
---


Ship it!




Ship It!

- Sid Wagle


On Feb. 4, 2016, 11:54 p.m., Aravindan Vijayan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43125/
> ---
> 
> (Updated Feb. 4, 2016, 11:54 p.m.)
> 
> 
> Review request for Ambari, Dmytro Sen, Sumit Mohanty, Sid Wagle, and Yusaku 
> Sako.
> 
> 
> Bugs: AMBARI-14892
> https://issues.apache.org/jira/browse/AMBARI-14892
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Add a MASTER component called Grafana to AMS service.
> 
> Include install and start/stop/status scripts for the grafana server.
> 
> Config Management for Ambari Metrics - Grafana also part of this patch.
> 
> 
> Diffs
> -
> 
>   ambari-metrics/ambari-metrics-grafana/conf/unix/ambari-metrics-grafana 
> 1de5401 
>   ambari-metrics/ambari-metrics-grafana/conf/unix/ams-grafana-env.sh 20986cb 
>   ambari-metrics/ambari-metrics-grafana/conf/unix/ams-grafana.ini e42a92f 
>   
> ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/PhoenixHBaseAccessor.java
>  5067454 
>   
> ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/AbstractMiniHBaseClusterTest.java
>  8cbc56b 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-grafana-env.xml
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-grafana-ini.xml
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/metainfo.xml
>  48469df 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py
>  8fdf4ba 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py
>  cf498ec 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_monitor.py
>  a1d6a1d 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py
>  a1de919 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/status.py
>  59466ad 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/status_params.py
>  d446baa 
>   ambari-server/src/main/resources/stacks/HDP/2.0.6/role_command_order.json 
> a480e2a 
>   
> ambari-server/src/test/python/stacks/2.0.6/AMBARI_METRICS/test_metrics_grafana.py
>  PRE-CREATION 
>   ambari-server/src/test/python/stacks/2.0.6/configs/default.json f421aec 
> 
> Diff: https://reviews.apache.org/r/43125/diff/
> 
> 
> Testing
> ---
> 
> Manual testing done by installing ambari-metrics-grafana rpm on a host and 
> testing the patch.
> 
> 
> Thanks,
> 
> Aravindan Vijayan
> 
>

[jira] [Commented] (AMBARI-14928) Ambari throws NPE in kerberos mode U14/S11

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-14928:


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

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

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

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

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

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

  org.apache.ambari.server.upgrade.UpgradeCatalog222Test

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

This message is automatically generated.

> Ambari throws NPE in kerberos mode U14/S11
> --
>
> Key: AMBARI-14928
> URL: https://issues.apache.org/jira/browse/AMBARI-14928
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14928-trunk.patch
>
>
> From ambari-server.log:
> {code}
> 04 Feb 2016 13:02:35,377 ERROR [main] KerberosChecker:115 - Cannot locate KDC
> 04 Feb 2016 13:02:35,378 ERROR [main] AmbariServer:822 - Failed to run the 
> Ambari Server
> org.apache.ambari.server.AmbariException: Ambari Server Kerberos credentials 
> check failed. 
> Check KDC availability and JAAS configuration in 
> /etc/ambari-server/conf/krb5JAASLogin.conf
>   at 
> org.apache.ambari.server.controller.utilities.KerberosChecker.checkJaasConfiguration(KerberosChecker.java:116)
>   at 
> org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:817)
> 04 Feb 2016 13:02:35,380 ERROR [main] AmbariServer:721 - Error stopping the 
> server
> java.lang.NullPointerException
>   at 
> org.apache.ambari.server.controller.AmbariServer.stop(AmbariServer.java:719)
>   at 
> org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:824)
> {code}



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

[jira] [Updated] (AMBARI-14892) Add Grafana as a component to AMS

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan updated AMBARI-14892:
---
Attachment: AMBARI-14892.patch

> Add Grafana as a component to AMS
> -
>
> Key: AMBARI-14892
> URL: https://issues.apache.org/jira/browse/AMBARI-14892
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-metrics
>Affects Versions: 2.2.1
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14892.patch
>
>
> Add a MASTER component called Grafana to AMS service.
> Include install and start/stop script for the grafana server



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

[jira] [Commented] (AMBARI-14931) HAWQ service checks failing for single node clusters

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-14931:


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

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

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

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

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

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

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

This message is automatically generated.

> HAWQ service checks failing for single node clusters
> 
>
> Key: AMBARI-14931
> URL: https://issues.apache.org/jira/browse/AMBARI-14931
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Reporter: Newton Alex
>Assignee: Newton Alex
> Attachments: AMBARI-14931.patch
>
>
> Here is the log:
> ```
> 2016-02-04 19:01:30,163 - SQL command executed failed: export PGPORT=10432 && 
> source /usr/local/hawq/greenplum_path.sh && psql -d template1 -c \\\"DROP  
> TABLE IF EXISTS ambari_hawq_test;\\\"
> Returncode: 127
> Stdout: 
> Stderr: psql: warning: extra command-line argument "IF" ignored
> psql: warning: extra command-line argument "EXISTS" ignored
> psql: warning: extra command-line argument "ambari_hawq_test" ignored
> psql: FATAL:  no pg_hba.conf entry for host "[local]", user "TABLE", database 
> "template1", SSL off
> -bash: ": command not found
> 2016-02-04 19:01:30,164 - SERVICE CHECK FAILED: HAWQ was not able to write 
> and query from a table
> 2016-02-04 19:01:30,229 - SQL command executed failed: export PGPORT=10432 && 
> source /usr/local/hawq/greenplum_path.sh && psql -d template1 -c \\\"DROP  
> TABLE IF EXISTS ambari_hawq_test;\\\"
> Returncode: 127
> Stdout: 
> Stderr: psql: warning: extra command-line argument "IF" ignored
> psql: warning: extra command-line argument "EXISTS" ignored
> psql: warning: extra command-line argument "ambari_hawq_test" ignored
> psql: FATAL:  no pg_hba.conf entry for host "[local]", user "TABLE", database 
> "template1", SSL off
> -bash: ": command not found
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/HAWQ/2.0.0/package/scripts/service_check.py",
>  line 170, in 
> HAWQServiceCheck().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 238, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HAWQ/2.0.0/package/scripts/service_check.py",
>  line 48, in service_check
> self.check_hawq()
>   File 
> "/var/lib/ambari-agent/cache/common-services/HAWQ/2.0.0/package/scripts/service_check.py",
>  line 99, in check_hawq
> self.drop_table(table)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HAWQ/2.0.0/package/scripts/service_check.py",
>  line 131, in drop_table
> exec_psql_cmd(sql_cmd, self.active_master_host, self.active_master_port)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HAWQ/2.0.0/package/scripts/utils.py",
>  line 106, in exec_psql_cmd
> raise Fail("SQL command executed failed.")
> resource_management.core.exceptions.Fail: SQL command executed failed.
> ```



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

[jira] [Updated] (AMBARI-14745) Ambari server throws error when unused configs are present in blueprint

[JIRA]

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

Olivér Szabó updated AMBARI-14745:
--
Attachment: (was: AMBARI-14745.patch)

> Ambari server throws error when unused configs are present in blueprint
> ---
>
> Key: AMBARI-14745
> URL: https://issues.apache.org/jira/browse/AMBARI-14745
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14745.patch, AMBARI-14745_branch-2.2.patch
>
>
> When trying to create unsecure cluster, ambari server throws error when 
> Ranger configs are present in the blueprint.
> Error Message seen:
> “ [pool-6-thread-1] ERROR org.apache.ambari.server.topology.TopologyManager - 
> TopologyManager.ConfigureClusterTask: An exception occurred while attempting 
> to process cluster configs and set on cluster: 
> java.lang.IllegalArgumentException: Unable to update configuration property 
> 'policymgr_external_url' with topology information. Component 'RANGER_ADMIN' 
> is mapped to an invalid number of hosts '0'.
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$SingleHostTopologyUpdater.updateForClusterCreate(BlueprintConfigurationProcessor.java:1270)



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

[jira] [Updated] (AMBARI-14745) Ambari server throws error when unused configs are present in blueprint

[JIRA]

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

Olivér Szabó updated AMBARI-14745:
--
Attachment: AMBARI-14745.patch

> Ambari server throws error when unused configs are present in blueprint
> ---
>
> Key: AMBARI-14745
> URL: https://issues.apache.org/jira/browse/AMBARI-14745
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14745.patch, AMBARI-14745_branch-2.2.patch
>
>
> When trying to create unsecure cluster, ambari server throws error when 
> Ranger configs are present in the blueprint.
> Error Message seen:
> “ [pool-6-thread-1] ERROR org.apache.ambari.server.topology.TopologyManager - 
> TopologyManager.ConfigureClusterTask: An exception occurred while attempting 
> to process cluster configs and set on cluster: 
> java.lang.IllegalArgumentException: Unable to update configuration property 
> 'policymgr_external_url' with topology information. Component 'RANGER_ADMIN' 
> is mapped to an invalid number of hosts '0'.
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$SingleHostTopologyUpdater.updateForClusterCreate(BlueprintConfigurationProcessor.java:1270)



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

Re: Review Request 42572: Ambari server throws error when unused configs are present in blueprint

[Oliver Szabo]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/42572/
---

(Updated Feb. 5, 2016, 12:51 a.m.)


Review request for Ambari, Laszlo Puskas, Robert Nettleton, Sandor Magyari, 
Sumit Mohanty, and Sebastian Toader.


Changes
---

rebase / resolve conflicts


Bugs: AMBARI-14745
https://issues.apache.org/jira/browse/AMBARI-14745


Repository: ambari


Description
---

In case of a blueprint contains unused config types -> updaters can apply on 
the unused properties. In same cases this can cause exceptions. E.g.: single 
host updater on a property -> no host found for a service.


Diffs (updated)
-

  
ambari-server/src/main/java/org/apache/ambari/server/topology/ClusterConfigurationRequest.java
 464aee7 
  
ambari-server/src/main/java/org/apache/ambari/server/topology/Configuration.java
 108ff74 
  
ambari-server/src/test/java/org/apache/ambari/server/topology/ClusterConfigurationRequestTest.java
 5967a64 
  
ambari-server/src/test/java/org/apache/ambari/server/topology/ClusterInstallWithoutStartTest.java
 dd66b1b 
  
ambari-server/src/test/java/org/apache/ambari/server/topology/ConfigurationTest.java
 e971e03 
  
ambari-server/src/test/java/org/apache/ambari/server/topology/TopologyManagerTest.java
 7810f92 

Diff: https://reviews.apache.org/r/42572/diff/


Testing
---

Unit testing is in progress.
FT: blueprints with unused config types.


Thanks,

Oliver Szabo

[jira] [Created] (AMBARI-14932) "download zip" does not work

[Keta Patel (JIRA)]

Keta Patel created AMBARI-14932:
---

 Summary: "download zip"  does not work
 Key: AMBARI-14932
 URL: https://issues.apache.org/jira/browse/AMBARI-14932
 Project: Ambari
  Issue Type: Bug
  Components: ambari-views, contrib
Affects Versions: trunk
Reporter: Keta Patel
Assignee: Keta Patel


Steps to Reproduce:
1. go to "View" - "FILES" - " Create Instance"
2. go to hdfs file view
3. click "download zip" icon
The click doesn't download any file. The REST call returns 200 OK status.




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

[jira] [Commented] (AMBARI-14932) "download zip" does not work

[Keta Patel (JIRA)]

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

Keta Patel commented on AMBARI-14932:
-

[~srimanth.gunturi], I would like to get some insight from you on this issue as 
this is related to the changes made in AMBARI-14228.

1.
The patch submitted for the Jira AMBARI-14228 has changed the "download" 
function in the 
"ambari/contrib/views/files/src/main/resources/ui/app/controllers/file.js" 
This is seen in images named "file_1.tiff" and "file_2.tiff"

2.
The new function created "downloadFile" makes a call to the "linkFor" function 
in "ambari/contrib/views/files/src/main/resources/ui/app/adapter.js" with a new 
parameter "checkperm". The corresponding changes made to adapter.js file can be 
seen in "adapter.tiff".
Note:
 
This "checkperm" paramter is used only when the "option" is "browse" (i.e. to 
download an individual file). It is not being used for the other 2 APIs with 
"option" of "zip" and "concat".

3.
The "DownloadService.tiff" shows the server code changes made for "browse" API 
where they use "checkperm" to decide if the response should contain "allowed" 
property or not.
"file_2.tiff" shows how if the return value does not contain "data.allowed", 
further processing to download does not occur.

My questions:
1.) What is the purpose of setting "allowed" to true in the response if we 
always pass "checkperm" as true?
2.) Should the issue of handling "zip" and "concat" APIs involve change with 
the Response having "allowed" property or changing the condition in 
"downloadFile" function of the controller before calling the API?
3.) We are calling "linkFor" 2 times in the "downloadFile" of the controller. 
Why is this double call required? Can't we use the same link saved from the 
earlier call instead of calling "linkFor" again?

Thank you!

> "download zip"  does not work
> -
>
> Key: AMBARI-14932
> URL: https://issues.apache.org/jira/browse/AMBARI-14932
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views, contrib
>Affects Versions: trunk
>Reporter: Keta Patel
>Assignee: Keta Patel
> Attachments: DownloadService.tiff, adapter.tiff, file_1.tiff, 
> file_2.tiff, screenshot.tiff
>
>
> Steps to Reproduce:
> 1. go to "View" - "FILES" - " Create Instance"
> 2. go to hdfs file view
> 3. click "download zip" icon
> The click doesn't download any file. The REST call returns 200 OK status.



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

Re: Review Request 43226: HAWQ service failure on single node clusters

[jun aoki]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43226/#review117918
---


Ship it!




Ship It!

- jun aoki


On Feb. 4, 2016, 11:08 p.m., Newton Alex wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43226/
> ---
> 
> (Updated Feb. 4, 2016, 11:08 p.m.)
> 
> 
> Review request for Ambari.
> 
> 
> Bugs: AMBARI-14931
> https://issues.apache.org/jira/browse/AMBARI-14931
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Fix for HAWQ service failure on single node clusters
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/utils.py
>  e607a28 
> 
> Diff: https://reviews.apache.org/r/43226/diff/
> 
> 
> Testing
> ---
> 
> Manual testing done
> 
> Single Node:
> ```
> 2016-02-04 20:24:22,716 - Validating data inserted, finding sum of all the 
> inserted entries. Expected output: 55
> 2016-02-04 20:24:22,716 - Command executed: su - gpadmin -c "export 
> PGPORT=10432 && source /usr/local/hawq/greenplum_path.sh && psql -t -d 
> template1 -c \"SELECT sum(col1) FROM ambari_hawq_test;\""
> 2016-02-04 20:24:23,481 - Output:
>   55
> 
> 
> 2016-02-04 20:24:23,482 - Dropping ambari_hawq_test table if exists
> 2016-02-04 20:24:23,482 - Command executed: su - gpadmin -c "export 
> PGPORT=10432 && source /usr/local/hawq/greenplum_path.sh && psql -d template1 
> -c \"DROP  TABLE IF EXISTS ambari_hawq_test;\""
> 2016-02-04 20:24:23,697 - Output:
> DROP TABLE
> 
> 2016-02-04 20:24:23,698 - PXF not installed. Skipping HAWQ-PXF checks...
> 2016-02-04 20:24:23,698 - Service check completed successfully
> ```
> 
> 
> Multi Node:
> ```
> 2016-02-04 22:42:33,348 - Validating data inserted, finding sum of all the 
> inserted entries. Expected output: 55
> 2016-02-04 22:42:33,349 - Command executed: su - gpadmin -c 'ssh -o 
> StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null 
> c6410.ambari.apache.org "export PGPORT=5432 && source 
> /usr/local/hawq/greenplum_path.sh && psql -t -d template1 -c \"SELECT 
> sum(col1) FROM ambari_hawq_test;\" " '
> 2016-02-04 22:42:33,904 - Output:
>   55
> 
> 
> 2016-02-04 22:42:33,904 - Dropping ambari_hawq_test table if exists
> 2016-02-04 22:42:33,905 - Command executed: su - gpadmin -c 'ssh -o 
> StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null 
> c6410.ambari.apache.org "export PGPORT=5432 && source 
> /usr/local/hawq/greenplum_path.sh && psql -d template1 -c \"DROP  TABLE IF 
> EXISTS ambari_hawq_test;\" " '
> 2016-02-04 22:42:34,131 - Output:
> DROP TABLE
> 
> 2016-02-04 22:42:34,131 - PXF not installed. Skipping HAWQ-PXF checks...
> 2016-02-04 22:42:34,132 - Service check completed successfully
> ```
> 
> 
> Thanks,
> 
> Newton Alex
> 
>

[jira] [Updated] (AMBARI-14745) Ambari server throws error when unused configs are present in blueprint

[JIRA]

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

Olivér Szabó updated AMBARI-14745:
--
Attachment: AMBARI-14745_branch-2.2.patch

> Ambari server throws error when unused configs are present in blueprint
> ---
>
> Key: AMBARI-14745
> URL: https://issues.apache.org/jira/browse/AMBARI-14745
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14745_branch-2.2.patch
>
>
> When trying to create unsecure cluster, ambari server throws error when 
> Ranger configs are present in the blueprint.
> Error Message seen:
> “ [pool-6-thread-1] ERROR org.apache.ambari.server.topology.TopologyManager - 
> TopologyManager.ConfigureClusterTask: An exception occurred while attempting 
> to process cluster configs and set on cluster: 
> java.lang.IllegalArgumentException: Unable to update configuration property 
> 'policymgr_external_url' with topology information. Component 'RANGER_ADMIN' 
> is mapped to an invalid number of hosts '0'.
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$SingleHostTopologyUpdater.updateForClusterCreate(BlueprintConfigurationProcessor.java:1270)



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

[jira] [Updated] (AMBARI-14745) Ambari server throws error when unused configs are present in blueprint

[JIRA]

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

Olivér Szabó updated AMBARI-14745:
--
Attachment: (was: AMBARI-14745.patch)

> Ambari server throws error when unused configs are present in blueprint
> ---
>
> Key: AMBARI-14745
> URL: https://issues.apache.org/jira/browse/AMBARI-14745
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14745_branch-2.2.patch
>
>
> When trying to create unsecure cluster, ambari server throws error when 
> Ranger configs are present in the blueprint.
> Error Message seen:
> “ [pool-6-thread-1] ERROR org.apache.ambari.server.topology.TopologyManager - 
> TopologyManager.ConfigureClusterTask: An exception occurred while attempting 
> to process cluster configs and set on cluster: 
> java.lang.IllegalArgumentException: Unable to update configuration property 
> 'policymgr_external_url' with topology information. Component 'RANGER_ADMIN' 
> is mapped to an invalid number of hosts '0'.
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$SingleHostTopologyUpdater.updateForClusterCreate(BlueprintConfigurationProcessor.java:1270)



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

[jira] [Updated] (AMBARI-14745) Ambari server throws error when unused configs are present in blueprint

[JIRA]

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

Olivér Szabó updated AMBARI-14745:
--
Attachment: (was: AMBARI-14745_branch-2.2.patch)

> Ambari server throws error when unused configs are present in blueprint
> ---
>
> Key: AMBARI-14745
> URL: https://issues.apache.org/jira/browse/AMBARI-14745
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14745_branch-2.2.patch
>
>
> When trying to create unsecure cluster, ambari server throws error when 
> Ranger configs are present in the blueprint.
> Error Message seen:
> “ [pool-6-thread-1] ERROR org.apache.ambari.server.topology.TopologyManager - 
> TopologyManager.ConfigureClusterTask: An exception occurred while attempting 
> to process cluster configs and set on cluster: 
> java.lang.IllegalArgumentException: Unable to update configuration property 
> 'policymgr_external_url' with topology information. Component 'RANGER_ADMIN' 
> is mapped to an invalid number of hosts '0'.
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$SingleHostTopologyUpdater.updateForClusterCreate(BlueprintConfigurationProcessor.java:1270)



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

[jira] [Updated] (AMBARI-14885) After exporting blueprint from existing cluster knox_master_secret is exported

[Amruta Borkar (JIRA)]

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

Amruta Borkar updated AMBARI-14885:
---
Attachment: AMBARI-14885.patch

Modified Password property check condition to include secret property check 
condition. 
Added corresponding test cases.

> After exporting blueprint from existing cluster knox_master_secret is exported
> --
>
> Key: AMBARI-14885
> URL: https://issues.apache.org/jira/browse/AMBARI-14885
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, blueprints
>Affects Versions: 2.2.0
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Attachments: AMBARI-14885.patch
>
>
> After exporting blueprint from existing cluster knox_master_secret is also 
> exported
> Due to this property, the same blueprint file cannot be used to create 
> another cluster, this property need to be removed to create a cluster from 
> the file.
> User needs to remove the property in order to use the blueprint.
> Error shown:
> {
>   "status" : 400,
>   "message" : "Blueprint configuration validation failed: Secret references 
> are not allowed in blueprints, replace following properties with real 
> passwords:\n  Config:knox-env Property:knox_master_secret\n"
> }



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

[jira] [Commented] (AMBARI-14902) Make AMS Grafana component available as a repo package

[jun aoki (JIRA)]

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

jun aoki commented on AMBARI-14902:
---

hi [~dsen], with your change, ambari-metrics-collector and 
ambari-metrics-hadoop-sink are not longer produced. Is it a expected behavior?
Could you let us know why they are no longer required after adding grafana?

> Make AMS Grafana component available as a repo package
> --
>
> Key: AMBARI-14902
> URL: https://issues.apache.org/jira/browse/AMBARI-14902
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-metrics
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14902-trunk-2.patch
>
>
> Grafana 2.6.0 to be installed as an AMS component. We need this to be a part 
> of the Ambari repo so that Ambari can install it with AMS.



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

[jira] [Commented] (AMBARI-14929) Enable security wizard hangs

[jun aoki (JIRA)]

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

jun aoki commented on AMBARI-14929:
---

Hi [~srimanth.gunturi][~u39kun], thank you for getting my attention and sorry 
for the regression. 
We tested for fresh install single node case but did not go all the way till 
make it secured.
Lessons learnt here and will make sure Step7 controller is touched, we will 
test thoroughly till kerberos.

> Enable security wizard hangs 
> -
>
> Key: AMBARI-14929
> URL: https://issues.apache.org/jira/browse/AMBARI-14929
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.1
>Reporter: Srimanth Gunturi
>Assignee: Srimanth Gunturi
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-14929.patch, Screen Shot 2016-02-04 at 10.22.58 
> AM.png, Screen Shot 2016-02-04 at 10.23.27 AM.png
>
>
> Enabling security wizard hangs in the _Configure Kerberos_ page with below 
> error in the Javascript console.
> {noformat}
> Uncaught TypeError: Cannot convert undefined or null to object
> App.WizardStep7Controller.Em.Controller.extend.applyServicesConfigs @ 
> app.js:38205
> App.KerberosWizardStep2Controller.App.WizardStep7Controller.extend.loadStep @ 
> app.js:9420
> newFunc @ vendor.js:2627
> (anonymous function) @ app.js:174969
> invoke @ vendor.js:5055
> invokeNextTimers @ vendor.js:5552
> app.js:54881 
> App.serviceMetricsMapper execution time: 86.719ms
> {noformat}
> See attached screenshots.



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