Re: Review Request 41432: AMBARI-14390. EU from HDP 2.1 to 2.3 added NULL properties

[Dmitro Lisnichenko]

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

Ship it!


Ship It!

- Dmitro Lisnichenko


On Dec. 16, 2015, 6:25 a.m., Alejandro Fernandez wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/41432/
> ---
> 
> (Updated Dec. 16, 2015, 6:25 a.m.)
> 
> 
> Review request for Ambari, Dmytro Grinenko, Dmitro Lisnichenko, Jonathan 
> Hurley, Jayush Luniya, and Nate Cole.
> 
> 
> Bugs: AMBARI-14390
> https://issues.apache.org/jira/browse/AMBARI-14390
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> *Steps:*
> With Ambari 2.2.0, setup HDP 2.1 cluster (non HA, unsecure) with following 
> services: hbase,pig,slider,hive,oozie,sqoop,flume,falcon,storm
> Did Express Upgrade from HDP 2.1 to 2.3.4 and let it finish
> Observe the configs of various services
> 
> *Result:*
> Observed that the values of several properties showed up as blank and 
> required (mostly security related). Here is the list:
> 
> HDFS:
> 
> * hdfs_principal_name (hadoop-env, value is null, remove if not kerberized)
> * hdfs_user_keytab (hadoop-env, value is null, remove if not kerberized)
> * dfs.namenode.inode.attributes.provider.class (hdfs-site, value is null, set 
> to "org.apache.ranger.authorization.hadoop.RangerHdfsAuthorizer" if Ranger is 
> present, which it is not in HDP 2.1)
> 
> YARN:
> 
> * yarn.authorization-provider (yarn-site, value is null, set to 
> "org.apache.ranger.authorization.yarn.authorizer.RangerYarnAuthorizer" if 
> Ranger is present, which it is not in HDP 2.1)
> 
> Tez:
> 
> * tez.tez-ui.history-url.base (also tracked by AMBARI-14389, tez-site, value 
> is null, set to {code} 
> '{0}://{1}:{2}/#/main/views/TEZ/{3}/TEZ_CLUSTER_INSTANCE'.format(server_protocol,
>  server_host, server_port, latest_tez_jar_version) {code} by Stack Advisor)
> 
> HBase:
> 
> * hbase_principal_name (hbase-env, value is null, remove if not kerberized)
> * hbase_user_keytab (hbase-env, value is null, remove if not kerberized)
> 
> ZK:
> 
> * zookeeper_keytab_path (zookeeper-env, value is null, remove if not 
> kerberized)
> * zookeeper_principal_name (zookeeper-env, value is null, remove if not 
> kerberized)
> 
> Storm:
> 
> * nimbus_keytab  (storm-env, value is null, remove if not kerberized)
> * nimbus_principal_name (storm-env, value is null, remove if not kerberized)
> * storm_keytab (storm-env, value is null, remove if not kerberized)
> * storm_principal_name (storm-env, value is null, remove if not kerberized)
> * storm_ui_keytab (storm-env, value is null, remove if not kerberized)
> * storm_ui_principal_name (storm-env, value is null, remove if not kerberized)
> * nimbus.authorizer (storm-site, need help from Storm team on what to set 
> this to since it depends on whether kerberos is enabled and Ranger is present)
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
>  1e59b58 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/ConfigMergeHelper.java
>  b799bc7 
>   
> ambari-server/src/main/resources/stacks/HDP/2.1/upgrades/nonrolling-upgrade-2.3.xml
>  ef4b531 
>   ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/config-upgrade.xml 
> ab384db 
> 
> Diff: https://reviews.apache.org/r/41432/diff/
> 
> 
> Testing
> ---
> 
> Installed Ambari 2.2.0 with HDP 2.1 and all of the services listed above, 
> then performed Express Upgrade to HDP 2.3 and verified through the configs 
> page that no properties had null values.
> This happened because of all of the kerberos-related properties in stack HDP 
> 2.3 have null, so the merging of configurations was adding the property.
> 
> mvn clean test
> 
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 1:01:45.515s
> [INFO] Finished at: Tue Dec 15 20:24:13 PST 2015
> [INFO] Final Memory: 120M/4042M
> [INFO] 
> 
> 
> 
> Thanks,
> 
> Alejandro Fernandez
> 
>

Re: [ANNOUNCE] Di Li as a new committer for Ambari

[Mithun Mathew]

Congrats Di!!!

On Tue, Dec 15, 2015 at 12:39 PM, Yusaku Sako 
wrote:

> Hi all,
>
> It is my pleasure to announce that Di Li has become a committer for Ambari.
>
> Di has been providing meaningful contributions in areas that tend to get
> overlooked
> (usability, getting the details right, pluggability, etc.) in a full-stack
> manner to improve
> various aspects of Ambari, including Ambari Agent, Ambari Web, and Ambari
> Server.
>
> Congratulations, Di!
>
> Yusaku
>



-- 
*Mithun Mathew* (Matt)

   - www.linkedin.com/in/mithunmatt/

[jira] [Updated] (AMBARI-14394) Add ability to restart all host components with stale_configs=true with one API request

[Siddharth Wagle (JIRA)]

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

Siddharth Wagle updated AMBARI-14394:
-
Description: 
Provide ability to filter host components using a predicate that allows bulk 
ops like RESTART of stale configs with a simple API call.

Example:
{code}
{
  "RequestInfo": {
"context": "Restart stale",
"operational_level": "host_component",
"command": "RESTART"
  },
  "Requests/resource_filters": [
{
  "hosts_predicate": "HostRoles/stale_configs=true"
}
  ]
}
{code}

This API call should allow user to perform custom command restart on all host 
components with stale configurations.

  was:
Provide ability to filter host components using a predicate that allows bulk 
ops like RESTART of stale configs with a simple API call.

Example:
{code}
{
  "RequestInfo": {
"context": "Restart stale",
"operational_level": "host_component",
"command": "RESTART"
  },
  "Requests/resource_filters": [
{
  "hosts_predicate": "HostRoles/stale_config=true"
}
  ]
}
{code}

This API call should allow user to perform custom command restart on all host 
components with stale configurations.


> Add ability to restart all host components with stale_configs=true with one 
> API request
> ---
>
> Key: AMBARI-14394
> URL: https://issues.apache.org/jira/browse/AMBARI-14394
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.4.0
>
>
> Provide ability to filter host components using a predicate that allows bulk 
> ops like RESTART of stale configs with a simple API call.
> Example:
> {code}
> {
>   "RequestInfo": {
> "context": "Restart stale",
> "operational_level": "host_component",
> "command": "RESTART"
>   },
>   "Requests/resource_filters": [
> {
>   "hosts_predicate": "HostRoles/stale_configs=true"
> }
>   ]
> }
> {code}
> This API call should allow user to perform custom command restart on all host 
> components with stale configurations.



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

[jira] [Commented] (AMBARI-14392) Move logic to ambari-web, for adding parameters to hdfs-client.xml for HAWQ when HAWQ is installed on NN HA cluster

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-14392:


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

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

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

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

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

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

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

This message is automatically generated.

> Move logic to ambari-web, for adding parameters to hdfs-client.xml for HAWQ 
> when HAWQ is installed on NN HA cluster
> ---
>
> Key: AMBARI-14392
> URL: https://issues.apache.org/jira/browse/AMBARI-14392
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Affects Versions: trunk
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: 2.3.0, trunk
>
> Attachments: AMBARI-14392.patch
>
>
> Currently, the parameters required by HAWQ to work on NN HA cluster are added 
> to hdfs-client.xml using python code in common-services. 
> This does not show up on the UI.
> This ticket is to show the parameters on the UI, and add them to 
> hdfs-client.xml by leveraging code in ambari-web.



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

[jira] [Commented] (AMBARI-14194) Enforce granular role-based access control for metrics functions

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14194:
-

ABORTED: Integrated in Ambari-trunk-Commit #4047 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4047/])
AMBARI-14194. Role Based Access Control support for Metrics (Swapan (smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7153112e7951af1b91c2254202148fd6afd83726])
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/MetricsReportPropertyProviderProxy.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/jmx/JMXPropertyProvider.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AbstractPropertyProvider.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/RestMetricsPropertyProvider.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/MetricsPropertyProviderProxy.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/MetricsPropertyProvider.java
* 
ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AuthorizationHelper.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/ThreadPoolEnabledPropertyProvider.java
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/timeline/AMSPropertyProviderTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/ganglia/GangliaPropertyProviderTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/RestMetricsPropertyProviderTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/JMXPropertyProviderTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StackDefinedPropertyProvider.java
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/StackDefinedPropertyProviderTest.java


> Enforce granular role-based access control for metrics functions
> 
>
> Key: AMBARI-14194
> URL: https://issues.apache.org/jira/browse/AMBARI-14194
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.3.0, 2.4.0
>Reporter: Robert Levas
>Assignee: Swapan Shridhar
>  Labels: rbac1
> Fix For: 2.3.0
>
> Attachments: AMBARI-14194_trunk.patch
>
>
> Enforce granular role-based access control for metrics functions:
> || || Cluster\\User || Service\\Operator || Service\\Administrator || 
> Cluster\\Operator || Cluster\\Administrator || Administrator ||
> |View service metrics  |(+)|(+)|(+)|(+)|(+)|(+)|
> |View host metrics  |(+)|(+)|(+)|(+)|(+)|(+)|
> |View cluster metrics  |(+)|(+)|(+)|(+)|(+)|(+)|
> Entry points affected:
> * TBD



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

Handling flume complex flows

[saloni udani]

Hi

Apache Ambari's Flume service doesn't support flume complex flows as of
now. https://flume.apache.org/FlumeUserGuide.html#complex-flows

So flume.conf cannot run a topology with either source or sink missing. I
have already fixed this into my ambari stack and would like to contribute
it to apache ambari. Let me know how can I do this.


Thanks

Re: Review Request 41432: AMBARI-14390. EU from HDP 2.1 to 2.3 added NULL properties

[Mahadev Konar]

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

Ship it!


Ship It!

- Mahadev Konar


On Dec. 16, 2015, 4:25 a.m., Alejandro Fernandez wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/41432/
> ---
> 
> (Updated Dec. 16, 2015, 4:25 a.m.)
> 
> 
> Review request for Ambari, Dmytro Grinenko, Dmitro Lisnichenko, Jonathan 
> Hurley, Jayush Luniya, and Nate Cole.
> 
> 
> Bugs: AMBARI-14390
> https://issues.apache.org/jira/browse/AMBARI-14390
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> *Steps:*
> With Ambari 2.2.0, setup HDP 2.1 cluster (non HA, unsecure) with following 
> services: hbase,pig,slider,hive,oozie,sqoop,flume,falcon,storm
> Did Express Upgrade from HDP 2.1 to 2.3.4 and let it finish
> Observe the configs of various services
> 
> *Result:*
> Observed that the values of several properties showed up as blank and 
> required (mostly security related). Here is the list:
> 
> HDFS:
> 
> * hdfs_principal_name (hadoop-env, value is null, remove if not kerberized)
> * hdfs_user_keytab (hadoop-env, value is null, remove if not kerberized)
> * dfs.namenode.inode.attributes.provider.class (hdfs-site, value is null, set 
> to "org.apache.ranger.authorization.hadoop.RangerHdfsAuthorizer" if Ranger is 
> present, which it is not in HDP 2.1)
> 
> YARN:
> 
> * yarn.authorization-provider (yarn-site, value is null, set to 
> "org.apache.ranger.authorization.yarn.authorizer.RangerYarnAuthorizer" if 
> Ranger is present, which it is not in HDP 2.1)
> 
> Tez:
> 
> * tez.tez-ui.history-url.base (also tracked by AMBARI-14389, tez-site, value 
> is null, set to {code} 
> '{0}://{1}:{2}/#/main/views/TEZ/{3}/TEZ_CLUSTER_INSTANCE'.format(server_protocol,
>  server_host, server_port, latest_tez_jar_version) {code} by Stack Advisor)
> 
> HBase:
> 
> * hbase_principal_name (hbase-env, value is null, remove if not kerberized)
> * hbase_user_keytab (hbase-env, value is null, remove if not kerberized)
> 
> ZK:
> 
> * zookeeper_keytab_path (zookeeper-env, value is null, remove if not 
> kerberized)
> * zookeeper_principal_name (zookeeper-env, value is null, remove if not 
> kerberized)
> 
> Storm:
> 
> * nimbus_keytab  (storm-env, value is null, remove if not kerberized)
> * nimbus_principal_name (storm-env, value is null, remove if not kerberized)
> * storm_keytab (storm-env, value is null, remove if not kerberized)
> * storm_principal_name (storm-env, value is null, remove if not kerberized)
> * storm_ui_keytab (storm-env, value is null, remove if not kerberized)
> * storm_ui_principal_name (storm-env, value is null, remove if not kerberized)
> * nimbus.authorizer (storm-site, need help from Storm team on what to set 
> this to since it depends on whether kerberos is enabled and Ranger is present)
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
>  1e59b58 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/ConfigMergeHelper.java
>  b799bc7 
>   
> ambari-server/src/main/resources/stacks/HDP/2.1/upgrades/nonrolling-upgrade-2.3.xml
>  ef4b531 
>   ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/config-upgrade.xml 
> ab384db 
> 
> Diff: https://reviews.apache.org/r/41432/diff/
> 
> 
> Testing
> ---
> 
> Installed Ambari 2.2.0 with HDP 2.1 and all of the services listed above, 
> then performed Express Upgrade to HDP 2.3 and verified through the configs 
> page that no properties had null values.
> This happened because of all of the kerberos-related properties in stack HDP 
> 2.3 have null, so the merging of configurations was adding the property.
> 
> mvn clean test
> 
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 1:01:45.515s
> [INFO] Finished at: Tue Dec 15 20:24:13 PST 2015
> [INFO] Final Memory: 120M/4042M
> [INFO] 
> 
> 
> 
> Thanks,
> 
> Alejandro Fernandez
> 
>

[jira] [Commented] (AMBARI-14390) EU from HDP 2.1 to 2.3 added NULL properties

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-14390:


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

This message is automatically generated.

> EU from HDP 2.1 to 2.3 added NULL properties
> 
>
> Key: AMBARI-14390
> URL: https://issues.apache.org/jira/browse/AMBARI-14390
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.2.1
>
> Attachments: AMBARI-14390.branch-2.2.patch, AMBARI-14390.trunk.patch, 
> AMBARI-14390_1.png, AMBARI-14390_2.png, AMBARI-14390_3.png
>
>
> *Steps:*
> With Ambari 2.2.0, setup HDP 2.1 cluster (non HA, unsecure) with following 
> services: hbase,pig,slider,hive,oozie,sqoop,flume,falcon,storm
> Did Express Upgrade from HDP 2.1 to 2.3.4 and let it finish
> Observe the configs of various services
> *Result:*
> Observed that the values of several properties showed up as blank and 
> required (mostly security related). Here is the list:
> h3. HDFS:
> * hdfs_principal_name (hadoop-env, value is null, remove if not kerberized)
> * hdfs_user_keytab (hadoop-env, value is null, remove if not kerberized)
> * dfs.namenode.inode.attributes.provider.class (hdfs-site, value is null, set 
> to "org.apache.ranger.authorization.hadoop.RangerHdfsAuthorizer" if Ranger is 
> present, which it is not in HDP 2.1)
> h3. YARN:
> * yarn.authorization-provider (yarn-site, value is null, set to 
> "org.apache.ranger.authorization.yarn.authorizer.RangerYarnAuthorizer" if 
> Ranger is present, which it is not in HDP 2.1)
> h3. Tez:
> * tez.tez-ui.history-url.base (also tracked by AMBARI-14389, tez-site, value 
> is null, set to {code} 
> '{0}://{1}:{2}/#/main/views/TEZ/{3}/TEZ_CLUSTER_INSTANCE'.format(server_protocol,
>  server_host, server_port, latest_tez_jar_version) {code} by Stack Advisor)
> h3. HBase:
> * hbase_principal_name (hbase-env, value is null, remove if not kerberized)
> * hbase_user_keytab (hbase-env, value is null, remove if not kerberized)
> h3. ZK:
> * zookeeper_keytab_path (zookeeper-env, value is null, remove if not 
> kerberized)
> * zookeeper_principal_name (zookeeper-env, value is null, remove if not 
> kerberized)
> h3. Storm:
> * nimbus_keytab  (storm-env, value is null, remove if not kerberized)
> * nimbus_principal_name (storm-env, value is null, remove if not kerberized)
> * storm_keytab (storm-env, value is null, remove if not kerberized)
> * storm_principal_name (storm-env, value is null, remove if not kerberized)
> * storm_ui_keytab (storm-env, value is null, remove if not kerberized)
> * storm_ui_principal_name (storm-env, value is null, remove if not kerberized)
> * nimbus.authorizer (storm-site, need help from Storm team on what to set 
> this to since it depends on whether kerberos is enabled and Ranger is present)
> Attached few screenshots
> We may have more such issues for properties of services other than the ones 
> with which the cluster was created at 2.1; so while fixing the issue, please 
> ensure that all services are taken care of



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

Re: Review Request 41432: AMBARI-14390. EU from HDP 2.1 to 2.3 added NULL properties

[Alejandro Fernandez]

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

(Updated Dec. 16, 2015, 4:25 a.m.)


Review request for Ambari, Dmytro Grinenko, Dmitro Lisnichenko, Jonathan 
Hurley, Jayush Luniya, and Nate Cole.


Changes
---

Unit tests passed


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


Repository: ambari


Description
---

*Steps:*
With Ambari 2.2.0, setup HDP 2.1 cluster (non HA, unsecure) with following 
services: hbase,pig,slider,hive,oozie,sqoop,flume,falcon,storm
Did Express Upgrade from HDP 2.1 to 2.3.4 and let it finish
Observe the configs of various services

*Result:*
Observed that the values of several properties showed up as blank and required 
(mostly security related). Here is the list:

HDFS:

* hdfs_principal_name (hadoop-env, value is null, remove if not kerberized)
* hdfs_user_keytab (hadoop-env, value is null, remove if not kerberized)
* dfs.namenode.inode.attributes.provider.class (hdfs-site, value is null, set 
to "org.apache.ranger.authorization.hadoop.RangerHdfsAuthorizer" if Ranger is 
present, which it is not in HDP 2.1)

YARN:

* yarn.authorization-provider (yarn-site, value is null, set to 
"org.apache.ranger.authorization.yarn.authorizer.RangerYarnAuthorizer" if 
Ranger is present, which it is not in HDP 2.1)

Tez:

* tez.tez-ui.history-url.base (also tracked by AMBARI-14389, tez-site, value is 
null, set to {code} 
'{0}://{1}:{2}/#/main/views/TEZ/{3}/TEZ_CLUSTER_INSTANCE'.format(server_protocol,
 server_host, server_port, latest_tez_jar_version) {code} by Stack Advisor)

HBase:

* hbase_principal_name (hbase-env, value is null, remove if not kerberized)
* hbase_user_keytab (hbase-env, value is null, remove if not kerberized)

ZK:

* zookeeper_keytab_path (zookeeper-env, value is null, remove if not kerberized)
* zookeeper_principal_name (zookeeper-env, value is null, remove if not 
kerberized)

Storm:

* nimbus_keytab  (storm-env, value is null, remove if not kerberized)
* nimbus_principal_name (storm-env, value is null, remove if not kerberized)
* storm_keytab (storm-env, value is null, remove if not kerberized)
* storm_principal_name (storm-env, value is null, remove if not kerberized)
* storm_ui_keytab (storm-env, value is null, remove if not kerberized)
* storm_ui_principal_name (storm-env, value is null, remove if not kerberized)
* nimbus.authorizer (storm-site, need help from Storm team on what to set this 
to since it depends on whether kerberos is enabled and Ranger is present)


Diffs
-

  
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
 1e59b58 
  
ambari-server/src/main/java/org/apache/ambari/server/state/ConfigMergeHelper.java
 b799bc7 
  
ambari-server/src/main/resources/stacks/HDP/2.1/upgrades/nonrolling-upgrade-2.3.xml
 ef4b531 
  ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/config-upgrade.xml 
ab384db 

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


Testing (updated)
---

Installed Ambari 2.2.0 with HDP 2.1 and all of the services listed above, then 
performed Express Upgrade to HDP 2.3 and verified through the configs page that 
no properties had null values.
This happened because of all of the kerberos-related properties in stack HDP 
2.3 have null, so the merging of configurations was adding the property.

mvn clean test

