[jira] [Updated] (AMBARI-12617) Ranger admin install fails with umask 027

[Gautam Borad (JIRA)]

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

Gautam Borad updated AMBARI-12617:
--
Attachment: (was: AMBARI-12617.patch)

> Ranger admin install fails with umask 027
> -
>
> Key: AMBARI-12617
> URL: https://issues.apache.org/jira/browse/AMBARI-12617
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.0
> Environment: Centos6
> Oracle12 DB
> JDK: Oracle JDK8
>Reporter: Gautam Borad
>Assignee: Gautam Borad
>
> Ranger admin fails to install as jdbc driver has insuffcient permissions



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

Re: Review Request 37033: Ranger admin install fails with umask 027

[Gautam Borad]

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

(Updated Aug. 5, 2015, 6:30 a.m.)


Review request for Ambari, Alejandro Fernandez, Mahadev Konar, Velmurugan 
Periasamy, and Yusaku Sako.


Changes
---

Resolved failing unit tests.


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


Repository: ambari


Description
---

Ranger admin fails to install as jdbc driver has insuffcient permissions


Diffs (updated)
-

  
ambari-common/src/main/python/resource_management/libraries/functions/setup_ranger_plugin.py
 35d4953 
  
ambari-common/src/main/python/resource_management/libraries/functions/setup_ranger_plugin_xml.py
 070dec6 
  
ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/setup_ranger.py
 71996d2 
  
ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/setup_ranger_xml.py
 6f6a02b 
  ambari-server/src/test/python/stacks/2.2/RANGER/test_ranger_admin.py 24c8afe 

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


Testing
---

Tested Ranger installation on a Ambari based cluster having Ranger (using 
Oracle12 DB), HDFS, Zookeeper.


Thanks,

Gautam Borad

[jira] [Updated] (AMBARI-12617) Ranger admin install fails with umask 027

[Gautam Borad (JIRA)]

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

Gautam Borad updated AMBARI-12617:
--
Attachment: AMBARI-12617.patch

> Ranger admin install fails with umask 027
> -
>
> Key: AMBARI-12617
> URL: https://issues.apache.org/jira/browse/AMBARI-12617
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.0
> Environment: Centos6
> Oracle12 DB
> JDK: Oracle JDK8
>Reporter: Gautam Borad
>Assignee: Gautam Borad
> Attachments: AMBARI-12617.patch
>
>
> Ranger admin fails to install as jdbc driver has insuffcient permissions



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

[jira] [Commented] (AMBARI-12635) If the "current" stack version status is OUT_OF_SYNC, no version box is displayed on Admin > Stacks > Version page

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-12635:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12748698/AMBARI-12635.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.

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

This message is automatically generated.

> If the "current" stack version status is OUT_OF_SYNC, no version box is 
> displayed on Admin > Stacks > Version page
> --
>
> Key: AMBARI-12635
> URL: https://issues.apache.org/jira/browse/AMBARI-12635
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.1.2
>
> Attachments: AMBARI-12635.patch
>
>
> Under some circumstances, the current stack version can be in OUT_OF_SYNC 
> state. When this happens, no version box is displayed under Admin > Stacks > 
> Versions, even for the current stack version. Current stack version should 
> always be visible.



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

Re: Review Request 37112: Ensure Flume can be deployed without any additional services

[Sid Wagle]

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

Ship it!


Ship It!

- Sid Wagle


