date:20160310

[jira] [Commented] (AMBARI-15375) NPE while gathering JMX ports from configs

2016-03-10 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on AMBARI-15375:


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

This message is automatically generated.

> NPE while gathering JMX ports from configs
> --
>
> Key: AMBARI-15375
> URL: https://issues.apache.org/jira/browse/AMBARI-15375
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Myroslav Papirkovskyy
>Assignee: Myroslav Papirkovskyy
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15375.patch, AMBARI-15375_branch-2.2.patch
>
>
> Sometimes getting JMX ports from configs throws NPE exception.
> {noformat}
> org.apache.ambari.server.controller.spi.SystemException: Caught exception 
> getting JMX metrics : null
>   at 
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider.rethrowSystemException(ThreadPoolEnabledPropertyProvider.java:245)
>   at 
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider.populateResources(ThreadPoolEnabledPropertyProvider.java:155)
>   at 
> org.apache.ambari.server.controller.internal.StackDefinedPropertyProvider.populateResources(StackDefinedPropertyProvider.java:200)
>   at 
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.populateResources(ClusterControllerImpl.java:146)
>   at 
> org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:406)
>   at 
> org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:216)
>   at 
> org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:68)
>   at 
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:135)
>   at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:106)
>   at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:75)
>   at 
> org.apache.ambari.server.api.services.HostComponentService.getHostComponent(HostComponentService.java:89)
>   at sun.reflect.GeneratedMethodAccessor106.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>   at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
>   at 
>

[jira] [Commented] (AMBARI-15368) there are some mistake in vendor.js when insatll hbase

2016-03-10 Thread wuhui (JIRA)


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

wuhui commented on AMBARI-15368:


change the name of the image to hbase_error.png

> there are some mistake in vendor.js when insatll hbase
> --
>
> Key: AMBARI-15368
> URL: https://issues.apache.org/jira/browse/AMBARI-15368
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.1
>Reporter: wuhui
> Fix For: 2.1.1
>
> Attachments: hbase_error.png
>
>
> if you install hbase there will be a error at the step7 in vendor.js which 
> showed uncaught Error: could not respond to event 
> didChangeData in state rootState 



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

[jira] [Updated] (AMBARI-15382) Alert for updating HAWQ namespace after enabling HDFS HA

2016-03-10 Thread Lav Jain (JIRA)


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

Lav Jain updated AMBARI-15382:
--
Fix Version/s: 2.2.2
Affects Version/s: trunk
   Status: Patch Available  (was: Open)

> Alert for updating HAWQ namespace after enabling HDFS HA 
> -
>
> Key: AMBARI-15382
> URL: https://issues.apache.org/jira/browse/AMBARI-15382
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Affects Versions: trunk, 2.2.0
>Reporter: Lav Jain
>Assignee: Lav Jain
>Priority: Minor
> Fix For: 2.2.2
>
> Attachments: AMBARI-15382.branch22.patch, AMBARI-15382.patch, Screen 
> Shot 2016-03-10 at 5.06.47 PM.png, Screen Shot 2016-03-10 at 5.13.41 PM.png
>
>
> Alert user on step1 of the wizard (conditional if HAWQ is installed). Repeat 
> the message when the namenode HA wizard is done.



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

[jira] [Updated] (AMBARI-15368) there are some mistake in vendor.js when insatll hbase

2016-03-10 Thread wuhui (JIRA)


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

wuhui updated AMBARI-15368:
---
Attachment: (was: select-hbase-error.png)

> there are some mistake in vendor.js when insatll hbase
> --
>
> Key: AMBARI-15368
> URL: https://issues.apache.org/jira/browse/AMBARI-15368
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.1
>Reporter: wuhui
> Fix For: 2.1.1
>
>
> if you install hbase there will be a error at the step7 in vendor.js which 
> showed uncaught Error: could not respond to event 
> didChangeData in state rootState 



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

[jira] [Updated] (AMBARI-15297) In the step 2 of install resourcemanager ha ,the hosts showd in mistake

2016-03-10 Thread wuhui (JIRA)


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

wuhui updated AMBARI-15297:
---
Attachment: (was: ra_error.jpg)

> In the step 2 of install resourcemanager ha ,the hosts showd in mistake
> ---
>
> Key: AMBARI-15297
> URL: https://issues.apache.org/jira/browse/AMBARI-15297
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.1
>Reporter: wuhui
> Fix For: 2.1.1
>
>
> In the step 2 of install RM HA,if you select the extra host for the HA 
> host,it will show a error host which not match with the selected host.



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

[jira] [Commented] (AMBARI-15357) Rename Service Action 'HAWQ Check' to 'HAWQ Config Check'

2016-03-10 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on AMBARI-15357:


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

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

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

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

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

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

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

This message is automatically generated.

> Rename Service Action 'HAWQ Check' to 'HAWQ Config Check'
> -
>
> Key: AMBARI-15357
> URL: https://issues.apache.org/jira/browse/AMBARI-15357
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Reporter: Goutam Tadi
>Assignee: Goutam Tadi
>Priority: Minor
> Fix For: 2.2.2
>
> Attachments: AMBARI-15357-trunk.patch, AMBARI-15357-v1.trunk.patch
>
>




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

[jira] [Commented] (AMBARI-15378) Create multiple version state filters instead of one combined one on host page for version page

2016-03-10 Thread Hudson (JIRA)


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

Hudson commented on AMBARI-15378:
-

SUCCESS: Integrated in Ambari-trunk-Commit #4481 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4481/])
AMBARI-15378 Create multiple version state filters instead of one (rzang: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=171379abd1bd525c5ff9693f7e8bc27bc182fec4])
* ambari-web/app/controllers/main/host.js


> Create multiple version state filters instead of one combined one on host 
> page for version page
> ---
>
> Key: AMBARI-15378
> URL: https://issues.apache.org/jira/browse/AMBARI-15378
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
> Fix For: 2.4.0
>
> Attachments: AMBARI-15378.0.patch
>
>
> On version detail of versions page, if click the number of Not Installed 
> hosts, it will try to create filter "Version State: Installing, Installing, 
> Out of Sync", which is not a supported format of combo search box.
> It should create 3 individual filters.



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

[jira] [Commented] (AMBARI-15265) Install & Manage Zeppelin with Ambari

2016-03-10 Thread Hudson (JIRA)


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

Hudson commented on AMBARI-15265:
-

SUCCESS: Integrated in Ambari-trunk-Commit #4481 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4481/])
AMBARI-15265. Install & Manage Zeppelin with Ambari - RAT failure fix 
(smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a9d562171596f7bb9734e41e9c3ab83295205be8])
* 
ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/alert_check_zeppelin.py


> Install & Manage Zeppelin with Ambari
> -
>
> Key: AMBARI-15265
> URL: https://issues.apache.org/jira/browse/AMBARI-15265
> Project: Ambari
>  Issue Type: New Feature
>Reporter: Renjith Kamath
> Fix For: 2.2.2
>
> Attachments: AMBARI-15265_branch-2.2-2.patch, 
> AMBARI-15265_branch-2.2-3.patch, AMBARI-15265_branch-2.2-4.patch, 
> AMBARI-15265_branch-2.2-5.patch, AMBARI-15265_branch-2.2-6.patch, 
> AMBARI-15265_branch-2.2.patch
>
>
> Ambari to support the following scenario for Zeppelin Service
> * Install of Zeppelin
> * Provide start/stop of Zeppelin component
> * Configure Zeppelin with Ambari including Zeppelin LDAP Authentication
> * Ambari to provide Quicklink from Ambari to Zeppelin
> * Ambari to Kerberize a cluster with Zeppelin in it.



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

[jira] [Commented] (AMBARI-15376) Fix typo in get_stack_version

2016-03-10 Thread Hudson (JIRA)


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

Hudson commented on AMBARI-15376:
-

SUCCESS: Integrated in Ambari-trunk-Commit #4481 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4481/])
AMBARI-15376: Fix typo in get_stack_version (jluniya) (jluniya: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7cdb16c1d8e575dc00b71877858abe9d95bdd871])
* 
ambari-common/src/main/python/resource_management/libraries/functions/get_stack_version.py