[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 1:01:45.515s
[INFO] Finished at: Tue Dec 15 20:24:13 PST 2015
[INFO] Final Memory: 120M/4042M
[INFO] 


Thanks,

Alejandro Fernandez

[jira] [Updated] (AMBARI-14395) Restarting all affected services

[Henry Sowell (JIRA)]

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

Henry Sowell updated AMBARI-14395:
--
Affects Version/s: trunk

> Restarting all affected services
> 
>
> Key: AMBARI-14395
> URL: https://issues.apache.org/jira/browse/AMBARI-14395
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Affects Versions: trunk
>Reporter: Henry Sowell
>Priority: Minor
>  Labels: features
>
> If any change or error occurs that affects multiple services on the cluster 
> you now have a couple of options to go in and restart the affected service:
> - From the dashboard, select "Actions", Stop All, and then Start All (not 
> recommended)
> - You can go into each service individually restarting the affected service
> This is unnecessary, burdensome, and can potentially lead to problems on the 
> cluster. I would recommend adding a selection to the "Actions" drop-down for 
> "Restart affected services". This would prevent users from having to go into 
> each service to perform restarts and from them using the hammer of stop all 
> start all.



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

[jira] [Updated] (AMBARI-14395) Restarting all affected services

[Henry Sowell (JIRA)]

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

Henry Sowell updated AMBARI-14395:
--
Component/s: ambari-web

> Restarting all affected services
> 
>
> Key: AMBARI-14395
> URL: https://issues.apache.org/jira/browse/AMBARI-14395
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Affects Versions: trunk
>Reporter: Henry Sowell
>Priority: Minor
>  Labels: features
>
> If any change or error occurs that affects multiple services on the cluster 
> you now have a couple of options to go in and restart the affected service:
> - From the dashboard, select "Actions", Stop All, and then Start All (not 
> recommended)
> - You can go into each service individually restarting the affected service
> This is unnecessary, burdensome, and can potentially lead to problems on the 
> cluster. I would recommend adding a selection to the "Actions" drop-down for 
> "Restart affected services". This would prevent users from having to go into 
> each service to perform restarts and from them using the hammer of stop all 
> start all.



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

[jira] [Created] (AMBARI-14395) Restarting all affected services

[Henry Sowell (JIRA)]

Henry Sowell created AMBARI-14395:
-

 Summary: Restarting all affected services
 Key: AMBARI-14395
 URL: https://issues.apache.org/jira/browse/AMBARI-14395
 Project: Ambari
  Issue Type: Improvement
Reporter: Henry Sowell
Priority: Minor


If any change or error occurs that affects multiple services on the cluster you 
now have a couple of options to go in and restart the affected service:

- From the dashboard, select "Actions", Stop All, and then Start All (not 
recommended)
- You can go into each service individually restarting the affected service

This is unnecessary, burdensome, and can potentially lead to problems on the 
cluster. I would recommend adding a selection to the "Actions" drop-down for 
"Restart affected services". This would prevent users from having to go into 
each service to perform restarts and from them using the hammer of stop all 
start all.



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

[VOTE] Ambari 2.2.0 - RC1

[Jaimin Jetly]

Hi all,


I have created an Apache Ambari 2.2.0 Release Candidate (RC1).


GIT source tag: 
https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=log;h=refs/tags/release-2.2.0-rc1


Staging site: http://people.apache.org/~jaimin/apache-ambari-2.2.0-rc1/


PGP release key used (signed using D30E6003): 
http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x85041753D30E6003?

One can look into the issues fixed in this release at https://goo.gl/AU3h70


Vote will be open for 72 hours.


[ ] +1 approve

[ ] +0 no opinion

[ ] -1 disapprove (and reason why)


Here's my vote to start: +1


Thanks

Jaimin Jetly

Apache Ambari 2.2.0 Release Manager

Re: [VOTE] Ambari 2.2.0 - RC0

[Jaimin Jetly]

-1. 
On further verificiation, I found that ambari version update was missing. I 
will create RC1 and send out vote for the same.

-- Thanks
Jaimin Jetly
Apache Ambari 2.2.0 Release Manager

From: Jaimin Jetly 
Sent: Tuesday, December 15, 2015 5:33 PM
To: Ambari
Subject: [VOTE] Ambari 2.2.0 - RC0

Hi all,


I have created an Apache Ambari 2.2.0 Release Candidate (RC0).


GIT source tag: 
https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=log;h=refs/tags/release-2.2.0-rc0


Staging site: http://people.apache.org/~jaimin/apache-ambari-2.2.0-rc0/


PGP release key used (signed using D30E6003?): 
http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x85041753D30E6003?

?

One can look into the issues fixed in this release at 
 
https://goo.gl/AU3h70


Vote will be open for 72 hours.


[ ] +1 approve

[ ] +0 no opinion

[ ] -1 disapprove (and reason why)


Here's my vote to start: +1


Thanks

Jaimin Jetly

Apache Ambari 2.2.0 Release Manager

?

Re: Review Request 41151: Co-locate HAWQSEGMENT on hosts that have DATANODE component

[Alejandro Fernandez]

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



ambari-web/app/controllers/main/service/add_controller.js (line 414)


Please add Jaimin Jetly and Richard Zang to the code review.


- Alejandro Fernandez


On Dec. 10, 2015, 4:21 a.m., Lav Jain wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/41151/
> ---
> 
> (Updated Dec. 10, 2015, 4:21 a.m.)
> 
> 
> Review request for Ambari, Alexander Denissov, Alejandro Fernandez, bhuvnesh 
> chaudhary, jun aoki, Matt, Newton Alex, and Oleksandr Diachenko.
> 
> 
> Bugs: AMBARI-14301
> https://issues.apache.org/jira/browse/AMBARI-14301
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Looks like stackadvisor is used only upon a fresh install if no changes are 
> made to the master components. In that case, the client/slaves are installed 
> on all the hosts, so HAWQSEGMENT is co-located with DATANODE by default.
> If HDFS is already installed and HAWQ is enabled using add services, then 
> Ambari chooses all hosts that do not have a MASTER component installed. This 
> determination is being done in the javascript code.
> This patch is changing the hostlist for HAWQSEGMENT to be the same as 
> DATANODE in the latter case.
> 
> 
> Diffs
> -
> 
>   ambari-web/app/controllers/main/service/add_controller.js 1f8133d 
> 
> Diff: https://reviews.apache.org/r/41151/diff/
> 
> 
> Testing
> ---
> 
> Manually tested.
> 
> 
> Thanks,
> 
> Lav Jain
> 
>

Review Request 41432: AMBARI-14390. EU from HDP 2.1 to 2.3 added NULL properties

[Alejandro Fernandez]

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

Review request for Ambari, Dmytro Grinenko, Dmitro Lisnichenko, Jonathan 
Hurley, Jayush Luniya, and Nate Cole.


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


Repository: ambari


Description
---

*Steps:*
With Ambari 2.2.0, setup HDP 2.1 cluster (non HA, unsecure) with following 
services: hbase,pig,slider,hive,oozie,sqoop,flume,falcon,storm
Did Express Upgrade from HDP 2.1 to 2.3.4 and let it finish
Observe the configs of various services

*Result:*
Observed that the values of several properties showed up as blank and required 
(mostly security related). Here is the list:

HDFS:

* hdfs_principal_name (hadoop-env, value is null, remove if not kerberized)
* hdfs_user_keytab (hadoop-env, value is null, remove if not kerberized)
* dfs.namenode.inode.attributes.provider.class (hdfs-site, value is null, set 
to "org.apache.ranger.authorization.hadoop.RangerHdfsAuthorizer" if Ranger is 
present, which it is not in HDP 2.1)

YARN:

* yarn.authorization-provider (yarn-site, value is null, set to 
"org.apache.ranger.authorization.yarn.authorizer.RangerYarnAuthorizer" if 
Ranger is present, which it is not in HDP 2.1)

Tez:

* tez.tez-ui.history-url.base (also tracked by AMBARI-14389, tez-site, value is 
null, set to {code} 
'{0}://{1}:{2}/#/main/views/TEZ/{3}/TEZ_CLUSTER_INSTANCE'.format(server_protocol,
 server_host, server_port, latest_tez_jar_version) {code} by Stack Advisor)

HBase:

* hbase_principal_name (hbase-env, value is null, remove if not kerberized)
* hbase_user_keytab (hbase-env, value is null, remove if not kerberized)

ZK:

* zookeeper_keytab_path (zookeeper-env, value is null, remove if not kerberized)
* zookeeper_principal_name (zookeeper-env, value is null, remove if not 
kerberized)

Storm:

* nimbus_keytab  (storm-env, value is null, remove if not kerberized)
* nimbus_principal_name (storm-env, value is null, remove if not kerberized)
* storm_keytab (storm-env, value is null, remove if not kerberized)
* storm_principal_name (storm-env, value is null, remove if not kerberized)
* storm_ui_keytab (storm-env, value is null, remove if not kerberized)
* storm_ui_principal_name (storm-env, value is null, remove if not kerberized)
* nimbus.authorizer (storm-site, need help from Storm team on what to set this 
to since it depends on whether kerberos is enabled and Ranger is present)


Diffs
-

  
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
 1e59b58 
  
ambari-server/src/main/java/org/apache/ambari/server/state/ConfigMergeHelper.java
 b799bc7 
  
ambari-server/src/main/resources/stacks/HDP/2.1/upgrades/nonrolling-upgrade-2.3.xml
 ef4b531 
  ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/config-upgrade.xml 
ab384db 

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


Testing
---

Installed Ambari 2.2.0 with HDP 2.1 and all of the services listed above, then 
performed Express Upgrade to HDP 2.3 and verified through the configs page that 
no properties had null values.
This happened because of all of the kerberos-related properties in stack HDP 
2.3 have null, so the merging of configurations was adding the property.

Waiting for unit test results.


Thanks,

Alejandro Fernandez

[jira] [Updated] (AMBARI-14390) EU from HDP 2.1 to 2.3 added NULL properties

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-14390:
-
Attachment: AMBARI-14390.branch-2.2.patch
AMBARI-14390.trunk.patch

> EU from HDP 2.1 to 2.3 added NULL properties
> 
>
> Key: AMBARI-14390
> URL: https://issues.apache.org/jira/browse/AMBARI-14390
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.2.1
>
> Attachments: AMBARI-14390.branch-2.2.patch, AMBARI-14390.trunk.patch, 
> AMBARI-14390_1.png, AMBARI-14390_2.png, AMBARI-14390_3.png
>
>
> *Steps:*
> With Ambari 2.2.0, setup HDP 2.1 cluster (non HA, unsecure) with following 
> services: hbase,pig,slider,hive,oozie,sqoop,flume,falcon,storm
> Did Express Upgrade from HDP 2.1 to 2.3.4 and let it finish
> Observe the configs of various services
> *Result:*
> Observed that the values of several properties showed up as blank and 
> required (mostly security related). Here is the list:
> h3. HDFS:
> * hdfs_principal_name (hadoop-env, value is null, remove if not kerberized)
> * hdfs_user_keytab (hadoop-env, value is null, remove if not kerberized)
> * dfs.namenode.inode.attributes.provider.class (hdfs-site, value is null, set 
> to "org.apache.ranger.authorization.hadoop.RangerHdfsAuthorizer" if Ranger is 
> present, which it is not in HDP 2.1)
> h3. YARN:
> * yarn.authorization-provider (yarn-site, value is null, set to 
> "org.apache.ranger.authorization.yarn.authorizer.RangerYarnAuthorizer" if 
> Ranger is present, which it is not in HDP 2.1)
> h3. Tez:
> * tez.tez-ui.history-url.base (also tracked by AMBARI-14389, tez-site, value 
> is null, set to {code} 
> '{0}://{1}:{2}/#/main/views/TEZ/{3}/TEZ_CLUSTER_INSTANCE'.format(server_protocol,
>  server_host, server_port, latest_tez_jar_version) {code} by Stack Advisor)
> h3. HBase:
> * hbase_principal_name (hbase-env, value is null, remove if not kerberized)
> * hbase_user_keytab (hbase-env, value is null, remove if not kerberized)
> h3. ZK:
> * zookeeper_keytab_path (zookeeper-env, value is null, remove if not 
> kerberized)
> * zookeeper_principal_name (zookeeper-env, value is null, remove if not 
> kerberized)
> h3. Storm:
> * nimbus_keytab  (storm-env, value is null, remove if not kerberized)
> * nimbus_principal_name (storm-env, value is null, remove if not kerberized)
> * storm_keytab (storm-env, value is null, remove if not kerberized)
> * storm_principal_name (storm-env, value is null, remove if not kerberized)
> * storm_ui_keytab (storm-env, value is null, remove if not kerberized)
> * storm_ui_principal_name (storm-env, value is null, remove if not kerberized)
> * nimbus.authorizer (storm-site, need help from Storm team on what to set 
> this to since it depends on whether kerberos is enabled and Ranger is present)
> Attached few screenshots
> We may have more such issues for properties of services other than the ones 
> with which the cluster was created at 2.1; so while fixing the issue, please 
> ensure that all services are taken care of



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

[jira] [Updated] (AMBARI-14390) EU from HDP 2.1 to 2.3 added NULL properties

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-14390:
-
Attachment: (was: AMBARI-14390.branch-2.2.patch)

> EU from HDP 2.1 to 2.3 added NULL properties
> 
>
> Key: AMBARI-14390
> URL: https://issues.apache.org/jira/browse/AMBARI-14390
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.2.1
>
> Attachments: AMBARI-14390_1.png, AMBARI-14390_2.png, 
> AMBARI-14390_3.png
>
>
> *Steps:*
> With Ambari 2.2.0, setup HDP 2.1 cluster (non HA, unsecure) with following 
> services: hbase,pig,slider,hive,oozie,sqoop,flume,falcon,storm
> Did Express Upgrade from HDP 2.1 to 2.3.4 and let it finish
> Observe the configs of various services
> *Result:*
> Observed that the values of several properties showed up as blank and 
> required (mostly security related). Here is the list:
> h3. HDFS:
> * hdfs_principal_name (hadoop-env, value is null, remove if not kerberized)
> * hdfs_user_keytab (hadoop-env, value is null, remove if not kerberized)
> * dfs.namenode.inode.attributes.provider.class (hdfs-site, value is null, set 
> to "org.apache.ranger.authorization.hadoop.RangerHdfsAuthorizer" if Ranger is 
> present, which it is not in HDP 2.1)
> h3. YARN:
> * yarn.authorization-provider (yarn-site, value is null, set to 
> "org.apache.ranger.authorization.yarn.authorizer.RangerYarnAuthorizer" if 
> Ranger is present, which it is not in HDP 2.1)
> h3. Tez:
> * tez.tez-ui.history-url.base (also tracked by AMBARI-14389, tez-site, value 
> is null, set to {code} 
> '{0}://{1}:{2}/#/main/views/TEZ/{3}/TEZ_CLUSTER_INSTANCE'.format(server_protocol,
>  server_host, server_port, latest_tez_jar_version) {code} by Stack Advisor)
> h3. HBase:
> * hbase_principal_name (hbase-env, value is null, remove if not kerberized)
> * hbase_user_keytab (hbase-env, value is null, remove if not kerberized)
> h3. ZK:
> * zookeeper_keytab_path (zookeeper-env, value is null, remove if not 
> kerberized)
> * zookeeper_principal_name (zookeeper-env, value is null, remove if not 
> kerberized)
> h3. Storm:
> * nimbus_keytab  (storm-env, value is null, remove if not kerberized)
> * nimbus_principal_name (storm-env, value is null, remove if not kerberized)
> * storm_keytab (storm-env, value is null, remove if not kerberized)
> * storm_principal_name (storm-env, value is null, remove if not kerberized)
> * storm_ui_keytab (storm-env, value is null, remove if not kerberized)
> * storm_ui_principal_name (storm-env, value is null, remove if not kerberized)
> * nimbus.authorizer (storm-site, need help from Storm team on what to set 
> this to since it depends on whether kerberos is enabled and Ranger is present)
> Attached few screenshots
> We may have more such issues for properties of services other than the ones 
> with which the cluster was created at 2.1; so while fixing the issue, please 
> ensure that all services are taken care of



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

[jira] [Updated] (AMBARI-14390) EU from HDP 2.1 to 2.3 added NULL properties

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-14390:
-
Attachment: AMBARI-14390.branch-2.2.patch

> EU from HDP 2.1 to 2.3 added NULL properties
> 
>
> Key: AMBARI-14390
> URL: https://issues.apache.org/jira/browse/AMBARI-14390
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.2.1
>
> Attachments: AMBARI-14390.branch-2.2.patch, AMBARI-14390_1.png, 
> AMBARI-14390_2.png, AMBARI-14390_3.png
>
>
> *Steps:*
> With Ambari 2.2.0, setup HDP 2.1 cluster (non HA, unsecure) with following 
> services: hbase,pig,slider,hive,oozie,sqoop,flume,falcon,storm
> Did Express Upgrade from HDP 2.1 to 2.3.4 and let it finish
> Observe the configs of various services
> *Result:*
> Observed that the values of several properties showed up as blank and 
> required (mostly security related). Here is the list:
> h3. HDFS:
> * hdfs_principal_name (hadoop-env, value is null, remove if not kerberized)
> * hdfs_user_keytab (hadoop-env, value is null, remove if not kerberized)
> * dfs.namenode.inode.attributes.provider.class (hdfs-site, value is null, set 
> to "org.apache.ranger.authorization.hadoop.RangerHdfsAuthorizer" if Ranger is 
> present, which it is not in HDP 2.1)
> h3. YARN:
> * yarn.authorization-provider (yarn-site, value is null, set to 
> "org.apache.ranger.authorization.yarn.authorizer.RangerYarnAuthorizer" if 
> Ranger is present, which it is not in HDP 2.1)
> h3. Tez:
> * tez.tez-ui.history-url.base (also tracked by AMBARI-14389, tez-site, value 
> is null, set to {code} 
> '{0}://{1}:{2}/#/main/views/TEZ/{3}/TEZ_CLUSTER_INSTANCE'.format(server_protocol,
>  server_host, server_port, latest_tez_jar_version) {code} by Stack Advisor)
> h3. HBase:
> * hbase_principal_name (hbase-env, value is null, remove if not kerberized)
> * hbase_user_keytab (hbase-env, value is null, remove if not kerberized)
> h3. ZK:
> * zookeeper_keytab_path (zookeeper-env, value is null, remove if not 
> kerberized)
> * zookeeper_principal_name (zookeeper-env, value is null, remove if not 
> kerberized)
> h3. Storm:
> * nimbus_keytab  (storm-env, value is null, remove if not kerberized)
> * nimbus_principal_name (storm-env, value is null, remove if not kerberized)
> * storm_keytab (storm-env, value is null, remove if not kerberized)
> * storm_principal_name (storm-env, value is null, remove if not kerberized)
> * storm_ui_keytab (storm-env, value is null, remove if not kerberized)
> * storm_ui_principal_name (storm-env, value is null, remove if not kerberized)
> * nimbus.authorizer (storm-site, need help from Storm team on what to set 
> this to since it depends on whether kerberos is enabled and Ranger is present)
> Attached few screenshots
> We may have more such issues for properties of services other than the ones 
> with which the cluster was created at 2.1; so while fixing the issue, please 
> ensure that all services are taken care of



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

[jira] [Updated] (AMBARI-14390) EU from HDP 2.1 to 2.3 added properties as NULL

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-14390:
-
Summary: EU from HDP 2.1 to 2.3 added properties as NULL  (was: Several 
properties showed up as blank after EU from HDP 2.1 to HDP 2.3)

> EU from HDP 2.1 to 2.3 added properties as NULL
> ---
>
> Key: AMBARI-14390
> URL: https://issues.apache.org/jira/browse/AMBARI-14390
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.2.1
>
> Attachments: AMBARI-14390_1.png, AMBARI-14390_2.png, 
> AMBARI-14390_3.png
>
>
> *Steps:*
> With Ambari 2.2.0, setup HDP 2.1 cluster (non HA, unsecure) with following 
> services: hbase,pig,slider,hive,oozie,sqoop,flume,falcon,storm
> Did Express Upgrade from HDP 2.1 to 2.3.4 and let it finish
> Observe the configs of various services
> *Result:*
> Observed that the values of several properties showed up as blank and 
> required (mostly security related). Here is the list:
> h3. HDFS:
> * hdfs_principal_name (hadoop-env, value is null, remove if not kerberized)
> * hdfs_user_keytab (hadoop-env, value is null, remove if not kerberized)
> * dfs.namenode.inode.attributes.provider.class (hdfs-site, value is null, set 
> to "org.apache.ranger.authorization.hadoop.RangerHdfsAuthorizer" if Ranger is 
> present, which it is not in HDP 2.1)
> h3. YARN:
> * yarn.authorization-provider (yarn-site, value is null, set to 
> "org.apache.ranger.authorization.yarn.authorizer.RangerYarnAuthorizer" if 
> Ranger is present, which it is not in HDP 2.1)
> h3. Tez:
> * tez.tez-ui.history-url.base (also tracked by AMBARI-14389, tez-site, value 
> is null, set to {code} 
> '{0}://{1}:{2}/#/main/views/TEZ/{3}/TEZ_CLUSTER_INSTANCE'.format(server_protocol,
>  server_host, server_port, latest_tez_jar_version) {code} by Stack Advisor)
> h3. HBase:
> * hbase_principal_name (hbase-env, value is null, remove if not kerberized)
> * hbase_user_keytab (hbase-env, value is null, remove if not kerberized)
> h3. ZK:
> * zookeeper_keytab_path (zookeeper-env, value is null, remove if not 
> kerberized)
> * zookeeper_principal_name (zookeeper-env, value is null, remove if not 
> kerberized)
> h3. Storm:
> * nimbus_keytab  (storm-env, value is null, remove if not kerberized)
> * nimbus_principal_name (storm-env, value is null, remove if not kerberized)
> * storm_keytab (storm-env, value is null, remove if not kerberized)
> * storm_principal_name (storm-env, value is null, remove if not kerberized)
> * storm_ui_keytab (storm-env, value is null, remove if not kerberized)
> * storm_ui_principal_name (storm-env, value is null, remove if not kerberized)
> * nimbus.authorizer (storm-site, need help from Storm team on what to set 
> this to since it depends on whether kerberos is enabled and Ranger is present)
> Attached few screenshots
> We may have more such issues for properties of services other than the ones 
> with which the cluster was created at 2.1; so while fixing the issue, please 
> ensure that all services are taken care of



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

[jira] [Updated] (AMBARI-14390) EU from HDP 2.1 to 2.3 added NULL properties

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-14390:
-
Summary: EU from HDP 2.1 to 2.3 added NULL properties  (was: EU from HDP 
2.1 to 2.3 added properties as NULL)

> EU from HDP 2.1 to 2.3 added NULL properties
> 
>
> Key: AMBARI-14390
> URL: https://issues.apache.org/jira/browse/AMBARI-14390
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.2.1
>
> Attachments: AMBARI-14390_1.png, AMBARI-14390_2.png, 
> AMBARI-14390_3.png
>
>
> *Steps:*
> With Ambari 2.2.0, setup HDP 2.1 cluster (non HA, unsecure) with following 
> services: hbase,pig,slider,hive,oozie,sqoop,flume,falcon,storm
> Did Express Upgrade from HDP 2.1 to 2.3.4 and let it finish
> Observe the configs of various services
> *Result:*
> Observed that the values of several properties showed up as blank and 
> required (mostly security related). Here is the list:
> h3. HDFS:
> * hdfs_principal_name (hadoop-env, value is null, remove if not kerberized)
> * hdfs_user_keytab (hadoop-env, value is null, remove if not kerberized)
> * dfs.namenode.inode.attributes.provider.class (hdfs-site, value is null, set 
> to "org.apache.ranger.authorization.hadoop.RangerHdfsAuthorizer" if Ranger is 
> present, which it is not in HDP 2.1)
> h3. YARN:
> * yarn.authorization-provider (yarn-site, value is null, set to 
> "org.apache.ranger.authorization.yarn.authorizer.RangerYarnAuthorizer" if 
> Ranger is present, which it is not in HDP 2.1)
> h3. Tez:
> * tez.tez-ui.history-url.base (also tracked by AMBARI-14389, tez-site, value 
> is null, set to {code} 
> '{0}://{1}:{2}/#/main/views/TEZ/{3}/TEZ_CLUSTER_INSTANCE'.format(server_protocol,
>  server_host, server_port, latest_tez_jar_version) {code} by Stack Advisor)
> h3. HBase:
> * hbase_principal_name (hbase-env, value is null, remove if not kerberized)
> * hbase_user_keytab (hbase-env, value is null, remove if not kerberized)
> h3. ZK:
> * zookeeper_keytab_path (zookeeper-env, value is null, remove if not 
> kerberized)
> * zookeeper_principal_name (zookeeper-env, value is null, remove if not 
> kerberized)
> h3. Storm:
> * nimbus_keytab  (storm-env, value is null, remove if not kerberized)
> * nimbus_principal_name (storm-env, value is null, remove if not kerberized)
> * storm_keytab (storm-env, value is null, remove if not kerberized)
> * storm_principal_name (storm-env, value is null, remove if not kerberized)
> * storm_ui_keytab (storm-env, value is null, remove if not kerberized)
> * storm_ui_principal_name (storm-env, value is null, remove if not kerberized)
> * nimbus.authorizer (storm-site, need help from Storm team on what to set 
> this to since it depends on whether kerberos is enabled and Ranger is present)
> Attached few screenshots
> We may have more such issues for properties of services other than the ones 
> with which the cluster was created at 2.1; so while fixing the issue, please 
> ensure that all services are taken care of



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

Review Request 41430: Remove HDP 2.4 from Stack options for installation.

[Swapan Shridhar]

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

Review request for Ambari, Sumit Mohanty and Jeff Sposetti.


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


Repository: ambari


Description
---

Remove HDP 2.4 from Stack options for installation.

HDP 2.4 shouldn't be shown as an option for installation as its not ready.

2nd part remaining is making 2.3.ECS as default. Raised a bug for that 
(BUG-49960).


Diffs
-

  ambari-server/src/main/resources/stacks/HDP/2.4/metainfo.xml 5d312a0 

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


Testing
---

Done. Screenshot attached show 2.4 not showing up in installation screen.


File Attachments


HDP 2.4 option doesn't show up now
  
https://reviews.apache.org/media/uploaded/files/2015/12/16/1e497827-ad28-4696-9f7c-da0ab8eabfe2__2.4_not_shown_in_Stack_options.png
2.4 not shown in Stack options.png
  
https://reviews.apache.org/media/uploaded/files/2015/12/16/9a40355c-477e-4760-b833-2da740422d7c__2.4_not_shown_in_Stack_options.png


Thanks,

Swapan Shridhar

Re: [ANNOUNCE] Di Li as a new committer for Ambari

[Eric Yang]

Congratulation Di!

regards,
Eric

On Tue, Dec 15, 2015 at 5:13 PM, Jeff Zhang  wrote:

> Congratulation Di
>
> On Wed, Dec 16, 2015 at 4:39 AM, Yusaku Sako 
> wrote:
>
>> Hi all,
>>
>> It is my pleasure to announce that Di Li has become a committer for Ambari.
>>
>> Di has been providing meaningful contributions in areas that tend to get 
>> overlooked
>> (usability, getting the details right, pluggability, etc.) in a full-stack 
>> manner to improve
>> various aspects of Ambari, including Ambari Agent, Ambari Web, and Ambari 
>> Server.
>>
>> Congratulations, Di!
>>
>> Yusaku   
>>
>>
>
>
> --
> Best Regards
>
> Jeff Zhang
>

Re: Review Request 41430: Remove HDP 2.4 from Stack options for installation.

[Swapan Shridhar]

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

(Updated Dec. 16, 2015, 1:47 a.m.)


Review request for Ambari, Sumit Mohanty and Jeff Sposetti.


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


Repository: ambari


Description
---

Remove HDP 2.4 from Stack options for installation.

HDP 2.4 shouldn't be shown as an option for installation as its not ready.

2nd part remaining is making 2.3.ECS as default. Raised a bug for that 
(BUG-49960).


Diffs
-

  ambari-server/src/main/resources/stacks/HDP/2.4/metainfo.xml 5d312a0 

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


Testing
---

Done. Screenshot attached show 2.4 not showing up in installation screen.


File Attachments (updated)


2.4 not shown in Stack options.png
  
https://reviews.apache.org/media/uploaded/files/2015/12/16/9a40355c-477e-4760-b833-2da740422d7c__2.4_not_shown_in_Stack_options.png


Thanks,

Swapan Shridhar

[jira] [Commented] (AMBARI-14393) Remove HDP 2.4 from Stack options for installation.

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-14393:


LGTM, +1

> Remove HDP 2.4 from Stack options for installation.
> ---
>
> Key: AMBARI-14393
> URL: https://issues.apache.org/jira/browse/AMBARI-14393
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.3.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.3.0
>
> Attachments: 2.4 not shown in Stack options.png, AMBARI-14393.patch
>
>
> HDP 2.4 shouldn't be shown as an option for installation as its not ready.



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

Re: Review Request 41107: Role Based Access Control support for Metrics.

[Jonathan Hurley]

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

Ship it!


Ship It!

- Jonathan Hurley


On Dec. 15, 2015, 7:59 p.m., Swapan Shridhar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/41107/
> ---
> 
> (Updated Dec. 15, 2015, 7:59 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jonathan Hurley, Nate Cole, 
> Robert Levas, Sumit Mohanty, and Sid Wagle.
> 
> 
> Bugs: AMBARI-14192
> https://issues.apache.org/jira/browse/AMBARI-14192
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Role Based Access Control support for Metrics.
> 
> 
> * With the base infrastructure already in place for "Role Based Access 
> Control(RBAC)", this change introduces the RBAC support for AMbari Metrics. 
> Before the doing the metrics population, to be send back, it does an 
> authorization check for the current user in consideration for the VIEW 
> METRICE permissoions.
>   
> 
> * The mapping is as follows :
> 
> Resource.InternalType.Cluster -> CLUSTER_VIEW_METRICS
> Resource.InternalType.HOST -> HOST_VIEW_METRICS
> Resource.InternalType.Component -> SERVICE_VIEW_METRICS
> Resource.InternalType.HostComponent -> SERVICE_VIEW_METRICS
> 
> * For a user requesting Metrics and not having Au`thorization, 
> AuthorizationException is raised.
> 
> 
> NOTE : 
> 
> As of now the below exist (Will be creating a JIRA for them). 
> 
> - when the VIEW USER logs in, it sees the VIEW listed for which it is 
> entitled for, but clicking on the CAPACITY SCHEDULER (YARN) VIEW results in 
> ERROR :
> 
> "Couldn't connect to the cluster
> RA040 I/O error while requesting Ambari". 
> REASON : This view internally calls meytrics for which it doesn't have the 
> permissions.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AbstractPropertyProvider.java
>  4a0c44f 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StackDefinedPropertyProvider.java
>  a1b4f3f 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/jmx/JMXPropertyProvider.java
>  2748dd4 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/MetricsPropertyProvider.java
>  f1c5c81 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/MetricsPropertyProviderProxy.java
>  ac11556 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/MetricsReportPropertyProviderProxy.java
>  4d2ce01 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/RestMetricsPropertyProvider.java
>  b32adda 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/ThreadPoolEnabledPropertyProvider.java
>  8a35636 
>   
> ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AuthorizationHelper.java
>  0c675b8 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/internal/StackDefinedPropertyProviderTest.java
>  bb6673c 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/JMXPropertyProviderTest.java
>  f0c1280 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/RestMetricsPropertyProviderTest.java
>  82b42f2 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/ganglia/GangliaPropertyProviderTest.java
>  6fefffe 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/timeline/AMSPropertyProviderTest.java
>  6b5926b 
> 
> Diff: https://reviews.apache.org/r/41107/diff/
> 
> 
> Testing
> ---
> 
> - Ambari Server Deployment and tested for "View USER (only view 
> permissions)", 'admin' login (all permissions) and SERVICE OPERATOR role.
> - UT : PASSES.
> - UNIT tests modified as part of this change, tested : Success.
> - 
> - API :
> 
> 
> View User :
> -
> 
> [root@c6401 ambari-server]# curl -u viewUser:aaa 
> "http://c6401:8080/api/v1/clusters/c1/hosts/c6401.ambari.apache.org?fields=metrics/network/bytes_in[1449532831,1449534631,15],metrics/network/bytes_out[1449532831,1449534631,15]";
> {
>   "status" : 403,
>   "message" : "The authenticated user does not have authorization to view 
> Host metrics"
> }
> 
> 
> Cluster Administrator Role:
> --
> 
> [root@c6401 ambari-server]# curl -u clusAdmin:aaa 
> "http://c6401:8080/api/v1/clusters/c1/hosts/c6401.ambari.apache.org?fields=metrics/network/bytes_in[1449532831,1449534631,15],metrics/network/bytes_out[1449532831,1449534631,15]";
> {
>   "href" : 
> "http://c6401:8080/api/v1/clusters/c1/hosts/c6401.ambari.apache.org?fields=metrics/network/bytes_in[1449532831,1449534631,15],metrics/network/b

[jira] [Created] (AMBARI-14394) Add ability to restart all host components with stale_configs=true with one API request

[Siddharth Wagle (JIRA)]

Siddharth Wagle created AMBARI-14394:


 Summary: Add ability to restart all host components with 
stale_configs=true with one API request
 Key: AMBARI-14394
 URL: https://issues.apache.org/jira/browse/AMBARI-14394
 Project: Ambari
  Issue Type: Improvement
  Components: ambari-server
Affects Versions: 2.0.0
Reporter: Siddharth Wagle
Assignee: Siddharth Wagle
Priority: Critical
 Fix For: 2.4.0


Provide ability to filter host components using a predicate that allows bulk 
ops like RESTART of stale configs with a simple API call.

Example:
{code}
{
  "RequestInfo": {
"context": "Restart stale",
"operational_level": "host_component",
"command": "RESTART"
  },
  "Requests/resource_filters": [
{
  "hosts_predicate": "HostRoles/stale_config=true"
}
  ]
}
{code}

This API call should allow user to perform custom command restart on all host 
components with stale configurations.



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

[jira] [Updated] (AMBARI-14393) Remove HDP 2.4 from Stack options for installation.

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar updated AMBARI-14393:
-
Attachment: AMBARI-14393.patch

> Remove HDP 2.4 from Stack options for installation.
> ---
>
> Key: AMBARI-14393
> URL: https://issues.apache.org/jira/browse/AMBARI-14393
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.3.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.3.0
>
> Attachments: 2.4 not shown in Stack options.png, AMBARI-14393.patch
>
>
> HDP 2.4 shouldn't be shown as an option for installation as its not ready.



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

[jira] [Updated] (AMBARI-14393) Remove HDP 2.4 from Stack options for installation.

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-14393:
---
Description: HDP 2.4 shouldn't be shown as an option for installation as 
its not ready.  (was: For the "Erie-techpreview-dec" release, HDP 2.4 shouldn't 
be shown as an option for installation.)

> Remove HDP 2.4 from Stack options for installation.
> ---
>
> Key: AMBARI-14393
> URL: https://issues.apache.org/jira/browse/AMBARI-14393
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.3.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.3.0
>
> Attachments: 2.4 not shown in Stack options.png
>
>
> HDP 2.4 shouldn't be shown as an option for installation as its not ready.



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

[VOTE] Ambari 2.2.0 - RC0

[Jaimin Jetly]

Hi all,


I have created an Apache Ambari 2.2.0 Release Candidate (RC0).


GIT source tag: 
https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=log;h=refs/tags/release-2.2.0-rc0


Staging site: http://people.apache.org/~jaimin/apache-ambari-2.2.0-rc0/


PGP release key used (signed using D30E6003?): 
http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x85041753D30E6003?

?

One can look into the issues fixed in this release at 
 
https://goo.gl/AU3h70


Vote will be open for 72 hours.


[ ] +1 approve

[ ] +0 no opinion

[ ] -1 disapprove (and reason why)


Here's my vote to start: +1


Thanks

Jaimin Jetly

Apache Ambari 2.2.0 Release Manager

?

[jira] [Updated] (AMBARI-14393) Remove HDP 2.4 from Stack options for installation.

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar updated AMBARI-14393:
-
Attachment: 2.4 not shown in Stack options.png

Screenshot: 2.4 not shown in Stack options now.

> Remove HDP 2.4 from Stack options for installation.
> ---
>
> Key: AMBARI-14393
> URL: https://issues.apache.org/jira/browse/AMBARI-14393
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.3.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.3.0
>
> Attachments: 2.4 not shown in Stack options.png
>
>
> For the "Erie-techpreview-dec" release, HDP 2.4 shouldn't be shown as an 
> option for installation.



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

Re: [ANNOUNCE] Di Li as a new committer for Ambari

[Jeff Zhang]

Congratulation Di

On Wed, Dec 16, 2015 at 4:39 AM, Yusaku Sako  wrote:

> Hi all,
>
> It is my pleasure to announce that Di Li has become a committer for Ambari.
>
> Di has been providing meaningful contributions in areas that tend to get 
> overlooked
> (usability, getting the details right, pluggability, etc.) in a full-stack 
> manner to improve
> various aspects of Ambari, including Ambari Agent, Ambari Web, and Ambari 
> Server.
>
> Congratulations, Di!
>
> Yusaku
>
>


-- 
Best Regards

Jeff Zhang

[jira] [Commented] (AMBARI-14393) Remove HDP 2.4 from Stack options for installation.

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar commented on AMBARI-14393:
--

Fix: Made "ambari-server/src/main/resources/stacks/HDP/2.4/metainfo.xml" active 
filed to false.

> Remove HDP 2.4 from Stack options for installation.
> ---
>
> Key: AMBARI-14393
> URL: https://issues.apache.org/jira/browse/AMBARI-14393
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.3.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.3.0
>
>
> For the "Erie-techpreview-dec" release, HDP 2.4 shouldn't be shown as an 
> option for installation.



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

[jira] [Created] (AMBARI-14393) Remove HDP 2.4 from Stack options for installation.

[Swapan Shridhar (JIRA)]

Swapan Shridhar created AMBARI-14393:


 Summary: Remove HDP 2.4 from Stack options for installation.
 Key: AMBARI-14393
 URL: https://issues.apache.org/jira/browse/AMBARI-14393
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.3.0
Reporter: Swapan Shridhar
Assignee: Swapan Shridhar
Priority: Critical
 Fix For: 2.3.0


For the "Erie-techpreview-dec" release, HDP 2.,4 shouldn't be shown as option 
for installation.



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

[jira] [Updated] (AMBARI-14393) Remove HDP 2.4 from Stack options for installation.

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar updated AMBARI-14393:
-
Description: For the "Erie-techpreview-dec" release, HDP 2.4 shouldn't be 
shown as an option for installation.  (was: For the "Erie-techpreview-dec" 
release, HDP 2.4 shouldn't be shown as option for installation.)

> Remove HDP 2.4 from Stack options for installation.
> ---
>
> Key: AMBARI-14393
> URL: https://issues.apache.org/jira/browse/AMBARI-14393
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.3.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.3.0
>
>
> For the "Erie-techpreview-dec" release, HDP 2.4 shouldn't be shown as an 
> option for installation.



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

[jira] [Updated] (AMBARI-14393) Remove HDP 2.4 from Stack options for installation.

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar updated AMBARI-14393:
-
Description: For the "Erie-techpreview-dec" release, HDP 2.4 shouldn't be 
shown as option for installation.  (was: For the "Erie-techpreview-dec" 
release, HDP 2.,4 shouldn't be shown as option for installation.)

> Remove HDP 2.4 from Stack options for installation.
> ---
>
> Key: AMBARI-14393
> URL: https://issues.apache.org/jira/browse/AMBARI-14393
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.3.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.3.0
>
>
> For the "Erie-techpreview-dec" release, HDP 2.4 shouldn't be shown as option 
> for installation.



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

Re: Review Request 41107: Role Based Access Control support for Metrics.

[Sumit Mohanty]

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

Ship it!


Ship It!

- Sumit Mohanty


On Dec. 16, 2015, 12:59 a.m., Swapan Shridhar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/41107/
> ---
> 
> (Updated Dec. 16, 2015, 12:59 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jonathan Hurley, Nate Cole, 
> Robert Levas, Sumit Mohanty, and Sid Wagle.
> 
> 
> Bugs: AMBARI-14192
> https://issues.apache.org/jira/browse/AMBARI-14192
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Role Based Access Control support for Metrics.
> 
> 
> * With the base infrastructure already in place for "Role Based Access 
> Control(RBAC)", this change introduces the RBAC support for AMbari Metrics. 
> Before the doing the metrics population, to be send back, it does an 
> authorization check for the current user in consideration for the VIEW 
> METRICE permissoions.
>   
> 
> * The mapping is as follows :
> 
> Resource.InternalType.Cluster -> CLUSTER_VIEW_METRICS
> Resource.InternalType.HOST -> HOST_VIEW_METRICS
> Resource.InternalType.Component -> SERVICE_VIEW_METRICS
> Resource.InternalType.HostComponent -> SERVICE_VIEW_METRICS
> 
> * For a user requesting Metrics and not having Au`thorization, 
> AuthorizationException is raised.
> 
> 
> NOTE : 
> 
> As of now the below exist (Will be creating a JIRA for them). 
> 
> - when the VIEW USER logs in, it sees the VIEW listed for which it is 
> entitled for, but clicking on the CAPACITY SCHEDULER (YARN) VIEW results in 
> ERROR :
> 
> "Couldn't connect to the cluster
> RA040 I/O error while requesting Ambari". 
> REASON : This view internally calls meytrics for which it doesn't have the 
> permissions.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AbstractPropertyProvider.java
>  4a0c44f 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StackDefinedPropertyProvider.java
>  a1b4f3f 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/jmx/JMXPropertyProvider.java
>  2748dd4 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/MetricsPropertyProvider.java
>  f1c5c81 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/MetricsPropertyProviderProxy.java
>  ac11556 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/MetricsReportPropertyProviderProxy.java
>  4d2ce01 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/RestMetricsPropertyProvider.java
>  b32adda 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/ThreadPoolEnabledPropertyProvider.java
>  8a35636 
>   
> ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AuthorizationHelper.java
>  0c675b8 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/internal/StackDefinedPropertyProviderTest.java
>  bb6673c 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/JMXPropertyProviderTest.java
>  f0c1280 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/RestMetricsPropertyProviderTest.java
>  82b42f2 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/ganglia/GangliaPropertyProviderTest.java
>  6fefffe 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/timeline/AMSPropertyProviderTest.java
>  6b5926b 
> 
> Diff: https://reviews.apache.org/r/41107/diff/
> 
> 
> Testing
> ---
> 
> - Ambari Server Deployment and tested for "View USER (only view 
> permissions)", 'admin' login (all permissions) and SERVICE OPERATOR role.
> - UT : PASSES.
> - UNIT tests modified as part of this change, tested : Success.
> - 
> - API :
> 
> 
> View User :
> -
> 
> [root@c6401 ambari-server]# curl -u viewUser:aaa 
> "http://c6401:8080/api/v1/clusters/c1/hosts/c6401.ambari.apache.org?fields=metrics/network/bytes_in[1449532831,1449534631,15],metrics/network/bytes_out[1449532831,1449534631,15]";
> {
>   "status" : 403,
>   "message" : "The authenticated user does not have authorization to view 
> Host metrics"
> }
> 
> 
> Cluster Administrator Role:
> --
> 
> [root@c6401 ambari-server]# curl -u clusAdmin:aaa 
> "http://c6401:8080/api/v1/clusters/c1/hosts/c6401.ambari.apache.org?fields=metrics/network/bytes_in[1449532831,1449534631,15],metrics/network/bytes_out[1449532831,1449534631,15]";
> {
>   "href" : 
> "http://c6401:8080/api/v1/clusters/c1/hosts/c6401.ambari.apache.org?fields=metrics/network/bytes_in[1449532831,1449534631,15],metrics/network/b

[jira] [Updated] (AMBARI-14194) Enforce granular role-based access control for metrics functions

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar updated AMBARI-14194:
-
Attachment: AMBARI-14194_trunk.patch

> Enforce granular role-based access control for metrics functions
> 
>
> Key: AMBARI-14194
> URL: https://issues.apache.org/jira/browse/AMBARI-14194
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.3.0, 2.4.0
>Reporter: Robert Levas
>Assignee: Swapan Shridhar
>  Labels: rbac1
> Fix For: 2.3.0, 2.4.0
>
> Attachments: AMBARI-14194_trunk.patch
>
>
> Enforce granular role-based access control for metrics functions:
> || || Cluster\\User || Service\\Operator || Service\\Administrator || 
> Cluster\\Operator || Cluster\\Administrator || Administrator ||
> |View service metrics  |(+)|(+)|(+)|(+)|(+)|(+)|
> |View host metrics  |(+)|(+)|(+)|(+)|(+)|(+)|
> |View cluster metrics  |(+)|(+)|(+)|(+)|(+)|(+)|
> Entry points affected:
> * TBD



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

[jira] [Updated] (AMBARI-14194) Enforce granular role-based access control for metrics functions

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar updated AMBARI-14194:
-
Attachment: (was: AMBARI-14194.patch)

> Enforce granular role-based access control for metrics functions
> 
>
> Key: AMBARI-14194
> URL: https://issues.apache.org/jira/browse/AMBARI-14194
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.3.0, 2.4.0
>Reporter: Robert Levas
>Assignee: Swapan Shridhar
>  Labels: rbac1
> Fix For: 2.3.0, 2.4.0
>
> Attachments: AMBARI-14194_trunk.patch
>
>
> Enforce granular role-based access control for metrics functions:
> || || Cluster\\User || Service\\Operator || Service\\Administrator || 
> Cluster\\Operator || Cluster\\Administrator || Administrator ||
> |View service metrics  |(+)|(+)|(+)|(+)|(+)|(+)|
> |View host metrics  |(+)|(+)|(+)|(+)|(+)|(+)|
> |View cluster metrics  |(+)|(+)|(+)|(+)|(+)|(+)|
> Entry points affected:
> * TBD



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

Re: Review Request 41107: Role Based Access Control support for Metrics.

[Swapan Shridhar]

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

(Updated Dec. 16, 2015, 12:59 a.m.)


Review request for Ambari, Alejandro Fernandez, Jonathan Hurley, Nate Cole, 
Robert Levas, Sumit Mohanty, and Sid Wagle.


Changes
---

- Updated the code based on Jonathan and Nate's comments.


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


Repository: ambari


Description (updated)
---

Role Based Access Control support for Metrics.


* With the base infrastructure already in place for "Role Based Access 
Control(RBAC)", this change introduces the RBAC support for AMbari Metrics. 
Before the doing the metrics population, to be send back, it does an 
authorization check for the current user in consideration for the VIEW METRICE 
permissoions.
  

* The mapping is as follows :

Resource.InternalType.Cluster -> CLUSTER_VIEW_METRICS
Resource.InternalType.HOST -> HOST_VIEW_METRICS
Resource.InternalType.Component -> SERVICE_VIEW_METRICS
Resource.InternalType.HostComponent -> SERVICE_VIEW_METRICS

* For a user requesting Metrics and not having Au`thorization, 
AuthorizationException is raised.


NOTE : 

As of now the below exist (Will be creating a JIRA for them). 

- when the VIEW USER logs in, it sees the VIEW listed for which it is entitled 
for, but clicking on the CAPACITY SCHEDULER (YARN) VIEW results in ERROR :

"Couldn't connect to the cluster
RA040 I/O error while requesting Ambari". 
REASON : This view internally calls meytrics for which it doesn't have the 
permissions.


Diffs (updated)
-

  
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AbstractPropertyProvider.java
 4a0c44f 
  
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StackDefinedPropertyProvider.java
 a1b4f3f 
  
ambari-server/src/main/java/org/apache/ambari/server/controller/jmx/JMXPropertyProvider.java
 2748dd4 
  
ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/MetricsPropertyProvider.java
 f1c5c81 
  
ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/MetricsPropertyProviderProxy.java
 ac11556 
  
ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/MetricsReportPropertyProviderProxy.java
 4d2ce01 
  
ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/RestMetricsPropertyProvider.java
 b32adda 
  
ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/ThreadPoolEnabledPropertyProvider.java
 8a35636 
  
ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AuthorizationHelper.java
 0c675b8 
  
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/StackDefinedPropertyProviderTest.java
 bb6673c 
  
ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/JMXPropertyProviderTest.java
 f0c1280 
  
ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/RestMetricsPropertyProviderTest.java
 82b42f2 
  
ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/ganglia/GangliaPropertyProviderTest.java
 6fefffe 
  
ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/timeline/AMSPropertyProviderTest.java
 6b5926b 

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


Testing (updated)
---

- Ambari Server Deployment and tested for "View USER (only view permissions)", 
'admin' login (all permissions) and SERVICE OPERATOR role.
- UT : PASSES.
- UNIT tests modified as part of this change, tested : Success.
- 
- API :


View User :
-

[root@c6401 ambari-server]# curl -u viewUser:aaa 
"http://c6401:8080/api/v1/clusters/c1/hosts/c6401.ambari.apache.org?fields=metrics/network/bytes_in[1449532831,1449534631,15],metrics/network/bytes_out[1449532831,1449534631,15]";
{
  "status" : 403,
  "message" : "The authenticated user does not have authorization to view Host 
metrics"
}


Cluster Administrator Role:
--

[root@c6401 ambari-server]# curl -u clusAdmin:aaa 
"http://c6401:8080/api/v1/clusters/c1/hosts/c6401.ambari.apache.org?fields=metrics/network/bytes_in[1449532831,1449534631,15],metrics/network/bytes_out[1449532831,1449534631,15]";
{
  "href" : 
"http://c6401:8080/api/v1/clusters/c1/hosts/c6401.ambari.apache.org?fields=metrics/network/bytes_in[1449532831,1449534631,15],metrics/network/bytes_out[1449532831,1449534631,15]";,
  "Hosts" : {
"cluster_name" : "c1",
"host_name" : "c6401.ambari.apache.org"
  }
}


Service Operator:


[root@c6401 ambari-server]# curl -u servOp:aaa 
"http://c6401:8080/api/v1/clusters/c1/hosts/c6401.ambari.apache.org?fields=metrics/network/bytes_in[1449532831,1449534631,15],metrics/network/bytes_out[1449532831,1449534631,15]";
{
  "href" : 
"http://c6401:8080/api/v1/clusters/c1/hosts/c6401.ambari.apache.org?fields=metrics/n

[jira] [Updated] (AMBARI-14392) Move logic to ambari-web, for adding parameters to hdfs-client.xml for HAWQ when HAWQ is installed on NN HA cluster

[Matt (JIRA)]

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

Matt updated AMBARI-14392:
--
Attachment: AMBARI-14392.patch

> Move logic to ambari-web, for adding parameters to hdfs-client.xml for HAWQ 
> when HAWQ is installed on NN HA cluster
> ---
>
> Key: AMBARI-14392
> URL: https://issues.apache.org/jira/browse/AMBARI-14392
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Affects Versions: trunk
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: 2.3.0, trunk
>
> Attachments: AMBARI-14392.patch
>
>
> Currently, the parameters required by HAWQ to work on NN HA cluster are added 
> to hdfs-client.xml using python code in common-services. 
> This does not show up on the UI.
> This ticket is to show the parameters on the UI, and add them to 
> hdfs-client.xml by leveraging code in ambari-web.



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

Re: Review Request 41107: Role Based Access Control support for Metrics.

[Swapan Shridhar]

> On Dec. 15, 2015, 1:06 p.m., Nate Cole wrote:
> > ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AbstractPropertyProvider.java,
> >  lines 119-127
> > 
> >
> > This assumes that all passed-in resources are the same?

Yes.


- Swapan


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


On Dec. 12, 2015, 10:40 a.m., Swapan Shridhar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/41107/
> ---
> 
> (Updated Dec. 12, 2015, 10:40 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jonathan Hurley, Nate Cole, 
> Robert Levas, Sumit Mohanty, and Sid Wagle.
> 
> 
> Bugs: AMBARI-14192
> https://issues.apache.org/jira/browse/AMBARI-14192
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Role Based Access Control support for Metrics.
> 
> 
> * With the base infrastructure already in place for "Role Based Access 
> Control(RBAC)", this change introduces the RBAC support for AMbari Metrics. 
> Before the doing the metrics population, to be send back, it does an 
> authorization check for the current user in consideration for the VIEW 
> METRICE permissoions.
>   
> 
> * The mapping is as follows :
> 
> Resource.InternalType.Cluster -> CLUSTER_VIEW_METRICS
> Resource.InternalType.HOST -> HOST_VIEW_METRICS
> Resource.InternalType.Component -> SERVICE_VIEW_METRICS
> Resource.InternalType.HostComponent -> SERVICE_VIEW_METRICS
> 
> * For a user requesting Metrics and not having Au`thorization, 
> AuthorizationException is raised.
> 
> 
> NOTE : 
> 
> As of now, the when the VIEW USER logs in, it see the VIEW listed for which 
> it is entitled for, but clicking on the VIEW results in ERROR :
> 
> "Couldn't connect to the cluster
> RA040 I/O error while requesting Ambari". 
> 
> 
> Two Screenshots attached.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AbstractPropertyProvider.java
>  4a0c44f 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StackDefinedPropertyProvider.java
>  a1b4f3f 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/jmx/JMXPropertyProvider.java
>  2748dd4 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/MetricsPropertyProvider.java
>  f1c5c81 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/MetricsPropertyProviderProxy.java
>  ac11556 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/MetricsReportPropertyProviderProxy.java
>  4d2ce01 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/RestMetricsPropertyProvider.java
>  b32adda 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/ThreadPoolEnabledPropertyProvider.java
>  8a35636 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/internal/StackDefinedPropertyProviderTest.java
>  bb6673c 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/JMXPropertyProviderTest.java
>  f0c1280 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/RestMetricsPropertyProviderTest.java
>  82b42f2 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/ganglia/GangliaPropertyProviderTest.java
>  6fefffe 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/timeline/AMSPropertyProviderTest.java
>  6b5926b 
> 
> Diff: https://reviews.apache.org/r/41107/diff/
> 
> 
> Testing
> ---
> 
> - Ambari Server Deployment and tested for "View USER (only view 
> permissions)", 'admin' login(all permissions) and SERVICE OPERATOR role.
> - UT : PASSES.
> - UNIT tests modified as part of this change, tested : Success.
> - 
> - API :
> 
> 
> View User :
> -
> 
> [root@c6401 ambari-server]# curl -u viewUser:aaa 
> "http://c6401:8080/api/v1/clusters/c1/hosts/c6401.ambari.apache.org?fields=metrics/network/bytes_in[1449532831,1449534631,15],metrics/network/bytes_out[1449532831,1449534631,15]";
> {
>   "status" : 403,
>   "message" : "The authenticated user does not have authorization to view 
> Host metrics"
> }
> 
> 
> Cluster Administrator Role:
> --
> 
> [root@c6401 ambari-server]# curl -u clusAdmin:aaa 
> "http://c6401:8080/api/v1/clusters/c1/hosts/c6401.ambari.apache.org?fields=metrics/network/bytes_in[1449532831,1449534631,15],metrics/network/bytes_out[1449532831,1449534631,15]";
> {
>   "href" : 
> "http://c6401:8080/api/v1/clusters/c1/hosts/c6401.ambari.apache.org?fields=metrics/network/bytes_in[14

Review Request 41427: Move logic to ambari-web, for adding parameters to hdfs-client.xml for HAWQ when HAWQ is installed on NN HA cluster

[Matt]

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

Review request for Ambari, Alexander Denissov, Alejandro Fernandez, bhuvnesh 
chaudhary, Jaimin Jetly, jun aoki, Jayush Luniya, Lav Jain, Newton Alex, and 
Oleksandr Diachenko.


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


Repository: ambari


Description
---

Currently, the parameters required by HAWQ to work on NN HA cluster are added 
to hdfs-client.xml using python code in common-services. 
This does not show up on the UI.

This ticket is to show the parameters on the UI, and add them to 
hdfs-client.xml by leveraging code in ambari-web.


Diffs
-

  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/common.py
 ac81b11 
  ambari-web/app/controllers/wizard/step7_controller.js 8877dbc 
  ambari-web/test/controllers/wizard/step7_test.js 334563d 

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


Testing
---

Yes


Thanks,

Matt

Re: Review Request 41107: Role Based Access Control support for Metrics.

[Swapan Shridhar]

> On Dec. 14, 2015, 3:31 p.m., Jonathan Hurley wrote:
> > ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AbstractPropertyProvider.java,
> >  lines 117-150
> > 
> >
> > I'm a little concerned about these methods taking the first item in the 
> > collection. We know that moving forward we're going to probably need to 
> > support multiple clusters and multiple service instances - taking the first 
> > and using it seems wrong here.

- getClusterNameFromResources : Fixed. Will be looping to gather all the 
cluster names.
- getResourceTypeFromResources : Not fixed. The resources Set passed in will 
always have same Type.


- Swapan


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


On Dec. 12, 2015, 10:40 a.m., Swapan Shridhar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/41107/
> ---
> 
> (Updated Dec. 12, 2015, 10:40 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jonathan Hurley, Nate Cole, 
> Robert Levas, Sumit Mohanty, and Sid Wagle.
> 
> 
> Bugs: AMBARI-14192
> https://issues.apache.org/jira/browse/AMBARI-14192
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Role Based Access Control support for Metrics.
> 
> 
> * With the base infrastructure already in place for "Role Based Access 
> Control(RBAC)", this change introduces the RBAC support for AMbari Metrics. 
> Before the doing the metrics population, to be send back, it does an 
> authorization check for the current user in consideration for the VIEW 
> METRICE permissoions.
>   
> 
> * The mapping is as follows :
> 
> Resource.InternalType.Cluster -> CLUSTER_VIEW_METRICS
> Resource.InternalType.HOST -> HOST_VIEW_METRICS
> Resource.InternalType.Component -> SERVICE_VIEW_METRICS
> Resource.InternalType.HostComponent -> SERVICE_VIEW_METRICS
> 
> * For a user requesting Metrics and not having Au`thorization, 
> AuthorizationException is raised.
> 
> 
> NOTE : 
> 
> As of now, the when the VIEW USER logs in, it see the VIEW listed for which 
> it is entitled for, but clicking on the VIEW results in ERROR :
> 
> "Couldn't connect to the cluster
> RA040 I/O error while requesting Ambari". 
> 
> 
> Two Screenshots attached.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AbstractPropertyProvider.java
>  4a0c44f 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StackDefinedPropertyProvider.java
>  a1b4f3f 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/jmx/JMXPropertyProvider.java
>  2748dd4 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/MetricsPropertyProvider.java
>  f1c5c81 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/MetricsPropertyProviderProxy.java
>  ac11556 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/MetricsReportPropertyProviderProxy.java
>  4d2ce01 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/RestMetricsPropertyProvider.java
>  b32adda 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/ThreadPoolEnabledPropertyProvider.java
>  8a35636 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/internal/StackDefinedPropertyProviderTest.java
>  bb6673c 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/JMXPropertyProviderTest.java
>  f0c1280 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/RestMetricsPropertyProviderTest.java
>  82b42f2 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/ganglia/GangliaPropertyProviderTest.java
>  6fefffe 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/timeline/AMSPropertyProviderTest.java
>  6b5926b 
> 
> Diff: https://reviews.apache.org/r/41107/diff/
> 
> 
> Testing
> ---
> 
> - Ambari Server Deployment and tested for "View USER (only view 
> permissions)", 'admin' login(all permissions) and SERVICE OPERATOR role.
> - UT : PASSES.
> - UNIT tests modified as part of this change, tested : Success.
> - 
> - API :
> 
> 
> View User :
> -
> 
> [root@c6401 ambari-server]# curl -u viewUser:aaa 
> "http://c6401:8080/api/v1/clusters/c1/hosts/c6401.ambari.apache.org?fields=metrics/network/bytes_in[1449532831,1449534631,15],metrics/network/bytes_out[1449532831,1449534631,15]";
> {
>   "status" : 403,
>   "message" : "The authenticated user does not have authorization to view 
> Host metrics"
> }
> 
> 
> Cluster Administ

[jira] [Created] (AMBARI-14392) Move logic to ambari-web, for adding parameters to hdfs-client.xml for HAWQ when HAWQ is installed on NN HA cluster

[Matt (JIRA)]

Matt created AMBARI-14392:
-

 Summary: Move logic to ambari-web, for adding parameters to 
hdfs-client.xml for HAWQ when HAWQ is installed on NN HA cluster
 Key: AMBARI-14392
 URL: https://issues.apache.org/jira/browse/AMBARI-14392
 Project: Ambari
  Issue Type: Improvement
  Components: ambari-web
Affects Versions: trunk
Reporter: Matt
Assignee: Matt
Priority: Minor
 Fix For: 2.3.0, trunk


Currently, the parameters required by HAWQ to work on NN HA cluster are added 
to hdfs-client.xml using python code in common-services. 
This does not show up on the UI.

This ticket is to show the parameters on the UI, and add them to 
hdfs-client.xml by leveraging code in ambari-web.



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

[jira] [Commented] (AMBARI-14346) Apache Build Failure: Surefire crashes

[Ajit Kumar (JIRA)]

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

Ajit Kumar commented on AMBARI-14346:
-

[~jluniya]
I would prefer to inherit surefire version from parent pom instead of updating 
version everywhere. I tested by deleting version entries in all pom.xml (except 
contrib/ambari-scom/*) in addendum.patch and running  "mvn clean test". All 
projects are using 2.19 of surefire plugin except ambari-metrics pacakge.

ambari-metrics package currently doesn't inherit pom from ambari-project. I 
checked with [~swagle] and we should be able add inheritance. I'll add another 
patch with all changes.

> Apache Build Failure: Surefire crashes
> --
>
> Key: AMBARI-14346
> URL: https://issues.apache.org/jira/browse/AMBARI-14346
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.3.0
>Reporter: Jayush Luniya
>Assignee: Ajit Kumar
>Priority: Blocker
> Fix For: 2.3.0
>
> Attachments: AMBARI-14346.addendum.patch, rb41267.patch
>
>
> https://builds.apache.org/job/Ambari-trunk-Commit/4012/console
> Surefire crashes. This looks like 
> https://issues.apache.org/jira/browse/SUREFIRE-967. We should update surefire 
> plugin version from 2.13 to 2.15+
> {code}
> ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec 
> (ambari-web unit tests) on project ambari-web: Command execution failed. 
> Process exited with an error: 1 (Exit value: 1) -> [Help 1]
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.13:test (default-test) on 
> project ambari-server: ExecutionException; nested exception is 
> java.util.concurrent.ExecutionException: java.lang.RuntimeException: There 
> was an error in the forked process
> [ERROR] org.apache.maven.surefire.testset.TestSetFailedException: 
> java.lang.ArrayIndexOutOfBoundsException: 0; nested exception is 
> java.lang.ArrayIndexOutOfBoundsException: 0
> [ERROR] java.lang.ArrayIndexOutOfBoundsException: 0
> [ERROR] at 
> org.apache.maven.surefire.report.SmartStackTraceParser.rootIsInclass(SmartStackTraceParser.java:176)
> [ERROR] at 
> org.apache.maven.surefire.report.SmartStackTraceParser.getString(SmartStackTraceParser.java:131)
> [ERROR] at 
> org.apache.maven.surefire.common.junit4.JUnit4StackTraceWriter.smartTrimmedStackTrace(JUnit4StackTraceWriter.java:73)
> [ERROR] at 
> org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:328)
> [ERROR] at 
> org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:312)
> [ERROR] at 
> org.apache.maven.surefire.booter.ForkingRunListener.toString(ForkingRunListener.java:258)
> [ERROR] at 
> org.apache.maven.surefire.booter.ForkingRunListener.testError(ForkingRunListener.java:131)
> [ERROR] at 
> org.apache.maven.surefire.common.junit4.JUnit4RunListener.testFailure(JUnit4RunListener.java:111)
> [ERROR] at 
> org.junit.runner.notification.RunNotifier$4.notifyListener(RunNotifier.java:100)
> [ERROR] at 
> org.junit.runner.notification.RunNotifier$SafeNotifier.run(RunNotifier.java:41)
> [ERROR] at 
> org.junit.runner.notification.RunNotifier.fireTestFailure(RunNotifier.java:97)
> [ERROR] at 
> org.junit.internal.runners.model.EachTestNotifier.addFailure(EachTestNotifier.java:26)
> [ERROR] at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:267)
> [ERROR] at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
> [ERROR] at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
> [ERROR] at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
> [ERROR] at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
> [ERROR] at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
> [ERROR] at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
> [ERROR] at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
> [ERROR] at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
> [ERROR] at 
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
> [ERROR] at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
> [ERROR] at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
> [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR] at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> [ERROR] at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [ERROR] at java.lang.reflect.Method.invoke(Method.java:606)
> [ERROR] at 
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUti

[jira] [Updated] (AMBARI-14390) Several properties showed up as blank after EU from HDP 2.1 to HDP 2.3

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-14390:
-
Description: 
*Steps:*
With Ambari 2.2.0, setup HDP 2.1 cluster (non HA, unsecure) with following 
services: hbase,pig,slider,hive,oozie,sqoop,flume,falcon,storm
Did Express Upgrade from HDP 2.1 to 2.3.4 and let it finish
Observe the configs of various services

*Result:*
Observed that the values of several properties showed up as blank and required 
(mostly security related). Here is the list:

h3. HDFS:
* hdfs_principal_name (hadoop-env, value is null, remove if not kerberized)
* hdfs_user_keytab (hadoop-env, value is null, remove if not kerberized)
* dfs.namenode.inode.attributes.provider.class (hdfs-site, value is null, set 
to "org.apache.ranger.authorization.hadoop.RangerHdfsAuthorizer" if Ranger is 
present, which it is not in HDP 2.1)

h3. YARN:
* yarn.authorization-provider (yarn-site, value is null, set to 
"org.apache.ranger.authorization.yarn.authorizer.RangerYarnAuthorizer" if 
Ranger is present, which it is not in HDP 2.1)

h3. Tez:
* tez.tez-ui.history-url.base (also tracked by AMBARI-14389, tez-site, value is 
null, set to {code} 
'{0}://{1}:{2}/#/main/views/TEZ/{3}/TEZ_CLUSTER_INSTANCE'.format(server_protocol,
 server_host, server_port, latest_tez_jar_version) {code} by Stack Advisor)

h3. HBase:
* hbase_principal_name (hbase-env, value is null, remove if not kerberized)
* hbase_user_keytab (hbase-env, value is null, remove if not kerberized)

h3. ZK:
* zookeeper_keytab_path (zookeeper-env, value is null, remove if not kerberized)
* zookeeper_principal_name (zookeeper-env, value is null, remove if not 
kerberized)

h3. Storm:
* nimbus_keytab  (storm-env, value is null, remove if not kerberized)
* nimbus_principal_name (storm-env, value is null, remove if not kerberized)
* storm_keytab (storm-env, value is null, remove if not kerberized)
* storm_principal_name (storm-env, value is null, remove if not kerberized)
* storm_ui_keytab (storm-env, value is null, remove if not kerberized)
* storm_ui_principal_name (storm-env, value is null, remove if not kerberized)
* nimbus.authorizer (storm-site, need help from Storm team on what to set this 
to since it depends on whether kerberos is enabled and Ranger is present)

Attached few screenshots

We may have more such issues for properties of services other than the ones 
with which the cluster was created at 2.1; so while fixing the issue, please 
ensure that all services are taken care of

  was:
*Steps:*
With Ambari 2.2.0, setup HDP 2.1 cluster (non HA, unsecure) with following 
services: hbase,pig,slider,hive,oozie,sqoop,flume,falcon,storm
Did Express Upgrade from HDP 2.1 to 2.3.4 and let it finish
Observe the configs of various services

*Result:*
Observed that the values of several properties showed up as blank and required 
(mostly security related). Here is the list:

h3. HDFS:
* hdfs_principal_name (hadoop-env, value is null, remove if not kerberized)
* hdfs_user_keytab (hadoop-env, value is null, remove if not kerberized)
* dfs.namenode.inode.attributes.provider.class (hdfs-site, value is null, set 
to "org.apache.ranger.authorization.hadoop.RangerHdfsAuthorizer" if Ranger is 
present, which it is not in HDP 2.1)

h3. YARN:
* yarn.authorization-provider (yarn-site, value is null, set to 
"org.apache.ranger.authorization.yarn.authorizer.RangerYarnAuthorizer" if 
Ranger is present, which it is not in HDP 2.1)

h3. Tez:
* tez.tez-ui.history-url.base (also tracked by BUG-49613, tez-site, value is 
null, set to {code} 
'{0}://{1}:{2}/#/main/views/TEZ/{3}/TEZ_CLUSTER_INSTANCE'.format(server_protocol,
 server_host, server_port, latest_tez_jar_version) {code} by Stack Advisor)

h3. HBase:
* hbase_principal_name (hbase-env, value is null, remove if not kerberized)
* hbase_user_keytab (hbase-env, value is null, remove if not kerberized)

h3. ZK:
* zookeeper_keytab_path (zookeeper-env, value is null, remove if not kerberized)
* zookeeper_principal_name (zookeeper-env, value is null, remove if not 
kerberized)

h3. Storm:
* nimbus_keytab  (storm-env, value is null, remove if not kerberized)
* nimbus_principal_name (storm-env, value is null, remove if not kerberized)
* storm_keytab (storm-env, value is null, remove if not kerberized)
* storm_principal_name (storm-env, value is null, remove if not kerberized)
* storm_ui_keytab (storm-env, value is null, remove if not kerberized)
* storm_ui_principal_name (storm-env, value is null, remove if not kerberized)
* nimbus.authorizer (storm-site, need help from Storm team on what to set this 
to since it depends on whether kerberos is enabled and Ranger is present)

Attached few screenshots

We may have more such issues for properties of services other than the ones 
with which the cluster was created at 2.1; so while fixing the issue, please 
ensure that all services are taken care of


> Several 

[jira] [Commented] (AMBARI-14274) RU: Better text message about backup Oozie database

[Yusaku Sako (JIRA)]

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

Yusaku Sako commented on AMBARI-14274:
--

Failure not related to this commit.

> RU: Better text message about backup Oozie database
> ---
>
> Key: AMBARI-14274
> URL: https://issues.apache.org/jira/browse/AMBARI-14274
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Di Li
>Assignee: Di Li
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-14274.patch
>
>
> Oozie DB may be on a different node than the Oozie node. The text currently 
> reads "Before continuing, please backup the Oozie Server database on 
> .mydomain.com" 
> The text is only valid when Oozie db is on the same node as Oozie server.
> The proposal here is to change the text to "Before continuing, please backup 
> the Oozie Server database referenced by the Oozie server located on 
> xxx.mydomain.com."



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

[jira] [Commented] (AMBARI-14381) Role-Based Access Control: UX and Bugs

[Yusaku Sako (JIRA)]

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

Yusaku Sako commented on AMBARI-14381:
--

Failure not related to this commit.

> Role-Based Access Control: UX and Bugs
> --
>
> Key: AMBARI-14381
> URL: https://issues.apache.org/jira/browse/AMBARI-14381
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin, ambari-web
>Affects Versions: 2.3.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.3.0
>
> Attachments: AMBARI-14381.patch
>
>
> Role-Based Access Control: UX and Bugs



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

[jira] [Commented] (AMBARI-14293) While doing express upgrade multiple Clients and Services Failed to start

[Yusaku Sako (JIRA)]

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

Yusaku Sako commented on AMBARI-14293:
--

Failure not related to this commit.

> While doing express upgrade multiple Clients and Services Failed to start
> -
>
> Key: AMBARI-14293
> URL: https://issues.apache.org/jira/browse/AMBARI-14293
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.2.0
>
> Attachments: AMBARI-14293.patch
>
>
> During nightly run over Centos7 express upgrade test cases failed because of 
> TEZ Client issue.
> Restart of Tez Client failed after upgrade because of conf file missing.
> After logging on box I found the soft links /etc/tez/conf & 
> /usr/hdp/current/tez-client/conf pointing in loop to each other.
> [root@os-r7-test-2 tez-client]# ls -l /usr/hdp/2.3.4.0-3426/tez/conf
> lrwxrwxrwx. 1 root root 13 Dec  8 05:05 /usr/hdp/2.3.4.0-3426/tez/conf -> 
> /etc/tez/conf
> [root@os-r7-test-2 tez-client]# ls -l /etc/tez/conf
> lrwxrwxrwx. 1 root root 32 Dec  8 02:23 /etc/tez/conf -> 
> /usr/hdp/current/tez-client/conf
> [root@os-r7-test-2 tez-client]# ls -l /usr/hdp/current/tez-client/conf
> lrwxrwxrwx. 1 root root 13 Dec  8 05:05 /usr/hdp/current/tez-client/conf -> 
> /etc/tez/conf
> [root@os-r7-test-2 tez-client]#
> Error on UI
> {code}
> Traceback (most recent call last):
> File 
> "/var/lib/ambari-agent/cache/common-services/TEZ/0.4.0.2.1/package/scripts/tez_client.py",
>  line 104, in 
> TezClient().execute()
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 217, in execute
> method(env)
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 486, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File 
> "/var/lib/ambari-agent/cache/common-services/TEZ/0.4.0.2.1/package/scripts/tez_client.py",
>  line 59, in pre_upgrade_restart
> conf_select.select(params.stack_name, "tez", params.version)
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/conf_select.py",
>  line 247, in select
> shell.checked_call(get_cmd("set-conf-dir", package, version), 
> logoutput=False, quiet=False, sudo=True)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 70, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 92, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 291, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'conf-select 
> set-conf-dir --package tez --stack-version 2.3.4.0-3426 --conf-version 0' 
> returned 1. /usr/hdp/2.3.4.0-3426/tez/conf does not exist
> {code}
> Observed this issue for other components too AFTER 'Ignore and Proceed' the 
> Tez client error
> The error was seen for following components:
> Pig client, Hive server, Metastore, Hive client, Spark service, spark client. 
> See attached file for output



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

[jira] [Updated] (AMBARI-14390) Several properties showed up as blank after EU from HDP 2.1 to HDP 2.3

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-14390:
-
Description: 
*Steps:*
With Ambari 2.2.0, setup HDP 2.1 cluster (non HA, unsecure) with following 
services: hbase,pig,slider,hive,oozie,sqoop,flume,falcon,storm
Did Express Upgrade from HDP 2.1 to 2.3.4 and let it finish
Observe the configs of various services

*Result:*
Observed that the values of several properties showed up as blank and required 
(mostly security related). Here is the list:

h3. HDFS:
* hdfs_principal_name (hadoop-env, value is null, remove if not kerberized)
* hdfs_user_keytab (hadoop-env, value is null, remove if not kerberized)
* dfs.namenode.inode.attributes.provider.class (hdfs-site, value is null, set 
to "org.apache.ranger.authorization.hadoop.RangerHdfsAuthorizer" if Ranger is 
present, which it is not in HDP 2.1)

h3. YARN:
* yarn.authorization-provider (yarn-site, value is null, set to 
"org.apache.ranger.authorization.yarn.authorizer.RangerYarnAuthorizer" if 
Ranger is present, which it is not in HDP 2.1)

h3. Tez:
* tez.tez-ui.history-url.base (also tracked by BUG-49613, tez-site, value is 
null, set to {code} 
'{0}://{1}:{2}/#/main/views/TEZ/{3}/TEZ_CLUSTER_INSTANCE'.format(server_protocol,
 server_host, server_port, latest_tez_jar_version) {code} by Stack Advisor)

h3. HBase:
* hbase_principal_name (hbase-env, value is null, remove if not kerberized)
* hbase_user_keytab (hbase-env, value is null, remove if not kerberized)

h3. ZK:
* zookeeper_keytab_path (zookeeper-env, value is null, remove if not kerberized)
* zookeeper_principal_name (zookeeper-env, value is null, remove if not 
kerberized)

h3. Storm:
* nimbus_keytab  (storm-env, value is null, remove if not kerberized)
* nimbus_principal_name (storm-env, value is null, remove if not kerberized)
* storm_keytab (storm-env, value is null, remove if not kerberized)
* storm_principal_name (storm-env, value is null, remove if not kerberized)
* storm_ui_keytab (storm-env, value is null, remove if not kerberized)
* storm_ui_principal_name (storm-env, value is null, remove if not kerberized)
* nimbus.authorizer (storm-site, need help from Storm team on what to set this 
to since it depends on whether kerberos is enabled and Ranger is present)

Attached few screenshots

We may have more such issues for properties of services other than the ones 
with which the cluster was created at 2.1; so while fixing the issue, please 
ensure that all services are taken care of

  was:
*Steps:*
With Ambari 2.2.0, setup HDP 2.1 cluster (non HA, unsecure) with following 
services: hbase,pig,slider,hive,oozie,sqoop,flume,falcon,storm
Did Express Upgrade from HDP 2.1 to 2.3.4 and let it finish
Observe the configs of various services

*Result:*
Observed that the values of several properties showed up as blank and required 
(mostly security related). Here is the list:

h3. HDFS:
* hdfs_principal_name (hadoop-env, value is null, remove if not kerberized)
* hdfs_user_keytab (hadoop-env, value is null, remove if not kerberized)
* dfs.namenode.inode.attributes.provider.class (hdfs-site, value is null, set 
to "org.apache.ranger.authorization.hadoop.RangerHdfsAuthorizer" if Ranger is 
present, which it is not in HDP 2.1)

h3. YARN:
* yarn.authorization-provider (yarn-site, value is null, set to 
"org.apache.ranger.authorization.yarn.authorizer.RangerYarnAuthorizer" if 
Ranger is present, which it is not in HDP 2.1)

h3. Tez:
* tez.tez-ui.history-url.base (also tracked by BUG-49613, tez-site, value is 
null, set to 
'{0}://{1}:{2}/#/main/views/TEZ/{3}/TEZ_CLUSTER_INSTANCE'.format(server_protocol,
 server_host, server_port, latest_tez_jar_version) by Stack Advisor)

h3. HBase:
* hbase_principal_name (hbase-env, value is null, remove if not kerberized)
* hbase_user_keytab (hbase-env, value is null, remove if not kerberized)

h3. ZK:
* zookeeper_keytab_path (zookeeper-env, value is null, remove if not kerberized)
* zookeeper_principal_name (zookeeper-env, value is null, remove if not 
kerberized)

h3. Storm:
* nimbus_keytab  (storm-env, value is null, remove if not kerberized)
* nimbus_principal_name (storm-env, value is null, remove if not kerberized)
* storm_keytab (storm-env, value is null, remove if not kerberized)
* storm_principal_name (storm-env, value is null, remove if not kerberized)
* storm_ui_keytab (storm-env, value is null, remove if not kerberized)
* storm_ui_principal_name (storm-env, value is null, remove if not kerberized)
* nimbus.authorizer (storm-site, need help from Storm team on what to set this 
to since it depends on whether kerberos is enabled and Ranger is present)

Attached few screenshots

We may have more such issues for properties of services other than the ones 
with which the cluster was created at 2.1; so while fixing the issue, please 
ensure that all services are taken care of


> Several properties showed

[jira] [Updated] (AMBARI-14390) Several properties showed up as blank after EU from HDP 2.1 to HDP 2.3

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-14390:
-
Description: 
*Steps:*
With Ambari 2.2.0, setup HDP 2.1 cluster (non HA, unsecure) with following 
services: hbase,pig,slider,hive,oozie,sqoop,flume,falcon,storm
Did Express Upgrade from HDP 2.1 to 2.3.4 and let it finish
Observe the configs of various services

*Result:*
Observed that the values of several properties showed up as blank and required 
(mostly security related). Here is the list:

h3. HDFS:
* hdfs_principal_name (hadoop-env, value is null, remove if not kerberized)
* hdfs_user_keytab (hadoop-env, value is null, remove if not kerberized)
* dfs.namenode.inode.attributes.provider.class (hdfs-site, value is null, set 
to "org.apache.ranger.authorization.hadoop.RangerHdfsAuthorizer" if Ranger is 
present, which it is not in HDP 2.1)

h3. YARN:
* yarn.authorization-provider (yarn-site, value is null, set to 
"org.apache.ranger.authorization.yarn.authorizer.RangerYarnAuthorizer" if 
Ranger is present, which it is not in HDP 2.1)

h3. Tez:
* tez.tez-ui.history-url.base (also tracked by BUG-49613, tez-site, value is 
null, set to 
'{0}://{1}:{2}/#/main/views/TEZ/{3}/TEZ_CLUSTER_INSTANCE'.format(server_protocol,
 server_host, server_port, latest_tez_jar_version) by Stack Advisor)

h3. HBase:
* hbase_principal_name (hbase-env, value is null, remove if not kerberized)
* hbase_user_keytab (hbase-env, value is null, remove if not kerberized)

h3. ZK:
* zookeeper_keytab_path (zookeeper-env, value is null, remove if not kerberized)
* zookeeper_principal_name (zookeeper-env, value is null, remove if not 
kerberized)

h3. Storm:
* nimbus_keytab  (storm-env, value is null, remove if not kerberized)
* nimbus_principal_name (storm-env, value is null, remove if not kerberized)
* storm_keytab (storm-env, value is null, remove if not kerberized)
* storm_principal_name (storm-env, value is null, remove if not kerberized)
* storm_ui_keytab (storm-env, value is null, remove if not kerberized)
* storm_ui_principal_name (storm-env, value is null, remove if not kerberized)
* nimbus.authorizer (storm-site, need help from Storm team on what to set this 
to since it depends on whether kerberos is enabled and Ranger is present)

Attached few screenshots

We may have more such issues for properties of services other than the ones 
with which the cluster was created at 2.1; so while fixing the issue, please 
ensure that all services are taken care of

  was:
*Steps:*
With Ambari 2.2.0, setup HDP 2.1 cluster (non HA, unsecure) with following 
services: hbase,pig,slider,hive,oozie,sqoop,flume,falcon,storm
Did Express Upgrade from HDP 2.1 to 2.3.4 and let it finish
Observe the configs of various services

*Result:*
Observed that the values of several properties showed up as blank and required 
(mostly security related). Here is the list:

HDFS: hdfs_principal_name, hdfs_user_keytab, 
dfs.namenode.inode.attributes.provider.class
YARN: yarn.authorization-provider
Tez: tez.tez-ui.history-url.base (also tracked by BUG-49613)
HBase: hbase_principal_name, hbase_user_keytab
ZK: zookeeper_keytab_path, zookeeper_principal_name
Storm: nimbus_keytab, nimbus_principal_name, storm_keytab, 
storm_principal_name, storm_ui_keytab, storm_ui_principal_name, 
nimbus.authorizer

Attached few screenshots

We may have more such issues for properties of services other than the ones 
with which the cluster was created at 2.1; so while fixing the issue, please 
ensure that all services are taken care of.


> Several properties showed up as blank after EU from HDP 2.1 to HDP 2.3
> --
>
> Key: AMBARI-14390
> URL: https://issues.apache.org/jira/browse/AMBARI-14390
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.2.1
>
> Attachments: AMBARI-14390_1.png, AMBARI-14390_2.png, 
> AMBARI-14390_3.png
>
>
> *Steps:*
> With Ambari 2.2.0, setup HDP 2.1 cluster (non HA, unsecure) with following 
> services: hbase,pig,slider,hive,oozie,sqoop,flume,falcon,storm
> Did Express Upgrade from HDP 2.1 to 2.3.4 and let it finish
> Observe the configs of various services
> *Result:*
> Observed that the values of several properties showed up as blank and 
> required (mostly security related). Here is the list:
> h3. HDFS:
> * hdfs_principal_name (hadoop-env, value is null, remove if not kerberized)
> * hdfs_user_keytab (hadoop-env, value is null, remove if not kerberized)
> * dfs.namenode.inode.attributes.provider.class (hdfs-site, value is null, set 
> to "org.apache.ranger.authorization.hadoop.RangerHdfsAuthorizer" if Ranger is 
> present, which it is not in HDP 2.1)
> h3. YA

[jira] [Updated] (AMBARI-12686) [RM HA] YARN service shows RED when one of RM goes down but the active RM works fine

[Vishal Ghugare (JIRA)]

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

Vishal Ghugare updated AMBARI-12686:

Attachment: AMBARI-12686_trunk.patch

Patch to fix YARN Service status [RM HA].

> [RM HA] YARN service shows RED when one of RM goes down but the active RM 
> works fine
> 
>
> Key: AMBARI-12686
> URL: https://issues.apache.org/jira/browse/AMBARI-12686
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.0
>Reporter: Weiwei Yang
>Assignee: Vishal Ghugare
>Priority: Critical
> Attachments: 1RM_DOWN.jpg, AMBARI-12686_trunk.patch
>
>
> In a RM HA setup, YARN could work ever there is only 1 RM available, I would 
> expect the service status for YARN is yellow or green(with alerts) from UI 
> instead of red.



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

[jira] [Updated] (AMBARI-12570) Cluster creates stuck at 9x% (deadlock sql exception)

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-12570:
---
Fix Version/s: (was: 2.3.0)
   2.1.1

> Cluster creates stuck at 9x% (deadlock sql exception)
> -
>
> Key: AMBARI-12570
> URL: https://issues.apache.org/jira/browse/AMBARI-12570
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.1.1
>
> Attachments: AMBARI-12570.patch, AMBARI-12570.patch.1
>
>
> Similar to AMBARI-12526, Ambari installation via a blueprint on SQL Azure 
> gets stuck somewhere between 90% and 100% because of a SQL Database deadlock. 
> This is always between {{hostcomponentstate.current_state}} and 
> {{hostcomponentstate.version}}. 
> {code}
> Rollback reason: 
> Local Exception Stack: 
> Exception [EclipseLink-4002] (Eclipse Persistence Services - 
> 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: com.microsoft.sqlserver.jdbc.SQLServerException: 
> Transaction (Process ID 62) was deadlocked on lock resources with another 
> process and has been chosen as the deadlock victim. Rerun the transaction.
> Error Code: 1205
> Call: UPDATE hostcomponentstate SET current_state = ? WHERE 
> component_name = ?) AND (host_id = ?)) AND (cluster_id = ?)) AND 
> (service_name = ?))
>   bind => [5 parameters bound]
>   at 
> org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:331)
>   at 
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:900)
>   at 
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeNoSelect(DatabaseAccessor.java:962)
>   at 
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:631)
>   at 
> org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatch(ParameterizedSQLBatchWritingMechanism.java:149)
>   at 
> org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatchedStatements(ParameterizedSQLBatchWritingMechanism.java:134)
>   at 
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.writesCompleted(DatabaseAccessor.java:1836)
>   at 
> org.eclipse.persistence.internal.sessions.AbstractSession.writesCompleted(AbstractSession.java:4244)
>   at 
> org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.writesCompleted(UnitOfWorkImpl.java:5594)
>   at 
> org.eclipse.persistence.internal.sessions.RepeatableWriteUnitOfWork.writeChanges(RepeatableWriteUnitOfWork.java:453)
>   at 
> org.eclipse.persistence.internal.jpa.EntityManagerImpl.flush(EntityManagerImpl.java:863)
>   at 
> org.eclipse.persistence.internal.jpa.QueryImpl.performPreQueryFlush(QueryImpl.java:963)
>   at 
> org.eclipse.persistence.internal.jpa.QueryImpl.executeReadQuery(QueryImpl.java:207)
>   at 
> org.eclipse.persistence.internal.jpa.QueryImpl.getSingleResult(QueryImpl.java:517)
>   at 
> org.eclipse.persistence.internal.jpa.EJBQueryImpl.getSingleResult(EJBQueryImpl.java:400)
>   at org.apache.ambari.server.orm.dao.DaoUtils.selectOne(DaoUtils.java:80)
>   at org.apache.ambari.server.orm.dao.StackDAO.find(StackDAO.java:93)
>   at 
> org.apache.ambari.server.orm.AmbariLocalSessionInterceptor.invoke(AmbariLocalSessionInterceptor.java:53)
>   at 
> org.apache.ambari.server.state.svccomphost.ServiceComponentHostImpl.setStackVersion(ServiceComponentHostImpl.java:1058)
>   at 
> org.apache.ambari.server.state.svccomphost.ServiceComponentHostImpl$ServiceComponentHostOpStartedTransition.transition(ServiceComponentHostImpl.java:628)
>   at 
> org.apache.ambari.server.state.svccomphost.ServiceComponentHostImpl$ServiceComponentHostOpStartedTransition.transition(ServiceComponentHostImpl.java:610)
>   at 
> org.apache.ambari.server.state.fsm.StateMachineFactory$SingleInternalArc.doTransition(StateMachineFactory.java:354)
>   at 
> org.apache.ambari.server.state.fsm.StateMachineFactory.doTransition(StateMachineFactory.java:294)
>   at 
> org.apache.ambari.server.state.fsm.StateMachineFactory.access$300(StateMachineFactory.java:39)
>   at 
> org.apache.ambari.server.state.fsm.StateMachineFactory$InternalStateMachine.doTransition(StateMachineFactory.java:440)
>   at 
> org.apache.ambari.server.state.svccomphost.ServiceComponentHostImpl.handleEvent(ServiceComponentHostImpl.java:901)
>   at 
> org.apache.ambari.server.state.cluster.ClusterImpl.processServiceComponentHostEvents(ClusterImpl.java:2508)
>   at 
> org.apache.ambari.serve

[jira] [Updated] (AMBARI-14390) Several properties showed up as blank after EU from HDP 2.1 to HDP 2.3

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-14390:
-
Fix Version/s: (was: 2.2.0)
   2.2.1

> Several properties showed up as blank after EU from HDP 2.1 to HDP 2.3
> --
>
> Key: AMBARI-14390
> URL: https://issues.apache.org/jira/browse/AMBARI-14390
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.2.1
>
> Attachments: AMBARI-14390_1.png, AMBARI-14390_2.png, 
> AMBARI-14390_3.png
>
>
> *Steps:*
> With Ambari 2.2.0, setup HDP 2.1 cluster (non HA, unsecure) with following 
> services: hbase,pig,slider,hive,oozie,sqoop,flume,falcon,storm
> Did Express Upgrade from HDP 2.1 to 2.3.4 and let it finish
> Observe the configs of various services
> *Result:*
> Observed that the values of several properties showed up as blank and 
> required (mostly security related). Here is the list:
> HDFS: hdfs_principal_name, hdfs_user_keytab, 
> dfs.namenode.inode.attributes.provider.class
> YARN: yarn.authorization-provider
> Tez: tez.tez-ui.history-url.base (also tracked by BUG-49613)
> HBase: hbase_principal_name, hbase_user_keytab
> ZK: zookeeper_keytab_path, zookeeper_principal_name
> Storm: nimbus_keytab, nimbus_principal_name, storm_keytab, 
> storm_principal_name, storm_ui_keytab, storm_ui_principal_name, 
> nimbus.authorizer
> Attached few screenshots
> We may have more such issues for properties of services other than the ones 
> with which the cluster was created at 2.1; so while fixing the issue, please 
> ensure that all services are taken care of.



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

[jira] [Updated] (AMBARI-14389) tez view disappeared after upgrading from ambari 2.1.2 to 2.2.2.0

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-14389:
-
Fix Version/s: (was: 2.2.0)
   2.2.1

> tez view disappeared after upgrading from ambari 2.1.2 to 2.2.2.0
> -
>
> Key: AMBARI-14389
> URL: https://issues.apache.org/jira/browse/AMBARI-14389
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Alejandro Fernandez
> Fix For: 2.2.1
>
>
> STR:
> * Install ambari 2.1.2 with tez view installed.
> * Upgrade Ambari to 2.2.0.0
> Tez view is no longer present, all of the other views are present.
> Tez is failing to come up due to a missing property,
> {code:java}
> 10 Dec 2015 00:37:09,789 ERROR [qtp-ambari-client-8651] ProxyHelper:68 - 
> Cannot access the url: 
> http://pre-prod-poc-10.novalocal:8188/ws/v1/timeline/TEZ_VERTEX_ID?limit=9007199254740991&primaryFilter=TEZ_DAG_ID:dag_1449704814067_0017_1&_=1449707810538&;
> java.net.SocketTimeoutException: Read timed out
>   at java.net.SocketInputStream.socketRead0(Native Method)
>   at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
>   at java.net.SocketInputStream.read(SocketInputStream.java:170)
>   at java.net.SocketInputStream.read(SocketInputStream.java:141)
>   at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
>   at java.io.BufferedInputStream.read1(BufferedInputStream.java:286)
>   at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
>   at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:704)
>   at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647)
>   at 
> sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1535)
>   at 
> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1440)
>   at 
> java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)
>   at 
> org.apache.ambari.server.controller.internal.URLStreamProvider.processURL(URLStreamProvider.java:209)
>   at 
> org.apache.ambari.server.view.ViewURLStreamProvider.getHttpURLConnection(ViewURLStreamProvider.java:239)
>   at 
> org.apache.ambari.server.view.ViewURLStreamProvider.getConnection(ViewURLStreamProvider.java:146)
>   at 
> org.apache.ambari.server.view.ViewURLStreamProvider.getConnectionAs(ViewURLStreamProvider.java:163)
>   at 
> org.apache.ambari.server.view.ViewURLStreamProvider.getConnectionAsCurrent(ViewURLStreamProvider.java:180)
>   at 
> org.apache.ambari.view.tez.utils.ProxyHelper.getResponse(ProxyHelper.java:55)
>   at 
> org.apache.ambari.view.tez.rest.BaseProxyResource.getData(BaseProxyResource.java:55)
>   at sun.reflect.GeneratedMethodAccessor1465.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
> {code}
> The manual upgrade catalogs (2.1->2.3, and 2.2->2.3), had this,
> {code}
>   "tez.tez-ui.history-url.base": {
> "value": "{TEZ_HISTORY_URL_BASE}",
> "template": "yes"
>   },
> {code}
> That property was introduced in HDP 2.2, so any EU/RUs at that version or 
> higher are ok.
> The default value in tez-site.xml is empty since stack advisor is the one to 
> populate a value, hence why EU from 2.1->2.3 isn't giving it a value.
> *This will require changes to the config pack.*



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

[jira] [Created] (AMBARI-14391) Add a test to verify Role Based Access Control for a non-admin user

[Nahappan Somasundaram (JIRA)]

Nahappan Somasundaram created AMBARI-14391:
--

 Summary: Add a test to verify Role Based Access Control for a 
non-admin user
 Key: AMBARI-14391
 URL: https://issues.apache.org/jira/browse/AMBARI-14391
 Project: Ambari
  Issue Type: Sub-task
  Components: ambari-server
Affects Versions: 2.3.0
Reporter: Nahappan Somasundaram
Assignee: Nahappan Somasundaram
 Fix For: 2.3.0


With the new RBAC feature, users with privilege levels can be added. Write a 
new test to add a non-admin user and try to perform a task that is not 
authorized for that user.



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

[jira] [Commented] (AMBARI-14381) Role-Based Access Control: UX and Bugs

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14381:
-

FAILURE: Integrated in Ambari-trunk-Commit #4045 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4045/])
AMBARI-14381. Role-Based Access Control: UX and Bugs (rzang) (rzang: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a66fc1b2fe915430a6564af9a61c4ffbf4c6d07b])
* ambari-web/app/controllers/global/user_settings_controller.js
* ambari-web/app/messages.js
* ambari-admin/src/main/resources/ui/admin-web/app/views/leftNavbar.html
* 
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/users/UsersShowCtrl.js
* ambari-admin/src/main/resources/ui/admin-web/app/views/groups/edit.html
* 
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/clusters/ClustersManageAccessCtrl.js
* ambari-admin/src/main/resources/ui/admin-web/app/views/users/show.html
* 
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/clusters/UserAccessListCtrl.js
* ambari-web/app/templates/common/settings.hbs
* ambari-admin/src/main/resources/ui/admin-web/app/views/users/list.html
* 
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/groups/GroupsEditCtrl.js
* 
ambari-admin/src/main/resources/ui/admin-web/app/views/clusters/userAccessList.html


> Role-Based Access Control: UX and Bugs
> --
>
> Key: AMBARI-14381
> URL: https://issues.apache.org/jira/browse/AMBARI-14381
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin, ambari-web
>Affects Versions: 2.3.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.3.0
>
> Attachments: AMBARI-14381.patch
>
>
> Role-Based Access Control: UX and Bugs



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

[jira] [Commented] (AMBARI-14293) While doing express upgrade multiple Clients and Services Failed to start

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14293:
-

FAILURE: Integrated in Ambari-trunk-Commit #4045 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4045/])
AMBARI-14293. While doing express upgrade multiple Clients and Services 
(dlysnichenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d154f451c4164036e72421eae8a53282715503d3])
* ambari-server/src/main/resources/custom_actions/scripts/install_packages.py
* 
ambari-common/src/main/python/resource_management/libraries/functions/conf_select.py


> While doing express upgrade multiple Clients and Services Failed to start
> -
>
> Key: AMBARI-14293
> URL: https://issues.apache.org/jira/browse/AMBARI-14293
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.2.0
>
> Attachments: AMBARI-14293.patch
>
>
> During nightly run over Centos7 express upgrade test cases failed because of 
> TEZ Client issue.
> Restart of Tez Client failed after upgrade because of conf file missing.
> After logging on box I found the soft links /etc/tez/conf & 
> /usr/hdp/current/tez-client/conf pointing in loop to each other.
> [root@os-r7-test-2 tez-client]# ls -l /usr/hdp/2.3.4.0-3426/tez/conf
> lrwxrwxrwx. 1 root root 13 Dec  8 05:05 /usr/hdp/2.3.4.0-3426/tez/conf -> 
> /etc/tez/conf
> [root@os-r7-test-2 tez-client]# ls -l /etc/tez/conf
> lrwxrwxrwx. 1 root root 32 Dec  8 02:23 /etc/tez/conf -> 
> /usr/hdp/current/tez-client/conf
> [root@os-r7-test-2 tez-client]# ls -l /usr/hdp/current/tez-client/conf
> lrwxrwxrwx. 1 root root 13 Dec  8 05:05 /usr/hdp/current/tez-client/conf -> 
> /etc/tez/conf
> [root@os-r7-test-2 tez-client]#
> Error on UI
> {code}
> Traceback (most recent call last):
> File 
> "/var/lib/ambari-agent/cache/common-services/TEZ/0.4.0.2.1/package/scripts/tez_client.py",
>  line 104, in 
> TezClient().execute()
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 217, in execute
> method(env)
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 486, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File 
> "/var/lib/ambari-agent/cache/common-services/TEZ/0.4.0.2.1/package/scripts/tez_client.py",
>  line 59, in pre_upgrade_restart
> conf_select.select(params.stack_name, "tez", params.version)
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/conf_select.py",
>  line 247, in select
> shell.checked_call(get_cmd("set-conf-dir", package, version), 
> logoutput=False, quiet=False, sudo=True)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 70, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 92, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 291, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'conf-select 
> set-conf-dir --package tez --stack-version 2.3.4.0-3426 --conf-version 0' 
> returned 1. /usr/hdp/2.3.4.0-3426/tez/conf does not exist
> {code}
> Observed this issue for other components too AFTER 'Ignore and Proceed' the 
> Tez client error
> The error was seen for following components:
> Pig client, Hive server, Metastore, Hive client, Spark service, spark client. 
> See attached file for output



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

[jira] [Commented] (AMBARI-14274) RU: Better text message about backup Oozie database

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14274:
-

FAILURE: Integrated in Ambari-trunk-Commit #4045 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4045/])
AMBARI-14274: RU: Better text message about backup Oozie database (dili) (dili: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a196eed8030bea498b437ba923b461db031bf096])
* 
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.2.xml
* ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.2.xml
* ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml
* 
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.3.xml
* 
ambari-server/src/main/resources/stacks/HDP/2.1/upgrades/nonrolling-upgrade-2.3.xml
* ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.3.xml
* 
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.3.xml
* 
ambari-server/src/test/resources/stacks/HDP/2.1.1/upgrades/upgrade_nonrolling_new_stack.xml


> RU: Better text message about backup Oozie database
> ---
>
> Key: AMBARI-14274
> URL: https://issues.apache.org/jira/browse/AMBARI-14274
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Di Li
>Assignee: Di Li
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-14274.patch
>
>
> Oozie DB may be on a different node than the Oozie node. The text currently 
> reads "Before continuing, please backup the Oozie Server database on 
> .mydomain.com" 
> The text is only valid when Oozie db is on the same node as Oozie server.
> The proposal here is to change the text to "Before continuing, please backup 
> the Oozie Server database referenced by the Oozie server located on 
> xxx.mydomain.com."



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

[jira] [Updated] (AMBARI-13643) Warn if Xmn size is oversubscribed in AMS HBase master and region server config

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-13643:
-
Fix Version/s: 2.2.0

> Warn if Xmn size is oversubscribed in AMS HBase master and region server 
> config
> ---
>
> Key: AMBARI-13643
> URL: https://issues.apache.org/jira/browse/AMBARI-13643
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.1.2
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.2.0
>
> Attachments: AMBARI-13642-3-2.patch
>
>
> Problem/Bug
> While setting the AMS configuration, the user can set any unbounded value for 
> the Xmn settings. This might lead to undesirable outcomes from the JVM.
> Fix
> Provide validation of Xmn settings based on AMS mode.
> If AMS is operating in embedded mode
>   regionserver_xmn  12-20% of ( hbase_master_heapsize + 
> hbase_regionserver_heapsize)
> If AMS is operating in distributed distributed mode
>   hbase_master_xmn  12 - 20% of hbase_master_heapsize
>   regionserver_xmn  12 - 20% of hbase_regionserver_heapsize



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

[jira] [Updated] (AMBARI-13642) Kafka fails to start unless AMS is installed

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-13642:
-
Fix Version/s: 2.2.0

> Kafka fails to start unless AMS is installed
> 
>
> Key: AMBARI-13642
> URL: https://issues.apache.org/jira/browse/AMBARI-13642
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.1.2
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.2.0
>
> Attachments: AMBARI-13642-3-2.patch
>
>
> Problem
> When Kafka is installed on a cluster where AMS was never installed, the 
> installation fails.
> Bug
> The kafka.metrics.reporter property had a default value pointing to a 
> Reporter class provided by AMS.
> Fix
> Change default value of kafka.metrics.reporter to empty string. Change the 
> property to the appropriate AMS Kafka reporter class dynamically though stack 
> recommendations, if AMS is installed.



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

Re: Review Request 41397: AMBARI-14383 Add support for Ranger TagSync process as a component under RANGER

[Alejandro Fernandez]

> On Dec. 15, 2015, 6:43 p.m., Alejandro Fernandez wrote:
> > ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/ranger_tagsync.py,
> >  line 72
> > 
> >
> > Is this already supported by hdp-select?

Actually, we need to be careful with this.
If they user is on HDP 2.3 without this new component, we need to ensure that 
installing bits doesn't add it. Otherwise, when we call conf-select for all 
packages found in /usr/hdp/[new_version] it may attempt to conf-select a 
component that doesn't exist yet.


- Alejandro


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


On Dec. 15, 2015, 4:46 p.m., Gautam Borad wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/41397/
> ---
> 
> (Updated Dec. 15, 2015, 4:46 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, Madhan 
> Neethiraj, Mahadev Konar, Nate Cole, Sumit Mohanty, Selvamohan Neethiraj, and 
> Velmurugan Periasamy.
> 
> 
> Bugs: AMBARI-14383
> https://issues.apache.org/jira/browse/AMBARI-14383
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Ranger TagSync is a separate component that will be responsible for 
> synchronizing the tags from Apache Atlas into Apache Ranger (db).
> 
> Add Ranger TagSync component under existing RANGER service.
> The component will be a master component
> Ability to start/stop the component independently of Ranger Admin.
> Ability to install the component on any host of the cluster
> Support should be available only from HDP 2.3
> 
> 
> Diffs
> -
> 
>   
> ambari-common/src/main/python/resource_management/libraries/functions/conf_select.py
>  fd83c53 
>   
> ambari-common/src/main/python/resource_management/libraries/functions/hdp_select.py
>  5628f33 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/params.py
>  b6e5ee9 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/ranger_service.py
>  4f711c3 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/ranger_tagsync.py
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/setup_ranger_xml.py
>  8de0d80 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/services/RANGER/configuration/ranger-tagsync-site.xml
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/services/RANGER/metainfo.xml 
> 2fb8a9a 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.3.xml
>  cf3afbe 
>   ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml 
> cce20be 
> 
> Diff: https://reviews.apache.org/r/41397/diff/
> 
> 
> Testing
> ---
> 
> Installed Ranger on centos 6 and enabled Ranger TagSync module.
> 
> Tested minor upgrade from 2.3.x to 2.3.xx
> 
> 
> Thanks,
> 
> Gautam Borad
> 
>

Re: Review Request 41047: AMBARI-11268: Quick links for custom services

[Yusaku Sako]

> On Dec. 15, 2015, 8:23 p.m., Yusaku Sako wrote:
> > Hi Di, can you upload the latest patch to the JIRA, so that it goes thru 
> > the Hadoop QA testing?  Thanks.
> 
> Di Li wrote:
> hello Yusaku,
> 
> yes, just added the latest patch to the JIRA.
> 
> Thanks.

Great.  Thanks Di.


- Yusaku


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


On Dec. 15, 2015, 5:29 p.m., Di Li wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/41047/
> ---
> 
> (Updated Dec. 15, 2015, 5:29 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, Richard Zang, 
> and Yusaku Sako.
> 
> 
> Bugs: AMBARI-11268
> https://issues.apache.org/jira/browse/AMBARI-11268
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> The existing version of the Ambari (2.0) does not have a declarative way to 
> add "Quick Links" for the custom services. Currently, to add a "Quick Links" 
> dropdown one has to do add quick links definitions to the UI code, making it 
> very difficult for custom services to have quick links.
> 
> The proposed changes here introduced a way to allow services to 
> define/inherite/update quick links via quicklinks.json
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/api/resources/ResourceInstanceFactoryImpl.java
>  27609e7 
>   
> ambari-server/src/main/java/org/apache/ambari/server/api/resources/StackServiceResourceDefinition.java
>  45302ff 
>   
> ambari-server/src/main/java/org/apache/ambari/server/api/services/AmbariMetaInfo.java
>  e35e7ac 
>   
> ambari-server/src/main/java/org/apache/ambari/server/api/services/StacksService.java
>  76397fb 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AbstractControllerResourceProvider.java
>  d47d8d3 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/QuickLinkArtifactResourceProvider.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/spi/Resource.java
>  55816a3 
>   
> ambari-server/src/main/java/org/apache/ambari/server/stack/QuickLinksConfigurationModule.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/stack/ServiceModule.java 
> c2a2a0c 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/QuickLinksConfigurationInfo.java
>  PRE-CREATION 
>   ambari-server/src/main/java/org/apache/ambari/server/state/ServiceInfo.java 
> a58cda3 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/quicklinks/Check.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/quicklinks/Link.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/quicklinks/Port.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/quicklinks/Protocol.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/quicklinks/QuickLinks.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/quicklinks/QuickLinksConfiguration.java
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/metainfo.xml
>  ae58b5c 
>   
> ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/quicklinks/quicklinks.json
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/metainfo.xml 
> 515f385 
>   
> ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/quicklinks/quicklinks.json
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDP/2.0.6/services/OOZIE/metainfo.xml 
> dad6dc1 
>   
> ambari-server/src/main/resources/stacks/HDP/2.0.6/services/OOZIE/quicklinks/quicklinks.json
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/RANGER/metainfo.xml 
> 4d1b305 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/RANGER/quicklinks/quicklinks.json
>  PRE-CREATION 
>   ambari-server/src/main/resources/stacks/HDP/2.2/services/SPARK/metainfo.xml 
> db11d05 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/SPARK/quicklinks/quicklinks.json
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/services/ACCUMULO/metainfo.xml
>  352341b 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/services/ACCUMULO/quicklinks/quicklinks.json
>  PRE-CREATION 
>   ambari-server/src/main/resources/stacks/HDP/2.3/services/ATLAS/metainfo.xml 
> fee10d3 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/services/ATLAS/quicklinks/quicklinks.json
>  PRE-CREATION 
>   ambari-server/src/main/resources/stacks/HDP/2.3/services/HBASE/met

[jira] [Commented] (AMBARI-14388) Revert AMBARI-14249 and ignore offending tests

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14388:
-

ABORTED: Integrated in Ambari-trunk-Commit #4044 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4044/])
AMBARI-14388 Revert AMBARI-14249 and ignore offending tests (dsen) (dsen: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=5024b2b2eabe8cc0ed541b07cbbb84869e4507c5])
* 
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/RequestDAOTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/AlertDefinitionDAOTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/AlertDispatchDAOTest.java


> Revert AMBARI-14249 and ignore offending tests
> --
>
> Key: AMBARI-14388
> URL: https://issues.apache.org/jira/browse/AMBARI-14388
> Project: Ambari
>  Issue Type: Bug
>  Components: test
>Affects Versions: 2.2.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.2.0
>
> Attachments: AMBARI-14388.patch
>
>
> Revert AMBARI-14249 and ignore offending tests



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

[jira] [Commented] (AMBARI-14249) Entity removal done trough the EntityManager (AlertHistory, AlertNotice)

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14249:
-

ABORTED: Integrated in Ambari-trunk-Commit #4044 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4044/])
Revert "AMBARI-14249. Failing unit tests / Entity removal using the (dsen: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=96e8ba4c6dcf65f42f3de8087ff527f54c04])
* 
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/AlertDispatchDAOTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/AlertDefinitionDAOTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/AlertNoticeEntity.java
* 
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/AlertsDAOTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/AlertHistoryEntity.java
* 
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/AlertDispatchDAO.java
* 
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/RequestDAOTest.java
* ambari-server/src/main/java/org/apache/ambari/server/orm/dao/AlertsDAO.java
AMBARI-14388 Revert AMBARI-14249 and ignore offending tests (dsen) (dsen: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=5024b2b2eabe8cc0ed541b07cbbb84869e4507c5])
* 
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/RequestDAOTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/AlertDefinitionDAOTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/AlertDispatchDAOTest.java


> Entity removal done trough the EntityManager (AlertHistory, AlertNotice)
> 
>
> Key: AMBARI-14249
> URL: https://issues.apache.org/jira/browse/AMBARI-14249
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Laszlo Puskas
>Assignee: Laszlo Puskas
>Priority: Critical
>  Labels: patch
> Fix For: 2.2.0
>
> Attachments: AMBARI-14249.v1.patch, AMBARI-14249.v2.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Removal of entities need to be done through the EntityManager in order for 
> the shared cache to remain consistent.



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

[jira] [Commented] (AMBARI-14293) While doing express upgrade multiple Clients and Services Failed to start

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14293:
-

FAILURE: Integrated in Ambari-branch-2.2 #77 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/77/])
AMBARI-14293. While doing express upgrade multiple Clients and Services 
(dlysnichenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=dddfeb33cc0f71d5a9ecfad44ce00cd26feebe75])
* 
ambari-common/src/main/python/resource_management/libraries/functions/conf_select.py
* ambari-server/src/main/resources/custom_actions/scripts/install_packages.py


> While doing express upgrade multiple Clients and Services Failed to start
> -
>
> Key: AMBARI-14293
> URL: https://issues.apache.org/jira/browse/AMBARI-14293
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.2.0
>
> Attachments: AMBARI-14293.patch
>
>
> During nightly run over Centos7 express upgrade test cases failed because of 
> TEZ Client issue.
> Restart of Tez Client failed after upgrade because of conf file missing.
> After logging on box I found the soft links /etc/tez/conf & 
> /usr/hdp/current/tez-client/conf pointing in loop to each other.
> [root@os-r7-test-2 tez-client]# ls -l /usr/hdp/2.3.4.0-3426/tez/conf
> lrwxrwxrwx. 1 root root 13 Dec  8 05:05 /usr/hdp/2.3.4.0-3426/tez/conf -> 
> /etc/tez/conf
> [root@os-r7-test-2 tez-client]# ls -l /etc/tez/conf
> lrwxrwxrwx. 1 root root 32 Dec  8 02:23 /etc/tez/conf -> 
> /usr/hdp/current/tez-client/conf
> [root@os-r7-test-2 tez-client]# ls -l /usr/hdp/current/tez-client/conf
> lrwxrwxrwx. 1 root root 13 Dec  8 05:05 /usr/hdp/current/tez-client/conf -> 
> /etc/tez/conf
> [root@os-r7-test-2 tez-client]#
> Error on UI
> {code}
> Traceback (most recent call last):
> File 
> "/var/lib/ambari-agent/cache/common-services/TEZ/0.4.0.2.1/package/scripts/tez_client.py",
>  line 104, in 
> TezClient().execute()
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 217, in execute
> method(env)
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 486, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File 
> "/var/lib/ambari-agent/cache/common-services/TEZ/0.4.0.2.1/package/scripts/tez_client.py",
>  line 59, in pre_upgrade_restart
> conf_select.select(params.stack_name, "tez", params.version)
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/conf_select.py",
>  line 247, in select
> shell.checked_call(get_cmd("set-conf-dir", package, version), 
> logoutput=False, quiet=False, sudo=True)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 70, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 92, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 291, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'conf-select 
> set-conf-dir --package tez --stack-version 2.3.4.0-3426 --conf-version 0' 
> returned 1. /usr/hdp/2.3.4.0-3426/tez/conf does not exist
> {code}
> Observed this issue for other components too AFTER 'Ignore and Proceed' the 
> Tez client error
> The error was seen for following components:
> Pig client, Hive server, Metastore, Hive client, Spark service, spark client. 
> See attached file for output



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

[jira] [Commented] (AMBARI-14249) Entity removal done trough the EntityManager (AlertHistory, AlertNotice)

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14249:
-

FAILURE: Integrated in Ambari-branch-2.2 #77 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/77/])
Revert "AMBARI-14249. Failing unit tests / Entity removal using the (dsen: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=bb4fb9ed6e03ca13b1b55102e8585cba666d3acf])
* 
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/AlertDefinitionDAOTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/AlertHistoryEntity.java
* 
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/AlertNoticeEntity.java
* 
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/AlertDispatchDAO.java
* 
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/AlertDispatchDAOTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/RequestDAOTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/AlertsDAOTest.java
* ambari-server/src/main/java/org/apache/ambari/server/orm/dao/AlertsDAO.java
AMBARI-14388 Revert AMBARI-14249 and ignore offending tests (dsen) (dsen: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e5ce144a0a32f51e12715ddb8bd5803fd1d690da])
* 
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/AlertDispatchDAOTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/AlertDefinitionDAOTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/RequestDAOTest.java


> Entity removal done trough the EntityManager (AlertHistory, AlertNotice)
> 
>
> Key: AMBARI-14249
> URL: https://issues.apache.org/jira/browse/AMBARI-14249
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Laszlo Puskas
>Assignee: Laszlo Puskas
>Priority: Critical
>  Labels: patch
> Fix For: 2.2.0
>
> Attachments: AMBARI-14249.v1.patch, AMBARI-14249.v2.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Removal of entities need to be done through the EntityManager in order for 
> the shared cache to remain consistent.



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

[jira] [Commented] (AMBARI-14388) Revert AMBARI-14249 and ignore offending tests

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14388:
-

FAILURE: Integrated in Ambari-branch-2.2 #77 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/77/])
AMBARI-14388 Revert AMBARI-14249 and ignore offending tests (dsen) (dsen: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e5ce144a0a32f51e12715ddb8bd5803fd1d690da])
* 
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/AlertDispatchDAOTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/AlertDefinitionDAOTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/RequestDAOTest.java


> Revert AMBARI-14249 and ignore offending tests
> --
>
> Key: AMBARI-14388
> URL: https://issues.apache.org/jira/browse/AMBARI-14388
> Project: Ambari
>  Issue Type: Bug
>  Components: test
>Affects Versions: 2.2.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.2.0
>
> Attachments: AMBARI-14388.patch
>
>
> Revert AMBARI-14249 and ignore offending tests



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

Re: Review Request 41358: Enforce granular role-based access control for alert functions

[Jonathan Hurley]

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



ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertHistoryResourceProvider.java
 (line 174)


Consider that you can have 100,000 historical alerts in the system. Do you 
really want to iterate over all of them every time? That's a lot of entity 
checking. Meanwhile, alert history is read-only, so you should only have to 
check this once outside of the loop, no?



ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertNoticeResourceProvider.java
 (line 164)


Consider that you can have 10,000 current alerts in the system. Do you 
really want to iterate over all of them every time? That's a lot of entity 
checking. Meanwhile, alert notices are read-only, so you should only have to 
check this once outside of the loop, no?



ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertTargetResourceProvider.java
 (lines 131 - 134)


Alert targets are actually not bound to a cluster; they are defined on the 
api/v1/alert_target endpoint. As a result, should this be a different 
permission?



ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AmbariAuthorizationFilter.java
 (line 75)


Alert targets are their own endpoint, not scoped under a cluster.


- Jonathan Hurley


On Dec. 14, 2015, 1:51 p.m., Robert Levas wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/41358/
> ---
> 
> (Updated Dec. 14, 2015, 1:51 p.m.)
> 
> 
> Review request for Ambari, Jonathan Hurley, Myroslav Papirkovskyy, Nate Cole, 
> and Sid Wagle.
> 
> 
> Bugs: AMBARI-14141
> https://issues.apache.org/jira/browse/AMBARI-14141
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Enforce granular role-based access control for alert functions:
> 
> | Cluster User | Service Operator | Service 
> Administrator | Cluster Operator | Cluster Administrator | Administrator 
> |--|--|---|--|---|---
> 
> View alerts (service)   | (+)  | (+)  | (+)   
> | (+)  | (+)   | (+)
> Enable/disable alerts (service) |  |  | (+)   
> | (+)  | (+)   | (+)
> View alerts (cluster)   | (+)  | (+)  | (+)   
> | (+)  | (+)   | (+)
> Enable/disable alerts (cluster) |  |  |   
> |  | (+)   | (+)
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AbstractControllerResourceProvider.java
>  d47d8d3 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertDefinitionResourceProvider.java
>  bc5f956 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertGroupResourceProvider.java
>  215bc8e 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertHistoryResourceProvider.java
>  89ee69a 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertNoticeResourceProvider.java
>  8f0e526 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertResourceProvider.java
>  4dc4dcf 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertResourceProviderUtils.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertTargetResourceProvider.java
>  a310259 
>   
> ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AmbariAuthorizationFilter.java
>  d817ad7 
>   
> ambari-server/src/main/java/org/apache/ambari/server/security/authorization/RoleAuthorization.java
>  02eb5b4 
>   
> ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog230.java
>  ee2b9b1 
>   ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql 788c2a7 
>   ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql ae560d9 
>   ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql 155a6a7 
>   ambari-server/src/main/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql 
> 4c20767 
>   ambari-server/

[jira] [Commented] (AMBARI-14339) Stack advisor validations for HAWQ

[Newton Alex (JIRA)]

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

Newton Alex commented on AMBARI-14339:
--

The ABORT comment from Hudson is due to some other Ambari install issue. Not 
directly related to the patch. The commit after this has passed 
(https://builds.apache.org/job/Ambari-trunk-Commit/4039/).


> Stack advisor validations for HAWQ
> --
>
> Key: AMBARI-14339
> URL: https://issues.apache.org/jira/browse/AMBARI-14339
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Affects Versions: 2.1.1
>Reporter: Newton Alex
>Assignee: Newton Alex
> Fix For: 2.1.2
>
> Attachments: AMBARI-14339.patch
>
>
> Ensure that stack advisor 
> - recommends a non 5432 port when HAWQ master components are collocated with 
> Ambari Server
> - recommends a non root directory for all the data and temp directories or 
> HAWQ



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

[jira] [Commented] (AMBARI-11670) Width of services menu container is fixed and causes part of longer service names to be rendered outside the frame

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-11670:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/1290/AMBARI-11670.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:red}-1 core tests{color}.  The test build failed in ambari-web 

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

This message is automatically generated.

> Width of services menu container is fixed and causes part of longer service 
> names to be rendered outside the frame
> --
>
> Key: AMBARI-11670
> URL: https://issues.apache.org/jira/browse/AMBARI-11670
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.0
>Reporter: Sangeeta Ravindran
>Assignee: Keta Patel
>Priority: Minor
> Attachments: AMBARI-11670.patch, big_alert_count.png, 
> long_service_name.png, service_name_and_alerts_with_fix.png
>
>
> If a service has a really long name (19 characters or more), part of the 
> service name is rendered outside the frame. Any action icons for e.g. refresh 
> also appear outside the frame.
> The frame width should change dynamically to accommodate a longer service 
> name or the service name should wrap to the next line.



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

[jira] [Commented] (AMBARI-14385) Robust Handling of Ambari properites and DB state.

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-14385:


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

This message is automatically generated.

> Robust Handling of Ambari properites and DB state.
> --
>
> Key: AMBARI-14385
> URL: https://issues.apache.org/jira/browse/AMBARI-14385
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-14385.patch
>
>
> Robust Handling of Ambari properites and DB state.



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

[ANNOUNCE] Aravindan Vijayan as new Ambari committer

[Siddharth Wagle]

Hi all,


I would like to announce Aravindan as new Ambari committer.


Aravindan has been making valuable contributions to Ambari in the area of 
Ambari Metrics Service.
He has contributed to fixing several Critical Jiras for the upcoming 2.2.0 
release.


Congratulations Aravindan.


- Sid

Re: Review Request 41397: AMBARI-14383 Add support for Ranger TagSync process as a component under RANGER

[Nate Cole]

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


I think until we know that hdp-select and conf-select will support this new 
component, that this component should be marked to not broadcast it's version.


ambari-common/src/main/python/resource_management/libraries/functions/conf_select.py
 (lines 108 - 113)


This will fail if conf-select doesn't support ranger-tagsync (which I 
didn't find on my handful of deployments).



ambari-common/src/main/python/resource_management/libraries/functions/hdp_select.py
 (line 64)


Not in hdp-select



ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/ranger_tagsync.py
 (line 71)


Same as Alejandro's comment - does conf-select support this?


- Nate Cole


On Dec. 15, 2015, 11:46 a.m., Gautam Borad wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/41397/
> ---
> 
> (Updated Dec. 15, 2015, 11:46 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, Madhan 
> Neethiraj, Mahadev Konar, Nate Cole, Sumit Mohanty, Selvamohan Neethiraj, and 
> Velmurugan Periasamy.
> 
> 
> Bugs: AMBARI-14383
> https://issues.apache.org/jira/browse/AMBARI-14383
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Ranger TagSync is a separate component that will be responsible for 
> synchronizing the tags from Apache Atlas into Apache Ranger (db).
> 
> Add Ranger TagSync component under existing RANGER service.
> The component will be a master component
> Ability to start/stop the component independently of Ranger Admin.
> Ability to install the component on any host of the cluster
> Support should be available only from HDP 2.3
> 
> 
> Diffs
> -
> 
>   
> ambari-common/src/main/python/resource_management/libraries/functions/conf_select.py
>  fd83c53 
>   
> ambari-common/src/main/python/resource_management/libraries/functions/hdp_select.py
>  5628f33 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/params.py
>  b6e5ee9 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/ranger_service.py
>  4f711c3 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/ranger_tagsync.py
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/setup_ranger_xml.py
>  8de0d80 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/services/RANGER/configuration/ranger-tagsync-site.xml
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/services/RANGER/metainfo.xml 
> 2fb8a9a 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.3.xml
>  cf3afbe 
>   ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml 
> cce20be 
> 
> Diff: https://reviews.apache.org/r/41397/diff/
> 
> 
> Testing
> ---
> 
> Installed Ranger on centos 6 and enabled Ranger TagSync module.
> 
> Tested minor upgrade from 2.3.x to 2.3.xx
> 
> 
> Thanks,
> 
> Gautam Borad
> 
>

[ANNOUNCE] Di Li as a new committer for Ambari

[Yusaku Sako]

Hi all,

It is my pleasure to announce that Di Li has become a committer for Ambari.

Di has been providing meaningful contributions in areas that tend to get 
overlooked
(usability, getting the details right, pluggability, etc.) in a full-stack 
manner to improve
various aspects of Ambari, including Ambari Agent, Ambari Web, and Ambari 
Server.

Congratulations, Di!

Yusaku

Re: Review Request 41397: AMBARI-14383 Add support for Ranger TagSync process as a component under RANGER

[Jonathan Hurley]

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


This is going to be a problem for Ambari. We don't have knowledge of specific 
stack versions. By adding this to the exist HDP 2.3 stack, it means that we'll 
offer it as an option, regardless of which version of the 2.3 stack you're 
installing. In many cases, this component won't actually be available. 

I don't think we can add new components after a stack has been published. This 
should go into HDP 2.4

- Jonathan Hurley


On Dec. 15, 2015, 11:46 a.m., Gautam Borad wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/41397/
> ---
> 
> (Updated Dec. 15, 2015, 11:46 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, Madhan 
> Neethiraj, Mahadev Konar, Nate Cole, Sumit Mohanty, Selvamohan Neethiraj, and 
> Velmurugan Periasamy.
> 
> 
> Bugs: AMBARI-14383
> https://issues.apache.org/jira/browse/AMBARI-14383
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Ranger TagSync is a separate component that will be responsible for 
> synchronizing the tags from Apache Atlas into Apache Ranger (db).
> 
> Add Ranger TagSync component under existing RANGER service.
> The component will be a master component
> Ability to start/stop the component independently of Ranger Admin.
> Ability to install the component on any host of the cluster
> Support should be available only from HDP 2.3
> 
> 
> Diffs
> -
> 
>   
> ambari-common/src/main/python/resource_management/libraries/functions/conf_select.py
>  fd83c53 
>   
> ambari-common/src/main/python/resource_management/libraries/functions/hdp_select.py
>  5628f33 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/params.py
>  b6e5ee9 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/ranger_service.py
>  4f711c3 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/ranger_tagsync.py
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/setup_ranger_xml.py
>  8de0d80 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/services/RANGER/configuration/ranger-tagsync-site.xml
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/services/RANGER/metainfo.xml 
> 2fb8a9a 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.3.xml
>  cf3afbe 
>   ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml 
> cce20be 
> 
> Diff: https://reviews.apache.org/r/41397/diff/
> 
> 
> Testing
> ---
> 
> Installed Ranger on centos 6 and enabled Ranger TagSync module.
> 
> Tested minor upgrade from 2.3.x to 2.3.xx
> 
> 
> Thanks,
> 
> Gautam Borad
> 
>

Re: Review Request 41047: AMBARI-11268: Quick links for custom services

[Di Li]

> On Dec. 15, 2015, 8:23 p.m., Yusaku Sako wrote:
> > Hi Di, can you upload the latest patch to the JIRA, so that it goes thru 
> > the Hadoop QA testing?  Thanks.

hello Yusaku,

yes, just added the latest patch to the JIRA.

Thanks.


- Di


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


On Dec. 15, 2015, 5:29 p.m., Di Li wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/41047/
> ---
> 
> (Updated Dec. 15, 2015, 5:29 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, Richard Zang, 
> and Yusaku Sako.
> 
> 
> Bugs: AMBARI-11268
> https://issues.apache.org/jira/browse/AMBARI-11268
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> The existing version of the Ambari (2.0) does not have a declarative way to 
> add "Quick Links" for the custom services. Currently, to add a "Quick Links" 
> dropdown one has to do add quick links definitions to the UI code, making it 
> very difficult for custom services to have quick links.
> 
> The proposed changes here introduced a way to allow services to 
> define/inherite/update quick links via quicklinks.json
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/api/resources/ResourceInstanceFactoryImpl.java
>  27609e7 
>   
> ambari-server/src/main/java/org/apache/ambari/server/api/resources/StackServiceResourceDefinition.java
>  45302ff 
>   
> ambari-server/src/main/java/org/apache/ambari/server/api/services/AmbariMetaInfo.java
>  e35e7ac 
>   
> ambari-server/src/main/java/org/apache/ambari/server/api/services/StacksService.java
>  76397fb 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AbstractControllerResourceProvider.java
>  d47d8d3 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/QuickLinkArtifactResourceProvider.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/spi/Resource.java
>  55816a3 
>   
> ambari-server/src/main/java/org/apache/ambari/server/stack/QuickLinksConfigurationModule.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/stack/ServiceModule.java 
> c2a2a0c 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/QuickLinksConfigurationInfo.java
>  PRE-CREATION 
>   ambari-server/src/main/java/org/apache/ambari/server/state/ServiceInfo.java 
> a58cda3 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/quicklinks/Check.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/quicklinks/Link.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/quicklinks/Port.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/quicklinks/Protocol.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/quicklinks/QuickLinks.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/quicklinks/QuickLinksConfiguration.java
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/metainfo.xml
>  ae58b5c 
>   
> ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/quicklinks/quicklinks.json
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/metainfo.xml 
> 515f385 
>   
> ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/quicklinks/quicklinks.json
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDP/2.0.6/services/OOZIE/metainfo.xml 
> dad6dc1 
>   
> ambari-server/src/main/resources/stacks/HDP/2.0.6/services/OOZIE/quicklinks/quicklinks.json
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/RANGER/metainfo.xml 
> 4d1b305 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/RANGER/quicklinks/quicklinks.json
>  PRE-CREATION 
>   ambari-server/src/main/resources/stacks/HDP/2.2/services/SPARK/metainfo.xml 
> db11d05 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/SPARK/quicklinks/quicklinks.json
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/services/ACCUMULO/metainfo.xml
>  352341b 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/services/ACCUMULO/quicklinks/quicklinks.json
>  PRE-CREATION 
>   ambari-server/src/main/resources/stacks/HDP/2.3/services/ATLAS/metainfo.xml 
> fee10d3 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/services/ATLAS/quicklinks/quicklinks.json
>  PRE-CREATION 
>   ambari-server/src/main/resources/stacks/HDP/2.3/services/HBASE/metainfo.xml 
> 90a31f5 
>   
> ambari-server/src/main/resources/stacks/HD

[jira] [Updated] (AMBARI-11268) Quick links for custom services

[Di Li (JIRA)]

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

Di Li updated AMBARI-11268:
---
Attachment: AMBARI-11268_code_refactored.patch

> Quick links for custom services
> ---
>
> Key: AMBARI-11268
> URL: https://issues.apache.org/jira/browse/AMBARI-11268
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: 2.1.0
>Reporter: Dmitry Vasilenko
>Assignee: Di Li
>  Labels: feature_custom_service
> Fix For: 2.3.0
>
> Attachments: AMBARI-11268.patch, AMBARI-11268_code_refactored.patch, 
> Stack Driven Quick Links.pdf
>
>
> The existing version of the Ambari (2.0) does not have a declarative way to 
> add "Quick Links" for the custom services. Currently, to add a "Quick Links" 
> dropdown one has to do the following:
> 1. Extract app.js file from /usr/lib/ambari-server/web/javascripts/app.js.gz 
> to some directory.
> 2. Add  MY_CUSTOM_SERVICE entry to the quickLinks: 
> {noformat}
>  mapQuickLinks: function (finalJson, item){
> if(!(item && item.ServiceInfo)) return;
> var quickLinks = {
>   OOZIE: [19],
>   GANGLIA: [20],
>   STORM: [31],
>   FALCON: [32],
>   RANGER: [33],
>   SPARK: [34],
>   MY_CUSTOM_SERVICE: [35]
> };
> {noformat}
> 3. Add an entry to 
> {noformat}
> App.QuickLinks.FIXTURES = [
>   {
> id: 35,
> label:'My Custom Service Admin UI',
> url:'%@://%@:8090/my_custom_service/admin',
> service_id: 'MY_CUSTOM_SERVICE',
> template:'%@://%@:8090/my_custom_service/admin'
>   },
> {noformat}
> 4. GZip the app.js and upload it to the Ambari server as  
> /usr/lib/ambari-server/web/javascripts/app.js.gz.
> Having a declarative way of adding "Quick Links" on the custom service level 
> will be much more convenient. 



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

Re: Review Request 41047: AMBARI-11268: Quick links for custom services

[Yusaku Sako]

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


Hi Di, can you upload the latest patch to the JIRA, so that it goes thru the 
Hadoop QA testing?  Thanks.

- Yusaku Sako


On Dec. 15, 2015, 5:29 p.m., Di Li wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/41047/
> ---
> 
> (Updated Dec. 15, 2015, 5:29 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, Richard Zang, 
> and Yusaku Sako.
> 
> 
> Bugs: AMBARI-11268
> https://issues.apache.org/jira/browse/AMBARI-11268
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> The existing version of the Ambari (2.0) does not have a declarative way to 
> add "Quick Links" for the custom services. Currently, to add a "Quick Links" 
> dropdown one has to do add quick links definitions to the UI code, making it 
> very difficult for custom services to have quick links.
> 
> The proposed changes here introduced a way to allow services to 
> define/inherite/update quick links via quicklinks.json
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/api/resources/ResourceInstanceFactoryImpl.java
>  27609e7 
>   
> ambari-server/src/main/java/org/apache/ambari/server/api/resources/StackServiceResourceDefinition.java
>  45302ff 
>   
> ambari-server/src/main/java/org/apache/ambari/server/api/services/AmbariMetaInfo.java
>  e35e7ac 
>   
> ambari-server/src/main/java/org/apache/ambari/server/api/services/StacksService.java
>  76397fb 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AbstractControllerResourceProvider.java
>  d47d8d3 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/QuickLinkArtifactResourceProvider.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/spi/Resource.java
>  55816a3 
>   
> ambari-server/src/main/java/org/apache/ambari/server/stack/QuickLinksConfigurationModule.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/stack/ServiceModule.java 
> c2a2a0c 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/QuickLinksConfigurationInfo.java
>  PRE-CREATION 
>   ambari-server/src/main/java/org/apache/ambari/server/state/ServiceInfo.java 
> a58cda3 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/quicklinks/Check.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/quicklinks/Link.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/quicklinks/Port.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/quicklinks/Protocol.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/quicklinks/QuickLinks.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/quicklinks/QuickLinksConfiguration.java
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/metainfo.xml
>  ae58b5c 
>   
> ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/quicklinks/quicklinks.json
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/metainfo.xml 
> 515f385 
>   
> ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/quicklinks/quicklinks.json
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDP/2.0.6/services/OOZIE/metainfo.xml 
> dad6dc1 
>   
> ambari-server/src/main/resources/stacks/HDP/2.0.6/services/OOZIE/quicklinks/quicklinks.json
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/RANGER/metainfo.xml 
> 4d1b305 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/RANGER/quicklinks/quicklinks.json
>  PRE-CREATION 
>   ambari-server/src/main/resources/stacks/HDP/2.2/services/SPARK/metainfo.xml 
> db11d05 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/SPARK/quicklinks/quicklinks.json
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/services/ACCUMULO/metainfo.xml
>  352341b 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/services/ACCUMULO/quicklinks/quicklinks.json
>  PRE-CREATION 
>   ambari-server/src/main/resources/stacks/HDP/2.3/services/ATLAS/metainfo.xml 
> fee10d3 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/services/ATLAS/quicklinks/quicklinks.json
>  PRE-CREATION 
>   ambari-server/src/main/resources/stacks/HDP/2.3/services/HBASE/metainfo.xml 
> 90a31f5 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/services/HBASE/quicklinks/quicklinks.json
>  PRE-CREATION 
>   ambari-server/src/main/resources/stacks/HDP/2.3/servi

[jira] [Commented] (AMBARI-14379) Kerberos: null host showing on UI

[Yusaku Sako (JIRA)]

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

Yusaku Sako commented on AMBARI-14379:
--

[~jaimin], the test failure is unrelated to this patch.

> Kerberos: null host showing on UI
> -
>
> Key: AMBARI-14379
> URL: https://issues.apache.org/jira/browse/AMBARI-14379
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.0
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
>Priority: Critical
> Fix For: 2.2.0
>
> Attachments: AMBARI-14379.patch
>
>




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

[jira] [Commented] (AMBARI-14379) Kerberos: null host showing on UI

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14379:
-

FAILURE: Integrated in Ambari-branch-2.2 #76 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/76/])
AMBARI-14379. Kerberos: null host showing on UI. (jaimin via yusaku) (yusaku: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4eee909b1064db707cf799851e9d461ef0f39077])
* ambari-web/app/models/stack_service.js


> Kerberos: null host showing on UI
> -
>
> Key: AMBARI-14379
> URL: https://issues.apache.org/jira/browse/AMBARI-14379
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.0
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
>Priority: Critical
> Fix For: 2.2.0
>
> Attachments: AMBARI-14379.patch
>
>




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

[jira] [Updated] (AMBARI-14390) Several properties showed up as blank after EU from HDP 2.1 to HDP 2.3

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-14390:
-
Attachment: AMBARI-14390_1.png
AMBARI-14390_2.png
AMBARI-14390_3.png

> Several properties showed up as blank after EU from HDP 2.1 to HDP 2.3
> --
>
> Key: AMBARI-14390
> URL: https://issues.apache.org/jira/browse/AMBARI-14390
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Alejandro Fernandez
> Fix For: 2.2.0
>
> Attachments: AMBARI-14390_1.png, AMBARI-14390_2.png, 
> AMBARI-14390_3.png
>
>
> *Steps:*
> With Ambari 2.2.0, setup HDP 2.1 cluster (non HA, unsecure) with following 
> services: hbase,pig,slider,hive,oozie,sqoop,flume,falcon,storm
> Did Express Upgrade from HDP 2.1 to 2.3.4 and let it finish
> Observe the configs of various services
> *Result:*
> Observed that the values of several properties showed up as blank and 
> required (mostly security related). Here is the list:
> HDFS: hdfs_principal_name, hdfs_user_keytab, 
> dfs.namenode.inode.attributes.provider.class
> YARN: yarn.authorization-provider
> Tez: tez.tez-ui.history-url.base (also tracked by BUG-49613)
> HBase: hbase_principal_name, hbase_user_keytab
> ZK: zookeeper_keytab_path, zookeeper_principal_name
> Storm: nimbus_keytab, nimbus_principal_name, storm_keytab, 
> storm_principal_name, storm_ui_keytab, storm_ui_principal_name, 
> nimbus.authorizer
> Attached few screenshots
> We may have more such issues for properties of services other than the ones 
> with which the cluster was created at 2.1; so while fixing the issue, please 
> ensure that all services are taken care of.



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

[jira] [Assigned] (AMBARI-14390) Several properties showed up as blank after EU from HDP 2.1 to HDP 2.3

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez reassigned AMBARI-14390:


Assignee: Alejandro Fernandez

> Several properties showed up as blank after EU from HDP 2.1 to HDP 2.3
> --
>
> Key: AMBARI-14390
> URL: https://issues.apache.org/jira/browse/AMBARI-14390
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.2.0
>
> Attachments: AMBARI-14390_1.png, AMBARI-14390_2.png, 
> AMBARI-14390_3.png
>
>
> *Steps:*
> With Ambari 2.2.0, setup HDP 2.1 cluster (non HA, unsecure) with following 
> services: hbase,pig,slider,hive,oozie,sqoop,flume,falcon,storm
> Did Express Upgrade from HDP 2.1 to 2.3.4 and let it finish
> Observe the configs of various services
> *Result:*
> Observed that the values of several properties showed up as blank and 
> required (mostly security related). Here is the list:
> HDFS: hdfs_principal_name, hdfs_user_keytab, 
> dfs.namenode.inode.attributes.provider.class
> YARN: yarn.authorization-provider
> Tez: tez.tez-ui.history-url.base (also tracked by BUG-49613)
> HBase: hbase_principal_name, hbase_user_keytab
> ZK: zookeeper_keytab_path, zookeeper_principal_name
> Storm: nimbus_keytab, nimbus_principal_name, storm_keytab, 
> storm_principal_name, storm_ui_keytab, storm_ui_principal_name, 
> nimbus.authorizer
> Attached few screenshots
> We may have more such issues for properties of services other than the ones 
> with which the cluster was created at 2.1; so while fixing the issue, please 
> ensure that all services are taken care of.



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

[jira] [Commented] (AMBARI-14381) Role-Based Access Control: UX and Bugs

[Xi Wang (JIRA)]

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

Xi Wang commented on AMBARI-14381:
--

+1 for patch

> Role-Based Access Control: UX and Bugs
> --
>
> Key: AMBARI-14381
> URL: https://issues.apache.org/jira/browse/AMBARI-14381
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin, ambari-web
>Affects Versions: 2.3.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.3.0
>
> Attachments: AMBARI-14381.patch
>
>
> Role-Based Access Control: UX and Bugs



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

[jira] [Commented] (AMBARI-14293) While doing express upgrade multiple Clients and Services Failed to start

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko commented on AMBARI-14293:
-

Committed new patch
   e5ce144..dddfeb3  branch-2.2 -> branch-2.2
   a196eed..d154f45  trunk -> trunk


> While doing express upgrade multiple Clients and Services Failed to start
> -
>
> Key: AMBARI-14293
> URL: https://issues.apache.org/jira/browse/AMBARI-14293
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.2.0
>
> Attachments: AMBARI-14293.patch
>
>
> During nightly run over Centos7 express upgrade test cases failed because of 
> TEZ Client issue.
> Restart of Tez Client failed after upgrade because of conf file missing.
> After logging on box I found the soft links /etc/tez/conf & 
> /usr/hdp/current/tez-client/conf pointing in loop to each other.
> [root@os-r7-test-2 tez-client]# ls -l /usr/hdp/2.3.4.0-3426/tez/conf
> lrwxrwxrwx. 1 root root 13 Dec  8 05:05 /usr/hdp/2.3.4.0-3426/tez/conf -> 
> /etc/tez/conf
> [root@os-r7-test-2 tez-client]# ls -l /etc/tez/conf
> lrwxrwxrwx. 1 root root 32 Dec  8 02:23 /etc/tez/conf -> 
> /usr/hdp/current/tez-client/conf
> [root@os-r7-test-2 tez-client]# ls -l /usr/hdp/current/tez-client/conf
> lrwxrwxrwx. 1 root root 13 Dec  8 05:05 /usr/hdp/current/tez-client/conf -> 
> /etc/tez/conf
> [root@os-r7-test-2 tez-client]#
> Error on UI
> {code}
> Traceback (most recent call last):
> File 
> "/var/lib/ambari-agent/cache/common-services/TEZ/0.4.0.2.1/package/scripts/tez_client.py",
>  line 104, in 
> TezClient().execute()
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 217, in execute
> method(env)
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 486, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File 
> "/var/lib/ambari-agent/cache/common-services/TEZ/0.4.0.2.1/package/scripts/tez_client.py",
>  line 59, in pre_upgrade_restart
> conf_select.select(params.stack_name, "tez", params.version)
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/conf_select.py",
>  line 247, in select
> shell.checked_call(get_cmd("set-conf-dir", package, version), 
> logoutput=False, quiet=False, sudo=True)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 70, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 92, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 291, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'conf-select 
> set-conf-dir --package tez --stack-version 2.3.4.0-3426 --conf-version 0' 
> returned 1. /usr/hdp/2.3.4.0-3426/tez/conf does not exist
> {code}
> Observed this issue for other components too AFTER 'Ignore and Proceed' the 
> Tez client error
> The error was seen for following components:
> Pig client, Hive server, Metastore, Hive client, Spark service, spark client. 
> See attached file for output



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

Re: Review Request 41047: AMBARI-11268: Quick links for custom services

[Di Li]

> On Dec. 14, 2015, 8:22 p.m., Jaimin Jetly wrote:
> > ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/quicklinks/quicklinks.json,
> >  lines 15-16
> > 
> >
> > What is the difference between url and template attribute ? When can 
> > they have different values ?
> 
> Di Li wrote:
> hello Jaimin,
> 
> This is the design carried forward from the hardcoded App.QuickLinks 
> model. The template field is used by the UI to format the actual external 
> url. UI set the result as the value of the url field, the url field is used 
> by the UI to create the external URLs.
> 
> Thank you.
> 
> Di
> 
> Jaimin Jetly wrote:
> Hi Di,
> Thanks for the explanation. I feel we can simplify the legacy design by 
> removing one of the field as it seems redundant. This will require some 
> chnage quick_link_views.js. We can track that as a seperate task on Apache 
> Ambari Jira.

hello Jaimin

thx for the review. I will create a separate jira for the url vs template issue 
once I get the current code committed.

Thanks.

Di


- Di


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


On Dec. 15, 2015, 5:29 p.m., Di Li wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/41047/
> ---
> 
> (Updated Dec. 15, 2015, 5:29 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, Richard Zang, 
> and Yusaku Sako.
> 
> 
> Bugs: AMBARI-11268
> https://issues.apache.org/jira/browse/AMBARI-11268
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> The existing version of the Ambari (2.0) does not have a declarative way to 
> add "Quick Links" for the custom services. Currently, to add a "Quick Links" 
> dropdown one has to do add quick links definitions to the UI code, making it 
> very difficult for custom services to have quick links.
> 
> The proposed changes here introduced a way to allow services to 
> define/inherite/update quick links via quicklinks.json
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/api/resources/ResourceInstanceFactoryImpl.java
>  27609e7 
>   
> ambari-server/src/main/java/org/apache/ambari/server/api/resources/StackServiceResourceDefinition.java
>  45302ff 
>   
> ambari-server/src/main/java/org/apache/ambari/server/api/services/AmbariMetaInfo.java
>  e35e7ac 
>   
> ambari-server/src/main/java/org/apache/ambari/server/api/services/StacksService.java
>  76397fb 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AbstractControllerResourceProvider.java
>  d47d8d3 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/QuickLinkArtifactResourceProvider.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/spi/Resource.java
>  55816a3 
>   
> ambari-server/src/main/java/org/apache/ambari/server/stack/QuickLinksConfigurationModule.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/stack/ServiceModule.java 
> c2a2a0c 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/QuickLinksConfigurationInfo.java
>  PRE-CREATION 
>   ambari-server/src/main/java/org/apache/ambari/server/state/ServiceInfo.java 
> a58cda3 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/quicklinks/Check.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/quicklinks/Link.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/quicklinks/Port.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/quicklinks/Protocol.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/quicklinks/QuickLinks.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/quicklinks/QuickLinksConfiguration.java
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/metainfo.xml
>  ae58b5c 
>   
> ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/quicklinks/quicklinks.json
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/metainfo.xml 
> 515f385 
>   
> ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/quicklinks/quicklinks.json
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDP/2.0.6/services/OOZIE/metainfo.xml 
> dad6dc1 
>   
> ambari-server/src/main/resources/stacks/HDP/2.0.6/services/OOZIE/quicklinks/quicklinks.json
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/service

[jira] [Created] (AMBARI-14390) Several properties showed up as blank after EU from HDP 2.1 to HDP 2.3

[Alejandro Fernandez (JIRA)]

Alejandro Fernandez created AMBARI-14390:


 Summary: Several properties showed up as blank after EU from HDP 
2.1 to HDP 2.3
 Key: AMBARI-14390
 URL: https://issues.apache.org/jira/browse/AMBARI-14390
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.2.0
Reporter: Alejandro Fernandez
 Fix For: 2.2.0


*Steps:*
With Ambari 2.2.0, setup HDP 2.1 cluster (non HA, unsecure) with following 
services: hbase,pig,slider,hive,oozie,sqoop,flume,falcon,storm
Did Express Upgrade from HDP 2.1 to 2.3.4 and let it finish
Observe the configs of various services

*Result:*
Observed that the values of several properties showed up as blank and required 
(mostly security related). Here is the list:

HDFS: hdfs_principal_name, hdfs_user_keytab, 
dfs.namenode.inode.attributes.provider.class
YARN: yarn.authorization-provider
Tez: tez.tez-ui.history-url.base (also tracked by BUG-49613)
HBase: hbase_principal_name, hbase_user_keytab
ZK: zookeeper_keytab_path, zookeeper_principal_name
Storm: nimbus_keytab, nimbus_principal_name, storm_keytab, 
storm_principal_name, storm_ui_keytab, storm_ui_principal_name, 
nimbus.authorizer

Attached few screenshots

We may have more such issues for properties of services other than the ones 
with which the cluster was created at 2.1; so while fixing the issue, please 
ensure that all services are taken care of.



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

Re: Review Request 41388: Role-Based Access Control: UX and Bugs

[Xi Wang]

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

Ship it!


Ship It!

- Xi Wang


On Dec. 15, 2015, 11:09 a.m., Richard Zang wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/41388/
> ---
> 
> (Updated Dec. 15, 2015, 11:09 a.m.)
> 
> 
> Review request for Ambari and Xi Wang.
> 
> 
> Bugs: AMBARI-14381
> https://issues.apache.org/jira/browse/AMBARI-14381
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Role-Based Access Control: UX and Bugs
> 
> 
> Diffs
> -
> 
>   
> ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/clusters/ClustersManageAccessCtrl.js
>  1f3d3f6 
>   
> ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/clusters/UserAccessListCtrl.js
>  4799e93 
>   
> ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/groups/GroupsEditCtrl.js
>  9e0c220 
>   
> ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/users/UsersShowCtrl.js
>  cd4e020 
>   
> ambari-admin/src/main/resources/ui/admin-web/app/views/clusters/userAccessList.html
>  64369ab 
>   ambari-admin/src/main/resources/ui/admin-web/app/views/groups/edit.html 
> 4934e1e 
>   ambari-admin/src/main/resources/ui/admin-web/app/views/leftNavbar.html 
> 7ff564a 
>   ambari-admin/src/main/resources/ui/admin-web/app/views/users/list.html 
> f2da12a 
>   ambari-admin/src/main/resources/ui/admin-web/app/views/users/show.html 
> ca89e39 
>   ambari-web/app/controllers/global/user_settings_controller.js 8a50059 
>   ambari-web/app/templates/common/settings.hbs 899b9cf 
> 
> Diff: https://reviews.apache.org/r/41388/diff/
> 
> 
> Testing
> ---
> 
> Manually tested on live cluster. All unit tests passed
> 
> 
> Thanks,
> 
> Richard Zang
> 
>

[jira] [Created] (AMBARI-14389) tez view disappeared after upgrading from ambari 2.1.2 to 2.2.2.0

[Alejandro Fernandez (JIRA)]

Alejandro Fernandez created AMBARI-14389:


 Summary: tez view disappeared after upgrading from ambari 2.1.2 to 
2.2.2.0
 Key: AMBARI-14389
 URL: https://issues.apache.org/jira/browse/AMBARI-14389
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.2.0
Reporter: Alejandro Fernandez
 Fix For: 2.2.0


STR:

* Install ambari 2.1.2 with tez view installed.
* Upgrade Ambari to 2.2.0.0

Tez view is no longer present, all of the other views are present.
Tez is failing to come up due to a missing property,
{code:java}
10 Dec 2015 00:37:09,789 ERROR [qtp-ambari-client-8651] ProxyHelper:68 - Cannot 
access the url: 
http://pre-prod-poc-10.novalocal:8188/ws/v1/timeline/TEZ_VERTEX_ID?limit=9007199254740991&primaryFilter=TEZ_DAG_ID:dag_1449704814067_0017_1&_=1449707810538&;
java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
at java.net.SocketInputStream.read(SocketInputStream.java:170)
at java.net.SocketInputStream.read(SocketInputStream.java:141)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:286)
at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:704)
at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647)
at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1535)
at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1440)
at 
java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)
at 
org.apache.ambari.server.controller.internal.URLStreamProvider.processURL(URLStreamProvider.java:209)
at 
org.apache.ambari.server.view.ViewURLStreamProvider.getHttpURLConnection(ViewURLStreamProvider.java:239)
at 
org.apache.ambari.server.view.ViewURLStreamProvider.getConnection(ViewURLStreamProvider.java:146)
at 
org.apache.ambari.server.view.ViewURLStreamProvider.getConnectionAs(ViewURLStreamProvider.java:163)
at 
org.apache.ambari.server.view.ViewURLStreamProvider.getConnectionAsCurrent(ViewURLStreamProvider.java:180)
at 
org.apache.ambari.view.tez.utils.ProxyHelper.getResponse(ProxyHelper.java:55)
at 
org.apache.ambari.view.tez.rest.BaseProxyResource.getData(BaseProxyResource.java:55)
at sun.reflect.GeneratedMethodAccessor1465.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
{code}


The manual upgrade catalogs (2.1->2.3, and 2.2->2.3), had this,
{code}
  "tez.tez-ui.history-url.base": {
"value": "{TEZ_HISTORY_URL_BASE}",
"template": "yes"
  },
{code}

That property was introduced in HDP 2.2, so any EU/RUs at that version or 
higher are ok.
The default value in tez-site.xml is empty since stack advisor is the one to 
populate a value, hence why EU from 2.1->2.3 isn't giving it a value.
*This will require changes to the config pack.*



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

[jira] [Commented] (AMBARI-14383) Add support for Ranger TagSync process as a component under RANGER

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-14383:


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

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

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

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

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

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

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

This message is automatically generated.

> Add support for Ranger TagSync process as a component under RANGER
> --
>
> Key: AMBARI-14383
> URL: https://issues.apache.org/jira/browse/AMBARI-14383
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Gautam Borad
>Assignee: Gautam Borad
> Fix For: 2.3.0, 2.4.0
>
> Attachments: AMBARI-14383.patch
>
>
> Ranger TagSync is a separate service that will be responsible for 
> synchronizing the tags from Apache Atlas into Apache Ranger (db).
> This jira will track changes required to install/configure TagSync from 
> Ambari.
> * Add Ranger TagSync component under existing RANGER service. 
> * The component will be a master component
> * Ability to start/stop the component independently of Ranger Admin.
> * Ability to install the component on any host of the cluster
> * Support should be available only from HDP 2.3
> * Any other changes required in Ambari stack to support such component



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

[jira] [Resolved] (AMBARI-14386) sync-ldap does not pull in group-member associations

[JIRA]

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

Olivér Szabó resolved AMBARI-14386.
---
Resolution: Duplicate

> sync-ldap does not pull in group-member associations
> 
>
> Key: AMBARI-14386
> URL: https://issues.apache.org/jira/browse/AMBARI-14386
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.0, 2.1.2
>Reporter: Shantanu Mundkur
>Assignee: Shantanu Mundkur
> Fix For: 2.2.0
>
>
> Reproduction Steps:
> 1. Configure ambari-server to use ldap by running ambari-server setup-ldap.
> 2. Run
> ambari-server sync-ldap --all
> or 
> ambari-server sync-ldap   -v --users ./users.csv --groups ./groups.csv
> 3. Users and groups are created, but group membership is not updated.
> Completed LDAP Sync.
> Summary:
>   memberships:
> removed = 0
> created = 0
>   users:
> updated = 0
> removed = 0
> created = 21
>   groups:
> updated = 0
> removed = 0
> created = 21



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

Re: Review Request 41138: [preview]While doing express upgrade multiple Clients and Services Failed to start

[Jonathan Hurley]

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

Ship it!


My main concern is that we've broken up `conf-select create` and `conf-select 
select` ... maybe we should keep them together.


ambari-common/src/main/python/resource_management/libraries/functions/conf_select.py
 (lines 433 - 446)


I'm wondering if we should also move this to keep it together with the 
`select` that was moved.



ambari-server/src/main/resources/custom_actions/scripts/install_packages.py 
(line 196)


Change log statement to:
`The current cluster stack of {0} does not require backing up 
configurations; only conf-select versioned config directories will be created.`


- Jonathan Hurley


On Dec. 15, 2015, 12:15 p.m., Dmitro Lisnichenko wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/41138/
> ---
> 
> (Updated Dec. 15, 2015, 12:15 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Dmytro Grinenko, Jonathan 
> Hurley, Jayush Luniya, and Nate Cole.
> 
> 
> Bugs: AMBARI-14293
> https://issues.apache.org/jira/browse/AMBARI-14293
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> During nightly run over Centos7 express upgrade test cases failed because of 
> TEZ Client issue.
> 
> Restart of Tez Client failed after upgrade because of conf file missing.
> 
> After logging on box I found the soft links /etc/tez/conf & 
> /usr/hdp/current/tez-client/conf pointing in loop to each other.
> 
> [root@os-r7-test-2 tez-client]# ls -l /usr/hdp/2.3.4.0-3426/tez/conf
> lrwxrwxrwx. 1 root root 13 Dec  8 05:05 /usr/hdp/2.3.4.0-3426/tez/conf -> 
> /etc/tez/conf
> [root@os-r7-test-2 tez-client]# ls -l /etc/tez/conf
> lrwxrwxrwx. 1 root root 32 Dec  8 02:23 /etc/tez/conf -> 
> /usr/hdp/current/tez-client/conf
> [root@os-r7-test-2 tez-client]# ls -l /usr/hdp/current/tez-client/conf
> lrwxrwxrwx. 1 root root 13 Dec  8 05:05 /usr/hdp/current/tez-client/conf -> 
> /etc/tez/conf
> [root@os-r7-test-2 tez-client]#
> 
> 
> Error on UI
> {code}
> Traceback (most recent call last):
> File 
> "/var/lib/ambari-agent/cache/common-services/TEZ/0.4.0.2.1/package/scripts/tez_client.py",
>  line 104, in 
> TezClient().execute()
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 217, in execute
> method(env)
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 486, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File 
> "/var/lib/ambari-agent/cache/common-services/TEZ/0.4.0.2.1/package/scripts/tez_client.py",
>  line 59, in pre_upgrade_restart
> conf_select.select(params.stack_name, "tez", params.version)
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/conf_select.py",
>  line 247, in select
> shell.checked_call(get_cmd("set-conf-dir", package, version), 
> logoutput=False, quiet=False, sudo=True)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 70, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 92, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 291, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'conf-select 
> set-conf-dir --package tez --stack-version 2.3.4.0-3426 --conf-version 0' 
> returned 1. /usr/hdp/2.3.4.0-3426/tez/conf does not exist
> {code}
> 
> 
> Observed this issue for other components too AFTER 'Ignore and Proceed' the 
> Tez client error
> The error was seen for following components:
> Pig client, Hive server, Metastore, Hive client, Spark service, spark client. 
> See attached file for output
> 
> 
> Diffs
> -
> 
>   
> ambari-common/src/main/python/resource_management/libraries/functions/conf_select.py
>  cd3fa5c 
>   ambari-server/src/main/resources/custom_actions/scripts/install_packages.py 
> ae66fe0 
> 
> Diff: https://reviews.apache.org/r/41138/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Dmitro Lisnichenko
> 
>

[jira] [Commented] (AMBARI-14386) sync-ldap does not pull in group-member associations

[JIRA]

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

Olivér Szabó commented on AMBARI-14386:
---

Hi Shantanu!
I already tested AMBARI-13767 with Openldap, freeIPA and AD. So I close this 
bug as duplicated. If you still get this problem it's most likely a 
configuration error in ambari.properties (e.g.: invalid membership attribute)

> sync-ldap does not pull in group-member associations
> 
>
> Key: AMBARI-14386
> URL: https://issues.apache.org/jira/browse/AMBARI-14386
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.0, 2.1.2
>Reporter: Shantanu Mundkur
>Assignee: Shantanu Mundkur
> Fix For: 2.2.0
>
>
> Reproduction Steps:
> 1. Configure ambari-server to use ldap by running ambari-server setup-ldap.
> 2. Run
> ambari-server sync-ldap --all
> or 
> ambari-server sync-ldap   -v --users ./users.csv --groups ./groups.csv
> 3. Users and groups are created, but group membership is not updated.
> Completed LDAP Sync.
> Summary:
>   memberships:
> removed = 0
> created = 0
>   users:
> updated = 0
> removed = 0
> created = 21
>   groups:
> updated = 0
> removed = 0
> created = 21



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

[jira] [Commented] (AMBARI-14274) RU: Better text message about backup Oozie database

[Di Li (JIRA)]

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

Di Li commented on AMBARI-14274:


Pushed to Apache Ambari trunk as commit: 
a196eed8030bea498b437ba923b461db031bf096
Link: 
https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=commit;h=a196eed8030bea498b437ba923b461db031bf096

> RU: Better text message about backup Oozie database
> ---
>
> Key: AMBARI-14274
> URL: https://issues.apache.org/jira/browse/AMBARI-14274
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Di Li
>Assignee: Di Li
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-14274.patch
>
>
> Oozie DB may be on a different node than the Oozie node. The text currently 
> reads "Before continuing, please backup the Oozie Server database on 
> .mydomain.com" 
> The text is only valid when Oozie db is on the same node as Oozie server.
> The proposal here is to change the text to "Before continuing, please backup 
> the Oozie Server database referenced by the Oozie server located on 
> xxx.mydomain.com."



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

Review Request 41388: Role-Based Access Control: UX and Bugs

[Richard Zang]

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

Review request for Ambari and Xi Wang.


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


Repository: ambari


Description
---

Role-Based Access Control: UX and Bugs


Diffs
-

  
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/clusters/ClustersManageAccessCtrl.js
 1f3d3f6 
  
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/clusters/UserAccessListCtrl.js
 4799e93 
  
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/groups/GroupsEditCtrl.js
 9e0c220 
  
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/users/UsersShowCtrl.js
 cd4e020 
  
ambari-admin/src/main/resources/ui/admin-web/app/views/clusters/userAccessList.html
 64369ab 
  ambari-admin/src/main/resources/ui/admin-web/app/views/groups/edit.html 
4934e1e 
  ambari-admin/src/main/resources/ui/admin-web/app/views/leftNavbar.html 
7ff564a 
  ambari-admin/src/main/resources/ui/admin-web/app/views/users/list.html 
f2da12a 
  ambari-admin/src/main/resources/ui/admin-web/app/views/users/show.html 
ca89e39 
  ambari-web/app/controllers/global/user_settings_controller.js 8a50059 
  ambari-web/app/templates/common/settings.hbs 899b9cf 

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


Testing
---

Manually tested on live cluster. All unit tests passed


Thanks,

Richard Zang

[jira] [Updated] (AMBARI-14315) Config properties does not appear in right order

[Alexander Denissov (JIRA)]

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

Alexander Denissov updated AMBARI-14315:

Fix Version/s: (was: trunk)
   2.3.0

> Config properties does not appear in right order
> 
>
> Key: AMBARI-14315
> URL: https://issues.apache.org/jira/browse/AMBARI-14315
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: trunk
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: 2.3.0
>
> Attachments: AMBARI-14315.patch
>
>
> Any property with index 0 in site_properties.js ends up at the bottom of the 
> config section. Property with index 0 should ideally be at the top.
> Reason why this happens:
> https://github.com/apache/ambari/blob/trunk/ambari-web/app/mappers/configs/stack_config_properties_mapper.js#L172
> config.index = uiConfigProperty.index || Infinity;
> When uiConfigProperty.index = 0, config.index = Infinity



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

Re: Review Request 41404: Revert AMBARI-14249 and ignore offending tests

[Mahadev Konar]

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

Ship it!


Ship It!

- Mahadev Konar


On Dec. 15, 2015, 4:37 p.m., Dmytro Sen wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/41404/
> ---
> 
> (Updated Dec. 15, 2015, 4:37 p.m.)
> 
> 
> Review request for Ambari, Jonathan Hurley and Mahadev Konar.
> 
> 
> Bugs: AMBARI-14388
> https://issues.apache.org/jira/browse/AMBARI-14388
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Revert AMBARI-14249 and ignore offending tests
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/test/java/org/apache/ambari/server/orm/dao/AlertDefinitionDAOTest.java
>  d0ad386 
>   
> ambari-server/src/test/java/org/apache/ambari/server/orm/dao/AlertDispatchDAOTest.java
>  9b269b4 
>   
> ambari-server/src/test/java/org/apache/ambari/server/orm/dao/RequestDAOTest.java
>  384ef31 
> 
> Diff: https://reviews.apache.org/r/41404/diff/
> 
> 
> Testing
> ---
> 
> Unit tests passed
> 
> 
> Thanks,
> 
> Dmytro Sen
> 
>

Re: Review Request 41047: AMBARI-11268: Quick links for custom services

[Jaimin Jetly]

> On Dec. 14, 2015, 8:22 p.m., Jaimin Jetly wrote:
> > ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/quicklinks/quicklinks.json,
> >  lines 15-16
> > 
> >
> > What is the difference between url and template attribute ? When can 
> > they have different values ?
> 
> Di Li wrote:
> hello Jaimin,
> 
> This is the design carried forward from the hardcoded App.QuickLinks 
> model. The template field is used by the UI to format the actual external 
> url. UI set the result as the value of the url field, the url field is used 
> by the UI to create the external URLs.
> 
> Thank you.
> 
> Di

Hi Di,
Thanks for the explanation. I feel we can simplify the legacy design by 
removing one of the field as it seems redundant. This will require some chnage 
quick_link_views.js. We can track that as a seperate task on Apache Ambari Jira.


- Jaimin


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


On Dec. 15, 2015, 5:29 p.m., Di Li wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/41047/
> ---
> 
> (Updated Dec. 15, 2015, 5:29 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, Richard Zang, 
> and Yusaku Sako.
> 
> 
> Bugs: AMBARI-11268
> https://issues.apache.org/jira/browse/AMBARI-11268
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> The existing version of the Ambari (2.0) does not have a declarative way to 
> add "Quick Links" for the custom services. Currently, to add a "Quick Links" 
> dropdown one has to do add quick links definitions to the UI code, making it 
> very difficult for custom services to have quick links.
> 
> The proposed changes here introduced a way to allow services to 
> define/inherite/update quick links via quicklinks.json
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/api/resources/ResourceInstanceFactoryImpl.java
>  27609e7 
>   
> ambari-server/src/main/java/org/apache/ambari/server/api/resources/StackServiceResourceDefinition.java
>  45302ff 
>   
> ambari-server/src/main/java/org/apache/ambari/server/api/services/AmbariMetaInfo.java
>  e35e7ac 
>   
> ambari-server/src/main/java/org/apache/ambari/server/api/services/StacksService.java
>  76397fb 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AbstractControllerResourceProvider.java
>  d47d8d3 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/QuickLinkArtifactResourceProvider.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/spi/Resource.java
>  55816a3 
>   
> ambari-server/src/main/java/org/apache/ambari/server/stack/QuickLinksConfigurationModule.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/stack/ServiceModule.java 
> c2a2a0c 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/QuickLinksConfigurationInfo.java
>  PRE-CREATION 
>   ambari-server/src/main/java/org/apache/ambari/server/state/ServiceInfo.java 
> a58cda3 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/quicklinks/Check.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/quicklinks/Link.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/quicklinks/Port.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/quicklinks/Protocol.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/quicklinks/QuickLinks.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/quicklinks/QuickLinksConfiguration.java
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/metainfo.xml
>  ae58b5c 
>   
> ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/quicklinks/quicklinks.json
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/metainfo.xml 
> 515f385 
>   
> ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/quicklinks/quicklinks.json
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDP/2.0.6/services/OOZIE/metainfo.xml 
> dad6dc1 
>   
> ambari-server/src/main/resources/stacks/HDP/2.0.6/services/OOZIE/quicklinks/quicklinks.json
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/RANGER/metainfo.xml 
> 4d1b305 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/RANGER/quicklinks/quicklinks.json
>  PRE-CREATION 
>   ambari-server/src/main/resources/s

[jira] [Commented] (AMBARI-14387) Exclude "/tmp" and mountpoints from suggested service data directories

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on AMBARI-14387:
-

GitHub user randerzander opened a pull request:

https://github.com/apache/ambari/pull/27

AMBARI-14387

Added excluded /tmp and /etc mountpounts to ambari-agent

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/randerzander/ambari branch-2.2

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ambari/pull/27.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #27


commit 4a441f8114ce3f652f9b6ac9a5f46bee11334a94
Author: Randy Gelhausen 
Date:   2015-12-15T19:03:28Z

Added excluded /tmp and /etc mountpounts to ambari-agent




> Exclude "/tmp" and  mountpoints from suggested service data directories
> ---
>
> Key: AMBARI-14387
> URL: https://issues.apache.org/jira/browse/AMBARI-14387
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Reporter: Randy Gelhausen
>
> Ambari agents running in Docker containers frequently have /tmp and /etc 
> mountpoints. Between HDFS, ZooKeeper, HBase, and YARN configs, it's very easy 
> to mistakenly accept a /tmp/hadoop suggested data directory. Any mountpoints 
> with /tmp or /etc should be omitted.



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