On Aug. 5, 2015, 2:43 a.m., Sumit Mohanty wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/37112/
> ---
> 
> (Updated Aug. 5, 2015, 2:43 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez and Sid Wagle.
> 
> 
> Bugs: AMBARI-12637
> https://issues.apache.org/jira/browse/AMBARI-12637
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Ensure Flume can be deployed without any additional services
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py
>  3ddefe3 
>   
> ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/scripts/rack_awareness.py
>  d24eb49 
>   ambari-server/src/test/python/stacks/2.0.6/FLUME/test_flume.py 8143005 
>   ambari-server/src/test/python/stacks/2.0.6/configs/flume_only.json 
> PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/37112/diff/
> 
> 
> Testing
> ---
> 
> Added an unit test and verified using manual install.
> 
> 
> Thanks,
> 
> Sumit Mohanty
> 
>

Re: Review Request 37112: Ensure Flume can be deployed without any additional services

[Sumit Mohanty]

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

(Updated Aug. 5, 2015, 2:43 a.m.)


Review request for Ambari, Alejandro Fernandez and Sid Wagle.


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


Repository: ambari


Description
---

Ensure Flume can be deployed without any additional services


Diffs (updated)
-

  
ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py
 3ddefe3 
  
ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/scripts/rack_awareness.py
 d24eb49 
  ambari-server/src/test/python/stacks/2.0.6/FLUME/test_flume.py 8143005 
  ambari-server/src/test/python/stacks/2.0.6/configs/flume_only.json 
PRE-CREATION 

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


Testing
---

Added an unit test and verified using manual install.


Thanks,

Sumit Mohanty

[jira] [Commented] (AMBARI-12628) When HDFS HA enabled with Ambari 2.1, several service failed to start

[Vincent.He (JIRA)]

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

Vincent.He commented on AMBARI-12628:
-

After more debug, make a big step in the issues and can workaround now,

1. I configured unlimit in /etc/profile.

2. When jmx.py to get the data, it can get the JSON data, but it also get an 
exception "/etc/profile: line 79: ulimit: open files: cannot modify limit: 
Operation not permitted", and the string passed to json parser is 
2015-08-04 22:29:38,386 - checked_call returned (0, '/etc/profile: line 79: 
ulimit: open files: cannot modify limit: Operation not permitted\n{\n  "beans" 
: [ {\n"name" : "Hadoop:service=NameNode,name=NameNodeStatus",\n
"modelerType" : "org.apache.hadoop.hdfs.server.namenode.NameNode",\n"State" 
: "active",\n"NNRole" : "NameNode",\n"HostAndPort" : 
"h02.bigdata.com:8020",\n"SecurityEnabled" : false,\n
"LastHATransitionTime" : 1438739950089\n  } ]\n}')

This is not a JSON string due to prefix exception added.

So the issue is why shell.checked_call will add the exception to the normal 
string return.


> When HDFS HA enabled with Ambari 2.1, several service failed to start 
> --
>
> Key: AMBARI-12628
> URL: https://issues.apache.org/jira/browse/AMBARI-12628
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.0
>Reporter: Vincent.He
>Priority: Critical
>
> Install Ambari 2.1 with HDP 2.3, when enabled HA for HDFS, serval service 
> failed to start like mapredurce history server, dig into more detail, it is 
> different from issue 12374.
> The issues reported is failed to decoded the JSON string,
> 2015-08-03 02:09:35,420 - Getting jmx metrics from NN failed. URL: 
> http://h03.bigdata.com:50070/jmx?qry=Hadoop:service=NameNode,name=NameNodeStatus
> Traceback (most recent call last):
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
>  line 40, in get_value_from_jmx
> data_dict = json.loads(data)
>   File "/usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py", line 
> 307, in loads
> return _default_decoder.decode(s)
>   File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line 
> 335, in decode
> obj, end = self.raw_decode(s, idx=_w(s, 0).end())
>   File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line 
> 353, in raw_decode
> raise ValueError("No JSON object could be decoded")
> ValueError: No JSON object could be decoded
> 2015-08-03 02:09:35,494 - Getting jmx metrics from NN failed. URL: 
> http://h02.bigdata.lenovo.com:50070/jmx?qry=Hadoop:service=NameNode,name=NameNodeStatus
> Traceback (most recent call last):
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
>  line 40, in get_value_from_jmx
> data_dict = json.loads(data)
>   File "/usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py", line 
> 307, in loads
> return _default_decoder.decode(s)
>   File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line 
> 335, in decode
> obj, end = self.raw_decode(s, idx=_w(s, 0).end())
>   File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line 
> 353, in raw_decode
> raise ValueError("No JSON object could be decoded")
> ValueError: No JSON object could be decoded
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py",
>  line 168, in 
> HistoryServer().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 218, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py",
>  line 91, in start
> self.configure(env) # FOR SECURITY
>   File 
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py",
>  line 55, in configure
> yarn(name="historyserver")
>   File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", 
> line 89, in thunk
> return fn(*args, **kwargs)
>   File 
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/yarn.py",
>  line 72, in yarn
> recursive_chmod=True
>   File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
> line 157, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 152, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 118, in run_action
> provider_action()
>   File 
> "/usr/

Review Request 37112: Ensure Flume can be deployed without any additional services

[Sumit Mohanty]

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

Review request for Ambari, Alejandro Fernandez and Sid Wagle.


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


Repository: ambari


Description
---

Ensure Flume can be deployed without any additional services


Diffs
-

  
ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py
 3ddefe3 
  
ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/scripts/rack_awareness.py
 d24eb49 
  ambari-server/src/test/python/stacks/2.0.6/FLUME/test_flume.py 8143005 

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


Testing
---

Added an unit test and verified using manual install.


Thanks,

Sumit Mohanty

[jira] [Updated] (AMBARI-12637) Ensure Flume can be deployed without any additional services

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-12637:
---
Attachment: (was: AMBARI-12637.patch)

> Ensure Flume can be deployed without any additional services
> 
>
> Key: AMBARI-12637
> URL: https://issues.apache.org/jira/browse/AMBARI-12637
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.1.1
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
> Fix For: 2.1.1
>
> Attachments: AMBARI-12637.patch
>
>
> Flume deployment fails as the code path expects {{hadoop-env}} to be present.



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

[jira] [Updated] (AMBARI-12637) Ensure Flume can be deployed without any additional services

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-12637:
---
Description: Flume deployment fails as the code expects {{hadoop-env}} to 
be present.  (was: Flume deployment fails as the code path expects 
{{hadoop-env}} to be present.)

> Ensure Flume can be deployed without any additional services
> 
>
> Key: AMBARI-12637
> URL: https://issues.apache.org/jira/browse/AMBARI-12637
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.1.1
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
> Fix For: 2.1.1
>
> Attachments: AMBARI-12637.patch
>
>
> Flume deployment fails as the code expects {{hadoop-env}} to be present.



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

[jira] [Updated] (AMBARI-12637) Ensure Flume can be deployed without any additional services

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-12637:
---
Attachment: AMBARI-12637.patch

> Ensure Flume can be deployed without any additional services
> 
>
> Key: AMBARI-12637
> URL: https://issues.apache.org/jira/browse/AMBARI-12637
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.1.1
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
> Fix For: 2.1.1
>
> Attachments: AMBARI-12637.patch
>
>
> Flume deployment fails as the code path expects {{hadoop-env}} to be present.



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

[jira] [Updated] (AMBARI-12641) Allow user to update Kerberos Descriptor from admin Kerberos page

[Jaimin D Jetly (JIRA)]

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

Jaimin D Jetly updated AMBARI-12641:

Description: 
Allow user to update _modifiable_ properties of the Kerberos Descriptor from 
within Kerberos administrator view. These updates should be stored in the 
cluster's Kerberos Descriptor _artifact resource_. 

Once changes have been saved, the _Regenerate Keytabs_ feature should be 
invoked to create any new/changed principals and update service configurations. 
As part of the process, services should be restarted once the Kerberos-related 
tasks are complete. 

> Allow user to update Kerberos Descriptor from admin Kerberos page
> -
>
> Key: AMBARI-12641
> URL: https://issues.apache.org/jira/browse/AMBARI-12641
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
>Priority: Critical
> Fix For: 2.1.0
>
>
> Allow user to update _modifiable_ properties of the Kerberos Descriptor from 
> within Kerberos administrator view. These updates should be stored in the 
> cluster's Kerberos Descriptor _artifact resource_. 
> Once changes have been saved, the _Regenerate Keytabs_ feature should be 
> invoked to create any new/changed principals and update service 
> configurations. As part of the process, services should be restarted once the 
> Kerberos-related tasks are complete. 



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

[jira] [Created] (AMBARI-12641) Allow user to update Kerberos Descriptor from admin Kerberos page

[Jaimin D Jetly (JIRA)]

Jaimin D Jetly created AMBARI-12641:
---

 Summary: Allow user to update Kerberos Descriptor from admin 
Kerberos page
 Key: AMBARI-12641
 URL: https://issues.apache.org/jira/browse/AMBARI-12641
 Project: Ambari
  Issue Type: Task
  Components: ambari-web
Affects Versions: 2.0.0
Reporter: Jaimin D Jetly
Assignee: Jaimin D Jetly
Priority: Critical
 Fix For: 2.1.0






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

[jira] [Commented] (AMBARI-12604) When regenerating Kerberos principals, ensure Kerberos Descriptor changes are applied to services

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-12604:


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

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

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

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

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

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

  
org.apache.ambari.server.security.authorization.AmbariLdapAuthenticationProviderForDNWithSpaceTest

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

This message is automatically generated.

> When regenerating Kerberos principals, ensure Kerberos Descriptor changes are 
> applied to services
> -
>
> Key: AMBARI-12604
> URL: https://issues.apache.org/jira/browse/AMBARI-12604
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.0.1, 2.1.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: kerberos, kerberos_descriptor
> Fix For: 2.2.0, 2.1.1
>
> Attachments: AMBARI-12604_branch-2.1_01.patch, 
> AMBARI-12604_trunk_01.patch
>
>
> When regenerating Kerberos principals, ensure Kerberos Descriptor changes are 
> applied to services.  
> It is possible for changes to be made to the Kerberos Descriptor.  One way to 
> propagate these changes into the service configurations is to process the 
> Kerberos Descriptor and update service configurations while performing tasks 
> for the "Regenerate Keytabs" operation. 



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

[jira] [Updated] (AMBARI-12640) Restarting of services does not observe intra-service dependency

[Tuong Truong (JIRA)]

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

Tuong Truong updated AMBARI-12640:
--
Summary: Restarting of services does not observe intra-service dependency  
(was: Restarting of services doesnot observe intra-service dependency )

> Restarting of services does not observe intra-service dependency
> 
>
> Key: AMBARI-12640
> URL: https://issues.apache.org/jira/browse/AMBARI-12640
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 1.7.0
>Reporter: Tuong Truong
>
> Currently, some services, such as Hive, manages sub subservice like database 
> service.   When starting a service, the order of the subservices are observed 
> to ensure they start properly.  However, for restarting of services,  the 
> dependency order is not observed. 
> In the case of Hive, the restart sequence is:
> HCat Client, 
> Hive Client, 
> Hive Metastore (has dependency on mysql, but started before) 
> HiveServer2, 
> MySQL server, 
> WebHCat server
> So if Mysql Server is down, then the HIve restart sequence will fail.
> To recreate the problem, stop MySQL server, then restart Hive service.  One 
> will see that the Hive Metastore service will fail to start.



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

[jira] [Created] (AMBARI-12640) Restarting of services doesnot observe intra-service dependency

[Tuong Truong (JIRA)]

Tuong Truong created AMBARI-12640:
-

 Summary: Restarting of services doesnot observe intra-service 
dependency 
 Key: AMBARI-12640
 URL: https://issues.apache.org/jira/browse/AMBARI-12640
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 1.7.0
Reporter: Tuong Truong


Currently, some services, such as Hive, manages sub subservice like database 
service.   When starting a service, the order of the subservices are observed 
to ensure they start properly.  However, for restarting of services,  the 
dependency order is not observed. 

In the case of Hive, the restart sequence is:
HCat Client, 
Hive Client, 
Hive Metastore (has dependency on mysql, but started before) 
HiveServer2, 
MySQL server, 
WebHCat server

So if Mysql Server is down, then the HIve restart sequence will fail.

To recreate the problem, stop MySQL server, then restart Hive service.  One 
will see that the Hive Metastore service will fail to start.



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

[jira] [Commented] (AMBARI-12510) ambari-server failed to properly detect of postgresql database status on RHEL 7.x

[Yusaku Sako (JIRA)]

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

Yusaku Sako commented on AMBARI-12510:
--

Thanks [~tctruong213].
Ambari also supports Ubuntu, so we need to make sure that works as well. 
However, I ran "service postgresql status" command on Ubuntu 12, and it always 
shows "running" regardless of the state, and the return code of the status 
command is always 0.  So in a way, it's already broken, so this patch does not 
make it any worse in that regard.

+[~sumitmohanty], your thoughts?

> ambari-server failed to properly detect of postgresql database status on RHEL 
> 7.x 
> --
>
> Key: AMBARI-12510
> URL: https://issues.apache.org/jira/browse/AMBARI-12510
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.0
> Environment: RHEL 7.0, 7.1
>Reporter: Tuong Truong
>Assignee: Tuong Truong
>  Labels: RHEL7.1
> Fix For: 2.1.1
>
> Attachments: AMBARI-12510-0.patch
>
>
> Ambari-server failed to initalize the postgre db when postgresql packages are 
> installed as part of Ambari installation on RHEL 7.1, and 7.0 in some 
> scenario.  
> Ambari-server detects status of Postgre via the "service postgresql status" 
> call, and perform regex on  the output for "running" or "stopped".   This 
> works OK for RHEL 6, but not for RHEL 7 as its output may include "running" 
> when postgres is not actually running.



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

[jira] [Commented] (AMBARI-12510) ambari-server failed to properly detect of postgresql database status on RHEL 7.x

[Tuong Truong (JIRA)]

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

Tuong Truong commented on AMBARI-12510:
---

[~u39kun]  any comment on this issue and how I can move it forward?

> ambari-server failed to properly detect of postgresql database status on RHEL 
> 7.x 
> --
>
> Key: AMBARI-12510
> URL: https://issues.apache.org/jira/browse/AMBARI-12510
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.0
> Environment: RHEL 7.0, 7.1
>Reporter: Tuong Truong
>Assignee: Tuong Truong
>  Labels: RHEL7.1
> Fix For: 2.1.1
>
> Attachments: AMBARI-12510-0.patch
>
>
> Ambari-server failed to initalize the postgre db when postgresql packages are 
> installed as part of Ambari installation on RHEL 7.1, and 7.0 in some 
> scenario.  
> Ambari-server detects status of Postgre via the "service postgresql status" 
> call, and perform regex on  the output for "running" or "stopped".   This 
> works OK for RHEL 6, but not for RHEL 7 as its output may include "running" 
> when postgres is not actually running.



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

[jira] [Created] (AMBARI-12639) Need ability to remove service from UI from a "dead" host in order to delete the host

[Tuong Truong (JIRA)]

Tuong Truong created AMBARI-12639:
-

 Summary: Need ability to remove service from UI from a "dead" host 
in order to delete the host
 Key: AMBARI-12639
 URL: https://issues.apache.org/jira/browse/AMBARI-12639
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 1.7.0
Reporter: Tuong Truong
Priority: Minor


If a node in a cluster is dead, and the node had master services installed, 
there is currently no way to delete the node from the cluster.  Ambari UI won't 
allow deletion of the node w/o first re/moving the master service.  However, 
there is no option in UI to re/move the service for a dead node (agent is not 
communicating with the server).

The work around is to use REST to re/move the service and then the node can be 
delete.



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

[jira] [Commented] (AMBARI-12636) Kerberos: fails check during enable Kerb with SLES

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-12636:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12748728/AMBARI-12636_01.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.

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

This message is automatically generated.

> Kerberos: fails check during enable Kerb with SLES
> --
>
> Key: AMBARI-12636
> URL: https://issues.apache.org/jira/browse/AMBARI-12636
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.0.0
> Environment: Ambari 2.1.1 Build #107
> HDP 2.3 GA
> ZK + AMS + Kafka
> SLES 11 SP3
> MIT KDC, all single node
> Register hosts / bootstrap agents via SSH
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
>  Labels: directory-permissions, install
> Fix For: 2.2.0
>
> Attachments: AMBARI-12636_01.patch
>
>
> When executing the Kerberos service check, the following error occurs:
> {code}
> stderr:   /var/lib/ambari-agent/data/errors-24.txt
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/KERBEROS/1.10.3-10/package/scripts/service_check.py",
>  line 81, in 
> KerberosServiceCheck().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 218, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/KERBEROS/1.10.3-10/package/scripts/service_check.py",
>  line 64, in service_check
> user=params.smoke_user
>   File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
> line 157, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 152, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 118, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 258, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 70, in inner
> result = function(command, **kwargs)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 92, in checked_call
> tries=tries, try_sleep=try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 291, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of '/usr/bin/kinit -c 
> /var/lib/ambari-agent/data/tmp/kerberos_service_check_cc_dd529fe1e15538ddfe9ce0347604d64c
>  -kt /etc/security/keytabs/kerberos.service_check.080315.keytab 
> mycluster-080...@example.com' returned 1. kinit(v5): Credentials cache 
> permissions incorrect when initializing cache 
> /var/lib/ambari-agent/data/tmp/kerberos_service_check_cc_dd529fe1e15538ddfe9ce0347604d64c
> stdout:   /var/lib/ambari-agent/data/output-24.txt
> Performing kinit using mycluster-080...@example.com
> 2015-08-03 19:11:57,085 - Execute['/usr/bin/kinit -c 
> /var/lib/ambari-agent/data/tmp/kerberos_service_check_cc_dd529fe1e15538ddfe9ce0347604d64c
>  -kt /etc/security/keytabs/kerberos.service_check.080315.keytab 
> mycluster-080...@example.com'] {'user': 'jambari-qa'}
> 2015-08-03 19:11:57,179 - 
> File['/var/lib/ambari-agent/data/tmp/kerberos_service_check_cc_dd529fe1e15538ddfe9ce0347604d64c']
>  {'action': ['delete']}
> {code}
> This error happens only on SLES, however the cause exists on all platforms.  
> The other platforms silently ignore the condition; which, however, does not 
> have any bearing on the results of the _kinit_ test. 
> *Cause*
> The "Credentials cache permissions in

[jira] [Created] (AMBARI-12638) Component deployment fails if tar not installed

[Marcin Szymanski (JIRA)]

Marcin Szymanski created AMBARI-12638:
-

 Summary: Component deployment fails if tar not installed
 Key: AMBARI-12638
 URL: https://issues.apache.org/jira/browse/AMBARI-12638
 Project: Ambari
  Issue Type: Bug
  Components: ambari-agent
Affects Versions: 2.1.0
 Environment: Oracle Linux on Azure
Reporter: Marcin Szymanski
Priority: Minor


{code}
Traceback (most recent call last):
  File 
"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL/scripts/hook.py",
 line 38, in 
BeforeInstallHook().execute()
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
 line 218, in execute
method(env)
  File 
"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL/scripts/hook.py",
 line 35, in hook
setup_java()
  File 
"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-INSTALL/scripts/shared_initialization.py",
 line 64, in setup_java
not_if = format("test -e {java_exec}")
  File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
line 157, in __init__
self.env.run()
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
line 152, in run
self.run_action(resource, action)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
line 118, in run_action
provider_action()
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
 line 258, in action_run
tries=self.resource.tries, try_sleep=self.resource.try_sleep)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 70, in inner
result = function(command, **kwargs)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 92, in checked_call
tries=tries, try_sleep=try_sleep)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 140, in _call_wrapper
result = _call(command, **kwargs_copy)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 291, in _call
raise Fail(err_msg)
resource_management.core.exceptions.Fail: Execution of 'mkdir -p 
/var/lib/ambari-agent/data/tmp/jdk && cd /var/lib/ambari-agent/data/tmp/jdk && 
tar -xf /var/lib/ambari-agent/data/tmp/jdk-8u40-linux-x64.tar.gz && 
ambari-sudo.sh cp -rp /var/lib/ambari-agent/data/tmp/jdk/* /usr/jdk64' returned 
127. /bin/bash: tar: command not found
{code}



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

Re: Review Request 37033: Ranger admin install fails with umask 027

[Sumit Mohanty]

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



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


Some unit tests need fixing:
FAIL: test_configure_default (test_ranger_admin.TestRangerAdmin)
FAIL: test_configure_secured (test_ranger_admin.TestRangerAdmin)
FAIL: test_start_default (test_ranger_admin.TestRangerAdmin)
FAIL: test_start_secured (test_ranger_admin.TestRangerAdmin)


- Sumit Mohanty


On Aug. 4, 2015, 9:36 a.m., Gautam Borad wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/37033/
> ---
> 
> (Updated Aug. 4, 2015, 9:36 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Mahadev Konar, Velmurugan 
> Periasamy, and Yusaku Sako.
> 
> 
> Bugs: AMBARI-12617
> https://issues.apache.org/jira/browse/AMBARI-12617
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Ranger admin fails to install as jdbc driver has insuffcient permissions
> 
> 
> Diffs
> -
> 
>   
> ambari-common/src/main/python/resource_management/libraries/functions/setup_ranger_plugin.py
>  35d4953 
>   
> ambari-common/src/main/python/resource_management/libraries/functions/setup_ranger_plugin_xml.py
>  070dec6 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/setup_ranger.py
>  71996d2 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/setup_ranger_xml.py
>  6f6a02b 
> 
> Diff: https://reviews.apache.org/r/37033/diff/
> 
> 
> Testing
> ---
> 
> Tested Ranger installation on a Ambari based cluster having Ranger (using 
> Oracle12 DB), HDFS, Zookeeper.
> 
> 
> Thanks,
> 
> Gautam Borad
> 
>

[jira] [Commented] (AMBARI-12582) Some properties on Kerberos configs tab are empty although the same properties on services configs are filled

[Hudson (JIRA)]

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

Hudson commented on AMBARI-12582:
-

FAILURE: Integrated in Ambari-branch-2.1 #321 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/321/])
Revert "AMBARI-12582. Some properties on Kerberos configs tab are empty 
although the same properties on services configs are filled (alexantonenko)" 
(rlevas: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=59c661711550500a0a5c5c7f4cf1bdcd8974fae9)
* ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/kerberos.json


> Some properties on Kerberos configs tab are empty although the same 
> properties on services configs are filled
> -
>
> Key: AMBARI-12582
> URL: https://issues.apache.org/jira/browse/AMBARI-12582
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.1.2
>
> Attachments: AMBARI-12582.patch, kerberosConfigs.png, 
> serviceConfig.png
>
>
> Steps:
> # Deploy cluster.
> # Enable security.
> Result: some properties on Kerberos configs tab are empty although the same 
> properties on services configs are filled.
> This issue is for a lot another properties.



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

Ambari should have a HA repository server

[Chen He]

Current it is on :

http://s3.amazonaws.com/dev.hortonworks.com/ambari/

However, I met problems twice because s3 instance is down;

It shouldn't be hard to create a HA for the repository. Let me know if I
can help.

Regards!

Chen

[jira] [Updated] (AMBARI-12637) Ensure Flume can be deployed without any additional services

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-12637:
---
Attachment: AMBARI-12637.patch

> Ensure Flume can be deployed without any additional services
> 
>
> Key: AMBARI-12637
> URL: https://issues.apache.org/jira/browse/AMBARI-12637
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.1.1
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
> Fix For: 2.1.1
>
> Attachments: AMBARI-12637.patch
>
>
> Flume deployment fails as the code path expects {{hadoop-env}} to be present.



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

[jira] [Created] (AMBARI-12637) Ensure Flume can be deployed without any additional services

[Sumit Mohanty (JIRA)]

Sumit Mohanty created AMBARI-12637:
--

 Summary: Ensure Flume can be deployed without any additional 
services
 Key: AMBARI-12637
 URL: https://issues.apache.org/jira/browse/AMBARI-12637
 Project: Ambari
  Issue Type: Bug
  Components: stacks
Affects Versions: 2.1.1
Reporter: Sumit Mohanty
Assignee: Sumit Mohanty
 Fix For: 2.1.1


Flume deployment fails as the code path expects {{hadoop-env}} to be present.



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

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

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-12570:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12748729/AMBARI-12570.patch.1
  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 5 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 .

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

This message is automatically generated.

> 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.se

[jira] [Updated] (AMBARI-12634) Clear passwords can be seen on Ambari UI service Configs tab via browser developer tool

[Yu Gao (JIRA)]

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

Yu Gao updated AMBARI-12634:

Description: HTML password type hides passwords with  on the service 
Configs page. However, everyone including non-admin users who has ambari access 
with READ-ONLY permission can see the real content of the passwords through 
developer tools, like firebug in firefox. For example, the database passwords 
for oozie/hive and master secret for knox are exposed in this way.  (was: HTML 
password type hides passwords with  on the service Configs page. However, 
everyone including non-admin users who has ambari access with READ-ONLY 
permission can see the real content of the passwords through developer tools, 
like firebug in firefox.)

> Clear passwords can be seen on Ambari UI service Configs tab via browser 
> developer tool
> ---
>
> Key: AMBARI-12634
> URL: https://issues.apache.org/jira/browse/AMBARI-12634
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: 2.1.0
>Reporter: Yu Gao
>  Labels: security
>
> HTML password type hides passwords with  on the service Configs page. 
> However, everyone including non-admin users who has ambari access with 
> READ-ONLY permission can see the real content of the passwords through 
> developer tools, like firebug in firefox. For example, the database passwords 
> for oozie/hive and master secret for knox are exposed in this way.



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

[jira] [Commented] (AMBARI-12563) Ambari return fail upon service check

[Hudson (JIRA)]

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

Hudson commented on AMBARI-12563:
-

FAILURE: Integrated in Ambari-branch-2.1 #320 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/320/])
AMBARI-12563.  Ambari alert return connection refuse because of motd (aonishuk) 
(aonishuk: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=eb8e925516231e912d88abf1bc642c35381a5e88)
* 
ambari-common/src/main/python/resource_management/libraries/functions/curl_krb_request.py


> Ambari return fail upon service check 
> --
>
> Key: AMBARI-12563
> URL: https://issues.apache.org/jira/browse/AMBARI-12563
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.1.1
>
>
> User has a third party monitoring tool that, whenever user do a
> 'su' it prints out the following message
> Hello user, have fun!
> Therefore, for example when user starts up namenode, Ambari is not able to
> phrase the status codes after executing the curl call for webHDFS, and throw
> error message and indicates the operation as fail. Meanwhile, the namenode is
> actually up and running.  
> This behavior also happens across other services, such as HBase.
> This issue is causing confusion upon starting of
> services/components.



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

Review Request 37094: Kerberos: fails check during enable Kerb with SLES

[Robert Levas]

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

Review request for Ambari, Andrew Onischuk, Dmytro Sen, Jayush Luniya, and 
Mahadev Konar.


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


Repository: ambari


Description
---

When executing the Kerberos service check, the following error occurs:
```
stderr:   /var/lib/ambari-agent/data/errors-24.txt

Traceback (most recent call last):
  File 
"/var/lib/ambari-agent/cache/common-services/KERBEROS/1.10.3-10/package/scripts/service_check.py",
 line 81, in 
KerberosServiceCheck().execute()
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
 line 218, in execute
method(env)
  File 
"/var/lib/ambari-agent/cache/common-services/KERBEROS/1.10.3-10/package/scripts/service_check.py",
 line 64, in service_check
user=params.smoke_user
  File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
line 157, in __init__
self.env.run()
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
line 152, in run
self.run_action(resource, action)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
line 118, in run_action
provider_action()
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
 line 258, in action_run
tries=self.resource.tries, try_sleep=self.resource.try_sleep)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 70, in inner
result = function(command, **kwargs)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 92, in checked_call
tries=tries, try_sleep=try_sleep)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 140, in _call_wrapper
result = _call(command, **kwargs_copy)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 291, in _call
raise Fail(err_msg)
resource_management.core.exceptions.Fail: Execution of '/usr/bin/kinit -c 
/var/lib/ambari-agent/data/tmp/kerberos_service_check_cc_dd529fe1e15538ddfe9ce0347604d64c
 -kt /etc/security/keytabs/kerberos.service_check.080315.keytab 
mycluster-080...@example.com' returned 1. kinit(v5): Credentials cache 
permissions incorrect when initializing cache 
/var/lib/ambari-agent/data/tmp/kerberos_service_check_cc_dd529fe1e15538ddfe9ce0347604d64c

stdout:   /var/lib/ambari-agent/data/output-24.txt

Performing kinit using mycluster-080...@example.com
2015-08-03 19:11:57,085 - Execute['/usr/bin/kinit -c 
/var/lib/ambari-agent/data/tmp/kerberos_service_check_cc_dd529fe1e15538ddfe9ce0347604d64c
 -kt /etc/security/keytabs/kerberos.service_check.080315.keytab 
mycluster-080...@example.com'] {'user': 'ambari-qa'}
2015-08-03 19:11:57,179 - 
File['/var/lib/ambari-agent/data/tmp/kerberos_service_check_cc_dd529fe1e15538ddfe9ce0347604d64c']
 {'action': ['delete']}
```

This error happens only on SLES, however the cause exists on all platforms.  
The other platforms silently ignore the condition; which, however, does not 
have any bearing on the results of the _kinit_ test. 

#Cause
The "Credentials cache permissions incorrect when initializing cache" issue is 
caused by the inability to write the Kerberos ticket cache file to the 
specified location. In the case it is 
/var/lib/ambari-agent/data/tmp/kerberos_service_check_cc_dd529fe1e15538ddfe9ce0347604d64c.
  The reason for the write failure is that /var/lib/ambari-agent/data/tmp is 
not writable by the user executing the _kinit_ call - which is the Ambari smoke 
test user (typically ambari-qa).  The directory's permissions are
```
drwxr-xr-x. 4 root root 4096 Aug  3 22:20 /var/lib/ambari-agent/data/tmp/
``` 
#Solution
In order for the ambari smoke test user to be able to write to the relevant 
directory (/var/lib/ambari-agent/data/tmp), the permissions must be set at 
least as follows
```
drwxrwxr-x. 4 root hadoop 4096 Aug  3 22:20 /var/lib/ambari-agent/data/tmp/
```

However, at the time this directory is created, it is not known what the name 
of the _hadoop_ group is, so the next best solution is to set the permissions 
as 
```
drwxrwxrwx. 4 root root 4096 Aug  3 22:20 /var/lib/ambari-agent/data/tmp/
```

If the ambari-agent is installed manually via the relevant package manager, the 
directory is created with the open permissions (777,  drwxrwxrwx) via the 
packages install_helper.sh post install script.  However if Ambari installs the 
agent via SSH, the directory is created with the more restrictive permissions 
(755, drwxr-xr-x) via the agent bootstrap.py script. 

To make these consistent, the following needs to be changed
#bootstrap.py:650
```
   command = "sudo mkdir -p {0} ; sudo chown -R {1} {0} ; sudo chmod 755 {3} ; 
sudo chmod 755 {2} ; sudo chmod 75

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

[Jonathan Hurley (JIRA)]

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

Jonathan Hurley updated AMBARI-12570:
-
Attachment: AMBARI-12570.patch.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.server.orm.AmbariJpaLocal

Re: Review Request 36895: Cluster creates stuck at 9x% (deadlock sql exception)

[Jonathan Hurley]

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

(Updated Aug. 4, 2015, 4:17 p.m.)


Review request for Ambari, Alejandro Fernandez, Nate Cole, and Sumit Mohanty.


Changes
---

Attached the wrong diff before


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


Repository: ambari


Description
---

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.

- We have dual X-locks on hostcomponentstate asking for U-locks when updating 
the CLUSTERED INDEX.
- Both dual X-locks, from different transactions and different processes, are 
on the same row (technically impossible) - based on the XML execution plan, we 
can see that the concurrent UPDATE statements are executing on different rows 
due to their CLUSTERED INDEX predicate.
- In Java, Ambari has locks which prevent concurrent U- or X-locks on the same 
row
- Only happens on SQL Server

My best suspicion right now is that we have a key hash collision happening on 
this table. That's why two processes appear to have the same lock even though 
they are on different rows.

Restricting row-level locking on this table will prevent locking on hash keys 
which could collide.


Diffs (updated)
-

  
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/HostComponentStateDAO.java
 fb585fd 
  
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/HostComponentStateEntity.java
 45e036b 
  
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/HostComponentStateEntityPK.java
 86e0dee 
  
ambari-server/src/main/java/org/apache/ambari/server/state/svccomphost/ServiceComponentHostImpl.java
 0850a79 
  
ambari-server/src/main/java/org/apache/ambari/server/upgrade/AbstractUpgradeCatalog.java
 edb1606 
  
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog220.java
 4eb7a80 
  ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql 1b67b24 
  ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql 16f6a0a 
  ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql cd6e27a 
  ambari-server/src/main/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql 
c7138be 
  ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql 0ff1aff 
  
ambari-server/src/test/java/org/apache/ambari/server/state/ServiceComponentTest.java
 96bbb1d 
  
ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ClustersTest.java
 ce1fd34 
  
ambari-server/src/test/java/org/apache/ambari/server/state/svccomphost/ServiceComponentHostTest.java
 f6ab0ec 
  
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog170Test.java
 93f7f8c 
  
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog200Test.java
 484c18d 

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


Testing
---

Deployed numerous clusters on PostgresSQL, SQL Server, and MySQL using both the 
Ambari UI and blueprints. Upgraded a 2.1 database on PostgresSQL, Oracle, 
MySQL, and SQL Server to verify that changes to the `hostcomponentstate` table 
were good.


Thanks,

Jonathan Hurley

[jira] [Updated] (AMBARI-12636) Kerberos: fails check during enable Kerb with SLES

[Robert Levas (JIRA)]

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

Robert Levas updated AMBARI-12636:
--
Attachment: AMBARI-12636_01.patch

> Kerberos: fails check during enable Kerb with SLES
> --
>
> Key: AMBARI-12636
> URL: https://issues.apache.org/jira/browse/AMBARI-12636
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.0.0
> Environment: Ambari 2.1.1 Build #107
> HDP 2.3 GA
> ZK + AMS + Kafka
> SLES 11 SP3
> MIT KDC, all single node
> Register hosts / bootstrap agents via SSH
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
>  Labels: directory-permissions, install
> Fix For: 2.2.0
>
> Attachments: AMBARI-12636_01.patch
>
>
> When executing the Kerberos service check, the following error occurs:
> {code}
> stderr:   /var/lib/ambari-agent/data/errors-24.txt
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/KERBEROS/1.10.3-10/package/scripts/service_check.py",
>  line 81, in 
> KerberosServiceCheck().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 218, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/KERBEROS/1.10.3-10/package/scripts/service_check.py",
>  line 64, in service_check
> user=params.smoke_user
>   File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
> line 157, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 152, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 118, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 258, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 70, in inner
> result = function(command, **kwargs)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 92, in checked_call
> tries=tries, try_sleep=try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 291, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of '/usr/bin/kinit -c 
> /var/lib/ambari-agent/data/tmp/kerberos_service_check_cc_dd529fe1e15538ddfe9ce0347604d64c
>  -kt /etc/security/keytabs/kerberos.service_check.080315.keytab 
> mycluster-080...@example.com' returned 1. kinit(v5): Credentials cache 
> permissions incorrect when initializing cache 
> /var/lib/ambari-agent/data/tmp/kerberos_service_check_cc_dd529fe1e15538ddfe9ce0347604d64c
> stdout:   /var/lib/ambari-agent/data/output-24.txt
> Performing kinit using mycluster-080...@example.com
> 2015-08-03 19:11:57,085 - Execute['/usr/bin/kinit -c 
> /var/lib/ambari-agent/data/tmp/kerberos_service_check_cc_dd529fe1e15538ddfe9ce0347604d64c
>  -kt /etc/security/keytabs/kerberos.service_check.080315.keytab 
> mycluster-080...@example.com'] {'user': 'jambari-qa'}
> 2015-08-03 19:11:57,179 - 
> File['/var/lib/ambari-agent/data/tmp/kerberos_service_check_cc_dd529fe1e15538ddfe9ce0347604d64c']
>  {'action': ['delete']}
> {code}
> This error happens only on SLES, however the cause exists on all platforms.  
> The other platforms silently ignore the condition; which, however, does not 
> have any bearing on the results of the _kinit_ test. 
> *Cause*
> The "Credentials cache permissions incorrect when initializing cache" issue 
> is caused by the inability to write the Kerberos ticket cache file to the 
> specified location. In the case it is 
> /var/lib/ambari-agent/data/tmp/kerberos_service_check_cc_dd529fe1e15538ddfe9ce0347604d64c.
>   The reason for the write failure is that /var/lib/ambari-agent/data/tmp is 
> not writable by the user executing the _kinit_ call - which is the Ambari 
> smoke test user (typically ambari-qa).  The directory's permissions are
> {noformat}
> drwxr-xr-x. 4 root root 4096 Aug  3 22:20 /var/lib/ambari-agent/data/tmp/
> {noformat}
> *Solution*
> In order for the ambari smoke test user to be able to write to the relevant 
> directory (/var/lib/ambari-agent/data/tmp), the permissions must be set at 
> least as follows
> {noformat}
> drwxrwxr-x. 4 root hadoop 4096 Aug  3 22:20 /var/lib/ambari-agent/data/tmp/
> {noformat}
> However, at the time this directory is created, it is not known wha

[jira] [Commented] (AMBARI-12582) Some properties on Kerberos configs tab are empty although the same properties on services configs are filled

[Hudson (JIRA)]

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

Hudson commented on AMBARI-12582:
-

FAILURE: Integrated in Ambari-trunk-Commit #3221 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3221/])
Revert "AMBARI-12582. Some properties on Kerberos configs tab are empty 
although the same properties on services configs are filled (alexantonenko)" 
(rlevas: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=1c58762886c323f9a024e9d463a646243119e5df)
* ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/kerberos.json


> Some properties on Kerberos configs tab are empty although the same 
> properties on services configs are filled
> -
>
> Key: AMBARI-12582
> URL: https://issues.apache.org/jira/browse/AMBARI-12582
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.1.2
>
> Attachments: AMBARI-12582.patch, kerberosConfigs.png, 
> serviceConfig.png
>
>
> Steps:
> # Deploy cluster.
> # Enable security.
> Result: some properties on Kerberos configs tab are empty although the same 
> properties on services configs are filled.
> This issue is for a lot another properties.



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

[jira] [Created] (AMBARI-12636) Kerberos: fails check during enable Kerb with SLES

[Robert Levas (JIRA)]

Robert Levas created AMBARI-12636:
-

 Summary: Kerberos: fails check during enable Kerb with SLES
 Key: AMBARI-12636
 URL: https://issues.apache.org/jira/browse/AMBARI-12636
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.0.0
 Environment: Ambari 2.1.1 Build #107
HDP 2.3 GA
ZK + AMS + Kafka
SLES 11 SP3
MIT KDC, all single node
Register hosts / bootstrap agents via SSH

Reporter: Robert Levas
Assignee: Robert Levas
Priority: Critical
 Fix For: 2.2.0


When executing the Kerberos service check, the following error occurs:
{code}
stderr:   /var/lib/ambari-agent/data/errors-24.txt

Traceback (most recent call last):
  File 
"/var/lib/ambari-agent/cache/common-services/KERBEROS/1.10.3-10/package/scripts/service_check.py",
 line 81, in 
KerberosServiceCheck().execute()
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
 line 218, in execute
method(env)
  File 
"/var/lib/ambari-agent/cache/common-services/KERBEROS/1.10.3-10/package/scripts/service_check.py",
 line 64, in service_check
user=params.smoke_user
  File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
line 157, in __init__
self.env.run()
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
line 152, in run
self.run_action(resource, action)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
line 118, in run_action
provider_action()
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
 line 258, in action_run
tries=self.resource.tries, try_sleep=self.resource.try_sleep)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 70, in inner
result = function(command, **kwargs)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 92, in checked_call
tries=tries, try_sleep=try_sleep)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 140, in _call_wrapper
result = _call(command, **kwargs_copy)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 291, in _call
raise Fail(err_msg)
resource_management.core.exceptions.Fail: Execution of '/usr/bin/kinit -c 
/var/lib/ambari-agent/data/tmp/kerberos_service_check_cc_dd529fe1e15538ddfe9ce0347604d64c
 -kt /etc/security/keytabs/kerberos.service_check.080315.keytab 
mycluster-080...@example.com' returned 1. kinit(v5): Credentials cache 
permissions incorrect when initializing cache 
/var/lib/ambari-agent/data/tmp/kerberos_service_check_cc_dd529fe1e15538ddfe9ce0347604d64c

stdout:   /var/lib/ambari-agent/data/output-24.txt

Performing kinit using mycluster-080...@example.com
2015-08-03 19:11:57,085 - Execute['/usr/bin/kinit -c 
/var/lib/ambari-agent/data/tmp/kerberos_service_check_cc_dd529fe1e15538ddfe9ce0347604d64c
 -kt /etc/security/keytabs/kerberos.service_check.080315.keytab 
mycluster-080...@example.com'] {'user': 'jambari-qa'}
2015-08-03 19:11:57,179 - 
File['/var/lib/ambari-agent/data/tmp/kerberos_service_check_cc_dd529fe1e15538ddfe9ce0347604d64c']
 {'action': ['delete']}
{code}

This error happens only on SLES, however the cause exists on all platforms.  
The other platforms silently ignore the condition; which, however, does not 
have any bearing on the results of the _kinit_ test. 

*Cause*
The "Credentials cache permissions incorrect when initializing cache" issue is 
caused by the inability to write the Kerberos ticket cache file to the 
specified location. In the case it is 
/var/lib/ambari-agent/data/tmp/kerberos_service_check_cc_dd529fe1e15538ddfe9ce0347604d64c.
  The reason for the write failure is that /var/lib/ambari-agent/data/tmp is 
not writable by the user executing the _kinit_ call - which is the Ambari smoke 
test user (typically ambari-qa).  The directory's permissions are
{noformat}
drwxr-xr-x. 4 root root 4096 Aug  3 22:20 /var/lib/ambari-agent/data/tmp/
{noformat}

*Solution*
In order for the ambari smoke test user to be able to write to the relevant 
directory (/var/lib/ambari-agent/data/tmp), the permissions must be set at 
least as follows
{noformat}
drwxrwxr-x. 4 root hadoop 4096 Aug  3 22:20 /var/lib/ambari-agent/data/tmp/
{noformat}
However, at the time this directory is created, it is not known what the name 
of the _hadoop_ group is, so the next best solution is to set the permissions 
as 
{noformat}
drwxrwxrwx. 4 root root 4096 Aug  3 22:20 /var/lib/ambari-agent/data/tmp/
{noformat}

If the ambari-agent is installed manually via the relevant package manager, the 
directory is created with the open permissions (777,  drwxrwxrwx) via the 
packages install_helper.sh post install script.  However if Ambari installs the 
agent via SSH, the directory is created with the m

[jira] [Commented] (AMBARI-12563) Ambari return fail upon service check

[Hudson (JIRA)]

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

Hudson commented on AMBARI-12563:
-

FAILURE: Integrated in Ambari-trunk-Commit #3220 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3220/])
AMBARI-12563.  Ambari alert return connection refuse because of motd (aonishuk) 
(aonishuk: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=000848949cd0b7d96bfd2ff56d56bc484c24c937)
* 
ambari-common/src/main/python/resource_management/libraries/functions/curl_krb_request.py


> Ambari return fail upon service check 
> --
>
> Key: AMBARI-12563
> URL: https://issues.apache.org/jira/browse/AMBARI-12563
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.1.1
>
>
> User has a third party monitoring tool that, whenever user do a
> 'su' it prints out the following message
> Hello user, have fun!
> Therefore, for example when user starts up namenode, Ambari is not able to
> phrase the status codes after executing the curl call for webHDFS, and throw
> error message and indicates the operation as fail. Meanwhile, the namenode is
> actually up and running.  
> This behavior also happens across other services, such as HBase.
> This issue is causing confusion upon starting of
> services/components.



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

Re: Review Request 36895: Cluster creates stuck at 9x% (deadlock sql exception)

[Jonathan Hurley]

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

(Updated Aug. 4, 2015, 3:45 p.m.)


Review request for Ambari, Alejandro Fernandez, Nate Cole, and Sumit Mohanty.


Changes
---

Includes the UpgradeCatalog220 work now.


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


Repository: ambari


Description
---

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.

- We have dual X-locks on hostcomponentstate asking for U-locks when updating 
the CLUSTERED INDEX.
- Both dual X-locks, from different transactions and different processes, are 
on the same row (technically impossible) - based on the XML execution plan, we 
can see that the concurrent UPDATE statements are executing on different rows 
due to their CLUSTERED INDEX predicate.
- In Java, Ambari has locks which prevent concurrent U- or X-locks on the same 
row
- Only happens on SQL Server

My best suspicion right now is that we have a key hash collision happening on 
this table. That's why two processes appear to have the same lock even though 
they are on different rows.

Restricting row-level locking on this table will prevent locking on hash keys 
which could collide.


Diffs (updated)
-

  
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/HostComponentStateDAO.java
 fb585fd 
  
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/HostComponentStateEntity.java
 45e036b 
  
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/HostComponentStateEntityPK.java
 86e0dee 
  
ambari-server/src/main/java/org/apache/ambari/server/state/svccomphost/ServiceComponentHostImpl.java
 0850a79 
  
ambari-server/src/main/java/org/apache/ambari/server/upgrade/AbstractUpgradeCatalog.java
 edb1606 
  
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog220.java
 4eb7a80 
  ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql 1b67b24 
  ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql 16f6a0a 
  ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql cd6e27a 
  ambari-server/src/main/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql 
c7138be 
  ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql 0ff1aff 
  
ambari-server/src/test/java/org/apache/ambari/server/state/ServiceComponentTest.java
 96bbb1d 
  
ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ClustersTest.java
 ce1fd34 
  
ambari-server/src/test/java/org/apache/ambari/server/state/svccomphost/ServiceComponentHostTest.java
 f6ab0ec 
  
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog170Test.java
 93f7f8c 
  
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog200Test.java
 484c18d 

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


Testing (updated)
---

Deployed numerous clusters on PostgresSQL, SQL Server, and MySQL using both the 
Ambari UI and blueprints. Upgraded a 2.1 database on PostgresSQL, Oracle, 
MySQL, and SQL Server to verify that changes to the `hostcomponentstate` table 
were good.


Thanks,

Jonathan Hurley

[jira] [Updated] (AMBARI-12582) Some properties on Kerberos configs tab are empty although the same properties on services configs are filled

[Robert Levas (JIRA)]

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

Robert Levas updated AMBARI-12582:
--
Fix Version/s: (was: 2.1.1)
   2.1.2

> Some properties on Kerberos configs tab are empty although the same 
> properties on services configs are filled
> -
>
> Key: AMBARI-12582
> URL: https://issues.apache.org/jira/browse/AMBARI-12582
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.1.2
>
> Attachments: AMBARI-12582.patch, kerberosConfigs.png, 
> serviceConfig.png
>
>
> Steps:
> # Deploy cluster.
> # Enable security.
> Result: some properties on Kerberos configs tab are empty although the same 
> properties on services configs are filled.
> This issue is for a lot another properties.



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

[jira] [Reopened] (AMBARI-12582) Some properties on Kerberos configs tab are empty although the same properties on services configs are filled

[Robert Levas (JIRA)]

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

Robert Levas reopened AMBARI-12582:
---

Reverted because this fix is not totally appropriate.  Adding a field to better 
handle generating auth-to-local ruleset creation for _user_ realms is in order. 

Reverted from trunk
{noformat}
commit 1c58762886c323f9a024e9d463a646243119e5df
Author: Robert Levas 
Date:   Tue Aug 4 15:36:01 2015 -0400
{noformat}

Reverted from branch-2.1
{noformat}
commit 59c661711550500a0a5c5c7f4cf1bdcd8974fae9
Author: Robert Levas 
Date:   Tue Aug 4 15:34:10 2015 -0400
{noformat}

> Some properties on Kerberos configs tab are empty although the same 
> properties on services configs are filled
> -
>
> Key: AMBARI-12582
> URL: https://issues.apache.org/jira/browse/AMBARI-12582
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.1.1
>
> Attachments: AMBARI-12582.patch, kerberosConfigs.png, 
> serviceConfig.png
>
>
> Steps:
> # Deploy cluster.
> # Enable security.
> Result: some properties on Kerberos configs tab are empty although the same 
> properties on services configs are filled.
> This issue is for a lot another properties.



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

Review Request 37093: When regenerating Kerberos principals, ensure Kerberos Descriptor changes are applied to services

[Robert Levas]

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

Review request for Ambari, Dmytro Sen, Jonathan Hurley, John Speidel, and 
Robert Nettleton.


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


Repository: ambari


Description
---

When regenerating Kerberos principals, ensure Kerberos Descriptor changes are 
applied to services.  

It is possible for changes to be made to the Kerberos Descriptor.  One way to 
propagate these changes into the service configurations is to process the 
Kerberos Descriptor and update service configurations while performing tasks 
for the "Regenerate Keytabs" operation.


Diffs
-

  
ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelperImpl.java
 d9ae5d5 
  
ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/KerberosServerAction.java
 57e5527 
  
ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/PrepareEnableKerberosServerAction.java
 9caf7df 
  
ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/PrepareKerberosIdentitiesServerAction.java
 55f75ad 
  
ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/UpdateKerberosConfigsServerAction.java
 f2484e6 
  
ambari-server/src/test/java/org/apache/ambari/server/controller/KerberosHelperTest.java
 467c3ac 

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


Testing
---

Manually tested on trunk and branch-2.1

#Local test results:
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 48:04.515s
[INFO] Finished at: Tue Aug 04 15:09:21 EDT 2015
[INFO] Final Memory: 65M/1376M
[INFO] 

#Jenkins test results: PENDING


Thanks,

Robert Levas

[jira] [Updated] (AMBARI-12604) When regenerating Kerberos principals, ensure Kerberos Descriptor changes are applied to services

[Robert Levas (JIRA)]

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

Robert Levas updated AMBARI-12604:
--
Fix Version/s: 2.2.0

> When regenerating Kerberos principals, ensure Kerberos Descriptor changes are 
> applied to services
> -
>
> Key: AMBARI-12604
> URL: https://issues.apache.org/jira/browse/AMBARI-12604
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.0.1, 2.1.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: kerberos, kerberos_descriptor
> Fix For: 2.2.0, 2.1.1
>
> Attachments: AMBARI-12604_branch-2.1_01.patch, 
> AMBARI-12604_trunk_01.patch
>
>
> When regenerating Kerberos principals, ensure Kerberos Descriptor changes are 
> applied to services.  
> It is possible for changes to be made to the Kerberos Descriptor.  One way to 
> propagate these changes into the service configurations is to process the 
> Kerberos Descriptor and update service configurations while performing tasks 
> for the "Regenerate Keytabs" operation. 



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

[jira] [Updated] (AMBARI-12604) When regenerating Kerberos principals, ensure Kerberos Descriptor changes are applied to services

[Robert Levas (JIRA)]

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

Robert Levas updated AMBARI-12604:
--
Attachment: AMBARI-12604_trunk_01.patch
AMBARI-12604_branch-2.1_01.patch

> When regenerating Kerberos principals, ensure Kerberos Descriptor changes are 
> applied to services
> -
>
> Key: AMBARI-12604
> URL: https://issues.apache.org/jira/browse/AMBARI-12604
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.0.1, 2.1.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: kerberos, kerberos_descriptor
> Fix For: 2.1.1
>
> Attachments: AMBARI-12604_branch-2.1_01.patch, 
> AMBARI-12604_trunk_01.patch
>
>
> When regenerating Kerberos principals, ensure Kerberos Descriptor changes are 
> applied to services.  
> It is possible for changes to be made to the Kerberos Descriptor.  One way to 
> propagate these changes into the service configurations is to process the 
> Kerberos Descriptor and update service configurations while performing tasks 
> for the "Regenerate Keytabs" operation. 



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

[jira] [Commented] (AMBARI-12632) NFSGateway fails to start on Centos6

[Hudson (JIRA)]

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

Hudson commented on AMBARI-12632:
-

FAILURE: Integrated in Ambari-branch-2.1 #319 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/319/])
AMBARI-12632. NFSGateway fails to start on Centos6 (aonishuk) (aonishuk: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f6154f83ce8cc3bfa11b7d4ddf8c24a17074d7f7)
* 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py


> NFSGateway fails to start on Centos6
> 
>
> Key: AMBARI-12632
> URL: https://issues.apache.org/jira/browse/AMBARI-12632
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.1.1
>
>
> stderr
> 
> 
> Traceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
>  line 131, in \nNFSGateway().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 218, in execute\nmethod(env)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
>  line 50, in start\nnfsgateway(action=\"start\")\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
>  line 61, in nfsgateway\nprepare_rpcbind()\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
>  line 52, in prepare_rpcbind\nraise Fail(\"Failed to start rpcbind or 
> portmap\")\nresource_management.core.exceptions.Fail: Failed to start rpcbind 
> or portmap\nTraceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
>  line 131, in \nNFSGateway().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 218, in execute\nmethod(env)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
>  line 50, in start\nnfsgateway(action=\"start\")\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
>  line 61, in nfsgateway\nprepare_rpcbind()\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
>  line 52, in prepare_rpcbind\nraise Fail(\"Failed to start rpcbind or 
> portmap\")\nresource_management.core.exceptions.Fail: Failed to start rpcbind 
> or portmap\nTraceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
>  line 131, in \nNFSGateway().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 218, in execute\nmethod(env)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
>  line 50, in start\nnfsgateway(action=\"start\")\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
>  line 61, in nfsgateway\nprepare_rpcbind()\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
>  line 52, in prepare_rpcbind\nraise Fail(\"Failed to start rpcbind or 
> portmap\")\nresource_management.core.exceptions.Fail: Failed to start rpcbind 
> or portmap\nTraceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
>  line 131, in \nNFSGateway().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 218, in execute\nmethod(env)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
>  line 50, in start\nnfsgateway(action=\"start\")\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
>  line 61, in nfsgateway\nprepare_rpcbind()\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
>  line 52, in prepare_rpcbind\nraise Fail(\"Failed to start rpcbind or 
> portmap\")\nresource_management.core.exceptions.Fail: Failed to start rpcbind 
> or portmap\nTraceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
>  line 131, in \nNFSGateway().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> 

[jira] [Commented] (AMBARI-12633) Yarn SC won't pass with motd enabled

[Hudson (JIRA)]

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

Hudson commented on AMBARI-12633:
-

FAILURE: Integrated in Ambari-branch-2.1 #319 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/319/])
AMBARI-12633. Yarn SC won't pass with motd enabled (aonishuk) (aonishuk: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=41aadeac48e945e07ce709d9e2b9315bfa56d520)
* ambari-server/src/test/python/stacks/2.0.6/YARN/test_yarn_service_check.py
* 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py


> Yarn SC won't pass with motd enabled
> 
>
> Key: AMBARI-12633
> URL: https://issues.apache.org/jira/browse/AMBARI-12633
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.1.1
>
>




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

Re: Review Request 37090: If the "current" stack version status is OUT_OF_SYNC, no version box is displayed on Admin > Stacks > Version page

[Andrew Onischuk]

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

Ship it!


Ship It!

- Andrew Onischuk


On Aug. 4, 2015, 6:05 p.m., Dmitro Lisnichenko wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/37090/
> ---
> 
> (Updated Aug. 4, 2015, 6:05 p.m.)
> 
> 
> Review request for Ambari, Andrew Onischuk and Andrii Tkach.
> 
> 
> Bugs: AMBARI-12635
> https://issues.apache.org/jira/browse/AMBARI-12635
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Under some circumstances, the current stack version can be in OUT_OF_SYNC 
> state. When this happens, no version box is displayed under Admin > Stacks > 
> Versions, even for the current stack version. Current stack version should 
> always be visible.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
>  6b92e87 
>   ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_box_view.js 
> 377db71 
>   ambari-web/app/views/main/admin/stack_upgrade/versions_view.js 0e21794 
>   ambari-web/test/views/main/admin/stack_upgrade/version_view_test.js a46cd0c 
> 
> Diff: https://reviews.apache.org/r/37090/diff/
> 
> 
> Testing
> ---
> 
> [INFO] 
> [INFO] Ambari Web  SUCCESS [34.425s]
> [INFO] Ambari Views .. SUCCESS [2.020s]
> [INFO] Ambari Metrics Common . SUCCESS [1.443s]
> [INFO] Ambari Server . SUCCESS 
> [1:03:45.349s]
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 1:04:23.818s
> [INFO] Finished at: Tue Aug 04 18:19:33 EEST 2015
> [INFO] Final Memory: 56M/372M
> [INFO] 
> 
> 
> 
> Thanks,
> 
> Dmitro Lisnichenko
> 
>

Review Request 37090: If the "current" stack version status is OUT_OF_SYNC, no version box is displayed on Admin > Stacks > Version page

[Dmitro Lisnichenko]

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

Review request for Ambari, Andrew Onischuk and Andrii Tkach.


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


Repository: ambari


Description
---

Under some circumstances, the current stack version can be in OUT_OF_SYNC 
state. When this happens, no version box is displayed under Admin > Stacks > 
Versions, even for the current stack version. Current stack version should 
always be visible.


Diffs
-

  
ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
 6b92e87 
  ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_box_view.js 
377db71 
  ambari-web/app/views/main/admin/stack_upgrade/versions_view.js 0e21794 
  ambari-web/test/views/main/admin/stack_upgrade/version_view_test.js a46cd0c 

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


Testing
---

[INFO] 
[INFO] Ambari Web  SUCCESS [34.425s]
[INFO] Ambari Views .. SUCCESS [2.020s]
[INFO] Ambari Metrics Common . SUCCESS [1.443s]
[INFO] Ambari Server . SUCCESS 
[1:03:45.349s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 1:04:23.818s
[INFO] Finished at: Tue Aug 04 18:19:33 EEST 2015
[INFO] Final Memory: 56M/372M
[INFO] 


Thanks,

Dmitro Lisnichenko

[jira] [Commented] (AMBARI-12633) Yarn SC won't pass with motd enabled

[Hudson (JIRA)]

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

Hudson commented on AMBARI-12633:
-

FAILURE: Integrated in Ambari-trunk-Commit #3219 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3219/])
AMBARI-12633. Yarn SC won't pass with motd enabled (aonishuk) (aonishuk: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=de15d42f0adb0fb50f7f7fe8105046cde75420e5)
* ambari-server/src/test/python/stacks/2.0.6/YARN/test_yarn_service_check.py
* 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py


> Yarn SC won't pass with motd enabled
> 
>
> Key: AMBARI-12633
> URL: https://issues.apache.org/jira/browse/AMBARI-12633
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.1.1
>
>




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

[jira] [Updated] (AMBARI-12635) If the "current" stack version status is OUT_OF_SYNC, no version box is displayed on Admin > Stacks > Version page

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-12635:

Attachment: AMBARI-12635.patch

> If the "current" stack version status is OUT_OF_SYNC, no version box is 
> displayed on Admin > Stacks > Version page
> --
>
> Key: AMBARI-12635
> URL: https://issues.apache.org/jira/browse/AMBARI-12635
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.1.2
>
> Attachments: AMBARI-12635.patch
>
>
> Under some circumstances, the current stack version can be in OUT_OF_SYNC 
> state. When this happens, no version box is displayed under Admin > Stacks > 
> Versions, even for the current stack version. Current stack version should 
> always be visible.



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

[jira] [Created] (AMBARI-12635) If the "current" stack version status is OUT_OF_SYNC, no version box is displayed on Admin > Stacks > Version page

[Dmitry Lysnichenko (JIRA)]

Dmitry Lysnichenko created AMBARI-12635:
---

 Summary: If the "current" stack version status is OUT_OF_SYNC, no 
version box is displayed on Admin > Stacks > Version page
 Key: AMBARI-12635
 URL: https://issues.apache.org/jira/browse/AMBARI-12635
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
 Fix For: 2.1.2


Under some circumstances, the current stack version can be in OUT_OF_SYNC 
state. When this happens, no version box is displayed under Admin > Stacks > 
Versions, even for the current stack version. Current stack version should 
always be visible.



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

[jira] [Commented] (AMBARI-12634) Clear passwords can be seen on Ambari UI service Configs tab via browser developer tool

[Yu Gao (JIRA)]

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

Yu Gao commented on AMBARI-12634:
-

One solution for this issue is to dynamically mask password properties on 
server side before sending it over to its UI/REST client.
   - For get requests that read service configurations - ambari server should 
mask properties of PASSWORD type to stars (like ***)
   - For put/post requests that modify service configurations - ambari server 
replaces the received stars value for properties of PASSWORD type with the 
original value saved in DB (with current implementation in ambari, simply 
removing those masked properties will delete them from DB as well); 
If a PASSWORD property is the one requested to be changed, ambari will accept 
the new values as normal. To protect the newly changed passwords in transit, 
ssl is one way which is already supported by ambari.


> Clear passwords can be seen on Ambari UI service Configs tab via browser 
> developer tool
> ---
>
> Key: AMBARI-12634
> URL: https://issues.apache.org/jira/browse/AMBARI-12634
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: 2.1.0
>Reporter: Yu Gao
>  Labels: security
>
> HTML password type hides passwords with  on the service Configs page. 
> However, everyone including non-admin users who has ambari access with 
> READ-ONLY permission can see the real content of the passwords through 
> developer tools, like firebug in firefox.



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

[jira] [Updated] (AMBARI-12634) Clear passwords can be seen on Ambari UI service Configs tab via browser developer tool

[Yu Gao (JIRA)]

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

Yu Gao updated AMBARI-12634:

Issue Type: Improvement  (was: Bug)

> Clear passwords can be seen on Ambari UI service Configs tab via browser 
> developer tool
> ---
>
> Key: AMBARI-12634
> URL: https://issues.apache.org/jira/browse/AMBARI-12634
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: 2.1.0
>Reporter: Yu Gao
>  Labels: security
>
> HTML password type hides passwords with  on the service Configs page. 
> However, everyone including non-admin users who has ambari access with 
> READ-ONLY permission can see the real content of the passwords through 
> developer tools, like firebug in firefox.



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

[jira] [Commented] (AMBARI-7656) Add support for Hbase REST API

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-7656:
---

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

This message is automatically generated.

> Add support for Hbase REST API
> --
>
> Key: AMBARI-7656
> URL: https://issues.apache.org/jira/browse/AMBARI-7656
> Project: Ambari
>  Issue Type: New Feature
>Reporter: Marcus Young
> Attachments: AMBARI-7656.patch, AMBARI-7656.patch, 
> hbase_restgatewayserver.py
>
>
> There is currently no first-class Hbase REST API support out of the box for 
> Ambari. It would be nice to have it install as part of the setup, so that it 
> can be managed via Ganglia, and propagate to every node in a cluster.



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

[jira] [Created] (AMBARI-12634) Clear passwords can be seen on Ambari UI service Configs tab via browser developer tool

[Yu Gao (JIRA)]

Yu Gao created AMBARI-12634:
---

 Summary: Clear passwords can be seen on Ambari UI service Configs 
tab via browser developer tool
 Key: AMBARI-12634
 URL: https://issues.apache.org/jira/browse/AMBARI-12634
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.1.0
Reporter: Yu Gao


HTML password type hides passwords with  on the service Configs page. 
However, everyone including non-admin users who has ambari access with 
READ-ONLY permission can see the real content of the passwords through 
developer tools, like firebug in firefox.



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

[jira] [Resolved] (AMBARI-12563) Ambari return fail upon service check

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk resolved AMBARI-12563.
--
Resolution: Fixed

Committed to trunk and branch-2.1

> Ambari return fail upon service check 
> --
>
> Key: AMBARI-12563
> URL: https://issues.apache.org/jira/browse/AMBARI-12563
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.1.1
>
>
> User has a third party monitoring tool that, whenever user do a
> 'su' it prints out the following message
> Hello user, have fun!
> Therefore, for example when user starts up namenode, Ambari is not able to
> phrase the status codes after executing the curl call for webHDFS, and throw
> error message and indicates the operation as fail. Meanwhile, the namenode is
> actually up and running.  
> This behavior also happens across other services, such as HBase.
> This issue is causing confusion upon starting of
> services/components.



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

Review Request 37085: Ambari alert return connection refuse because of motd

[Andrew Onischuk]

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

Review request for Ambari and Myroslav Papirkovskyy.


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


Repository: ambari


Description
---

System has a motd message that, whenever user do a 'su' it prints out the
following message



APPROVED PURPOSES ONLY\n SYSTEM ACTIVITIES MAY BE MONITORED

Therefore, for example when user starts up namenode, Ambari is not able to
phrase the status codes after executing the curl call for webHDFS, and throw
error message and indicates the operation as fail. Meanwhile, the namenode is
actually up and running. This behavior also happens across other services,
such as HBase.


Diffs
-

  
ambari-common/src/main/python/resource_management/libraries/functions/curl_krb_request.py
 589ec1e 

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


Testing
---

mvn clean test


Thanks,

Andrew Onischuk

Re: Review Request 37085: Ambari alert return connection refuse because of motd

[Myroslav Papirkovskyy]

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

Ship it!


Ship It!

- Myroslav Papirkovskyy


On Сер. 4, 2015, 7:56 після полудня, Andrew Onischuk wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/37085/
> ---
> 
> (Updated Сер. 4, 2015, 7:56 після полудня)
> 
> 
> Review request for Ambari and Myroslav Papirkovskyy.
> 
> 
> Bugs: AMBARI-12563
> https://issues.apache.org/jira/browse/AMBARI-12563
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> System has a motd message that, whenever user do a 'su' it prints out the
> following message
> 
> 
> 
> APPROVED PURPOSES ONLY\n SYSTEM ACTIVITIES MAY BE MONITORED
> 
> Therefore, for example when user starts up namenode, Ambari is not able to
> phrase the status codes after executing the curl call for webHDFS, and throw
> error message and indicates the operation as fail. Meanwhile, the namenode is
> actually up and running. This behavior also happens across other services,
> such as HBase.
> 
> 
> Diffs
> -
> 
>   
> ambari-common/src/main/python/resource_management/libraries/functions/curl_krb_request.py
>  589ec1e 
> 
> Diff: https://reviews.apache.org/r/37085/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Andrew Onischuk
> 
>

[jira] [Commented] (AMBARI-12631) Load current version and all versions info in parallel requests to reduce service config page loading time.

[Hudson (JIRA)]

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

Hudson commented on AMBARI-12631:
-

FAILURE: Integrated in Ambari-branch-2.1 #318 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/318/])
AMBARI-12631 Load current version and all versions info in parallel requests to 
reduce service config page loading time(additional patch). (ababiichuk) 
(ababiichuk: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6e6919baa24d214ae8e340580fd4e6bbebcdade6)
* ambari-web/test/controllers/main/service/info/config_test.js
* ambari-web/app/controllers/main/service/info/configs.js


> Load current version and all versions info in parallel requests to reduce 
> service config page loading time.
> ---
>
> Key: AMBARI-12631
> URL: https://issues.apache.org/jira/browse/AMBARI-12631
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.1.1
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.1.1
>
> Attachments: AMBARI-12631.patch, AMBARI-12631_1.patch
>
>




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

[jira] [Commented] (AMBARI-12622) Malformed Alert Data Can Prevent Alerts From Reporting

[Hudson (JIRA)]

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

Hudson commented on AMBARI-12622:
-

FAILURE: Integrated in Ambari-branch-2.1 #318 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/318/])
AMBARI-12622 - Malformed Alert Data Can Prevent Alerts From Reporting 
(jonathanhurley) (jhurley: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ad6c5c88dcf3b44a7a94d5fc49d8a0b8f600aba8)
* ambari-agent/src/main/python/ambari_agent/alerts/metric_alert.py
* ambari-agent/src/main/python/ambari_agent/alerts/base_alert.py
* ambari-agent/src/test/python/ambari_agent/TestAlerts.py
* ambari-agent/src/main/python/ambari_agent/AlertSchedulerHandler.py


> Malformed Alert Data Can Prevent Alerts From Reporting
> --
>
> Key: AMBARI-12622
> URL: https://issues.apache.org/jira/browse/AMBARI-12622
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.0.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.1.1
>
> Attachments: AMBARI-12622.patch
>
>
> If there is malformed template text in an alert definition, it will prevent 
> alerts from being reported correctly:
> {code}
> INFO 2015-07-23 14:10:15,209 scheduler.py:287 - Adding job tentatively -- it 
> will be properly scheduled when the scheduler starts
> INFO 2015-07-23 14:10:15,209 AlertSchedulerHandler.py:318 - [AlertScheduler] 
> Scheduling datanode_process with UUID 43536b17-596a-4f7d-87e6-c9034b2b99bc
> INFO 2015-07-23 14:10:15,209 AlertSchedulerHandler.py:134 - [AlertScheduler] 
> Starting ; 
> currently running: False
> INFO 2015-07-23 14:10:17,219 hostname.py:87 - Read public hostname 
> 'cn105-10.l42scl.hortonworks.com' using socket.getfqdn()
> INFO 2015-07-23 14:11:15,271 logger.py:66 - Execute['export 
> HIVE_CONF_DIR='/usr/hdp/current/hive-metastore/conf/conf.server' ; hive 
> --hiveconf hive.metastore.uris=thrift://cn105-10.l42scl.hortonworks.com:9083  
>--hiveconf hive.metastore.client.connect.retry.delay=1 
> --hiveconf hive.metastore.failure.retries=1 
> --hiveconf hive.metastore.connect.retries=1 --hiveconf 
> hive.metastore.client.socket.timeout=14 --hiveconf 
> hive.execution.engine=mr -e 'show databases;''] {'path': ['/bin/', 
> '/usr/bin/', '/usr/sbin/', '/usr/hdp/current/hive-metastore/bin'], 'user': 
> 'ambari-qa', 'timeout': 30}
> INFO 2015-07-23 14:11:15,274 logger.py:66 - Execute['! beeline -u 
> 'jdbc:hive2://cn105-10.l42scl.hortonworks.com:1/;transportMode=binary' -e 
> '' 2>&1| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid URL''] 
> {'path': ['/bin/', '/usr/bin/', '/usr/lib/hive/bin/', '/usr/sbin/'], 'user': 
> 'ambari-qa', 'timeout': 30}
> INFO 2015-07-23 14:12:15,277 logger.py:66 - Execute['! beeline -u 
> 'jdbc:hive2://cn105-10.l42scl.hortonworks.com:1/;transportMode=binary' -e 
> '' 2>&1| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid URL''] 
> {'path': ['/bin/', '/usr/bin/', '/usr/lib/hive/bin/', '/usr/sbin/'], 'user': 
> 'ambari-qa', 'timeout': 30}
> INFO 2015-07-23 14:12:15,284 logger.py:66 - Execute['export 
> HIVE_CONF_DIR='/usr/hdp/current/hive-metastore/conf/conf.server' ; hive 
> --hiveconf hive.metastore.uris=thrift://cn105-10.l42scl.hortonworks.com:9083  
>--hiveconf hive.metastore.client.connect.retry.delay=1 
> --hiveconf hive.metastore.failure.retries=1 
> --hiveconf hive.metastore.connect.retries=1 --hiveconf 
> hive.metastore.client.socket.timeout=14 --hiveconf 
> hive.execution.engine=mr -e 'show databases;''] {'path': ['/bin/', 
> '/usr/bin/', '/usr/sbin/', '/usr/hdp/current/hive-metastore/bin'], 'user': 
> 'ambari-qa', 'timeout': 30}
> ERROR 2015-07-23 14:12:15,293 scheduler.py:520 - Job 
> "28cad184-0e94-4b19-af31-56ab2c1d0a74 (trigger: interval[0:02:00], next run 
> at: 2015-07-23 14:14:15.207467)" raised an exception
> Traceback (most recent call last):
>   File 
> "/usr/lib/python2.6/site-packages/ambari_agent/apscheduler/scheduler.py", 
> line 512, in _run_job
> retval = job.func(*job.args, **job.kwargs)
>   File 
> "/usr/lib/python2.6/site-packages/ambari_agent/AlertSchedulerHandler.py", 
> line 114, in 
> return lambda: alert_def.collect()
>   File "/usr/lib/python2.6/site-packages/ambari_agent/alerts/base_alert.py", 
> line 153, in collect
> data['text'] = res_base_text.format(*res[1])
> ValueError: Unknown format code 'd' for object of type 'float'
> INFO 2015-07-23 14:13:15,264 logger.py:66 - Execute['export 
> HIVE_CONF_DIR='/usr/hdp/current/hive-metastore/conf/conf.server' ; hive 
> --hiveconf hive.metastore

[jira] [Resolved] (AMBARI-12633) Yarn SC won't pass with motd enabled

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk resolved AMBARI-12633.
--
Resolution: Fixed

Committed to trunk and branch-2.1

> Yarn SC won't pass with motd enabled
> 
>
> Key: AMBARI-12633
> URL: https://issues.apache.org/jira/browse/AMBARI-12633
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.1.1
>
>




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

Re: Review Request 37079: Yarn SC won't pass with motd enabled

[Myroslav Papirkovskyy]

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

Ship it!


Ship It!

- Myroslav Papirkovskyy


On Сер. 4, 2015, 6:53 після полудня, Andrew Onischuk wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/37079/
> ---
> 
> (Updated Сер. 4, 2015, 6:53 після полудня)
> 
> 
> Review request for Ambari and Myroslav Papirkovskyy.
> 
> 
> Bugs: AMBARI-12633
> https://issues.apache.org/jira/browse/AMBARI-12633
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py
>  1d593ba 
>   ambari-server/src/test/python/stacks/2.0.6/YARN/test_yarn_service_check.py 
> 65447c6 
> 
> Diff: https://reviews.apache.org/r/37079/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Andrew Onischuk
> 
>

[jira] [Created] (AMBARI-12633) Yarn SC won't pass with motd enabled

[Andrew Onischuk (JIRA)]

Andrew Onischuk created AMBARI-12633:


 Summary: Yarn SC won't pass with motd enabled
 Key: AMBARI-12633
 URL: https://issues.apache.org/jira/browse/AMBARI-12633
 Project: Ambari
  Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
 Fix For: 2.1.1






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

Review Request 37079: Yarn SC won't pass with motd enabled

[Andrew Onischuk]

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

Review request for Ambari and Myroslav Papirkovskyy.


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


Repository: ambari


Description
---


Diffs
-

  
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py
 1d593ba 
  ambari-server/src/test/python/stacks/2.0.6/YARN/test_yarn_service_check.py 
65447c6 

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


Testing
---

mvn clean test


Thanks,

Andrew Onischuk

[jira] [Commented] (AMBARI-12632) NFSGateway fails to start on Centos6

[Hudson (JIRA)]

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

Hudson commented on AMBARI-12632:
-

FAILURE: Integrated in Ambari-trunk-Commit #3218 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3218/])
AMBARI-12632. NFSGateway fails to start on Centos6 (aonishuk) (aonishuk: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=5da5456256d8a59c75e6a8f5e4cebef25af744b6)
* 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py


> NFSGateway fails to start on Centos6
> 
>
> Key: AMBARI-12632
> URL: https://issues.apache.org/jira/browse/AMBARI-12632
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.1.1
>
>
> stderr
> 
> 
> Traceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
>  line 131, in \nNFSGateway().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 218, in execute\nmethod(env)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
>  line 50, in start\nnfsgateway(action=\"start\")\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
>  line 61, in nfsgateway\nprepare_rpcbind()\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
>  line 52, in prepare_rpcbind\nraise Fail(\"Failed to start rpcbind or 
> portmap\")\nresource_management.core.exceptions.Fail: Failed to start rpcbind 
> or portmap\nTraceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
>  line 131, in \nNFSGateway().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 218, in execute\nmethod(env)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
>  line 50, in start\nnfsgateway(action=\"start\")\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
>  line 61, in nfsgateway\nprepare_rpcbind()\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
>  line 52, in prepare_rpcbind\nraise Fail(\"Failed to start rpcbind or 
> portmap\")\nresource_management.core.exceptions.Fail: Failed to start rpcbind 
> or portmap\nTraceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
>  line 131, in \nNFSGateway().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 218, in execute\nmethod(env)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
>  line 50, in start\nnfsgateway(action=\"start\")\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
>  line 61, in nfsgateway\nprepare_rpcbind()\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
>  line 52, in prepare_rpcbind\nraise Fail(\"Failed to start rpcbind or 
> portmap\")\nresource_management.core.exceptions.Fail: Failed to start rpcbind 
> or portmap\nTraceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
>  line 131, in \nNFSGateway().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 218, in execute\nmethod(env)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
>  line 50, in start\nnfsgateway(action=\"start\")\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
>  line 61, in nfsgateway\nprepare_rpcbind()\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
>  line 52, in prepare_rpcbind\nraise Fail(\"Failed to start rpcbind or 
> portmap\")\nresource_management.core.exceptions.Fail: Failed to start rpcbind 
> or portmap\nTraceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
>  line 131, in \nNFSGateway().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py

[jira] [Resolved] (AMBARI-12632) NFSGateway fails to start on Centos6

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk resolved AMBARI-12632.
--
Resolution: Fixed

Committed to trunk and branch-2.1

> NFSGateway fails to start on Centos6
> 
>
> Key: AMBARI-12632
> URL: https://issues.apache.org/jira/browse/AMBARI-12632
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.1.1
>
>
> stderr
> 
> 
> Traceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
>  line 131, in \nNFSGateway().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 218, in execute\nmethod(env)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
>  line 50, in start\nnfsgateway(action=\"start\")\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
>  line 61, in nfsgateway\nprepare_rpcbind()\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
>  line 52, in prepare_rpcbind\nraise Fail(\"Failed to start rpcbind or 
> portmap\")\nresource_management.core.exceptions.Fail: Failed to start rpcbind 
> or portmap\nTraceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
>  line 131, in \nNFSGateway().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 218, in execute\nmethod(env)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
>  line 50, in start\nnfsgateway(action=\"start\")\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
>  line 61, in nfsgateway\nprepare_rpcbind()\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
>  line 52, in prepare_rpcbind\nraise Fail(\"Failed to start rpcbind or 
> portmap\")\nresource_management.core.exceptions.Fail: Failed to start rpcbind 
> or portmap\nTraceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
>  line 131, in \nNFSGateway().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 218, in execute\nmethod(env)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
>  line 50, in start\nnfsgateway(action=\"start\")\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
>  line 61, in nfsgateway\nprepare_rpcbind()\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
>  line 52, in prepare_rpcbind\nraise Fail(\"Failed to start rpcbind or 
> portmap\")\nresource_management.core.exceptions.Fail: Failed to start rpcbind 
> or portmap\nTraceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
>  line 131, in \nNFSGateway().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 218, in execute\nmethod(env)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
>  line 50, in start\nnfsgateway(action=\"start\")\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
>  line 61, in nfsgateway\nprepare_rpcbind()\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
>  line 52, in prepare_rpcbind\nraise Fail(\"Failed to start rpcbind or 
> portmap\")\nresource_management.core.exceptions.Fail: Failed to start rpcbind 
> or portmap\nTraceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
>  line 131, in \nNFSGateway().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 218, in execute\nmethod(env)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
>  line 50, in start\nnfsgateway(action=\"start\")\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
>  line 61, in nfsgateway\nprepare_rpcbind()\n  File 
> \"

Re: [VOTE] Apache Ambari Release 2.0.2 RC2

[Mahadev Konar]

+1

On 8/3/15, 6:39 PM, "Alejandro Fernandez"  wrote:

>Hi,
>
>I have created an Apache Ambari 2.0.2 Release Candidate (RC2). This is a
>maintenance release for branch-2.0.maint
>
>GIT source tag:
>*https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=log;h=
>refs/tags/release-2.0.2-rc2
>refs/tags/release-2.0.2-rc2>*
>
>Staging site: http://people.apache.org/~alejandro/apache-ambari-2.0.2-rc2/
>
>PGP release key used (signed using 392F57AC):
>http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x2147F220392F57AC
>
>Updated KEYS file: https://dist.apache.org/repos/dist/release/ambari/KEYS
>
>One can look into the issues fixed in this release at
>https://issues.apache.org/jira/browse/AMBARI/fixforversion/12332747
>Total 2.0.2 JIRAs: 13
>Total JIRAs Resolved as Fixed: 13
>
>Vote will be open for 72 hours.
>[ ] +1 approve
>[ ] +0 no opinion
>[ ] -1 disapprove (and reason why)
>
>Here's my vote to start: +1
>
>Here's how to verify the tarball hashes:
>
>git clone --branch release-2.0.2-rc2
>https://git-wip-us.apache.org/repos/asf/ambari.git apache-ambari-2.0.2-src
>cd apache-ambari-2.0.2-src
>git clean -xdf
>cd ambari-web
>npm install
>ulimit -n 2048
>brunch build
>rm -rf node_modules
>mv public public-static
>cd ../..
>tar --exclude=.git --exclude=.gitignore --exclude=.gitattributes -zcvf
>apache-ambari-2.0.2-src.tar.gz apache-ambari-2.0.2-src
>
># Verify my signature,
>gpg --verify apache-ambari-2.0.2-src.tar.gz.asc
>apache-ambari-2.0.2-src.tar.gz
>gpg: Signature made Fri Jul 31 18:36:49 2015 PDT using RSA key ID 392F57AC
>gpg: Good signature from "Alejandro Fernandez (Apache Ambari Release
>Management) "
>
>openssl md5 apache-ambari-2.0.2-src.tar.gz >
>apache-ambari-2.0.2-src.tar.gz.md5# and compare to the file I provided
>openssl sha1 apache-ambari-2.0.2-src.tar.gz >
>apache-ambari-2.0.2-src.tar.gz.sha1  # and compare to the file I provided
>
># I made sure ratcheck passes
>cp -R apache-ambari-2.0.2-src apache-ambari-2.0.2-ratcheck
>cd apache-ambari-2.0.2-ratcheck
>mvn clean apache-rat:check
>
>Thanks,
>Alejandro Fernandez
>Apache Ambari PMC

Re: Review Request 37078: NFSGateway fails to start on Centos6

[Myroslav Papirkovskyy]

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

Ship it!


Ship It!

- Myroslav Papirkovskyy


On Сер. 4, 2015, 6:11 після полудня, Andrew Onischuk wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/37078/
> ---
> 
> (Updated Сер. 4, 2015, 6:11 після полудня)
> 
> 
> Review request for Ambari and Myroslav Papirkovskyy.
> 
> 
> Bugs: AMBARI-12632
> https://issues.apache.org/jira/browse/AMBARI-12632
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> stderr
> 
> 
> 
> Traceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
>  line 131, in \nNFSGateway().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 218, in execute\nmethod(env)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
>  line 50, in start\nnfsgateway(action=\"start\")\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
>  line 61, in nfsgateway\nprepare_rpcbind()\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
>  line 52, in prepare_rpcbind\nraise Fail(\"Failed to start rpcbind or 
> portmap\")\nresource_management.core.exceptions.Fail: Failed to start rpcbind 
> or portmap\nTraceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1
 .0.2.0/package/scripts/nfsgateway.py\", line 131, in \n
NFSGateway().execute()\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
 line 218, in execute\nmethod(env)\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
 line 50, in start\nnfsgateway(action=\"start\")\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
 line 61, in nfsgateway\nprepare_rpcbind()\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
 line 52, in prepare_rpcbind\nraise Fail(\"Failed to start rpcbind or 
portmap\")\nresource_management.core.exceptions.Fail: Failed to start rpcbind 
or portmap\nTraceback (most recent call last):\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
 line 131, in \nNFSGateway().execute()\n  File \"/u
 
sr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
 line 218, in execute\nmethod(env)\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
 line 50, in start\nnfsgateway(action=\"start\")\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
 line 61, in nfsgateway\nprepare_rpcbind()\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
 line 52, in prepare_rpcbind\nraise Fail(\"Failed to start rpcbind or 
portmap\")\nresource_management.core.exceptions.Fail: Failed to start rpcbind 
or portmap\nTraceback (most recent call last):\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
 line 131, in \nNFSGateway().execute()\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
 line 218, in execute\
 nmethod(env)\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
 line 50, in start\nnfsgateway(action=\"start\")\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
 line 61, in nfsgateway\nprepare_rpcbind()\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
 line 52, in prepare_rpcbind\nraise Fail(\"Failed to start rpcbind or 
portmap\")\nresource_management.core.exceptions.Fail: Failed to start rpcbind 
or portmap\nTraceback (most recent call last):\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
 line 131, in \nNFSGateway().execute()\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
 line 218, in execute\nmethod(env)\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/
 nfsgateway.py\", line 50, in start\nnfsgateway(action=\"start\")\n  File 
\"/var/lib/ambari-agent/cache/common-servi

Review Request 37078: NFSGateway fails to start on Centos6

[Andrew Onischuk]

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

Review request for Ambari and Myroslav Papirkovskyy.


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


Repository: ambari


Description
---

stderr



Traceback (most recent call last):\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
 line 131, in \nNFSGateway().execute()\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
 line 218, in execute\nmethod(env)\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
 line 50, in start\nnfsgateway(action=\"start\")\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
 line 61, in nfsgateway\nprepare_rpcbind()\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
 line 52, in prepare_rpcbind\nraise Fail(\"Failed to start rpcbind or 
portmap\")\nresource_management.core.exceptions.Fail: Failed to start rpcbind 
or portmap\nTraceback (most recent call last):\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0
 .2.0/package/scripts/nfsgateway.py\", line 131, in \n
NFSGateway().execute()\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
 line 218, in execute\nmethod(env)\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
 line 50, in start\nnfsgateway(action=\"start\")\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
 line 61, in nfsgateway\nprepare_rpcbind()\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
 line 52, in prepare_rpcbind\nraise Fail(\"Failed to start rpcbind or 
portmap\")\nresource_management.core.exceptions.Fail: Failed to start rpcbind 
or portmap\nTraceback (most recent call last):\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
 line 131, in \nNFSGateway().execute()\n  File \"/usr
 /lib/python2.6/site-packages/resource_management/libraries/script/script.py\", 
line 218, in execute\nmethod(env)\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
 line 50, in start\nnfsgateway(action=\"start\")\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
 line 61, in nfsgateway\nprepare_rpcbind()\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
 line 52, in prepare_rpcbind\nraise Fail(\"Failed to start rpcbind or 
portmap\")\nresource_management.core.exceptions.Fail: Failed to start rpcbind 
or portmap\nTraceback (most recent call last):\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
 line 131, in \nNFSGateway().execute()\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
 line 218, in execute\n 
method(env)\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
 line 50, in start\nnfsgateway(action=\"start\")\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
 line 61, in nfsgateway\nprepare_rpcbind()\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
 line 52, in prepare_rpcbind\nraise Fail(\"Failed to start rpcbind or 
portmap\")\nresource_management.core.exceptions.Fail: Failed to start rpcbind 
or portmap\nTraceback (most recent call last):\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
 line 131, in \nNFSGateway().execute()\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
 line 218, in execute\nmethod(env)\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nf
 sgateway.py\", line 50, in start\nnfsgateway(action=\"start\")\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
 line 61, in nfsgateway\nprepare_rpcbind()\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
 line 52, in prepare_rpcbind\nraise Fail(\"Failed to start rpcbind or 
portmap\")\nresource_management.core.exceptions.Fail: Failed to start rpcbind 
or portmap\nTraceback (most recent call last):\n  File 
\"/var/lib/ambari-agent/cache/common-serv

[jira] [Created] (AMBARI-12632) NFSGateway fails to start on Centos6

[Andrew Onischuk (JIRA)]

Andrew Onischuk created AMBARI-12632:


 Summary: NFSGateway fails to start on Centos6
 Key: AMBARI-12632
 URL: https://issues.apache.org/jira/browse/AMBARI-12632
 Project: Ambari
  Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
 Fix For: 2.1.1


stderr



Traceback (most recent call last):\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
 line 131, in \nNFSGateway().execute()\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
 line 218, in execute\nmethod(env)\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
 line 50, in start\nnfsgateway(action=\"start\")\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
 line 61, in nfsgateway\nprepare_rpcbind()\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
 line 52, in prepare_rpcbind\nraise Fail(\"Failed to start rpcbind or 
portmap\")\nresource_management.core.exceptions.Fail: Failed to start rpcbind 
or portmap\nTraceback (most recent call last):\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
 line 131, in \nNFSGateway().execute()\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
 line 218, in execute\nmethod(env)\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
 line 50, in start\nnfsgateway(action=\"start\")\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
 line 61, in nfsgateway\nprepare_rpcbind()\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
 line 52, in prepare_rpcbind\nraise Fail(\"Failed to start rpcbind or 
portmap\")\nresource_management.core.exceptions.Fail: Failed to start rpcbind 
or portmap\nTraceback (most recent call last):\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
 line 131, in \nNFSGateway().execute()\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
 line 218, in execute\nmethod(env)\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
 line 50, in start\nnfsgateway(action=\"start\")\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
 line 61, in nfsgateway\nprepare_rpcbind()\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
 line 52, in prepare_rpcbind\nraise Fail(\"Failed to start rpcbind or 
portmap\")\nresource_management.core.exceptions.Fail: Failed to start rpcbind 
or portmap\nTraceback (most recent call last):\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
 line 131, in \nNFSGateway().execute()\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
 line 218, in execute\nmethod(env)\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
 line 50, in start\nnfsgateway(action=\"start\")\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
 line 61, in nfsgateway\nprepare_rpcbind()\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
 line 52, in prepare_rpcbind\nraise Fail(\"Failed to start rpcbind or 
portmap\")\nresource_management.core.exceptions.Fail: Failed to start rpcbind 
or portmap\nTraceback (most recent call last):\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
 line 131, in \nNFSGateway().execute()\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
 line 218, in execute\nmethod(env)\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py\",
 line 50, in start\nnfsgateway(action=\"start\")\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
 line 61, in nfsgateway\nprepare_rpcbind()\n  File 
\"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py\",
 line 52, in prepare_rpcbind\nraise Fail(\"Failed to start rpcbind or 
portmap\")\nresource_management.core.exceptions.Fail: Failed to start rpcbind 
or portmap\nTraceback (most recent call last):\n  File 
\"/var/lib/ambari-agent/cache/

[jira] [Commented] (AMBARI-12622) Malformed Alert Data Can Prevent Alerts From Reporting

[Hudson (JIRA)]

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

Hudson commented on AMBARI-12622:
-

FAILURE: Integrated in Ambari-trunk-Commit #3217 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3217/])
AMBARI-12622 - Malformed Alert Data Can Prevent Alerts From Reporting 
(jonathanhurley) (jhurley: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=5dbb0e1b87a8720a1e20920190a552193ed90bf4)
* ambari-agent/src/main/python/ambari_agent/alerts/metric_alert.py
* ambari-agent/src/test/python/ambari_agent/TestAlerts.py
* ambari-agent/src/main/python/ambari_agent/AlertSchedulerHandler.py
* ambari-agent/src/main/python/ambari_agent/alerts/base_alert.py


> Malformed Alert Data Can Prevent Alerts From Reporting
> --
>
> Key: AMBARI-12622
> URL: https://issues.apache.org/jira/browse/AMBARI-12622
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.0.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.1.1
>
> Attachments: AMBARI-12622.patch
>
>
> If there is malformed template text in an alert definition, it will prevent 
> alerts from being reported correctly:
> {code}
> INFO 2015-07-23 14:10:15,209 scheduler.py:287 - Adding job tentatively -- it 
> will be properly scheduled when the scheduler starts
> INFO 2015-07-23 14:10:15,209 AlertSchedulerHandler.py:318 - [AlertScheduler] 
> Scheduling datanode_process with UUID 43536b17-596a-4f7d-87e6-c9034b2b99bc
> INFO 2015-07-23 14:10:15,209 AlertSchedulerHandler.py:134 - [AlertScheduler] 
> Starting ; 
> currently running: False
> INFO 2015-07-23 14:10:17,219 hostname.py:87 - Read public hostname 
> 'cn105-10.l42scl.hortonworks.com' using socket.getfqdn()
> INFO 2015-07-23 14:11:15,271 logger.py:66 - Execute['export 
> HIVE_CONF_DIR='/usr/hdp/current/hive-metastore/conf/conf.server' ; hive 
> --hiveconf hive.metastore.uris=thrift://cn105-10.l42scl.hortonworks.com:9083  
>--hiveconf hive.metastore.client.connect.retry.delay=1 
> --hiveconf hive.metastore.failure.retries=1 
> --hiveconf hive.metastore.connect.retries=1 --hiveconf 
> hive.metastore.client.socket.timeout=14 --hiveconf 
> hive.execution.engine=mr -e 'show databases;''] {'path': ['/bin/', 
> '/usr/bin/', '/usr/sbin/', '/usr/hdp/current/hive-metastore/bin'], 'user': 
> 'ambari-qa', 'timeout': 30}
> INFO 2015-07-23 14:11:15,274 logger.py:66 - Execute['! beeline -u 
> 'jdbc:hive2://cn105-10.l42scl.hortonworks.com:1/;transportMode=binary' -e 
> '' 2>&1| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid URL''] 
> {'path': ['/bin/', '/usr/bin/', '/usr/lib/hive/bin/', '/usr/sbin/'], 'user': 
> 'ambari-qa', 'timeout': 30}
> INFO 2015-07-23 14:12:15,277 logger.py:66 - Execute['! beeline -u 
> 'jdbc:hive2://cn105-10.l42scl.hortonworks.com:1/;transportMode=binary' -e 
> '' 2>&1| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid URL''] 
> {'path': ['/bin/', '/usr/bin/', '/usr/lib/hive/bin/', '/usr/sbin/'], 'user': 
> 'ambari-qa', 'timeout': 30}
> INFO 2015-07-23 14:12:15,284 logger.py:66 - Execute['export 
> HIVE_CONF_DIR='/usr/hdp/current/hive-metastore/conf/conf.server' ; hive 
> --hiveconf hive.metastore.uris=thrift://cn105-10.l42scl.hortonworks.com:9083  
>--hiveconf hive.metastore.client.connect.retry.delay=1 
> --hiveconf hive.metastore.failure.retries=1 
> --hiveconf hive.metastore.connect.retries=1 --hiveconf 
> hive.metastore.client.socket.timeout=14 --hiveconf 
> hive.execution.engine=mr -e 'show databases;''] {'path': ['/bin/', 
> '/usr/bin/', '/usr/sbin/', '/usr/hdp/current/hive-metastore/bin'], 'user': 
> 'ambari-qa', 'timeout': 30}
> ERROR 2015-07-23 14:12:15,293 scheduler.py:520 - Job 
> "28cad184-0e94-4b19-af31-56ab2c1d0a74 (trigger: interval[0:02:00], next run 
> at: 2015-07-23 14:14:15.207467)" raised an exception
> Traceback (most recent call last):
>   File 
> "/usr/lib/python2.6/site-packages/ambari_agent/apscheduler/scheduler.py", 
> line 512, in _run_job
> retval = job.func(*job.args, **job.kwargs)
>   File 
> "/usr/lib/python2.6/site-packages/ambari_agent/AlertSchedulerHandler.py", 
> line 114, in 
> return lambda: alert_def.collect()
>   File "/usr/lib/python2.6/site-packages/ambari_agent/alerts/base_alert.py", 
> line 153, in collect
> data['text'] = res_base_text.format(*res[1])
> ValueError: Unknown format code 'd' for object of type 'float'
> INFO 2015-07-23 14:13:15,264 logger.py:66 - Execute['export 
> HIVE_CONF_DIR='/usr/hdp/current/hive-metastore/conf/conf.server' ; hive 
> --hiveconf hive.met

[jira] [Commented] (AMBARI-12631) Load current version and all versions info in parallel requests to reduce service config page loading time.

[Hudson (JIRA)]

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

Hudson commented on AMBARI-12631:
-

FAILURE: Integrated in Ambari-trunk-Commit #3217 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3217/])
AMBARI-12631 Load current version and all versions info in parallel requests to 
reduce service config page loading time(additional patch). (ababiichuk) 
(ababiichuk: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b5bd53a10744a8ea9cf587fda58f453dd913b163)
* ambari-web/test/controllers/main/service/info/config_test.js
* ambari-web/app/controllers/main/service/info/configs.js


> Load current version and all versions info in parallel requests to reduce 
> service config page loading time.
> ---
>
> Key: AMBARI-12631
> URL: https://issues.apache.org/jira/browse/AMBARI-12631
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.1.1
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.1.1
>
> Attachments: AMBARI-12631.patch, AMBARI-12631_1.patch
>
>




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

[jira] [Commented] (AMBARI-12631) Load current version and all versions info in parallel requests to reduce service config page loading time.

[Hudson (JIRA)]

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

Hudson commented on AMBARI-12631:
-

SUCCESS: Integrated in Ambari-branch-2.1 #317 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/317/])
AMBARI-12631 Load current version and all versions info in parallel requests to 
reduce service config page loading time. (ababiichuk) (ababiichuk: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=db1c23ac39fb308dc44546982ccc90f3ccf69478)
* ambari-web/app/views/common/controls_view.js
* ambari-web/app/templates/common/configs/service_config.hbs
* ambari-web/app/mixins/main/service/configs/preload_requests_chain.js
* ambari-web/app/mixins.js
* ambari-web/app/mappers/configs/stack_config_properties_mapper.js
* ambari-web/app/controllers/main/service/info/configs.js
* ambari-web/test/controllers/main/host/configs_service_test.js
* ambari-web/app/data/HDP2.2/site_properties.js
* ambari-web/app/mixins/common/configs/configs_loader.js
* ambari-web/test/controllers/main/service/info/config_test.js


> Load current version and all versions info in parallel requests to reduce 
> service config page loading time.
> ---
>
> Key: AMBARI-12631
> URL: https://issues.apache.org/jira/browse/AMBARI-12631
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.1.1
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.1.1
>
> Attachments: AMBARI-12631.patch, AMBARI-12631_1.patch
>
>




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

[jira] [Commented] (AMBARI-12627) Ambari 2.0 -> 2.1 LDAP: error code 12

[Hudson (JIRA)]

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

Hudson commented on AMBARI-12627:
-

SUCCESS: Integrated in Ambari-branch-2.1 #317 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/317/])
AMBARI-12627 Ambari 2.0 -> 2.1 LDAP: error code 12 (dsen) (dsen: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=08a1a6eae444f4ae10b2a77c2e14c6a65aa921af)
* 
ambari-server/src/main/java/org/apache/ambari/server/security/authorization/LdapServerProperties.java
* 
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
* 
ambari-server/src/main/java/org/apache/ambari/server/security/ldap/AmbariLdapDataPopulator.java
* 
ambari-server/src/test/java/org/apache/ambari/server/security/ldap/AmbariLdapDataPopulatorTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/LdapSyncEventResourceProvider.java


> Ambari 2.0 -> 2.1 LDAP: error code 12
> -
>
> Key: AMBARI-12627
> URL: https://issues.apache.org/jira/browse/AMBARI-12627
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.1.1
>
> Attachments: AMBARI-12627_2.patch
>
>
> LDAP result pagination works well for large amounts of users needing to be 
> synchronized from Active Directory, which is the  common LDAP implementation. 
> For those using ODSEE 11g, however, it's unsupported. 
> For this reason, it would be beneficial to make this pagination option 
> configurable.
> For turning off ldap search results pagination add 
> authentication.ldap.pagination.enabled=false into ambari.properties file



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

[jira] [Commented] (AMBARI-12631) Load current version and all versions info in parallel requests to reduce service config page loading time.

[Hudson (JIRA)]

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

Hudson commented on AMBARI-12631:
-

SUCCESS: Integrated in Ambari-trunk-Commit #3216 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3216/])
AMBARI-12631 Load current version and all versions info in parallel requests to 
reduce service config page loading time. (ababiichuk) (ababiichuk: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=1063f2dddbb9a7e5f684f888f20ad63eecbed9ea)
* ambari-web/app/views/common/controls_view.js
* ambari-web/test/controllers/main/service/info/config_test.js
* ambari-web/test/controllers/main/host/configs_service_test.js
* ambari-web/app/mappers/configs/stack_config_properties_mapper.js
* ambari-web/app/mixins.js
* ambari-web/app/controllers/main/service/info/configs.js
* ambari-web/app/mixins/common/configs/configs_loader.js
* ambari-web/app/mixins/main/service/configs/preload_requests_chain.js
* ambari-web/app/data/HDP2.2/site_properties.js
* ambari-web/app/templates/common/configs/service_config.hbs


> Load current version and all versions info in parallel requests to reduce 
> service config page loading time.
> ---
>
> Key: AMBARI-12631
> URL: https://issues.apache.org/jira/browse/AMBARI-12631
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.1.1
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.1.1
>
> Attachments: AMBARI-12631.patch, AMBARI-12631_1.patch
>
>




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

[jira] [Commented] (AMBARI-12627) Ambari 2.0 -> 2.1 LDAP: error code 12

[Hudson (JIRA)]

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

Hudson commented on AMBARI-12627:
-

SUCCESS: Integrated in Ambari-trunk-Commit #3216 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3216/])
AMBARI-12627 Ambari 2.0 -> 2.1 LDAP: error code 12 (dsen) (dsen: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f3638bd83a6f2445421e03b2f99eb051873e41b6)
* 
ambari-server/src/main/java/org/apache/ambari/server/security/ldap/AmbariLdapDataPopulator.java
* 
ambari-server/src/main/java/org/apache/ambari/server/security/authorization/LdapServerProperties.java
* 
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/LdapSyncEventResourceProvider.java
* 
ambari-server/src/test/java/org/apache/ambari/server/security/ldap/AmbariLdapDataPopulatorTest.java


> Ambari 2.0 -> 2.1 LDAP: error code 12
> -
>
> Key: AMBARI-12627
> URL: https://issues.apache.org/jira/browse/AMBARI-12627
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.1.1
>
> Attachments: AMBARI-12627_2.patch
>
>
> LDAP result pagination works well for large amounts of users needing to be 
> synchronized from Active Directory, which is the  common LDAP implementation. 
> For those using ODSEE 11g, however, it's unsupported. 
> For this reason, it would be beneficial to make this pagination option 
> configurable.
> For turning off ldap search results pagination add 
> authentication.ldap.pagination.enabled=false into ambari.properties file



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

Re: Review Request 37040: Malformed Alert Data Can Prevent Alerts From Reporting

[Robert Levas]

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

Ship it!


Ship It!

- Robert Levas


On Aug. 4, 2015, 8:57 a.m., Jonathan Hurley wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/37040/
> ---
> 
> (Updated Aug. 4, 2015, 8:57 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Robert Levas, and Sid Wagle.
> 
> 
> Bugs: AMBARI-12622
> https://issues.apache.org/jira/browse/AMBARI-12622
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> If there is malformed template text in an alert definition, it will prevent 
> alerts from being reported correctly.
> 
> 
> Diffs
> -
> 
>   ambari-agent/src/main/python/ambari_agent/AlertSchedulerHandler.py c41397d 
>   ambari-agent/src/main/python/ambari_agent/alerts/base_alert.py 9151796 
>   ambari-agent/src/main/python/ambari_agent/alerts/metric_alert.py 6bcdacd 
>   ambari-agent/src/test/python/ambari_agent/TestAlerts.py 7b64445 
> 
> Diff: https://reviews.apache.org/r/37040/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Jonathan Hurley
> 
>

[jira] [Commented] (AMBARI-12631) Load current version and all versions info in parallel requests to reduce service config page loading time.

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk commented on AMBARI-12631:
---

additional patch committed to trunk and branch 2.1.1

> Load current version and all versions info in parallel requests to reduce 
> service config page loading time.
> ---
>
> Key: AMBARI-12631
> URL: https://issues.apache.org/jira/browse/AMBARI-12631
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.1.1
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.1.1
>
> Attachments: AMBARI-12631.patch, AMBARI-12631_1.patch
>
>




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

[jira] [Commented] (AMBARI-12631) Load current version and all versions info in parallel requests to reduce service config page loading time.

[Andrii Tkach (JIRA)]

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

Andrii Tkach commented on AMBARI-12631:
---

+1 for the additional patch

> Load current version and all versions info in parallel requests to reduce 
> service config page loading time.
> ---
>
> Key: AMBARI-12631
> URL: https://issues.apache.org/jira/browse/AMBARI-12631
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.1.1
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.1.1
>
> Attachments: AMBARI-12631.patch, AMBARI-12631_1.patch
>
>




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

[jira] [Updated] (AMBARI-12631) Load current version and all versions info in parallel requests to reduce service config page loading time.

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk updated AMBARI-12631:
--
Attachment: AMBARI-12631_1.patch

> Load current version and all versions info in parallel requests to reduce 
> service config page loading time.
> ---
>
> Key: AMBARI-12631
> URL: https://issues.apache.org/jira/browse/AMBARI-12631
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.1.1
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.1.1
>
> Attachments: AMBARI-12631.patch, AMBARI-12631_1.patch
>
>




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

[jira] [Commented] (AMBARI-12629) FE: Service summary memory leaks.

[Hudson (JIRA)]

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

Hudson commented on AMBARI-12629:
-

SUCCESS: Integrated in Ambari-branch-2.1 #316 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/316/])
AMBARI-12629. FE: Service summary memory leaks. (alexantonenko) (hiveww: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=96b13e5a46a691b64209522a543b20249a26d885)
* ambari-web/app/views/main/service/info/summary.js
* ambari-web/app/views/main/service/services/yarn.js
* ambari-web/app/views/main/service/services/hbase.js
* ambari-web/app/views/main/service/services/hdfs.js
* ambari-web/app/views/common/chart/linear_time.js
* ambari-web/app/views/main/service/info/components_list_view.js
* ambari-web/app/views/main/service/service.js
* ambari-web/app/templates/main/service/info/summary/master_components.hbs
* ambari-web/app/views/main/service/menu.js
* ambari-web/app/views/common/quick_view_link_view.js
* ambari-web/app/templates/main/service/info/summary/base.hbs


> FE: Service summary memory leaks.
> -
>
> Key: AMBARI-12629
> URL: https://issues.apache.org/jira/browse/AMBARI-12629
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.1.1
>
> Attachments: AMBARI-12629.patch
>
>
> Service summary page leaks differently depends on service type and displayed 
> content like quick links, additional component description, metrics, 
> component status etc.



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

[jira] [Commented] (AMBARI-12629) FE: Service summary memory leaks.

[Hudson (JIRA)]

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

Hudson commented on AMBARI-12629:
-

SUCCESS: Integrated in Ambari-trunk-Commit #3215 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3215/])
AMBARI-12629. FE: Service summary memory leaks. (alexantonenko) (hiveww: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d7b3ec8e1e47f792685630daaa17976ea193ac4e)
* ambari-web/app/views/main/service/menu.js
* ambari-web/app/views/common/chart/linear_time.js
* ambari-web/app/views/main/service/services/hbase.js
* ambari-web/app/views/main/service/info/summary.js
* ambari-web/app/views/main/service/info/components_list_view.js
* ambari-web/app/views/main/service/service.js
* ambari-web/app/views/common/quick_view_link_view.js
* ambari-web/app/views/main/service/services/hdfs.js
* ambari-web/app/views/main/service/services/yarn.js
* ambari-web/app/templates/main/service/info/summary/master_components.hbs
* ambari-web/app/templates/main/service/info/summary/base.hbs


> FE: Service summary memory leaks.
> -
>
> Key: AMBARI-12629
> URL: https://issues.apache.org/jira/browse/AMBARI-12629
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.1.1
>
> Attachments: AMBARI-12629.patch
>
>
> Service summary page leaks differently depends on service type and displayed 
> content like quick links, additional component description, metrics, 
> component status etc.



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

[jira] [Commented] (AMBARI-12631) Load current version and all versions info in parallel requests to reduce service config page loading time.

[Andrii Tkach (JIRA)]

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

Andrii Tkach commented on AMBARI-12631:
---

+1 for the patch

> Load current version and all versions info in parallel requests to reduce 
> service config page loading time.
> ---
>
> Key: AMBARI-12631
> URL: https://issues.apache.org/jira/browse/AMBARI-12631
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.1.1
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.1.1
>
> Attachments: AMBARI-12631.patch
>
>




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

[jira] [Updated] (AMBARI-12631) Load current version and all versions info in parallel requests to reduce service config page loading time.

[Andrii Babiichuk (JIRA)]

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

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

> Load current version and all versions info in parallel requests to reduce 
> service config page loading time.
> ---
>
> Key: AMBARI-12631
> URL: https://issues.apache.org/jira/browse/AMBARI-12631
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.1.1
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.1.1
>
> Attachments: AMBARI-12631.patch
>
>




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

[jira] [Created] (AMBARI-12631) Load current version and all versions info in parallel requests to reduce service config page loading time.

[Andrii Babiichuk (JIRA)]

Andrii Babiichuk created AMBARI-12631:
-

 Summary: Load current version and all versions info in parallel 
requests to reduce service config page loading time.
 Key: AMBARI-12631
 URL: https://issues.apache.org/jira/browse/AMBARI-12631
 Project: Ambari
  Issue Type: Task
  Components: ambari-web
Affects Versions: 2.1.1
Reporter: Andrii Babiichuk
Assignee: Andrii Babiichuk
Priority: Critical
 Fix For: 2.1.1






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

[jira] [Commented] (AMBARI-12627) Ambari 2.0 -> 2.1 LDAP: error code 12

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-12627:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12748636/AMBARI-12627_2.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.

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

This message is automatically generated.

> Ambari 2.0 -> 2.1 LDAP: error code 12
> -
>
> Key: AMBARI-12627
> URL: https://issues.apache.org/jira/browse/AMBARI-12627
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.1.1
>
> Attachments: AMBARI-12627_2.patch
>
>
> LDAP result pagination works well for large amounts of users needing to be 
> synchronized from Active Directory, which is the  common LDAP implementation. 
> For those using ODSEE 11g, however, it's unsupported. 
> For this reason, it would be beneficial to make this pagination option 
> configurable.
> For turning off ldap search results pagination add 
> authentication.ldap.pagination.enabled=false into ambari.properties file



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

[jira] [Commented] (AMBARI-12629) FE: Service summary memory leaks.

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko commented on AMBARI-12629:
--

+1 for the patch

> FE: Service summary memory leaks.
> -
>
> Key: AMBARI-12629
> URL: https://issues.apache.org/jira/browse/AMBARI-12629
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.1.1
>
> Attachments: AMBARI-12629.patch
>
>
> Service summary page leaks differently depends on service type and displayed 
> content like quick links, additional component description, metrics, 
> component status etc.



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

[jira] [Updated] (AMBARI-12629) FE: Service summary memory leaks.

[Antonenko Alexander (JIRA)]

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

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

> FE: Service summary memory leaks.
> -
>
> Key: AMBARI-12629
> URL: https://issues.apache.org/jira/browse/AMBARI-12629
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.1.1
>
> Attachments: AMBARI-12629.patch
>
>
> Service summary page leaks differently depends on service type and displayed 
> content like quick links, additional component description, metrics, 
> component status etc.



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

Review Request 37071: AMBARI-12630 : Handle Ranger KMS install for umask 027

[Gautam Borad]

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

Review request for Ambari, Alejandro Fernandez, Mahadev Konar, Velmurugan 
Periasamy, and Yusaku Sako.


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


Repository: ambari


Description
---

Handle scenario of : Ranger KMS fails to install as jdbc driver has insuffcient 
permissions.


Diffs
-

  
ambari-server/src/main/resources/common-services/RANGER_KMS/0.5.0.2.3/package/scripts/kms.py
 2551ccd 

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


Testing
---

Tested install of Ranger KMS in umask 027 having HDFS, ZooKeeper, Ranger 
installed via Ambari.


Thanks,

Gautam Borad

[jira] [Created] (AMBARI-12630) Handle Ranger KMS install for umask 027

[Gautam Borad (JIRA)]

Gautam Borad created AMBARI-12630:
-

 Summary: Handle Ranger KMS install for umask 027
 Key: AMBARI-12630
 URL: https://issues.apache.org/jira/browse/AMBARI-12630
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.1.0
Reporter: Gautam Borad
Assignee: Gautam Borad


Handle scenario of : Ranger KMS fails to install as jdbc driver has insuffcient 
permissions.




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

Re: Review Request 37059: Ambari 2.0 -> 2.1 LDAP: error code 12

[Dmytro Sen]

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

(Updated Авг. 4, 2015, 9:56 д.п.)


Review request for Ambari and Robert Levas.


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


Repository: ambari


Description
---

LDAP result pagination works well for large amounts of users needing to be 
synchronized from Active Directory, which is the common LDAP implementation. 
For those using ODSEE 11g, however, it's unsupported. 
For this reason, it would be beneficial to make this pagination option 
configurable.
For turning off ldap search results pagination add 
authentication.ldap.pagination.enabled=false into ambari.properties file


Diffs (updated)
-

  
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
 50fc6a6 
  
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/LdapSyncEventResourceProvider.java
 059a228 
  
ambari-server/src/main/java/org/apache/ambari/server/security/authorization/LdapServerProperties.java
 df314f1 
  
ambari-server/src/main/java/org/apache/ambari/server/security/ldap/AmbariLdapDataPopulator.java
 1d8fca1 
  
ambari-server/src/test/java/org/apache/ambari/server/security/ldap/AmbariLdapDataPopulatorTest.java
 fba56f9 

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


Testing (updated)
---

Unit tests passed


Thanks,

Dmytro Sen

[jira] [Updated] (AMBARI-12627) Ambari 2.0 -> 2.1 LDAP: error code 12

[Dmytro Sen (JIRA)]

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

Dmytro Sen updated AMBARI-12627:

Attachment: AMBARI-12627_2.patch

> Ambari 2.0 -> 2.1 LDAP: error code 12
> -
>
> Key: AMBARI-12627
> URL: https://issues.apache.org/jira/browse/AMBARI-12627
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.1.1
>
> Attachments: AMBARI-12627_2.patch
>
>
> LDAP result pagination works well for large amounts of users needing to be 
> synchronized from Active Directory, which is the  common LDAP implementation. 
> For those using ODSEE 11g, however, it's unsupported. 
> For this reason, it would be beneficial to make this pagination option 
> configurable.
> For turning off ldap search results pagination add 
> authentication.ldap.pagination.enabled=false into ambari.properties file



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

[jira] [Updated] (AMBARI-12627) Ambari 2.0 -> 2.1 LDAP: error code 12

[Dmytro Sen (JIRA)]

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

Dmytro Sen updated AMBARI-12627:

Attachment: (was: AMBARI-12627.patch)

> Ambari 2.0 -> 2.1 LDAP: error code 12
> -
>
> Key: AMBARI-12627
> URL: https://issues.apache.org/jira/browse/AMBARI-12627
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.1.1
>
> Attachments: AMBARI-12627_2.patch
>
>
> LDAP result pagination works well for large amounts of users needing to be 
> synchronized from Active Directory, which is the  common LDAP implementation. 
> For those using ODSEE 11g, however, it's unsupported. 
> For this reason, it would be beneficial to make this pagination option 
> configurable.
> For turning off ldap search results pagination add 
> authentication.ldap.pagination.enabled=false into ambari.properties file



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

[jira] [Created] (AMBARI-12629) FE: Service summary memory leaks.

[Antonenko Alexander (JIRA)]

Antonenko Alexander created AMBARI-12629:


 Summary: FE: Service summary memory leaks.
 Key: AMBARI-12629
 URL: https://issues.apache.org/jira/browse/AMBARI-12629
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.1.0
Reporter: Antonenko Alexander
Assignee: Antonenko Alexander
Priority: Critical
 Fix For: 2.1.1


Service summary page leaks differently depends on service type and displayed 
content like quick links, additional component description, metrics, component 
status etc.



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

Re: Review Request 37033: Ranger admin install fails with umask 027

[Gautam Borad]

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

(Updated Aug. 4, 2015, 9:36 a.m.)


Review request for Ambari, Alejandro Fernandez, Mahadev Konar, Velmurugan 
Periasamy, and Yusaku Sako.


Changes
---

Reverting changes needed for ojdbc6.jar


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


Repository: ambari


Description
---

Ranger admin fails to install as jdbc driver has insuffcient permissions


Diffs (updated)
-

  
ambari-common/src/main/python/resource_management/libraries/functions/setup_ranger_plugin.py
 35d4953 
  
ambari-common/src/main/python/resource_management/libraries/functions/setup_ranger_plugin_xml.py
 070dec6 
  
ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/setup_ranger.py
 71996d2 
  
ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/setup_ranger_xml.py
 6f6a02b 

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


Testing
---

Tested Ranger installation on a Ambari based cluster having Ranger (using 
Oracle12 DB), HDFS, Zookeeper.


Thanks,

Gautam Borad

[jira] [Updated] (AMBARI-7656) Add support for Hbase REST API

[xieshiju (JIRA)]

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

xieshiju updated AMBARI-7656:
-
Attachment: AMBARI-7656.patch

this file contain the python file and configure change.

> Add support for Hbase REST API
> --
>
> Key: AMBARI-7656
> URL: https://issues.apache.org/jira/browse/AMBARI-7656
> Project: Ambari
>  Issue Type: New Feature
>Reporter: Marcus Young
> Attachments: AMBARI-7656.patch, AMBARI-7656.patch, 
> hbase_restgatewayserver.py
>
>
> There is currently no first-class Hbase REST API support out of the box for 
> Ambari. It would be nice to have it install as part of the setup, so that it 
> can be managed via Ganglia, and propagate to every node in a cluster.



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