> Fix typo in get_stack_version
> -
>
> Key: AMBARI-15376
> URL: https://issues.apache.org/jira/browse/AMBARI-15376
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15376.patch
>
>
> Fix a typo introduced in AMBARI-15329 which causes get_stack_version to 
> report stack_version = None.
> 2016-03-10 18:57:13,534 - call['ambari-python-wrap /usr/bin/hdp-select status 
> hadoop-client'] {'timeout': 20}
> 2016-03-10 18:57:13,610 - call returned (0, 'hadoop-client - 2.5.0.0-80')
> 2016-03-10 18:57:13,611 - Failed to get extracted version with 
> /usr/bin/hdp-select



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

[jira] [Updated] (AMBARI-15382) Alert for updating HAWQ namespace after enabling HDFS HA

2016-03-10 Thread Lav Jain (JIRA)


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

Lav Jain updated AMBARI-15382:
--
Attachment: Screen Shot 2016-03-10 at 5.06.47 PM.png
Screen Shot 2016-03-10 at 5.13.41 PM.png

> Alert for updating HAWQ namespace after enabling HDFS HA 
> -
>
> Key: AMBARI-15382
> URL: https://issues.apache.org/jira/browse/AMBARI-15382
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Affects Versions: 2.2.0
>Reporter: Lav Jain
>Assignee: Lav Jain
>Priority: Minor
> Attachments: Screen Shot 2016-03-10 at 5.06.47 PM.png, Screen Shot 
> 2016-03-10 at 5.13.41 PM.png
>
>
> Alert user on step1 of the wizard (conditional if HAWQ is installed). Repeat 
> the message when the namenode HA wizard is done.



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

[jira] [Commented] (AMBARI-15374) Check To Ensure That All Components Are On The Same Version Before Upgrading

2016-03-10 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on AMBARI-15374:


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

This message is automatically generated.

> Check To Ensure That All Components Are On The Same Version Before Upgrading
> 
>
> Key: AMBARI-15374
> URL: https://issues.apache.org/jira/browse/AMBARI-15374
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.2.2
>
> Attachments: AMBARI-15374.patch
>
>
> Before beginning an upgrade, there should be a pre-upgrade check which 
> ensures that all known, versionable components are reporting the same 
> version. If any host component is reporting a version which does not match 
> the current repository version, then a warning should be produced. The 
> warning should provide information on the failed components, the expected 
> version, and the version they are reporting.
> Note that this is only for Ambari 2.2.x; Ambari 2.4.0 uses a new workflow for 
> how versions are recorded and stored during upgrade and does not need this.
> There are two ways to go about this:
> - Compare each service component host version to that of the {{CURRENT}} 
> {{repo_version}}. However, there could be cases where the {{repo_version}} 
> has not been calculated yet.
> - Compare each service component host version to each other.



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

[jira] [Created] (AMBARI-15379) UI Label changes for Ranger KMS and NFSGateway not uniform across pages

2016-03-10 Thread Dhanya Balasundaran (JIRA)

Dhanya Balasundaran created AMBARI-15379:


 Summary: UI Label changes for Ranger KMS and NFSGateway not 
uniform across pages
 Key: AMBARI-15379
 URL: https://issues.apache.org/jira/browse/AMBARI-15379
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.2.2
Reporter: Dhanya Balasundaran
 Fix For: 2.2.2


Recently "Ranger KMS Server" and "NFSGateway" have been changed at few places 
as "Ranger Kms Server" and "Nfs Gateway" and are now not uniform across the 
pages as they used to be hence creating problem in Automation tests.
Below pages are expected to have uniform Label convention
While adding Service in case of both Ranger KMS and NFS Gateway
Also in install wizard assignMasters page
Add Service wizard assignMaster page
(Ranger/HDFS) service page > summary
Hosts Page > add > NFSGateway
Host Page where Ranger KMS Server and NFSGateway are hosted (labels on Host 
details page)
Actual: Add service showing Ranger Kms Server and Nfs Gateway on few Pages
Expected: All Labels should be uniform (Original Labels were : "Ranger KMS 
Server" and "NFSGateway" which were uniform across)



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

[jira] [Updated] (AMBARI-15378) Create multiple version state filters instead of one combined one on host page for version page

2016-03-10 Thread Zhe (Joe) Wang (JIRA)


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

Zhe (Joe) Wang updated AMBARI-15378:

Attachment: AMBARI-15378.0.patch

Local ambari-web test passed.
24562 tests complete (21 seconds)
145 tests pending
Manual testing done.

> Create multiple version state filters instead of one combined one on host 
> page for version page
> ---
>
> Key: AMBARI-15378
> URL: https://issues.apache.org/jira/browse/AMBARI-15378
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
> Fix For: 2.4.0
>
> Attachments: AMBARI-15378.0.patch
>
>
> On version detail of versions page, if click the number of Not Installed 
> hosts, it will try to create filter "Version State: Installing, Installing, 
> Out of Sync", which is not a supported format of combo search box.
> It should create 3 individual filters.



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

[jira] [Updated] (AMBARI-15311) Update descriptions for HAWQ and PXF configurations

2016-03-10 Thread Goutam Tadi (JIRA)


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

Goutam Tadi updated AMBARI-15311:
-
Attachment: AMBARI-15311.v1-trunk.patch

> Update descriptions for HAWQ and PXF configurations
> ---
>
> Key: AMBARI-15311
> URL: https://issues.apache.org/jira/browse/AMBARI-15311
> Project: Ambari
>  Issue Type: Sub-task
>  Components: stacks
>Reporter: Matt
>Assignee: Goutam Tadi
>Priority: Minor
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-15311-trunk.patch, AMBARI-15311.v1-trunk.patch
>
>
> Update the descriptions for HAWQ and PXF configurations so that they are more 
> readable and convey the right message to the user.



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

[jira] [Created] (AMBARI-15378) Create multiple version state filters instead of one combined one on host page for version page

2016-03-10 Thread Zhe (Joe) Wang (JIRA)

Zhe (Joe) Wang created AMBARI-15378:
---

 Summary: Create multiple version state filters instead of one 
combined one on host page for version page
 Key: AMBARI-15378
 URL: https://issues.apache.org/jira/browse/AMBARI-15378
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.4.0
Reporter: Zhe (Joe) Wang
Assignee: Zhe (Joe) Wang
 Fix For: 2.4.0


On version detail of versions page, if click the number of Not Installed hosts, 
it will try to create filter "Version State: Installing, Installing, Out of 
Sync", which is not a supported format of combo search box.
It should create 3 individual filters.



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

[jira] [Updated] (AMBARI-15330) Bubble up errors during RU/EU

2016-03-10 Thread Alejandro Fernandez (JIRA)


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

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

> Bubble up errors during RU/EU
> -
>
> Key: AMBARI-15330
> URL: https://issues.apache.org/jira/browse/AMBARI-15330
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.4.0
>
> Attachments: AMBARI-15330.trunk.patch
>
>
> During RU/EU, need a way to bubble up an error of the current item that 
> failed. This is useful to quickly get a human-readable error that others UIs 
> can quickly retrieve.
> It can print a human-readable error, plus stdout and stderr.
> This would become part of the upgrade endpoint. e.g,
> api/v1/clusters/$name/upgrade_summary/$request_id
> {code}
> {
> attempt_cnt: 1,
> cluster_name: "c1",
> request_id: 1,
> fail_reason: "Failed calling RESTART ZOOKEEPER/ZOOKEEPER_SERVER on host 
> c6401.ambari.apache.org",
> // Notice that the rest are inherited from the failed task if it exists.
> command: "CUSTOM_COMMAND",
> command_detail: "RESTART ZOOKEEPER/ZOOKEEPER_SERVER",
> custom_command_name: "RESTART",
> end_time: -1,
> error_log: "/var/lib/ambari-agent/data/errors-1234.txt",
> exit_code: 1,
> host_name: "c6401.ambari.apache.org",
> id: 1234,
> output_log: "/var/lib/ambari-agent/data/output-1234.txt",
> role: "ZOOKEEPER_SERVER",
> stage_id: 1,
> start_time: 123456789,
> status: "HOLDING_FAILED",
> stdout: "",
> stderr: ""
> }
> {code}



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

[jira] [Updated] (AMBARI-15330) Bubble up errors during RU/EU

2016-03-10 Thread Alejandro Fernandez (JIRA)


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

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

> Bubble up errors during RU/EU
> -
>
> Key: AMBARI-15330
> URL: https://issues.apache.org/jira/browse/AMBARI-15330
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.4.0
>
> Attachments: AMBARI-15330.trunk.patch
>
>
> During RU/EU, need a way to bubble up an error of the current item that 
> failed. This is useful to quickly get a human-readable error that others UIs 
> can quickly retrieve.
> It can print a human-readable error, plus stdout and stderr.
> This would become part of the upgrade endpoint. e.g,
> api/v1/clusters/$name/upgrade_summary/$request_id
> {code}
> {
> attempt_cnt: 1,
> cluster_name: "c1",
> request_id: 1,
> fail_reason: "Failed calling RESTART ZOOKEEPER/ZOOKEEPER_SERVER on host 
> c6401.ambari.apache.org",
> // Notice that the rest are inherited from the failed task if it exists.
> command: "CUSTOM_COMMAND",
> command_detail: "RESTART ZOOKEEPER/ZOOKEEPER_SERVER",
> custom_command_name: "RESTART",
> end_time: -1,
> error_log: "/var/lib/ambari-agent/data/errors-1234.txt",
> exit_code: 1,
> host_name: "c6401.ambari.apache.org",
> id: 1234,
> output_log: "/var/lib/ambari-agent/data/output-1234.txt",
> role: "ZOOKEEPER_SERVER",
> stage_id: 1,
> start_time: 123456789,
> status: "HOLDING_FAILED",
> stdout: "",
> stderr: ""
> }
> {code}



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

[jira] [Updated] (AMBARI-15330) Bubble up errors during RU/EU

2016-03-10 Thread Alejandro Fernandez (JIRA)


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

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

> Bubble up errors during RU/EU
> -
>
> Key: AMBARI-15330
> URL: https://issues.apache.org/jira/browse/AMBARI-15330
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.4.0
>
> Attachments: AMBARI-15330.trunk.patch
>
>
> During RU/EU, need a way to bubble up an error of the current item that 
> failed. This is useful to quickly get a human-readable error that others UIs 
> can quickly retrieve.
> It can print a human-readable error, plus stdout and stderr.
> This would become part of the upgrade endpoint. e.g,
> api/v1/clusters/$name/upgrade_summary/$request_id
> {code}
> {
> attempt_cnt: 1,
> cluster_name: "c1",
> request_id: 1,
> fail_reason: "Failed calling RESTART ZOOKEEPER/ZOOKEEPER_SERVER on host 
> c6401.ambari.apache.org",
> // Notice that the rest are inherited from the failed task if it exists.
> command: "CUSTOM_COMMAND",
> command_detail: "RESTART ZOOKEEPER/ZOOKEEPER_SERVER",
> custom_command_name: "RESTART",
> end_time: -1,
> error_log: "/var/lib/ambari-agent/data/errors-1234.txt",
> exit_code: 1,
> host_name: "c6401.ambari.apache.org",
> id: 1234,
> output_log: "/var/lib/ambari-agent/data/output-1234.txt",
> role: "ZOOKEEPER_SERVER",
> stage_id: 1,
> start_time: 123456789,
> status: "HOLDING_FAILED",
> stdout: "",
> stderr: ""
> }
> {code}



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

[jira] [Updated] (AMBARI-15330) Bubble up errors during RU/EU

2016-03-10 Thread Alejandro Fernandez (JIRA)


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

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

> Bubble up errors during RU/EU
> -
>
> Key: AMBARI-15330
> URL: https://issues.apache.org/jira/browse/AMBARI-15330
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.4.0
>
> Attachments: AMBARI-15330.trunk.patch
>
>
> During RU/EU, need a way to bubble up an error of the current item that 
> failed. This is useful to quickly get a human-readable error that others UIs 
> can quickly retrieve.
> It can print a human-readable error, plus stdout and stderr.
> This would become part of the upgrade endpoint. e.g,
> api/v1/clusters/$name/upgrade_summary/$request_id
> {code}
> {
> attempt_cnt: 1,
> cluster_name: "c1",
> request_id: 1,
> fail_reason: "Failed calling RESTART ZOOKEEPER/ZOOKEEPER_SERVER on host 
> c6401.ambari.apache.org",
> // Notice that the rest are inherited from the failed task if it exists.
> command: "CUSTOM_COMMAND",
> command_detail: "RESTART ZOOKEEPER/ZOOKEEPER_SERVER",
> custom_command_name: "RESTART",
> end_time: -1,
> error_log: "/var/lib/ambari-agent/data/errors-1234.txt",
> exit_code: 1,
> host_name: "c6401.ambari.apache.org",
> id: 1234,
> output_log: "/var/lib/ambari-agent/data/output-1234.txt",
> role: "ZOOKEEPER_SERVER",
> stage_id: 1,
> start_time: 123456789,
> status: "HOLDING_FAILED",
> stdout: "",
> stderr: ""
> }
> {code}



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

[jira] [Commented] (AMBARI-15265) Install & Manage Zeppelin with Ambari

2016-03-10 Thread Hudson (JIRA)


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

Hudson commented on AMBARI-15265:
-

FAILURE: Integrated in Ambari-trunk-Commit #4480 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4480/])
AMBARI-15265. Install & Manage Zeppelin with Ambari (Renjith Kamath via 
(smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=76627aa8e4af8818fff6e9cd56e67b3df5344b10])
* ambari-server/src/main/resources/stacks/HDP/2.5/services/ZEPPELIN/metainfo.xml
* 
ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/metainfo.xml
* contrib/views/zeppelin/src/main/resources/WEB-INF/index.jsp
* 
contrib/views/zeppelin/src/main/java/org/apache/ambari/view/zeppelin/ZeppelinServlet.java
* contrib/views/zeppelin/pom.xml
* 
ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/configuration/zeppelin-config.xml
* 
ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/setup_snapshot.sh
* 
ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/kerberos.json
* 
ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/alerts.json
* 
ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/configuration/zeppelin-env.xml
* 
ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/status_params.py
* ambari-server/src/main/resources/stacks/HDP/2.5/role_command_order.json
* contrib/views/zeppelin/src/main/resources/WEB-INF/web.xml
* contrib/views/zeppelin/src/main/resources/view.xml
* 
ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/alert_check_zeppelin.py
* 
ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/params.py
* 
ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py
* contrib/views/pom.xml


> Install & Manage Zeppelin with Ambari
> -
>
> Key: AMBARI-15265
> URL: https://issues.apache.org/jira/browse/AMBARI-15265
> Project: Ambari
>  Issue Type: New Feature
>Reporter: Renjith Kamath
> Fix For: 2.2.2
>
> Attachments: AMBARI-15265_branch-2.2-2.patch, 
> AMBARI-15265_branch-2.2-3.patch, AMBARI-15265_branch-2.2-4.patch, 
> AMBARI-15265_branch-2.2-5.patch, AMBARI-15265_branch-2.2-6.patch, 
> AMBARI-15265_branch-2.2.patch
>
>
> Ambari to support the following scenario for Zeppelin Service
> * Install of Zeppelin
> * Provide start/stop of Zeppelin component
> * Configure Zeppelin with Ambari including Zeppelin LDAP Authentication
> * Ambari to provide Quicklink from Ambari to Zeppelin
> * Ambari to Kerberize a cluster with Zeppelin in it.



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

[jira] [Commented] (AMBARI-6432) FreeIPA Support in Ambari

2016-03-10 Thread Bolke de Bruin (JIRA)


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

Bolke de Bruin commented on AMBARI-6432:


And it should be possible (did not try) to use this with IPA 3

> FreeIPA Support in Ambari
> -
>
> Key: AMBARI-6432
> URL: https://issues.apache.org/jira/browse/AMBARI-6432
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: jay vyas
>Assignee: Bolke de Bruin
> Fix For: 2.4.0
>
> Attachments: AMBARI-6432-FreeIPA.patch, AMBARI-6432.patch, 
> AMBARI-6432.patch, AMBARI-6432.trunk.v1.patch, AMBARI-6432.trunk.v2.patch, 
> AMBARI-6432.trunk.v3.patch, AMBARI-6432.trunk.v4.patch, 
> AMBARI-6432.trunk.v5.patch, AMBARI-6432.trunk.v5.patch, ipa-patch-v0.5.patch
>
>
> FreeIPA Is a powerful tool for unifying identity, kerberos credentials, 
> across a cluster.
> A great value add for ambari would be to provide support for using FreeIPA to 
> kerberize services.  This would allow for 
> 1) better HCFS interoperability, because first class GID/UID is critical for 
> certain file systems (GlusterFS, Lustre, and any other file system which uses 
> kernel / FUSE apis for determining identity)
> 2) better enterprise interoperability.  Because of the fact that FreeIPA 
> makes it easy to interop with different identity solutions (like active 
> directory), it would make ambari easier to adopt for various enterprises.
> 3) broadens ambaris scope.  Now ambari could also allow people to setup the 
> users of their clusters, and at least some of the security features of their 
> clusters, all from one interface (no more manual handling of TGTs and such - 
> it could all be done quite easily via the ambari UI which could make calls to 
> underlying FreeIPA clients).



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

[jira] [Commented] (AMBARI-6432) FreeIPA Support in Ambari

2016-03-10 Thread Bolke de Bruin (JIRA)


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

Bolke de Bruin commented on AMBARI-6432:


[~rlevas] This latest patch is an intermediate update. A couple of things have 
been updated

1. toLower() has been implemented and applied
2. A cache for keytabs was added to createKeytab - this is the workaround the 
fact that this function gets called mutiple times for the same principal and 
thus generates a new keytab with a new kvno. I tried working with Ambari's 
internal createKeytab, but that did not generate valid keytabs ("password 
incorrect") (see also the commented out code).
3. Some smaller bugs have been squashed (using principal names instead of 
primary for example)


> FreeIPA Support in Ambari
> -
>
> Key: AMBARI-6432
> URL: https://issues.apache.org/jira/browse/AMBARI-6432
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: jay vyas
>Assignee: Bolke de Bruin
> Fix For: 2.4.0
>
> Attachments: AMBARI-6432-FreeIPA.patch, AMBARI-6432.patch, 
> AMBARI-6432.patch, AMBARI-6432.trunk.v1.patch, AMBARI-6432.trunk.v2.patch, 
> AMBARI-6432.trunk.v3.patch, AMBARI-6432.trunk.v4.patch, 
> AMBARI-6432.trunk.v5.patch, AMBARI-6432.trunk.v5.patch, ipa-patch-v0.5.patch
>
>
> FreeIPA Is a powerful tool for unifying identity, kerberos credentials, 
> across a cluster.
> A great value add for ambari would be to provide support for using FreeIPA to 
> kerberize services.  This would allow for 
> 1) better HCFS interoperability, because first class GID/UID is critical for 
> certain file systems (GlusterFS, Lustre, and any other file system which uses 
> kernel / FUSE apis for determining identity)
> 2) better enterprise interoperability.  Because of the fact that FreeIPA 
> makes it easy to interop with different identity solutions (like active 
> directory), it would make ambari easier to adopt for various enterprises.
> 3) broadens ambaris scope.  Now ambari could also allow people to setup the 
> users of their clusters, and at least some of the security features of their 
> clusters, all from one interface (no more manual handling of TGTs and such - 
> it could all be done quite easily via the ambari UI which could make calls to 
> underlying FreeIPA clients).



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

[jira] [Resolved] (AMBARI-15376) Fix typo in get_stack_version

2016-03-10 Thread Jayush Luniya (JIRA)


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

Jayush Luniya resolved AMBARI-15376.

Resolution: Fixed

> Fix typo in get_stack_version
> -
>
> Key: AMBARI-15376
> URL: https://issues.apache.org/jira/browse/AMBARI-15376
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15376.patch
>
>
> Fix a typo introduced in AMBARI-15329 which causes get_stack_version to 
> report stack_version = None.
> 2016-03-10 18:57:13,534 - call['ambari-python-wrap /usr/bin/hdp-select status 
> hadoop-client'] {'timeout': 20}
> 2016-03-10 18:57:13,610 - call returned (0, 'hadoop-client - 2.5.0.0-80')
> 2016-03-10 18:57:13,611 - Failed to get extracted version with 
> /usr/bin/hdp-select



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

[jira] [Commented] (AMBARI-15369) Ambari cannot enable NN HA in kerberos env

2016-03-10 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on AMBARI-15369:


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

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

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

This message is automatically generated.

> Ambari cannot enable NN HA in kerberos env
> --
>
> Key: AMBARI-15369
> URL: https://issues.apache.org/jira/browse/AMBARI-15369
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.2.2
>
> Attachments: AMBARI-15369_22.patch, AMBARI-15369_trunk.patch
>
>
> PROBLEM: In secured env, when try to enable NN HA, it will fail at step 2 
> when trying to add additional NN to the cluster with error:
> {code}
> 07 Mar 2016 16:35:45,083  INFO [qtp-ambari-client-25] 
> AbstractResourceProvider:798 - Caught an exception while updating host 
> components, retrying : java.lang.IllegalArgumentException: Missing KDC 
> administrator credentials.
> The KDC administrator credentials must be set as a persisted or temporary 
> credential resource.This may be done by issuing a POST to the 
> /api/v1/clusters/:clusterName/credentials/kdc.admin.credential API entry 
> point with the following payload:
> {
>   "Credential" : {
> "principal" : "(PRINCIPAL)", "key" : "(PASSWORD)", "type" : 
> "(persisted|temporary)"}
>   }
> }
> 07 Mar 2016 16:35:45,334  INFO [qtp-ambari-client-25] 
> AbstractResourceProvider:917 - Received a updateHostComponent request, 
> clusterName=sparkB, serviceName=HDFS, componentName=NAMENODE, 
> hostname=sparkb2.sec.support.com, request={ clusterName=sparkB, 
> serviceName=HDFS, componentName=NAMENODE, hostname=sparkb2.sec.support.com, 
> desiredState=INSTALLED, state=null, desiredStackId=null, staleConfig=null, 
> adminState=null}
> {code}



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

[jira] [Commented] (AMBARI-13364) Parameterize stack information used by common services

2016-03-10 Thread Tuong Truong (JIRA)


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

Tuong Truong commented on AMBARI-13364:
---

Hi [~jluniya],  Juanjo and I just quickly scanned thru the patch you submitted, 
and we both agree that this is a good improvement on our original design.   We 
are very happy that you are able to spend bandwidth on this.   Juanjo is 
actively working on this feature.  If Alex and other committers support your 
proposal, Juanjo can proceed refactoring the other services based on this new 
design.  Thanks again for your help.  We are looking forward for you leadership 
on this effort.

[~afernandez],  do you have any comment on Jayush's approach before Juanjo 
start refactoring?  

>  Parameterize stack information used by common services
> ---
>
> Key: AMBARI-13364
> URL: https://issues.apache.org/jira/browse/AMBARI-13364
> Project: Ambari
>  Issue Type: Story
>  Components: ambari-server
>Reporter: Tuong Truong
>Assignee: Juanjo Marron
> Attachments: AMBARI-13364 Parameterize stack information used by 
> common services.pdf, AMBARI-13364.patch, stack_featurizer.patch
>
>
> This feature will add a basic framework to remove hardcoded stack information 
> out of the common services and use parameter to get access to stack 
> information.  Currently, common services hardcodes much information specific 
> to Hortonworks' HDP stack including name (HDP), specific versions (2.0, 2.1, 
> 2.2), and install location.   This feature will propose a way of 
> configuration these information and parameterize them into the services for 
> reference as require. 



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

[jira] [Commented] (AMBARI-6432) FreeIPA Support in Ambari

2016-03-10 Thread Bolke de Bruin (JIRA)


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

Bolke de Bruin commented on AMBARI-6432:


I think I have hit a bug in CreateKeytabFilesServerAction. Newly generated 
keytabs for non service principals can reside in a cache. However, they seem 
never to be stored into this cache. Hence, keytabs always get regenerated. 

> FreeIPA Support in Ambari
> -
>
> Key: AMBARI-6432
> URL: https://issues.apache.org/jira/browse/AMBARI-6432
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: jay vyas
>Assignee: Bolke de Bruin
> Fix For: 2.4.0
>
> Attachments: AMBARI-6432-FreeIPA.patch, AMBARI-6432.patch, 
> AMBARI-6432.trunk.v1.patch, AMBARI-6432.trunk.v2.patch, 
> AMBARI-6432.trunk.v3.patch, AMBARI-6432.trunk.v4.patch, 
> AMBARI-6432.trunk.v5.patch, AMBARI-6432.trunk.v5.patch, ipa-patch-v0.5.patch
>
>
> FreeIPA Is a powerful tool for unifying identity, kerberos credentials, 
> across a cluster.
> A great value add for ambari would be to provide support for using FreeIPA to 
> kerberize services.  This would allow for 
> 1) better HCFS interoperability, because first class GID/UID is critical for 
> certain file systems (GlusterFS, Lustre, and any other file system which uses 
> kernel / FUSE apis for determining identity)
> 2) better enterprise interoperability.  Because of the fact that FreeIPA 
> makes it easy to interop with different identity solutions (like active 
> directory), it would make ambari easier to adopt for various enterprises.
> 3) broadens ambaris scope.  Now ambari could also allow people to setup the 
> users of their clusters, and at least some of the security features of their 
> clusters, all from one interface (no more manual handling of TGTs and such - 
> it could all be done quite easily via the ambari UI which could make calls to 
> underlying FreeIPA clients).



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

[jira] [Created] (AMBARI-15375) NPE while gathering JMX ports from configs

2016-03-10 Thread Myroslav Papirkovskyy (JIRA)

Myroslav Papirkovskyy created AMBARI-15375:
--

 Summary: NPE while gathering JMX ports from configs
 Key: AMBARI-15375
 URL: https://issues.apache.org/jira/browse/AMBARI-15375
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.2.2
Reporter: Myroslav Papirkovskyy
Assignee: Myroslav Papirkovskyy
Priority: Critical
 Fix For: 2.2.2


Sometimes getting JMX ports from configs throws NPE exception.

{noformat}
org.apache.ambari.server.controller.spi.SystemException: Caught exception 
getting JMX metrics : null
at 
org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider.rethrowSystemException(ThreadPoolEnabledPropertyProvider.java:245)
at 
org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider.populateResources(ThreadPoolEnabledPropertyProvider.java:155)
at 
org.apache.ambari.server.controller.internal.StackDefinedPropertyProvider.populateResources(StackDefinedPropertyProvider.java:200)
at 
org.apache.ambari.server.controller.internal.ClusterControllerImpl.populateResources(ClusterControllerImpl.java:146)
at 
org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:406)
at 
org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:216)
at 
org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:68)
at 
org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:135)
at 
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:106)
at 
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:75)
at 
org.apache.ambari.server.api.services.HostComponentService.getHostComponent(HostComponentService.java:89)
at sun.reflect.GeneratedMethodAccessor106.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at 
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
at 
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at 
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
at 
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
at 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:540)
at 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:715)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1496)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
at 
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118)
at 
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84)
at

[jira] [Updated] (AMBARI-13364) Parameterize stack information used by common services

2016-03-10 Thread Jayush Luniya (JIRA)


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

Jayush Luniya updated AMBARI-13364:
---
Attachment: stack_featurizer.patch

>  Parameterize stack information used by common services
> ---
>
> Key: AMBARI-13364
> URL: https://issues.apache.org/jira/browse/AMBARI-13364
> Project: Ambari
>  Issue Type: Story
>  Components: ambari-server
>Reporter: Tuong Truong
>Assignee: Juanjo Marron
> Attachments: AMBARI-13364 Parameterize stack information used by 
> common services.pdf, AMBARI-13364.patch, stack_featurizer.patch
>
>
> This feature will add a basic framework to remove hardcoded stack information 
> out of the common services and use parameter to get access to stack 
> information.  Currently, common services hardcodes much information specific 
> to Hortonworks' HDP stack including name (HDP), specific versions (2.0, 2.1, 
> 2.2), and install location.   This feature will propose a way of 
> configuration these information and parameterize them into the services for 
> reference as require. 



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

[jira] [Updated] (AMBARI-15338) After exporting blueprint from ranger enabled cluster ranger.service.https.attrib.keystore.pass is exported

2016-03-10 Thread Amruta Borkar (JIRA)


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

Amruta Borkar updated AMBARI-15338:
---
Status: Patch Available  (was: Open)

> After exporting blueprint from ranger enabled cluster 
> ranger.service.https.attrib.keystore.pass is exported
> ---
>
> Key: AMBARI-15338
> URL: https://issues.apache.org/jira/browse/AMBARI-15338
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, blueprints
>Affects Versions: 2.2.0
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Attachments: AMBARI-15338-trunk.patch, AMBARI-15338.patch
>
>
> After exporting a blueprint from Ranger enabled cluster 
> ranger.service.https.attrib.keystore.pass is also included, which needs to be 
> removed before using the same blueprint to create another cluster
> Error Show when used same blueprint:
> {
>   "status" : 400,
>   "message" : "Blueprint configuration validation failed: Secret references 
> are not allowed in blueprints, replace following properties with real 
> passwords:\n  Config:ranger-admin-site 
> Property:ranger.service.https.attrib.keystore.pass\n"
> }



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

[jira] [Commented] (AMBARI-15356) filtering on version not installed hosts from the versions page does not work

2016-03-10 Thread Andrii Tkach (JIRA)


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

Andrii Tkach commented on AMBARI-15356:
---

committed to trunk

> filtering on version not installed hosts from the versions page does not work
> -
>
> Key: AMBARI-15356
> URL: https://issues.apache.org/jira/browse/AMBARI-15356
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 2.4.0
>
> Attachments: AMBARI-15356.patch
>
>
> I registered a new version in ambari and installed it. It failed to install 
> on 1 of the 10 nodes.
> From the versions page i selected the link under the Not Installed section 
> and it gave info on what hosts the version is not installed on. When i 
> clicked Go To hosts page i was taken to the hosts page but no host was 
> visible. I had to go to the host page of the specific host and then install 
> the version again. So the filtering option of version not installed did not 
> work.
> Another thing we could improve is from the versions page add an option to 
> retry failed nodes only option. Today the user can only do re install on all 
> nodes.



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

[jira] [Commented] (AMBARI-15356) filtering on version not installed hosts from the versions page does not work

2016-03-10 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on AMBARI-15356:


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

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

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

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

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

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

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

This message is automatically generated.

> filtering on version not installed hosts from the versions page does not work
> -
>
> Key: AMBARI-15356
> URL: https://issues.apache.org/jira/browse/AMBARI-15356
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 2.4.0
>
> Attachments: AMBARI-15356.patch
>
>
> I registered a new version in ambari and installed it. It failed to install 
> on 1 of the 10 nodes.
> From the versions page i selected the link under the Not Installed section 
> and it gave info on what hosts the version is not installed on. When i 
> clicked Go To hosts page i was taken to the hosts page but no host was 
> visible. I had to go to the host page of the specific host and then install 
> the version again. So the filtering option of version not installed did not 
> work.
> Another thing we could improve is from the versions page add an option to 
> retry failed nodes only option. Today the user can only do re install on all 
> nodes.



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

[jira] [Updated] (AMBARI-15369) Ambari cannot enable NN HA in kerberos env

2016-03-10 Thread Antonenko Alexander (JIRA)


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

Antonenko Alexander updated AMBARI-15369:
-
Status: Patch Available  (was: Open)

> Ambari cannot enable NN HA in kerberos env
> --
>
> Key: AMBARI-15369
> URL: https://issues.apache.org/jira/browse/AMBARI-15369
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.2.2
>
> Attachments: AMBARI-15369_22.patch, AMBARI-15369_trunk.patch
>
>
> PROBLEM: In secured env, when try to enable NN HA, it will fail at step 2 
> when trying to add additional NN to the cluster with error:
> {code}
> 07 Mar 2016 16:35:45,083  INFO [qtp-ambari-client-25] 
> AbstractResourceProvider:798 - Caught an exception while updating host 
> components, retrying : java.lang.IllegalArgumentException: Missing KDC 
> administrator credentials.
> The KDC administrator credentials must be set as a persisted or temporary 
> credential resource.This may be done by issuing a POST to the 
> /api/v1/clusters/:clusterName/credentials/kdc.admin.credential API entry 
> point with the following payload:
> {
>   "Credential" : {
> "principal" : "(PRINCIPAL)", "key" : "(PASSWORD)", "type" : 
> "(persisted|temporary)"}
>   }
> }
> 07 Mar 2016 16:35:45,334  INFO [qtp-ambari-client-25] 
> AbstractResourceProvider:917 - Received a updateHostComponent request, 
> clusterName=sparkB, serviceName=HDFS, componentName=NAMENODE, 
> hostname=sparkb2.sec.support.com, request={ clusterName=sparkB, 
> serviceName=HDFS, componentName=NAMENODE, hostname=sparkb2.sec.support.com, 
> desiredState=INSTALLED, state=null, desiredStackId=null, staleConfig=null, 
> adminState=null}
> {code}



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

[jira] [Updated] (AMBARI-15371) Increase the default http header size of the Ambari server to 64k

2016-03-10 Thread Myroslav Papirkovskyy (JIRA)


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

Myroslav Papirkovskyy updated AMBARI-15371:
---
Status: Open  (was: Patch Available)

> Increase the default http header size of the Ambari server to 64k
> -
>
> Key: AMBARI-15371
> URL: https://issues.apache.org/jira/browse/AMBARI-15371
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Myroslav Papirkovskyy
>Assignee: Myroslav Papirkovskyy
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15371.patch, AMBARI-15371_branch-2.2.patch
>
>
> Increase the default http header size to 64k for Ambari server.



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

[jira] [Updated] (AMBARI-15373) Provide composite Kerberos Descriptor via the REST API

2016-03-10 Thread Robert Levas (JIRA)


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

Robert Levas updated AMBARI-15373:
--
 Assignee: Robert Levas
Affects Version/s: 2.4.0
   Labels: kerberos_descriptor rest_api  (was: )
Fix Version/s: 2.4.0
  Description: 
Provide an entry point in the REST API to retrieve the _composite_ Kerberos 
descriptor. This includes the default Kerberos descriptor built from the stack 
definitions overlaid with the (potentially sparse) Kerberos descriptor stored 
as an artifact of the cluster. 

The entry point should be a read-only sub-resource of "clusters", and should 
only be made available if asked for explicitly due to the size of the data that 
will be returned.

{noformat:title=Example API call}
GET /api/v1/clusters/:cluster_name/kerberos_descriptor
{noformat}


> Provide composite Kerberos Descriptor via the REST API
> --
>
> Key: AMBARI-15373
> URL: https://issues.apache.org/jira/browse/AMBARI-15373
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: kerberos_descriptor, rest_api
> Fix For: 2.4.0
>
>
> Provide an entry point in the REST API to retrieve the _composite_ Kerberos 
> descriptor. This includes the default Kerberos descriptor built from the 
> stack definitions overlaid with the (potentially sparse) Kerberos descriptor 
> stored as an artifact of the cluster. 
> The entry point should be a read-only sub-resource of "clusters", and should 
> only be made available if asked for explicitly due to the size of the data 
> that will be returned.
> {noformat:title=Example API call}
> GET /api/v1/clusters/:cluster_name/kerberos_descriptor
> {noformat}



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

[jira] [Created] (AMBARI-15373) Provide composite Kerberos Descriptor via the REST API

2016-03-10 Thread Robert Levas (JIRA)

Robert Levas created AMBARI-15373:
-

 Summary: Provide composite Kerberos Descriptor via the REST API
 Key: AMBARI-15373
 URL: https://issues.apache.org/jira/browse/AMBARI-15373
 Project: Ambari
  Issue Type: Task
  Components: ambari-server
Reporter: Robert Levas






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

[jira] [Updated] (AMBARI-15181) JS error on UI load

2016-03-10 Thread Oleg Nechiporenko (JIRA)


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

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

> JS error on UI load
> ---
>
> Key: AMBARI-15181
> URL: https://issues.apache.org/jira/browse/AMBARI-15181
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
> Environment: YARN should be installed
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15181.patch
>
>
> {noformat}
> Uncaught TypeError: Cannot read property 'map' of undefined
> {noformat}
> Code:
> {noformat}
> var alertsCount = 
> groupedByComponentName[master.get('componentName')].map(function 
> (alertDefinition) {
> {noformat}



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

[jira] [Resolved] (AMBARI-15349) Typo in the dependent key

2016-03-10 Thread Oleg Nechiporenko (JIRA)


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

Oleg Nechiporenko resolved AMBARI-15349.

Resolution: Duplicate

Duplicate for AMBARI-15350

> Typo in the dependent key
> -
>
> Key: AMBARI-15349
> URL: https://issues.apache.org/jira/browse/AMBARI-15349
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: ambari-2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: ambari-2.4.0
>
>
> {{ambari-web/app/controllers/main/service/info/configs.js}}
> #dependentConfigGroups
> {{groupsto...@each.name}} should be {{groupssto...@each.name}}



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

[jira] [Updated] (AMBARI-14874) Alert Instance filter issues

2016-03-10 Thread Oleg Nechiporenko (JIRA)


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

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

> Alert Instance filter issues
> 
>
> Key: AMBARI-14874
> URL: https://issues.apache.org/jira/browse/AMBARI-14874
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14874.patch, AMBARI-14874_branch-2.2.patch, 
> alert-instance-table.tiff, host-table.tiff
>
>
> See attached.
> 1) The text should be consistent with Hosts page filtering "No alert 
> instances to display"
> 2) The area should show "0 of 1 instances showing - clear filters", 
> consistent with Hosts page filtering.



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

[jira] [Updated] (AMBARI-15350) Typo in the dependent key

2016-03-10 Thread Oleg Nechiporenko (JIRA)


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

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

> Typo in the dependent key
> -
>
> Key: AMBARI-15350
> URL: https://issues.apache.org/jira/browse/AMBARI-15350
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-15350.patch
>
>
> {{ambari-web/app/controllers/main/service/info/configs.js}}
> #dependentConfigGroups
> {{groupsto...@each.name}} should be {{groupssto...@each.name}}



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

[jira] [Updated] (AMBARI-15371) Increase the default http header size of the Ambari server to 64k

2016-03-10 Thread Myroslav Papirkovskyy (JIRA)


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

Myroslav Papirkovskyy updated AMBARI-15371:
---
Status: Patch Available  (was: Open)

> Increase the default http header size of the Ambari server to 64k
> -
>
> Key: AMBARI-15371
> URL: https://issues.apache.org/jira/browse/AMBARI-15371
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Myroslav Papirkovskyy
>Assignee: Myroslav Papirkovskyy
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15371.patch, AMBARI-15371_branch-2.2.patch
>
>
> Increase the default http header size to 64k for Ambari server.



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

[jira] [Commented] (AMBARI-15371) Increase the default http header size of the Ambari server to 64k

2016-03-10 Thread Myroslav Papirkovskyy (JIRA)


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

Myroslav Papirkovskyy commented on AMBARI-15371:


Should be covered in integration tests. Unit tests not required.

> Increase the default http header size of the Ambari server to 64k
> -
>
> Key: AMBARI-15371
> URL: https://issues.apache.org/jira/browse/AMBARI-15371
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Myroslav Papirkovskyy
>Assignee: Myroslav Papirkovskyy
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15371.patch, AMBARI-15371_branch-2.2.patch
>
>
> Increase the default http header size to 64k for Ambari server.



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

[jira] [Updated] (AMBARI-15371) Increase the default http header size of the Ambari server to 64k

2016-03-10 Thread Myroslav Papirkovskyy (JIRA)


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

Myroslav Papirkovskyy updated AMBARI-15371:
---
Attachment: AMBARI-15371.patch
AMBARI-15371_branch-2.2.patch

> Increase the default http header size of the Ambari server to 64k
> -
>
> Key: AMBARI-15371
> URL: https://issues.apache.org/jira/browse/AMBARI-15371
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Myroslav Papirkovskyy
>Assignee: Myroslav Papirkovskyy
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15371.patch, AMBARI-15371_branch-2.2.patch
>
>
> Increase the default http header size to 64k for Ambari server.



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

[jira] [Updated] (AMBARI-15372) Zookeeper service check fails after removing a host

2016-03-10 Thread Andrew Onischuk (JIRA)


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

Andrew Onischuk updated AMBARI-15372:
-
Status: Patch Available  (was: Open)

> Zookeeper service check fails after removing a host 
> 
>
> Key: AMBARI-15372
> URL: https://issues.apache.org/jira/browse/AMBARI-15372
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.2.2
>
> Attachments: AMBARI-15372.patch
>
>
> This was reproduced in the rerun.  
> STR:  
> 1) Move all the masters from the host to be deleted(In this case, SNamenode
> was moved)  
> 2) Remove the host  
> 3) Run service checks
> Mapreduce service check fails here.
> Here is the live cluster: I am extending its life till 72 hours:  
>   
>  HDP/84552/>
> Artifacts:  artifacts/os-r6-phtdlu-ambari-rare-17r/ambari-rare-1457129950/artifacts/screen
> shots/com.hw.ambari.ui.tests.heavyweights.TestDeleteHostFromOriginalClusterAft
> erMoveMaster/test2_deleteAdditionalHostFromClusterAfterMoveMaster/_4_22_12_8_C
> hecking_smoke_test_for__ZOOKEEPER_service_failed/>



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

[jira] [Created] (AMBARI-15372) Zookeeper service check fails after removing a host

2016-03-10 Thread Andrew Onischuk (JIRA)

Andrew Onischuk created AMBARI-15372:


 Summary: Zookeeper service check fails after removing a host 
 Key: AMBARI-15372
 URL: https://issues.apache.org/jira/browse/AMBARI-15372
 Project: Ambari
  Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
 Fix For: 2.2.2
 Attachments: AMBARI-15372.patch

This was reproduced in the rerun.  
STR:  
1) Move all the masters from the host to be deleted(In this case, SNamenode
was moved)  
2) Remove the host  
3) Run service checks

Mapreduce service check fails here.

Here is the live cluster: I am extending its life till 72 hours:  
  


Artifacts: 





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

[jira] [Commented] (AMBARI-15351) Remove Service: Delete confirmation tweaks

2016-03-10 Thread Hudson (JIRA)


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

Hudson commented on AMBARI-15351:
-

ABORTED: Integrated in Ambari-trunk-Commit #4478 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4478/])
AMBARI-15351 Remove Service: Delete confirmation tweaks. (atkach) (atkach: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f9d317bd29dd88e46038ebfab34682ea524f2d37])
* ambari-web/app/controllers/main/service/item.js
* ambari-web/test/controllers/main/service/item_test.js
* ambari-web/app/messages.js


> Remove Service: Delete confirmation tweaks
> --
>
> Key: AMBARI-15351
> URL: https://issues.apache.org/jira/browse/AMBARI-15351
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15351.patch, confirm-delete.pptx
>
>
> See attached. Think we should be more explicit and use "delete" instead of 
> "yes". 



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

[jira] [Updated] (AMBARI-15357) Rename Service Action 'HAWQ Check' to 'HAWQ Config Check'

2016-03-10 Thread Goutam Tadi (JIRA)


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

Goutam Tadi updated AMBARI-15357:
-
Attachment: AMBARI-15357-v1.trunk.patch

> Rename Service Action 'HAWQ Check' to 'HAWQ Config Check'
> -
>
> Key: AMBARI-15357
> URL: https://issues.apache.org/jira/browse/AMBARI-15357
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Reporter: Goutam Tadi
>Assignee: Goutam Tadi
>Priority: Minor
> Fix For: 2.2.2
>
> Attachments: AMBARI-15357-trunk.patch, AMBARI-15357-v1.trunk.patch
>
>




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

[jira] [Commented] (AMBARI-15370) Login as regular user (no cluster access at all) but background ops are running about cluster

2016-03-10 Thread Oleg Nechiporenko (JIRA)


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

Oleg Nechiporenko commented on AMBARI-15370:


+1 for patch

> Login as regular user (no cluster access at all) but background ops are 
> running about cluster
> -
>
> Key: AMBARI-15370
> URL: https://issues.apache.org/jira/browse/AMBARI-15370
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-15370.patch, user-running-ui (4).tiff
>
>
> I created a local user and did not give them access to any cluster.
> Logged in and notice that Ambari Web is making calls to backend about cluster 
> items (hosts, alerts, etc).
> The calls come back 403 since this user doesn't have access to cluster 
> resources but these calls are not necessary overhead, and in case of real 
> problems, errors like this will confuse real errors.



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

[jira] [Updated] (AMBARI-15370) Login as regular user (no cluster access at all) but background ops are running about cluster

2016-03-10 Thread Antonenko Alexander (JIRA)


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

Antonenko Alexander updated AMBARI-15370:
-
Status: Patch Available  (was: Open)

> Login as regular user (no cluster access at all) but background ops are 
> running about cluster
> -
>
> Key: AMBARI-15370
> URL: https://issues.apache.org/jira/browse/AMBARI-15370
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-15370.patch, user-running-ui (4).tiff
>
>
> I created a local user and did not give them access to any cluster.
> Logged in and notice that Ambari Web is making calls to backend about cluster 
> items (hosts, alerts, etc).
> The calls come back 403 since this user doesn't have access to cluster 
> resources but these calls are not necessary overhead, and in case of real 
> problems, errors like this will confuse real errors.



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

[jira] [Updated] (AMBARI-15370) Login as regular user (no cluster access at all) but background ops are running about cluster

2016-03-10 Thread Antonenko Alexander (JIRA)


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

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

> Login as regular user (no cluster access at all) but background ops are 
> running about cluster
> -
>
> Key: AMBARI-15370
> URL: https://issues.apache.org/jira/browse/AMBARI-15370
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-15370.patch, user-running-ui (4).tiff
>
>
> I created a local user and did not give them access to any cluster.
> Logged in and notice that Ambari Web is making calls to backend about cluster 
> items (hosts, alerts, etc).
> The calls come back 403 since this user doesn't have access to cluster 
> resources but these calls are not necessary overhead, and in case of real 
> problems, errors like this will confuse real errors.



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

[jira] [Commented] (AMBARI-13216) Add a "Add" button to Repo management UI.

2016-03-10 Thread Hudson (JIRA)


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

Hudson commented on AMBARI-13216:
-

FAILURE: Integrated in Ambari-branch-2.2 #497 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/497/])
AMBARI-13216: Add a "Add" button to Repo management UI. (mithmatt) (matt: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d0b999e4261c72a8db8b6fa234ea9cb3db527552])
* 
ambari-admin/src/main/resources/ui/admin-web/test/unit/services/AddRepositoryModal_test.js
* 
ambari-admin/src/main/resources/ui/admin-web/app/views/modals/AddRepositoryModal.html
* 
ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/AddRepositoryModal.js
* 
ambari-admin/src/main/resources/ui/admin-web/test/unit/controllers/mainCtrl_test.js


> Add a "Add" button to Repo management UI.
> -
>
> Key: AMBARI-13216
> URL: https://issues.apache.org/jira/browse/AMBARI-13216
> Project: Ambari
>  Issue Type: Bug
>Reporter: jun aoki
>Assignee: Matt
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-13216-branch-2.2-orig.patch, 
> AMBARI-13216-branch-2.2-unit-test.patch, AMBARI-13216-branch-2.2-v1.patch, 
> AMBARI-13216-trunk-orig.patch, AMBARI-13216-trunk-v1.patch, 
> Ambariaddrepositoryfeaturedesigndocument_v1.pdf, Untitled.png, 
> screenshot-1.png, screenshot-2.png
>
>
> From UI, there is no way to add a new repo URL. (You can modify but not add). 
> This is a blocker when a service plugin is added to ambari-server.
> This maybe depends on https://issues.apache.org/jira/browse/AMBARI-13215



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

[jira] [Commented] (AMBARI-15341) Use pxf-service restart method when Restart action is called via Ambari

2016-03-10 Thread Hudson (JIRA)


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

Hudson commented on AMBARI-15341:
-

FAILURE: Integrated in Ambari-branch-2.2 #497 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/497/])
AMBARI-15341: Use pxf-service restart method when Restart action is (matt: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=11d2b252ec9738869099fee843f30c03998b1b19])
* 
ambari-server/src/main/resources/common-services/PXF/3.0.0/package/scripts/pxf.py


> Use pxf-service restart method when Restart action is called via Ambari
> ---
>
> Key: AMBARI-15341
> URL: https://issues.apache.org/jira/browse/AMBARI-15341
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: trunk
>Reporter: bhuvnesh chaudhary
>Assignee: bhuvnesh chaudhary
>Priority: Minor
> Fix For: trunk, 2.2.0
>
> Attachments: AMBARI-15341-1.patch, AMBARI-15341.patch
>
>
> Use pxf-service restart method when Restart action is called via Ambari.
> Currently we use pxf-service stop followed by pxf-service start, due to which 
> if pxf-service is already stopped, stop command fails.



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

[jira] [Updated] (AMBARI-15370) Login as regular user (no cluster access at all) but background ops are running about cluster

2016-03-10 Thread Antonenko Alexander (JIRA)


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

Antonenko Alexander updated AMBARI-15370:
-
Affects Version/s: (was: 2.4.0)
   2.2.0

> Login as regular user (no cluster access at all) but background ops are 
> running about cluster
> -
>
> Key: AMBARI-15370
> URL: https://issues.apache.org/jira/browse/AMBARI-15370
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: user-running-ui (4).tiff
>
>
> I created a local user and did not give them access to any cluster.
> Logged in and notice that Ambari Web is making calls to backend about cluster 
> items (hosts, alerts, etc).
> The calls come back 403 since this user doesn't have access to cluster 
> resources but these calls are not necessary overhead, and in case of real 
> problems, errors like this will confuse real errors.



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

[jira] [Created] (AMBARI-15370) Login as regular user (no cluster access at all) but background ops are running about cluster

2016-03-10 Thread Antonenko Alexander (JIRA)

Antonenko Alexander created AMBARI-15370:


 Summary: Login as regular user (no cluster access at all) but 
background ops are running about cluster
 Key: AMBARI-15370
 URL: https://issues.apache.org/jira/browse/AMBARI-15370
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.4.0
Reporter: Antonenko Alexander
Assignee: Antonenko Alexander
 Fix For: 2.4.0


I created a local user and did not give them access to any cluster.

Logged in and notice that Ambari Web is making calls to backend about cluster 
items (hosts, alerts, etc).

The calls come back 403 since this user doesn't have access to cluster 
resources but these calls are not necessary overhead, and in case of real 
problems, errors like this will confuse real errors.



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

[jira] [Created] (AMBARI-15369) Ambari cannot enable NN HA in kerberos env

2016-03-10 Thread Antonenko Alexander (JIRA)

Antonenko Alexander created AMBARI-15369:


 Summary: Ambari cannot enable NN HA in kerberos env
 Key: AMBARI-15369
 URL: https://issues.apache.org/jira/browse/AMBARI-15369
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.2.0
Reporter: Antonenko Alexander
Assignee: Antonenko Alexander
 Fix For: 2.4.0


PROBLEM: In secured env, when try to enable NN HA, it will fail at step 2 when 
trying to add additional NN to the cluster with error:
{code}
07 Mar 2016 16:35:45,083  INFO [qtp-ambari-client-25] 
AbstractResourceProvider:798 - Caught an exception while updating host 
components, retrying : java.lang.IllegalArgumentException: Missing KDC 
administrator credentials.
The KDC administrator credentials must be set as a persisted or temporary 
credential resource.This may be done by issuing a POST to the 
/api/v1/clusters/:clusterName/credentials/kdc.admin.credential API entry point 
with the following payload:
{
  "Credential" : {
"principal" : "(PRINCIPAL)", "key" : "(PASSWORD)", "type" : 
"(persisted|temporary)"}
  }
}
07 Mar 2016 16:35:45,334  INFO [qtp-ambari-client-25] 
AbstractResourceProvider:917 - Received a updateHostComponent request, 
clusterName=sparkB, serviceName=HDFS, componentName=NAMENODE, 
hostname=sparkb2.sec.support.com, request={ clusterName=sparkB, 
serviceName=HDFS, componentName=NAMENODE, hostname=sparkb2.sec.support.com, 
desiredState=INSTALLED, state=null, desiredStackId=null, staleConfig=null, 
adminState=null}
{code}



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

[jira] [Updated] (AMBARI-15311) Update descriptions for HAWQ and PXF configurations

2016-03-10 Thread Matt (JIRA)


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

Matt updated AMBARI-15311:
--
Status: Patch Available  (was: Open)

> Update descriptions for HAWQ and PXF configurations
> ---
>
> Key: AMBARI-15311
> URL: https://issues.apache.org/jira/browse/AMBARI-15311
> Project: Ambari
>  Issue Type: Sub-task
>  Components: stacks
>Reporter: Matt
>Assignee: Goutam Tadi
>Priority: Minor
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-15311-trunk.patch
>
>
> Update the descriptions for HAWQ and PXF configurations so that they are more 
> readable and convey the right message to the user.



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

[jira] [Commented] (AMBARI-15366) Errors on API requests for quick links info are not handled

2016-03-10 Thread Hudson (JIRA)


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

Hudson commented on AMBARI-15366:
-

SUCCESS: Integrated in Ambari-branch-2.2 #496 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/496/])
AMBARI-15366. Errors on API requests for quick links info are not (hiveww: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3efb9f1e8c7649c3d7fa96be64868b064dc8de65])
* ambari-web/app/assets/test/tests.js
* ambari-web/test/views/common/quick_view_link_view_test.js
* ambari-web/app/views/common/quick_view_link_view.js


> Errors on API requests for quick links info are not handled
> ---
>
> Key: AMBARI-15366
> URL: https://issues.apache.org/jira/browse/AMBARI-15366
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15366.patch
>
>
> If API request for host components info required to generate quick links 
> result returns error, infinite spinner is still displayed.



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

[jira] [Updated] (AMBARI-15341) Use pxf-service restart method when Restart action is called via Ambari

2016-03-10 Thread Matt (JIRA)


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

Matt updated AMBARI-15341:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Use pxf-service restart method when Restart action is called via Ambari
> ---
>
> Key: AMBARI-15341
> URL: https://issues.apache.org/jira/browse/AMBARI-15341
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: trunk
>Reporter: bhuvnesh chaudhary
>Assignee: bhuvnesh chaudhary
>Priority: Minor
> Fix For: trunk, 2.2.0
>
> Attachments: AMBARI-15341-1.patch, AMBARI-15341.patch
>
>
> Use pxf-service restart method when Restart action is called via Ambari.
> Currently we use pxf-service stop followed by pxf-service start, due to which 
> if pxf-service is already stopped, stop command fails.



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

[jira] [Commented] (AMBARI-15341) Use pxf-service restart method when Restart action is called via Ambari

2016-03-10 Thread Matt (JIRA)


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

Matt commented on AMBARI-15341:
---

Committed to trunk:
{code}
author  Matt    
Thu, 10 Mar 2016 04:11:31 -0800 (04:11 -0800)
committer   Matt    
Thu, 10 Mar 2016 04:11:31 -0800 (04:11 -0800)
commit  e1762a4281bbd78228c0ac162d8c19932de955e5
{code}
Committed to branch-2.2:
{code}
author  Matt    
Thu, 10 Mar 2016 04:12:41 -0800 (04:12 -0800)
committer   Matt    
Thu, 10 Mar 2016 04:12:41 -0800 (04:12 -0800)
commit  11d2b252ec9738869099fee843f30c03998b1b19
{code}
Marking as resolved.

> Use pxf-service restart method when Restart action is called via Ambari
> ---
>
> Key: AMBARI-15341
> URL: https://issues.apache.org/jira/browse/AMBARI-15341
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: trunk
>Reporter: bhuvnesh chaudhary
>Assignee: bhuvnesh chaudhary
>Priority: Minor
> Fix For: trunk, 2.2.0
>
> Attachments: AMBARI-15341-1.patch, AMBARI-15341.patch
>
>
> Use pxf-service restart method when Restart action is called via Ambari.
> Currently we use pxf-service stop followed by pxf-service start, due to which 
> if pxf-service is already stopped, stop command fails.



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

[jira] [Commented] (AMBARI-15350) Typo in the dependent key

2016-03-10 Thread Hudson (JIRA)


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

Hudson commented on AMBARI-15350:
-

SUCCESS: Integrated in Ambari-trunk-Commit #4477 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4477/])
AMBARI-15350. Typo in the dependent key (onechiporenko) (onechiporenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0c44129ad18fc6c30e1f49ffa0580fd2d64c3351])
* 
ambari-web/test/controllers/main/service/widgets/create/wizard_controller_test.js
* ambari-web/app/controllers/main/service/info/configs.js
* ambari-web/test/controllers/main_test.js


> Typo in the dependent key
> -
>
> Key: AMBARI-15350
> URL: https://issues.apache.org/jira/browse/AMBARI-15350
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-15350.patch
>
>
> {{ambari-web/app/controllers/main/service/info/configs.js}}
> #dependentConfigGroups
> {{groupsto...@each.name}} should be {{groupssto...@each.name}}



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

[jira] [Updated] (AMBARI-15367) Remove experimental flags for stackUpgrade, enhancedConfigs, and storeKDCCredentials

2016-03-10 Thread Antonenko Alexander (JIRA)


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

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

committed to trunk

> Remove experimental flags for stackUpgrade, enhancedConfigs, and 
> storeKDCCredentials
> 
>
> Key: AMBARI-15367
> URL: https://issues.apache.org/jira/browse/AMBARI-15367
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-15367.patch
>
>
> Since we fully support stack upgrades, enhanced configs, and 
> storeKDCCredentials now, we should drop these feature flags from App.supports.



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

[jira] [Commented] (AMBARI-15291) Edit text/labels in Add/Activate HAWQ Standby Master wizard

2016-03-10 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on AMBARI-15291:


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

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

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

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

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

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

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

This message is automatically generated.

> Edit text/labels in Add/Activate HAWQ Standby Master wizard
> ---
>
> Key: AMBARI-15291
> URL: https://issues.apache.org/jira/browse/AMBARI-15291
> Project: Ambari
>  Issue Type: Technical task
>  Components: ambari-web
>Affects Versions: trunk, 2.2.0
>Reporter: Lav Jain
>Assignee: Lav Jain
>Priority: Minor
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-15291.branch22.patch, 
> AMBARI-15291.branch22.v2.patch, AMBARI-15291.patch, AMBARI-15291.v2.patch
>
>




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

[jira] [Updated] (AMBARI-15356) filtering on version not installed hosts from the versions page does not work

2016-03-10 Thread Andrii Tkach (JIRA)


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

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

> filtering on version not installed hosts from the versions page does not work
> -
>
> Key: AMBARI-15356
> URL: https://issues.apache.org/jira/browse/AMBARI-15356
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 2.4.0
>
> Attachments: AMBARI-15356.patch
>
>
> I registered a new version in ambari and installed it. It failed to install 
> on 1 of the 10 nodes.
> From the versions page i selected the link under the Not Installed section 
> and it gave info on what hosts the version is not installed on. When i 
> clicked Go To hosts page i was taken to the hosts page but no host was 
> visible. I had to go to the host page of the specific host and then install 
> the version again. So the filtering option of version not installed did not 
> work.
> Another thing we could improve is from the versions page add an option to 
> retry failed nodes only option. Today the user can only do re install on all 
> nodes.



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

[jira] [Updated] (AMBARI-15356) filtering on version not installed hosts from the versions page does not work

2016-03-10 Thread Andrii Tkach (JIRA)


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

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

> filtering on version not installed hosts from the versions page does not work
> -
>
> Key: AMBARI-15356
> URL: https://issues.apache.org/jira/browse/AMBARI-15356
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 2.4.0
>
> Attachments: AMBARI-15356.patch
>
>
> I registered a new version in ambari and installed it. It failed to install 
> on 1 of the 10 nodes.
> From the versions page i selected the link under the Not Installed section 
> and it gave info on what hosts the version is not installed on. When i 
> clicked Go To hosts page i was taken to the hosts page but no host was 
> visible. I had to go to the host page of the specific host and then install 
> the version again. So the filtering option of version not installed did not 
> work.
> Another thing we could improve is from the versions page add an option to 
> retry failed nodes only option. Today the user can only do re install on all 
> nodes.



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

[jira] [Updated] (AMBARI-15351) Remove Service: Delete confirmation tweaks

2016-03-10 Thread Andrii Tkach (JIRA)


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

Andrii Tkach updated AMBARI-15351:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Remove Service: Delete confirmation tweaks
> --
>
> Key: AMBARI-15351
> URL: https://issues.apache.org/jira/browse/AMBARI-15351
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15351.patch, confirm-delete.pptx
>
>
> See attached. Think we should be more explicit and use "delete" instead of 
> "yes". 



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

[jira] [Commented] (AMBARI-15310) Host Service Summary Page does not display long service names well

2016-03-10 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on AMBARI-15310:


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

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

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

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

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

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

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

This message is automatically generated.

> Host Service Summary Page does not display long service names well
> --
>
> Key: AMBARI-15310
> URL: https://issues.apache.org/jira/browse/AMBARI-15310
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: trunk
>Reporter: Keta Patel
>Assignee: Keta Patel
>Priority: Minor
>  Labels: ambari-web
> Attachments: AMBARI-15310.patch, AMBARI-15310_Mar07.patch, 
> AMBARI-15310_Mar08.patch, AMBARI-15310_Mar09.patch, Component names with 
> ellipses and tooltip.tiff, Extra Long Service Names with Fix.tiff, Fixed 
> spacing with long service name.tiff, Original spacing with long service 
> name.tiff, Service names with ellipses and tooltip.tiff, Updated Fix 
> (Mar-07).tiff
>
>
> In Ambari UI, navigate to Hosts and click on the hostname where the service 
> is installed. The summary page displays the list of services installed.
> Observe that longer service names does not display well. The refresh icon 
> etc. spills to the next line (see attachment "Original spacing with long 
> service name").
> Also, note the indentation of the last button for Clients does not align well 
> with the buttons above it.



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

[jira] [Commented] (AMBARI-15351) Remove Service: Delete confirmation tweaks

2016-03-10 Thread Andrii Tkach (JIRA)


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

Andrii Tkach commented on AMBARI-15351:
---

committed to trunk

> Remove Service: Delete confirmation tweaks
> --
>
> Key: AMBARI-15351
> URL: https://issues.apache.org/jira/browse/AMBARI-15351
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15351.patch, confirm-delete.pptx
>
>
> See attached. Think we should be more explicit and use "delete" instead of 
> "yes". 



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

[jira] [Commented] (AMBARI-15297) In the step 2 of install resourcemanager ha ,the hosts showd in mistake

2016-03-10 Thread Antonenko Alexander (JIRA)


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

Antonenko Alexander commented on AMBARI-15297:
--

[~wuhui] I think this jira should have Type: Bug, instead of Epic.

> In the step 2 of install resourcemanager ha ,the hosts showd in mistake
> ---
>
> Key: AMBARI-15297
> URL: https://issues.apache.org/jira/browse/AMBARI-15297
> Project: Ambari
>  Issue Type: Epic
>  Components: ambari-web
>Affects Versions: 2.1.1
>Reporter: wuhui
> Fix For: 2.1.1
>
> Attachments: _thumb_22791.png
>
>
> In the step 2 of install RM HA,if you select the extra host for the HA 
> host,it will show a error host which not match with the selected host.



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

[jira] [Commented] (AMBARI-13216) Add a "Add" button to Repo management UI.

2016-03-10 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on AMBARI-13216:


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

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

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

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

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

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

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

This message is automatically generated.

> Add a "Add" button to Repo management UI.
> -
>
> Key: AMBARI-13216
> URL: https://issues.apache.org/jira/browse/AMBARI-13216
> Project: Ambari
>  Issue Type: Bug
>Reporter: jun aoki
>Assignee: Matt
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-13216-branch-2.2-orig.patch, 
> AMBARI-13216-branch-2.2-unit-test.patch, AMBARI-13216-branch-2.2-v1.patch, 
> AMBARI-13216-trunk-orig.patch, AMBARI-13216-trunk-v1.patch, 
> Ambariaddrepositoryfeaturedesigndocument_v1.pdf, Untitled.png, 
> screenshot-1.png, screenshot-2.png
>
>
> From UI, there is no way to add a new repo URL. (You can modify but not add). 
> This is a blocker when a service plugin is added to ambari-server.
> This maybe depends on https://issues.apache.org/jira/browse/AMBARI-13215



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

[jira] [Commented] (AMBARI-15296) Missing property: hive.server2.authentication.kerberos.keytab

2016-03-10 Thread Hudson (JIRA)


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

Hudson commented on AMBARI-15296:
-

SUCCESS: Integrated in Ambari-branch-2.2 #495 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/495/])
AMBARI-15296. Missing property: (stoader: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ea069b334ae0b163c0670145c02f10e92d64d101])
* ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py


> Missing property: hive.server2.authentication.kerberos.keytab
> -
>
> Key: AMBARI-15296
> URL: https://issues.apache.org/jira/browse/AMBARI-15296
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.2.1
>Reporter: Mahadev konar
>Assignee: Laszlo Puskas
> Fix For: 2.2.2
>
> Attachments: AMBARI-15296.v1.patch
>
>




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

[jira] [Commented] (AMBARI-15265) Install & Manage Zeppelin with Ambari

2016-03-10 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on AMBARI-15265:


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

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

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

{color:red}-1 javac{color:red}.  The patch appears to cause the build to 
fail.

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

This message is automatically generated.

> Install & Manage Zeppelin with Ambari
> -
>
> Key: AMBARI-15265
> URL: https://issues.apache.org/jira/browse/AMBARI-15265
> Project: Ambari
>  Issue Type: New Feature
>Reporter: Renjith Kamath
> Fix For: 2.2.2
>
> Attachments: AMBARI-15265_branch-2.2-2.patch, 
> AMBARI-15265_branch-2.2-3.patch, AMBARI-15265_branch-2.2-4.patch, 
> AMBARI-15265_branch-2.2-5.patch, AMBARI-15265_branch-2.2-6.patch, 
> AMBARI-15265_branch-2.2.patch
>
>
> Ambari to support the following scenario for Zeppelin Service
> * Install of Zeppelin
> * Provide start/stop of Zeppelin component
> * Configure Zeppelin with Ambari including Zeppelin LDAP Authentication
> * Ambari to provide Quicklink from Ambari to Zeppelin
> * Ambari to Kerberize a cluster with Zeppelin in it.



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

[jira] [Created] (AMBARI-15368) there are some mistake in vendor.js when insatll hbase

2016-03-10 Thread wuhui (JIRA)

wuhui created AMBARI-15368:
--

 Summary: there are some mistake in vendor.js when insatll hbase
 Key: AMBARI-15368
 URL: https://issues.apache.org/jira/browse/AMBARI-15368
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.1.1
Reporter: wuhui
 Fix For: 2.1.1


if you install hbase there will be a error at the step7 in vendor.js which 
showed uncaught Error: could not respond to event 
didChangeData in state rootState 



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

[jira] [Commented] (AMBARI-15331) AMS HBase FIFO compaction policy and Normalizer settings are not handled correctly

2016-03-10 Thread Hudson (JIRA)


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

Hudson commented on AMBARI-15331:
-

ABORTED: Integrated in Ambari-trunk-Commit #4476 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4476/])
AMBARI-15331. AMS HBase FIFO compaction policy and Normalizer settings (swagle: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5166908915fbef7b3e9cab2a5bfd17e44bfc1953])
* 
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-env.xml
* 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog220Test.java
* 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog220.java
* 
ambari-metrics/ambari-metrics-timelineservice/conf/unix/ambari-metrics-collector


> AMS HBase FIFO compaction policy and Normalizer settings are not handled 
> correctly
> --
>
> Key: AMBARI-15331
> URL: https://issues.apache.org/jira/browse/AMBARI-15331
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.2.0
>Reporter: Shantanu Mundkur
>Assignee: Shantanu Mundkur
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-15331.patch, AMBARI-15331.patch
>
>
> AMS HBase FIFO compaction policy and Normalizer settings are not handled 
> correctly.
> A user could change the defaults for these settings via configuration updates 
> but at least two problems would result. 
> 1) Updates to variables AMS_HBASE_FIFO_COMPACTION_ENABLED and 
> AMS_HBASE_NORMALIZER_ENABLED will not be honored.  Same would be the case for 
> the recent addition to ams-env  - AMS_HBASE_INIT_CHECK_ENABLED.
> 2) During upgrade to Ambari 2.2.0 these settings will not be correctly 
> handled due to incorrect variable names and leads to exceptions e.g if 
> AMS_HBASE_FIFO_COMPACTION_ENABLED  was expected to be set to 'false', for 
> instance if the AMS HBase version did not support FIFO compaction policy.



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

[jira] [Commented] (AMBARI-15321) Alerts : Support in Ambari for hive Server Interactive related Alerts.

2016-03-10 Thread Hudson (JIRA)


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

Hudson commented on AMBARI-15321:
-

ABORTED: Integrated in Ambari-trunk-Commit #4476 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4476/])
AMBARI-15321. Adding support for Hive Server Interactive Alerts (Swapan 
(smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=98b2b238e68b5632c9ea4da970baedf1c2918398])
* 
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/alerts/alert_hive_interactive_thrift_port.py
* ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/alerts.json


> Alerts : Support in Ambari for hive Server Interactive related Alerts.
> --
>
> Key: AMBARI-15321
> URL: https://issues.apache.org/jira/browse/AMBARI-15321
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.4.0
>
> Attachments: AMBARI-15321.patch
>
>
> - Adding support for alerts for Hive's component "Hive Server Interactive".
>   - Specific alerts added is for checking Thrift port status.



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

[jira] [Commented] (AMBARI-15367) Remove experimental flags for stackUpgrade, enhancedConfigs, and storeKDCCredentials

2016-03-10 Thread Oleg Nechiporenko (JIRA)


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

Oleg Nechiporenko commented on AMBARI-15367:


+1 for patch

> Remove experimental flags for stackUpgrade, enhancedConfigs, and 
> storeKDCCredentials
> 
>
> Key: AMBARI-15367
> URL: https://issues.apache.org/jira/browse/AMBARI-15367
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-15367.patch
>
>
> Since we fully support stack upgrades, enhanced configs, and 
> storeKDCCredentials now, we should drop these feature flags from App.supports.



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

[jira] [Updated] (AMBARI-15354) Edit alert UI is mis-aligned

2016-03-10 Thread Oleg Nechiporenko (JIRA)


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

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

> Edit alert UI is mis-aligned
> 
>
> Key: AMBARI-15354
> URL: https://issues.apache.org/jira/browse/AMBARI-15354
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-15354_branch-2.2.patch, web-timeout.tiff
>
>
> See attached.
> The Connection Timeout row is not aligned with the other columns. Seems Check 
> Interval is misaligned as well.



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

[jira] [Commented] (AMBARI-15354) Edit alert UI is mis-aligned

2016-03-10 Thread Oleg Nechiporenko (JIRA)


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

Oleg Nechiporenko commented on AMBARI-15354:


Patch for 2.2 can't be applied to the trunk

> Edit alert UI is mis-aligned
> 
>
> Key: AMBARI-15354
> URL: https://issues.apache.org/jira/browse/AMBARI-15354
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-15354_branch-2.2.patch, web-timeout.tiff
>
>
> See attached.
> The Connection Timeout row is not aligned with the other columns. Seems Check 
> Interval is misaligned as well.



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

[jira] [Created] (AMBARI-15367) Remove experimental flags for stackUpgrade, enhancedConfigs, and storeKDCCredentials

2016-03-10 Thread Antonenko Alexander (JIRA)

Antonenko Alexander created AMBARI-15367:


 Summary: Remove experimental flags for stackUpgrade, 
enhancedConfigs, and storeKDCCredentials
 Key: AMBARI-15367
 URL: https://issues.apache.org/jira/browse/AMBARI-15367
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.4.0
Reporter: Antonenko Alexander
Assignee: Antonenko Alexander
 Fix For: 2.4.0


Since we fully support stack upgrades, enhanced configs, and 
storeKDCCredentials now, we should drop these feature flags from App.supports.



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

[jira] [Created] (AMBARI-15366) Errors on API requests for quick links info are not handled

2016-03-10 Thread Antonenko Alexander (JIRA)

Antonenko Alexander created AMBARI-15366:


 Summary: Errors on API requests for quick links info are not 
handled
 Key: AMBARI-15366
 URL: https://issues.apache.org/jira/browse/AMBARI-15366
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.2.2
Reporter: Antonenko Alexander
Assignee: Antonenko Alexander
Priority: Critical
 Fix For: 2.2.2


If API request for host components info required to generate quick links result 
returns error, infinite spinner is still displayed.




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

[jira] [Commented] (AMBARI-15296) Missing property: hive.server2.authentication.kerberos.keytab

2016-03-10 Thread Sebastian Toader (JIRA)


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

Sebastian Toader commented on AMBARI-15296:
---

Committed to branch-2.2:

{code}
commit ea069b334ae0b163c0670145c02f10e92d64d101
Author: Toader, Sebastian 
Date:   Wed Mar 9 20:41:07 2016 +0100

AMBARI-15296. Missing property: 
hive.server2.authentication.kerberos.keytab. (Laszlo Puskas via stoader)

{code}

> Missing property: hive.server2.authentication.kerberos.keytab
> -
>
> Key: AMBARI-15296
> URL: https://issues.apache.org/jira/browse/AMBARI-15296
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.2.1
>Reporter: Mahadev konar
>Assignee: Laszlo Puskas
> Fix For: 2.2.2
>
> Attachments: AMBARI-15296.v1.patch
>
>




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

[jira] [Commented] (AMBARI-15350) Typo in the dependent key

2016-03-10 Thread Oleg Nechiporenko (JIRA)


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

Oleg Nechiporenko commented on AMBARI-15350:


Committed to trunk

> Typo in the dependent key
> -
>
> Key: AMBARI-15350
> URL: https://issues.apache.org/jira/browse/AMBARI-15350
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-15350.patch
>
>
> {{ambari-web/app/controllers/main/service/info/configs.js}}
> #dependentConfigGroups
> {{groupsto...@each.name}} should be {{groupssto...@each.name}}



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

[jira] [Commented] (AMBARI-13216) Add a "Add" button to Repo management UI.

2016-03-10 Thread Matt (JIRA)


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

Matt commented on AMBARI-13216:
---

Local test results for AMBARI-13216-branch-2.2-unit-test.patch:
{code}
INFO [karma]: Karma v0.12.16 server started at http://localhost:9876/
INFO [launcher]: Starting browser PhantomJS
INFO [PhantomJS 1.9.7 (Mac OS X)]: Connected on socket ZKdbyNfho85ETjJeisx6 
with id 60509021
PhantomJS 1.9.7 (Mac OS X): Executed 16 of 16 SUCCESS (0.015 secs / 0.091 secs)
{code}
{code}
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 12.856 s
[INFO] Finished at: 2016-03-10T00:01:40-08:00
[INFO] Final Memory: 22M/590M
[INFO] 
{code}

Local test results for AMBARI-13216-trunk-v1.patch:
{code}
INFO [karma]: Karma v0.12.16 server started at http://localhost:9876/
INFO [launcher]: Starting browser PhantomJS
INFO [PhantomJS 1.9.7 (Mac OS X)]: Connected on socket 2fbsUeOm2TAdhVw9iaWP 
with id 99812695
PhantomJS 1.9.7 (Mac OS X): Executed 82 of 82 SUCCESS (0.134 secs / 0.382 secs)
{code}
{code}
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 7.410 s
[INFO] Finished at: 2016-03-09T23:58:32-08:00
[INFO] Final Memory: 18M/435M
[INFO] 
{code}

> Add a "Add" button to Repo management UI.
> -
>
> Key: AMBARI-13216
> URL: https://issues.apache.org/jira/browse/AMBARI-13216
> Project: Ambari
>  Issue Type: Bug
>Reporter: jun aoki
>Assignee: Matt
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-13216-branch-2.2-orig.patch, 
> AMBARI-13216-branch-2.2-unit-test.patch, AMBARI-13216-branch-2.2-v1.patch, 
> AMBARI-13216-trunk-orig.patch, AMBARI-13216-trunk-v1.patch, 
> Ambariaddrepositoryfeaturedesigndocument_v1.pdf, Untitled.png, 
> screenshot-1.png, screenshot-2.png
>
>
> From UI, there is no way to add a new repo URL. (You can modify but not add). 
> This is a blocker when a service plugin is added to ambari-server.
> This maybe depends on https://issues.apache.org/jira/browse/AMBARI-13215



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

81 matches

Mail list logo