[jira] [Commented] (AMBARI-19618) Make cohosted components configurable in metainfo.xml instead of hardcoding in UI

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19618:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12848466/AMBARI-19618.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 8 new 
or modified test files.

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

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

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

  org.apache.ambari.server.stack.StackManagerTest
  org.apache.ambari.server.state.ConfigHelperTest

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

This message is automatically generated.

> Make cohosted components configurable in metainfo.xml instead of hardcoding 
> in UI
> -
>
> Key: AMBARI-19618
> URL: https://issues.apache.org/jira/browse/AMBARI-19618
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Yao Lei
> Fix For: trunk, 3.0.0
>
> Attachments: after_patched_hive1.png, after_patched_hive2.png, 
> after_patched_ranger1.png, after_patched_ranger2.png, 
> after_patched_ranger3.png, AMBARI-19618.patch
>
>
> Cohosted components information now is hardcoded in 
> stack_service_component.js  as following:
> App.StackServiceComponent.coHost = {
>   'WEBHCAT_SERVER': 'HIVE_SERVER'
> };
> It's better to move them from javascript to metainfom.xml by adding tag 
> in stack like following:
> 
>   WEBHCAT_SERVER
>   WebHCat Server
>   MASTER
>   1
>   true
>   true
>   HIVE_SERVER
> 
> 
>RANGER_USERSYNC
>Ranger Usersync
>MASTER
>1
>true
>RANGER_ADMIN
> 



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

[jira] [Updated] (AMBARI-19629) Move schemaTool invocation out of configure() to hive_metastore start()

[Doroszlai, Attila (JIRA)]

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

Doroszlai, Attila updated AMBARI-19629:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to 
[trunk|http://git-wip-us.apache.org/repos/asf/ambari/commit/6ba9bd0a] and 
[branch-2.5|http://git-wip-us.apache.org/repos/asf/ambari/commit/9a555e7b].

Unit test failure on branch-2.5 is intermittent, not related to this change:

{noformat}
Failed tests: 
  ClusterDeadlockTest.testDeadlockWithConfigsUpdate:309 [Deadlocked Thread:
{noformat}

> Move schemaTool invocation out of configure() to hive_metastore start()
> ---
>
> Key: AMBARI-19629
> URL: https://issues.apache.org/jira/browse/AMBARI-19629
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19629-branch-2.5.patch, AMBARI-19629-trunk.patch
>
>
> The {{schemaTool}} invocation should not be part of the {{configure}} method 
> as generally the {{configure}} method should be callable from {{install}} as 
> well and {{schemaTool}}  requires a running database to be available which is 
> not true if the default {{mysql}} database server shipped with {{hive}} is 
> used.
> Also since only one component can {{configure}} method at a time on the same 
> host in order to avoid overwriting common shared configs the {{configure}} 
> methods are synchronized across all components on a host. Having the 
> {{schemaTool}} lengthy operation in the {{configure}} method will delay the 
> execution of {{configure}} methods of the other components in case of 
> parallel command execution.



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

[jira] [Updated] (AMBARI-19642) Error during Alert: Unable to authenticate through LDAP for Hiveserver2 (also floods HS2 log with error messages)

[Sumit Mohanty (JIRA)]

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

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

> Error during Alert: Unable to authenticate through LDAP for Hiveserver2 (also 
> floods HS2 log with error messages)
> -
>
> Key: AMBARI-19642
> URL: https://issues.apache.org/jira/browse/AMBARI-19642
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19642.patch
>
>
> Ambari Alert can't authenticate through LDAP for HiveServer2 using the 
> ambari-qa user because there's no where set the ambari-qa password.
> {code}
> javax.security.sasl.SaslException: Error validating the login [Caused by 
> javax.security.sasl.AuthenticationException: Error validating LDAP user 
> [Caused by javax.naming.Authentic 
> ationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903C8, 
> comment: AcceptSecurityContext error, data 52e, v2580 
> at 
> org.apache.hive.service.auth.PlainSaslServer.evaluateResponse(PlainSaslServer.java:109)
>  
> at 
> org.apache.thrift.transport.TSaslTransport$SaslParticipant.evaluateChallengeOrResponse(TSaslTransport.java:509)
>  
> at org.apache.thrift.transport.TSaslTransport.open(TSaslTransport.java:264) 
> at 
> org.apache.thrift.transport.TSaslServerTransport.open(TSaslServerTransport.java:41)
>  
> at 
> org.apache.thrift.transport.TSaslServerTransport$Factory.getTransport(TSaslServerTransport.java:216)
>  
> at 
> org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:189)
>  
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>  
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>  
> at java.lang.Thread.run(Thread.java:744) 
> Caused by: javax.security.sasl.AuthenticationException: Error validating LDAP 
> user [Caused by javax.naming.AuthenticationException: [LDAP: error code 49 - 
> 80090308: LdapErr: DSID 
> -0C0903C8, comment: AcceptSecurityContext error, data 52e, v2580 
> at 
> org.apache.hive.service.auth.LdapAuthenticationProviderImpl.Authenticate(LdapAuthenticationProviderImpl.java:70)
>  
> at 
> org.apache.hive.service.auth.PlainSaslHelper$PlainServerCallbackHandler.handle(PlainSaslHelper.java:106)
>  
> at 
> org.apache.hive.service.auth.PlainSaslServer.evaluateResponse(PlainSaslServer.java:102)
>  
> ... 8 more 
> Caused by: javax.naming.AuthenticationException: [LDAP: error code 49 - 
> 80090308: LdapErr: DSID-0C0903C8, comment: AcceptSecurityContext error, data 
> 52e, v2580 
> at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3087) 
> at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3033) 
> at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2835) 
> at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2749) 
> at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:316) 
> at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:193) 
> at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:211) 
> at 
> com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:154) 
> at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:84) 
> at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684) 
> at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307) 
> at javax.naming.InitialContext.init(InitialContext.java:242) 
> at javax.naming.InitialContext.(InitialContext.java:216) 
> at 
> javax.naming.directory.InitialDirContext.(InitialDirContext.java:101) 
> at 
> org.apache.hive.service.auth.LdapAuthenticationProviderImpl.Authenticate(LdapAuthenticationProviderImpl.java:67)
>  
> ... 10 more 
> 2014-12-29 00:00:12,532 ERROR server.TThreadPoolServer 
> (TThreadPoolServer.java:run(215)) - Error occurred during processing of 
> message. 
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Error validating the login 
> at 
> org.apache.thrift.transport.TSaslServerTransport$Factory.getTransport(TSaslServerTransport.java:219)
>  
> at 
> org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:189)
>  
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>  
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>  
> at java.lang.Thread.run(Thread.java:744) 
> Caused by: org.apache.thrift.transport.TTransportException: Error validating 
> the login 
> at 
> org.apache.thrift.transport.TSaslTransport.sendAndThrowMessage(TSaslTransport.java:221)
> 

[jira] [Updated] (AMBARI-19642) Error during Alert: Unable to authenticate through LDAP for Hiveserver2 (also floods HS2 log with error messages)

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-19642:
---
Status: Patch Available  (was: Open)

> Error during Alert: Unable to authenticate through LDAP for Hiveserver2 (also 
> floods HS2 log with error messages)
> -
>
> Key: AMBARI-19642
> URL: https://issues.apache.org/jira/browse/AMBARI-19642
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19642.patch
>
>
> Ambari Alert can't authenticate through LDAP for HiveServer2 using the 
> ambari-qa user because there's no where set the ambari-qa password.
> {code}
> javax.security.sasl.SaslException: Error validating the login [Caused by 
> javax.security.sasl.AuthenticationException: Error validating LDAP user 
> [Caused by javax.naming.Authentic 
> ationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903C8, 
> comment: AcceptSecurityContext error, data 52e, v2580 
> at 
> org.apache.hive.service.auth.PlainSaslServer.evaluateResponse(PlainSaslServer.java:109)
>  
> at 
> org.apache.thrift.transport.TSaslTransport$SaslParticipant.evaluateChallengeOrResponse(TSaslTransport.java:509)
>  
> at org.apache.thrift.transport.TSaslTransport.open(TSaslTransport.java:264) 
> at 
> org.apache.thrift.transport.TSaslServerTransport.open(TSaslServerTransport.java:41)
>  
> at 
> org.apache.thrift.transport.TSaslServerTransport$Factory.getTransport(TSaslServerTransport.java:216)
>  
> at 
> org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:189)
>  
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>  
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>  
> at java.lang.Thread.run(Thread.java:744) 
> Caused by: javax.security.sasl.AuthenticationException: Error validating LDAP 
> user [Caused by javax.naming.AuthenticationException: [LDAP: error code 49 - 
> 80090308: LdapErr: DSID 
> -0C0903C8, comment: AcceptSecurityContext error, data 52e, v2580 
> at 
> org.apache.hive.service.auth.LdapAuthenticationProviderImpl.Authenticate(LdapAuthenticationProviderImpl.java:70)
>  
> at 
> org.apache.hive.service.auth.PlainSaslHelper$PlainServerCallbackHandler.handle(PlainSaslHelper.java:106)
>  
> at 
> org.apache.hive.service.auth.PlainSaslServer.evaluateResponse(PlainSaslServer.java:102)
>  
> ... 8 more 
> Caused by: javax.naming.AuthenticationException: [LDAP: error code 49 - 
> 80090308: LdapErr: DSID-0C0903C8, comment: AcceptSecurityContext error, data 
> 52e, v2580 
> at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3087) 
> at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3033) 
> at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2835) 
> at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2749) 
> at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:316) 
> at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:193) 
> at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:211) 
> at 
> com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:154) 
> at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:84) 
> at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684) 
> at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307) 
> at javax.naming.InitialContext.init(InitialContext.java:242) 
> at javax.naming.InitialContext.(InitialContext.java:216) 
> at 
> javax.naming.directory.InitialDirContext.(InitialDirContext.java:101) 
> at 
> org.apache.hive.service.auth.LdapAuthenticationProviderImpl.Authenticate(LdapAuthenticationProviderImpl.java:67)
>  
> ... 10 more 
> 2014-12-29 00:00:12,532 ERROR server.TThreadPoolServer 
> (TThreadPoolServer.java:run(215)) - Error occurred during processing of 
> message. 
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Error validating the login 
> at 
> org.apache.thrift.transport.TSaslServerTransport$Factory.getTransport(TSaslServerTransport.java:219)
>  
> at 
> org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:189)
>  
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>  
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>  
> at java.lang.Thread.run(Thread.java:744) 
> Caused by: org.apache.thrift.transport.TTransportException: Error validating 
> the login 
> at 
> 

[jira] [Commented] (AMBARI-19624) Missing fields for workflow SLA

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19624:


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

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

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

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

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

{color:red}-1 core tests{color}.  The test build failed in 
contrib/views/wfmanager/src/main/resources/ui 

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

This message is automatically generated.

> Missing fields for workflow SLA
> ---
>
> Key: AMBARI-19624
> URL: https://issues.apache.org/jira/browse/AMBARI-19624
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: Padma Priya Nagaraj
>  Labels: WFD
> Fix For: 2.5.0
>
> Attachments: AMBARI-19624_trunk.patch
>
>
> notification-msg and upstream-apps fields are missing for sla entity. Need to 
> add this for workflow and coordinator.



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

[jira] [Commented] (AMBARI-19629) Move schemaTool invocation out of configure() to hive_metastore start()

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19629:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #766 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/766/])
AMBARI-19629. Move schemaTool invocation out of configure() to (stoader: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9a555e7b14d8f6a85a052e94452f9376977b18f7])
* (edit) 
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py
* (edit) 
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py
* (edit) ambari-server/src/test/python/stacks/2.0.6/HIVE/test_hive_metastore.py
* (edit) ambari-server/src/test/python/stacks/2.1/HIVE/test_hive_metastore.py


> Move schemaTool invocation out of configure() to hive_metastore start()
> ---
>
> Key: AMBARI-19629
> URL: https://issues.apache.org/jira/browse/AMBARI-19629
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19629-branch-2.5.patch, AMBARI-19629-trunk.patch
>
>
> The {{schemaTool}} invocation should not be part of the {{configure}} method 
> as generally the {{configure}} method should be callable from {{install}} as 
> well and {{schemaTool}}  requires a running database to be available which is 
> not true if the default {{mysql}} database server shipped with {{hive}} is 
> used.
> Also since only one component can {{configure}} method at a time on the same 
> host in order to avoid overwriting common shared configs the {{configure}} 
> methods are synchronized across all components on a host. Having the 
> {{schemaTool}} lengthy operation in the {{configure}} method will delay the 
> execution of {{configure}} methods of the other components in case of 
> parallel command execution.



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

[jira] [Commented] (AMBARI-19629) Move schemaTool invocation out of configure() to hive_metastore start()

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19629:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6501 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6501/])
AMBARI-19629. Move schemaTool invocation out of configure() to (stoader: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6ba9bd0a7d5534838a7c1679675cf1848806990f])
* (edit) ambari-server/src/test/python/stacks/2.1/HIVE/test_hive_metastore.py
* (edit) 
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py
* (edit) 
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py
* (edit) ambari-server/src/test/python/stacks/2.0.6/HIVE/test_hive_metastore.py


> Move schemaTool invocation out of configure() to hive_metastore start()
> ---
>
> Key: AMBARI-19629
> URL: https://issues.apache.org/jira/browse/AMBARI-19629
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19629-branch-2.5.patch, AMBARI-19629-trunk.patch
>
>
> The {{schemaTool}} invocation should not be part of the {{configure}} method 
> as generally the {{configure}} method should be callable from {{install}} as 
> well and {{schemaTool}}  requires a running database to be available which is 
> not true if the default {{mysql}} database server shipped with {{hive}} is 
> used.
> Also since only one component can {{configure}} method at a time on the same 
> host in order to avoid overwriting common shared configs the {{configure}} 
> methods are synchronized across all components on a host. Having the 
> {{schemaTool}} lengthy operation in the {{configure}} method will delay the 
> execution of {{configure}} methods of the other components in case of 
> parallel command execution.



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

[jira] [Updated] (AMBARI-19641) Deleted configuration groups are displayed along with active group with is_current value set to true using Ambari API's

[Amruta Borkar (JIRA)]

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

Amruta Borkar updated AMBARI-19641:
---
Fix Version/s: trunk
   Status: Patch Available  (was: In Progress)

> Deleted configuration groups are displayed along with active group with 
> is_current value set to true using Ambari API's
> ---
>
> Key: AMBARI-19641
> URL: https://issues.apache.org/jira/browse/AMBARI-19641
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-19641.patch, ConfigHistory.png, 
> service_config_versions_HDFS_is_current
>
>
> Deleted config groups should not be displayed as active group. 



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

[jira] [Updated] (AMBARI-19641) Deleted configuration groups are displayed along with active group with is_current value set to true using Ambari API's

[Amruta Borkar (JIRA)]

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

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

> Deleted configuration groups are displayed along with active group with 
> is_current value set to true using Ambari API's
> ---
>
> Key: AMBARI-19641
> URL: https://issues.apache.org/jira/browse/AMBARI-19641
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-19641.patch, ConfigHistory.png, 
> service_config_versions_HDFS_is_current
>
>
> Deleted config groups should not be displayed as active group. 



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

[jira] [Commented] (AMBARI-19642) Error during Alert: Unable to authenticate through LDAP for Hiveserver2 (also floods HS2 log with error messages)

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-19642:


When LDAP is selected as the Hiveserver2 Authentication mechanism then the 
alert should switch to using username and password.

Introduce two new parameters for Hiveserver2 {{health_check_user}} and 
{{health_check_user_password}}. The default value for the user name should be 
the ambari service check user (namely ambari-qa). Default value for the 
password will be empty. Neither property should be required. If the 
authentication mechanism is selected as LDAP then stack advisor should warn 
(during validation) that valid username and password should be supplied that 
can authenticate using LDAP and this credential will be used by the Hive 
Alerts. Do not fail, if they are not supplied.

*Modification to the alert*

The alert currently uses the following command:
{code}
! beeline -u 
'jdbc:hive2://ctr-e101-1484344556054-0266-01-03.hwx.site:1/;transportMode=binary;principal=hive/_h...@example.com'
 -e '' 2>&1| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid URL'
{code}

When LDAP is enabled it (independent of whether kerberos is enabled or not) it 
should be modified to

{code}
! beeline -u 
'jdbc:hive2://ctr-e101-1484344556054-0266-01-03.hwx.site:1/;transportMode=binary'
 -n hrt_qa -p pwd -e '' 2>&1| awk '{print}'|grep -i -e 'Connection refused' -e 
'Invalid URL'
{code}

> Error during Alert: Unable to authenticate through LDAP for Hiveserver2 (also 
> floods HS2 log with error messages)
> -
>
> Key: AMBARI-19642
> URL: https://issues.apache.org/jira/browse/AMBARI-19642
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.5.0
>
>
> Ambari Alert can't authenticate through LDAP for HiveServer2 using the 
> ambari-qa user because there's no where set the ambari-qa password.
> {code}
> javax.security.sasl.SaslException: Error validating the login [Caused by 
> javax.security.sasl.AuthenticationException: Error validating LDAP user 
> [Caused by javax.naming.Authentic 
> ationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903C8, 
> comment: AcceptSecurityContext error, data 52e, v2580 
> at 
> org.apache.hive.service.auth.PlainSaslServer.evaluateResponse(PlainSaslServer.java:109)
>  
> at 
> org.apache.thrift.transport.TSaslTransport$SaslParticipant.evaluateChallengeOrResponse(TSaslTransport.java:509)
>  
> at org.apache.thrift.transport.TSaslTransport.open(TSaslTransport.java:264) 
> at 
> org.apache.thrift.transport.TSaslServerTransport.open(TSaslServerTransport.java:41)
>  
> at 
> org.apache.thrift.transport.TSaslServerTransport$Factory.getTransport(TSaslServerTransport.java:216)
>  
> at 
> org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:189)
>  
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>  
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>  
> at java.lang.Thread.run(Thread.java:744) 
> Caused by: javax.security.sasl.AuthenticationException: Error validating LDAP 
> user [Caused by javax.naming.AuthenticationException: [LDAP: error code 49 - 
> 80090308: LdapErr: DSID 
> -0C0903C8, comment: AcceptSecurityContext error, data 52e, v2580 
> at 
> org.apache.hive.service.auth.LdapAuthenticationProviderImpl.Authenticate(LdapAuthenticationProviderImpl.java:70)
>  
> at 
> org.apache.hive.service.auth.PlainSaslHelper$PlainServerCallbackHandler.handle(PlainSaslHelper.java:106)
>  
> at 
> org.apache.hive.service.auth.PlainSaslServer.evaluateResponse(PlainSaslServer.java:102)
>  
> ... 8 more 
> Caused by: javax.naming.AuthenticationException: [LDAP: error code 49 - 
> 80090308: LdapErr: DSID-0C0903C8, comment: AcceptSecurityContext error, data 
> 52e, v2580 
> at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3087) 
> at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3033) 
> at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2835) 
> at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2749) 
> at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:316) 
> at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:193) 
> at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:211) 
> at 
> com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:154) 
> at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:84) 
> at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684) 
> at 

[jira] [Updated] (AMBARI-19642) Error during Alert: Unable to authenticate through LDAP for Hiveserver2 (also floods HS2 log with error messages)

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-19642:
---
Description: 
Ambari Alert can't authenticate through LDAP for HiveServer2 using the 
ambari-qa user because there's no where set the ambari-qa password.

{code}
javax.security.sasl.SaslException: Error validating the login [Caused by 
javax.security.sasl.AuthenticationException: Error validating LDAP user [Caused 
by javax.naming.Authentic 
ationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903C8, 
comment: AcceptSecurityContext error, data 52e, v2580 
at 
org.apache.hive.service.auth.PlainSaslServer.evaluateResponse(PlainSaslServer.java:109)
 
at 
org.apache.thrift.transport.TSaslTransport$SaslParticipant.evaluateChallengeOrResponse(TSaslTransport.java:509)
 
at org.apache.thrift.transport.TSaslTransport.open(TSaslTransport.java:264) 
at 
org.apache.thrift.transport.TSaslServerTransport.open(TSaslServerTransport.java:41)
 
at 
org.apache.thrift.transport.TSaslServerTransport$Factory.getTransport(TSaslServerTransport.java:216)
 
at 
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:189)
 
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 
at java.lang.Thread.run(Thread.java:744) 
Caused by: javax.security.sasl.AuthenticationException: Error validating LDAP 
user [Caused by javax.naming.AuthenticationException: [LDAP: error code 49 - 
80090308: LdapErr: DSID 
-0C0903C8, comment: AcceptSecurityContext error, data 52e, v2580 
at 
org.apache.hive.service.auth.LdapAuthenticationProviderImpl.Authenticate(LdapAuthenticationProviderImpl.java:70)
 
at 
org.apache.hive.service.auth.PlainSaslHelper$PlainServerCallbackHandler.handle(PlainSaslHelper.java:106)
 
at 
org.apache.hive.service.auth.PlainSaslServer.evaluateResponse(PlainSaslServer.java:102)
 
... 8 more 
Caused by: javax.naming.AuthenticationException: [LDAP: error code 49 - 
80090308: LdapErr: DSID-0C0903C8, comment: AcceptSecurityContext error, data 
52e, v2580 
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3087) 
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3033) 
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2835) 
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2749) 
at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:316) 
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:193) 
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:211) 
at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:154) 
at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:84) 
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684) 
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307) 
at javax.naming.InitialContext.init(InitialContext.java:242) 
at javax.naming.InitialContext.(InitialContext.java:216) 
at javax.naming.directory.InitialDirContext.(InitialDirContext.java:101) 
at 
org.apache.hive.service.auth.LdapAuthenticationProviderImpl.Authenticate(LdapAuthenticationProviderImpl.java:67)
 
... 10 more 
2014-12-29 00:00:12,532 ERROR server.TThreadPoolServer 
(TThreadPoolServer.java:run(215)) - Error occurred during processing of 
message. 
java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
Error validating the login 
at 
org.apache.thrift.transport.TSaslServerTransport$Factory.getTransport(TSaslServerTransport.java:219)
 
at 
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:189)
 
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 
at java.lang.Thread.run(Thread.java:744) 
Caused by: org.apache.thrift.transport.TTransportException: Error validating 
the login 
at 
org.apache.thrift.transport.TSaslTransport.sendAndThrowMessage(TSaslTransport.java:221)
 
at org.apache.thrift.transport.TSaslTransport.open(TSaslTransport.java:297) 
at 
org.apache.thrift.transport.TSaslServerTransport.open(TSaslServerTransport.java:41)
 
at 
org.apache.thrift.transport.TSaslServerTransport$Factory.getTransport(TSaslServerTransport.java:216)
 
... 4 more
{code}

**LDAP doesn't except blank passwords**


It is expected that ambari-qa user able to authenticate through LDAP for 
HiveServer2

ANALYSIS:

1) We found when hive.server2.authentication=LDAP, the HiveServer2 log will 
show the LDAP error once Alert is turned on. 

2) Alert uses check_tcp_wrapper_sasl!1!LDAP!! 

3) When hive.server2.authentication=NONE, we don't get the Alert LDAP error for 
HiveServer2. 

or 

1) If we run "beeline" and !connect jdbc:hive2://:1 -n 
ambari-qa", we will get the LDAP error too.

  was:
Ambari Alert can't 

[jira] [Created] (AMBARI-19642) Error during Alert: Unable to authenticate through LDAP for Hiveserver2 (also floods HS2 log with error messages)

[Sumit Mohanty (JIRA)]

Sumit Mohanty created AMBARI-19642:
--

 Summary: Error during Alert: Unable to authenticate through LDAP 
for Hiveserver2 (also floods HS2 log with error messages)
 Key: AMBARI-19642
 URL: https://issues.apache.org/jira/browse/AMBARI-19642
 Project: Ambari
  Issue Type: Bug
  Components: stacks
Affects Versions: 2.5.0
Reporter: Sumit Mohanty
Assignee: Sumit Mohanty
Priority: Critical
 Fix For: 2.5.0


Ambari Alert can't authenticate through LDAP for HiveServer2 using the 
ambari-qa user because there's no where set the ambari-qa password.

javax.security.sasl.SaslException: Error validating the login [Caused by 
javax.security.sasl.AuthenticationException: Error validating LDAP user [Caused 
by javax.naming.Authentic 
ationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903C8, 
comment: AcceptSecurityContext error, data 52e, v2580 
at 
org.apache.hive.service.auth.PlainSaslServer.evaluateResponse(PlainSaslServer.java:109)
 
at 
org.apache.thrift.transport.TSaslTransport$SaslParticipant.evaluateChallengeOrResponse(TSaslTransport.java:509)
 
at org.apache.thrift.transport.TSaslTransport.open(TSaslTransport.java:264) 
at 
org.apache.thrift.transport.TSaslServerTransport.open(TSaslServerTransport.java:41)
 
at 
org.apache.thrift.transport.TSaslServerTransport$Factory.getTransport(TSaslServerTransport.java:216)
 
at 
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:189)
 
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 
at java.lang.Thread.run(Thread.java:744) 
Caused by: javax.security.sasl.AuthenticationException: Error validating LDAP 
user [Caused by javax.naming.AuthenticationException: [LDAP: error code 49 - 
80090308: LdapErr: DSID 
-0C0903C8, comment: AcceptSecurityContext error, data 52e, v2580 
at 
org.apache.hive.service.auth.LdapAuthenticationProviderImpl.Authenticate(LdapAuthenticationProviderImpl.java:70)
 
at 
org.apache.hive.service.auth.PlainSaslHelper$PlainServerCallbackHandler.handle(PlainSaslHelper.java:106)
 
at 
org.apache.hive.service.auth.PlainSaslServer.evaluateResponse(PlainSaslServer.java:102)
 
... 8 more 
Caused by: javax.naming.AuthenticationException: [LDAP: error code 49 - 
80090308: LdapErr: DSID-0C0903C8, comment: AcceptSecurityContext error, data 
52e, v2580 
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3087) 
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3033) 
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2835) 
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2749) 
at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:316) 
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:193) 
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:211) 
at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:154) 
at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:84) 
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684) 
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307) 
at javax.naming.InitialContext.init(InitialContext.java:242) 
at javax.naming.InitialContext.(InitialContext.java:216) 
at javax.naming.directory.InitialDirContext.(InitialDirContext.java:101) 
at 
org.apache.hive.service.auth.LdapAuthenticationProviderImpl.Authenticate(LdapAuthenticationProviderImpl.java:67)
 
... 10 more 
2014-12-29 00:00:12,532 ERROR server.TThreadPoolServer 
(TThreadPoolServer.java:run(215)) - Error occurred during processing of 
message. 
java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
Error validating the login 
at 
org.apache.thrift.transport.TSaslServerTransport$Factory.getTransport(TSaslServerTransport.java:219)
 
at 
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:189)
 
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 
at java.lang.Thread.run(Thread.java:744) 
Caused by: org.apache.thrift.transport.TTransportException: Error validating 
the login 
at 
org.apache.thrift.transport.TSaslTransport.sendAndThrowMessage(TSaslTransport.java:221)
 
at org.apache.thrift.transport.TSaslTransport.open(TSaslTransport.java:297) 
at 
org.apache.thrift.transport.TSaslServerTransport.open(TSaslServerTransport.java:41)
 
at 
org.apache.thrift.transport.TSaslServerTransport$Factory.getTransport(TSaslServerTransport.java:216)
 
... 4 more

**LDAP doesn't except blank passwords**


It is expected that ambari-qa user able to authenticate through LDAP for 
HiveServer2

ANALYSIS:

1) We found when hive.server2.authentication=LDAP, the HiveServer2 log will 
show 

[jira] [Updated] (AMBARI-19641) Deleted configuration groups are displayed along with active group with is_current value set to true using Ambari API's

[Amruta Borkar (JIRA)]

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

Amruta Borkar updated AMBARI-19641:
---
Description: Deleted config groups should not be displayed as active group 
with is_current flag set as true. 

> Deleted configuration groups are displayed along with active group with 
> is_current value set to true using Ambari API's
> ---
>
> Key: AMBARI-19641
> URL: https://issues.apache.org/jira/browse/AMBARI-19641
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Attachments: AMBARI-19641.patch, ConfigHistory.png, 
> service_config_versions_HDFS_is_current
>
>
> Deleted config groups should not be displayed as active group with is_current 
> flag set as true. 



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

[jira] [Updated] (AMBARI-19641) Deleted configuration groups are displayed along with active group with is_current value set to true using Ambari API's

[Amruta Borkar (JIRA)]

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

Amruta Borkar updated AMBARI-19641:
---
Description: Deleted config groups should not be displayed as active group. 
  (was: Deleted config groups should not be displayed as active group with 
is_current flag set as true. )

> Deleted configuration groups are displayed along with active group with 
> is_current value set to true using Ambari API's
> ---
>
> Key: AMBARI-19641
> URL: https://issues.apache.org/jira/browse/AMBARI-19641
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Attachments: AMBARI-19641.patch, ConfigHistory.png, 
> service_config_versions_HDFS_is_current
>
>
> Deleted config groups should not be displayed as active group. 



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

[jira] [Updated] (AMBARI-19641) Deleted configuration groups are displayed along with active group with is_current value set to true using Ambari API's

[Amruta Borkar (JIRA)]

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

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

> Deleted configuration groups are displayed along with active group with 
> is_current value set to true using Ambari API's
> ---
>
> Key: AMBARI-19641
> URL: https://issues.apache.org/jira/browse/AMBARI-19641
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Attachments: AMBARI-19641.patch, ConfigHistory.png, 
> service_config_versions_HDFS_is_current
>
>




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

[jira] [Updated] (AMBARI-19641) Deleted configuration groups are displayed along with active group with is_current value set to true using Ambari API's

[Amruta Borkar (JIRA)]

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

Amruta Borkar updated AMBARI-19641:
---
Attachment: ConfigHistory.png
service_config_versions_HDFS_is_current

> Deleted configuration groups are displayed along with active group with 
> is_current value set to true using Ambari API's
> ---
>
> Key: AMBARI-19641
> URL: https://issues.apache.org/jira/browse/AMBARI-19641
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Attachments: ConfigHistory.png, 
> service_config_versions_HDFS_is_current
>
>




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

[jira] [Created] (AMBARI-19641) Deleted configuration groups are displayed along with active group with is_current value set to true using Ambari API's

[Amruta Borkar (JIRA)]

Amruta Borkar created AMBARI-19641:
--

 Summary: Deleted configuration groups are displayed along with 
active group with is_current value set to true using Ambari API's
 Key: AMBARI-19641
 URL: https://issues.apache.org/jira/browse/AMBARI-19641
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Reporter: Amruta Borkar
Assignee: Amruta Borkar






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

[jira] [Updated] (AMBARI-19624) Missing fields for workflow SLA

[Padma Priya Nagaraj (JIRA)]

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

Padma Priya Nagaraj updated AMBARI-19624:
-
Attachment: AMBARI-19624_trunk.patch

> Missing fields for workflow SLA
> ---
>
> Key: AMBARI-19624
> URL: https://issues.apache.org/jira/browse/AMBARI-19624
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: Padma Priya Nagaraj
>  Labels: WFD
> Fix For: 2.5.0
>
> Attachments: AMBARI-19624_trunk.patch
>
>
> notification-msg and upstream-apps fields are missing for sla entity. Need to 
> add this for workflow and coordinator.



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

[jira] [Updated] (AMBARI-19624) Missing fields for workflow SLA

[Padma Priya Nagaraj (JIRA)]

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

Padma Priya Nagaraj updated AMBARI-19624:
-
Attachment: (was: AMBARI-19624_trunk.patch)

> Missing fields for workflow SLA
> ---
>
> Key: AMBARI-19624
> URL: https://issues.apache.org/jira/browse/AMBARI-19624
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: Padma Priya Nagaraj
>  Labels: WFD
> Fix For: 2.5.0
>
>
> notification-msg and upstream-apps fields are missing for sla entity. Need to 
> add this for workflow and coordinator.



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

[jira] [Updated] (AMBARI-19618) Make cohosted components configurable in metainfo.xml instead of hardcoding in UI

[Yao Lei (JIRA)]

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

Yao Lei updated AMBARI-19618:
-
Status: Patch Available  (was: Open)

> Make cohosted components configurable in metainfo.xml instead of hardcoding 
> in UI
> -
>
> Key: AMBARI-19618
> URL: https://issues.apache.org/jira/browse/AMBARI-19618
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Yao Lei
> Fix For: trunk, 3.0.0
>
> Attachments: after_patched_hive1.png, after_patched_hive2.png, 
> after_patched_ranger1.png, after_patched_ranger2.png, 
> after_patched_ranger3.png, AMBARI-19618.patch
>
>
> Cohosted components information now is hardcoded in 
> stack_service_component.js  as following:
> App.StackServiceComponent.coHost = {
>   'WEBHCAT_SERVER': 'HIVE_SERVER'
> };
> It's better to move them from javascript to metainfom.xml by adding tag 
> in stack like following:
> 
>   WEBHCAT_SERVER
>   WebHCat Server
>   MASTER
>   1
>   true
>   true
>   HIVE_SERVER
> 
> 
>RANGER_USERSYNC
>Ranger Usersync
>MASTER
>1
>true
>RANGER_ADMIN
> 



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

[jira] [Updated] (AMBARI-19618) Make cohosted components configurable in metainfo.xml instead of hardcoding in UI

[Yao Lei (JIRA)]

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

Yao Lei updated AMBARI-19618:
-
Summary: Make cohosted components configurable in metainfo.xml instead of 
hardcoding in UI  (was: Make cohost components configurable in metainfo.xml 
instead of hardcoding in UI)

> Make cohosted components configurable in metainfo.xml instead of hardcoding 
> in UI
> -
>
> Key: AMBARI-19618
> URL: https://issues.apache.org/jira/browse/AMBARI-19618
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Yao Lei
> Fix For: trunk, 3.0.0
>
> Attachments: after_patched_hive1.png, after_patched_hive2.png, 
> after_patched_ranger1.png, after_patched_ranger2.png, 
> after_patched_ranger3.png
>
>
> Cohost components information now is hardcoded in stack_service_component.js  
> as following:
> App.StackServiceComponent.coHost = {
>   'WEBHCAT_SERVER': 'HIVE_SERVER'
> };
> It's better to move them from javascript to metainfom.xml by adding tag 
> in stack like following:
> 
>   WEBHCAT_SERVER
>   WebHCat Server
>   MASTER
>   1
>   true
>   true
>   HIVE_SERVER
> 
> 
>RANGER_USERSYNC
>Ranger Usersync
>MASTER
>1
>true
>RANGER_ADMIN
> 



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

[jira] [Updated] (AMBARI-19618) Make cohosted components configurable in metainfo.xml instead of hardcoding in UI

[Yao Lei (JIRA)]

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

Yao Lei updated AMBARI-19618:
-
Description: 
Cohosted components information now is hardcoded in stack_service_component.js  
as following:

App.StackServiceComponent.coHost = {
  'WEBHCAT_SERVER': 'HIVE_SERVER'
};

It's better to move them from javascript to metainfom.xml by adding tag 
in stack like following:


  WEBHCAT_SERVER
  WebHCat Server
  MASTER
  1
  true
  true
  HIVE_SERVER



   RANGER_USERSYNC
   Ranger Usersync
   MASTER
   1
   true
   RANGER_ADMIN



  was:
Cohost components information now is hardcoded in stack_service_component.js  
as following:

App.StackServiceComponent.coHost = {
  'WEBHCAT_SERVER': 'HIVE_SERVER'
};

It's better to move them from javascript to metainfom.xml by adding tag 
in stack like following:


  WEBHCAT_SERVER
  WebHCat Server
  MASTER
  1
  true
  true
  HIVE_SERVER



   RANGER_USERSYNC
   Ranger Usersync
   MASTER
   1
   true
   RANGER_ADMIN




> Make cohosted components configurable in metainfo.xml instead of hardcoding 
> in UI
> -
>
> Key: AMBARI-19618
> URL: https://issues.apache.org/jira/browse/AMBARI-19618
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Yao Lei
> Fix For: trunk, 3.0.0
>
> Attachments: after_patched_hive1.png, after_patched_hive2.png, 
> after_patched_ranger1.png, after_patched_ranger2.png, 
> after_patched_ranger3.png
>
>
> Cohosted components information now is hardcoded in 
> stack_service_component.js  as following:
> App.StackServiceComponent.coHost = {
>   'WEBHCAT_SERVER': 'HIVE_SERVER'
> };
> It's better to move them from javascript to metainfom.xml by adding tag 
> in stack like following:
> 
>   WEBHCAT_SERVER
>   WebHCat Server
>   MASTER
>   1
>   true
>   true
>   HIVE_SERVER
> 
> 
>RANGER_USERSYNC
>Ranger Usersync
>MASTER
>1
>true
>RANGER_ADMIN
> 



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

[jira] [Updated] (AMBARI-19618) Make cohost components configurable in metainfo.xml instead of hardcoding in UI

[Yao Lei (JIRA)]

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

Yao Lei updated AMBARI-19618:
-
Attachment: after_patched_ranger3.png
after_patched_ranger2.png
after_patched_ranger1.png
after_patched_hive2.png
after_patched_hive1.png

> Make cohost components configurable in metainfo.xml instead of hardcoding in 
> UI
> ---
>
> Key: AMBARI-19618
> URL: https://issues.apache.org/jira/browse/AMBARI-19618
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Yao Lei
> Fix For: trunk, 3.0.0
>
> Attachments: after_patched_hive1.png, after_patched_hive2.png, 
> after_patched_ranger1.png, after_patched_ranger2.png, 
> after_patched_ranger3.png
>
>
> Cohost components information now is hardcoded in stack_service_component.js  
> as following:
> App.StackServiceComponent.coHost = {
>   'WEBHCAT_SERVER': 'HIVE_SERVER'
> };
> It's better to move them from javascript to metainfom.xml by adding tag 
> in stack like following:
> 
>   WEBHCAT_SERVER
>   WebHCat Server
>   MASTER
>   1
>   true
>   true
>   HIVE_SERVER
> 
> 
>RANGER_USERSYNC
>Ranger Usersync
>MASTER
>1
>true
>RANGER_ADMIN
> 



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

[jira] [Commented] (AMBARI-19601) Warnings on ambari server upgrade related to HDF paths

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19601:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6499 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6499/])
AMBARI-19601: Warnings on ambari server upgrade related to HDF paths (jluniya: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=77b5776617bb448019250d7785c103dbde4ecd24])
* (edit) ambari-server/src/main/package/rpm/preinstall.sh
* (edit) ambari-server/src/main/package/deb/control/preinst


> Warnings on ambari server upgrade related to HDF paths
> --
>
> Key: AMBARI-19601
> URL: https://issues.apache.org/jira/browse/AMBARI-19601
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.2
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.5.0
>
> Attachments: AMBARI-19601.patch
>
>
> Ambari 2.4.1.0 and HDF 2.0.1.0 was upgraded to Ambari 2.4.2.0 and HDF 2.1 
> mpack
> Saw the following warnings on ambari-server upgrade
> {code}
> [root@arpit-hdf-eu-5 ~]# ambari-server upgrade
> Using python  /usr/bin/python
> Upgrading ambari-server
> Updating properties in ambari.properties ...
> WARNING: Original file ambari-env.sh kept
> WARNING: Original file krb5JAASLogin.conf kept
> File krb5JAASLogin.conf updated.
> Fixing database objects owner
> Ambari Server configured for MySQL. Confirm you have made a backup of the 
> Ambari Server database [y/n] (y)?
> Upgrading database schema
> Adjusting ambari-server permissions and ownership...
> WARNING: Command chown  -R -L root /var/lib/ambari-server returned exit code 
> /var/lib/ambari-server with message: chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/repos': 
> No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/properties':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/metainfo.xml':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/ZOOKEEPER':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/LOGSEARCH':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/KAFKA':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/stack_advisor.py':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/AMBARI_INFRA':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/STORM':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/AMBARI_METRICS':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/KERBEROS':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/NIFI':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/RANGER':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/widgets.json':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/kerberos.json':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/configuration':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/role_command_order.json':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/hooks': 
> No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/common-services_21_11_16_21_33.old/NIFI/1.0.0':
>  No such file or directory
> Ambari Server 'upgrade' completed successfully.
> {code}



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

[jira] [Commented] (AMBARI-19637) No baseURL field on Register Version page if repoinfo.xml contains only one baseurl

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19637:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6499 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6499/])
AMBARI-19637 - No baseURL field on Register Version page if repoinfo.xml 
(rzang: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=53b3ecfd91eb2a4d21462c28e3df15f1fe18fbcb])
* (edit) ambari-admin/src/main/resources/ui/admin-web/app/styles/main.css
* (edit) 
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsEditCtrl.js
* (edit) 
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsCreateCtrl.js


> No baseURL field on Register Version page if repoinfo.xml contains only one 
> baseurl
> ---
>
> Key: AMBARI-19637
> URL: https://issues.apache.org/jira/browse/AMBARI-19637
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
>Priority: Critical
> Attachments: AMBARI-19637.patch
>
>
> The issue here is that if repoinfo.xml declares only one repo url per os 
> family, then UI fails  with list index out bounds error
> *repoinfo.xml*
> {code}
>   
> 
>   http://foo
>   PERF-1.0
>   PERF
>   true
> 
>   
> {code}
> errors in console 
> {code}TypeError: Cannot read property 'Repositories' of undefined
> at 
> http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4560:44
> at Array.forEach (native)
> at Scope.$scope.setVersionSelected 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4557:42)
> at 
> http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4669:16
> at wrappedCallback 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:23340:81)
> at 
> http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:23426:26
> at Scope.$eval 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24469:28)
> at Scope.$digest 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24281:31)
> at Scope.$apply 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24573:24)
> at done 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:20146:45)(anonymous
>  function) @ vendor.js:21839
> 6vendor.js:21839 TypeError: Cannot read property 'Repositories' of undefined
> at 
> http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4560:44
> at Array.forEach (native)
> at Scope.$scope.setVersionSelected 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4557:42)
> at Scope.$scope.onStackIdChange 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4578:12)
> at 
> http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:22614:21
> at callback 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:30903:17)
> at Scope.$eval 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24469:28)
> at Scope.$apply 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24567:23)
> at HTMLLIElement. 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:30908:23)
> at HTMLLIElement.jQuery.event.dispatch 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:4737:27){code}
> The hardcoded index is here:
> {code}response.updateObj.operating_systems.forEach(function(os) {
>   $scope.defaulfOSRepos[os.OperatingSystems.os_type] = {
> defaultBaseUrl: os.repositories[0].Repositories.base_url,
> defaultUtilsUrl: os.repositories[1].Repositories.base_url
>   };
> });{code}



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

[jira] [Updated] (AMBARI-19618) Make cohost components configurable in metainfo.xml instead of hardcoding in UI

[Yao Lei (JIRA)]

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

Yao Lei updated AMBARI-19618:
-
Fix Version/s: trunk

> Make cohost components configurable in metainfo.xml instead of hardcoding in 
> UI
> ---
>
> Key: AMBARI-19618
> URL: https://issues.apache.org/jira/browse/AMBARI-19618
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Yao Lei
> Fix For: trunk, 3.0.0
>
>
> Cohost components information now is hardcoded in stack_service_component.js  
> as following:
> App.StackServiceComponent.coHost = {
>   'WEBHCAT_SERVER': 'HIVE_SERVER'
> };
> It's better to move them from javascript to metainfom.xml by adding tag 
> in stack like following:
> 
>   WEBHCAT_SERVER
>   WebHCat Server
>   MASTER
>   1
>   true
>   true
>   HIVE_SERVER
> 
> 
>RANGER_USERSYNC
>Ranger Usersync
>MASTER
>1
>true
>RANGER_ADMIN
> 



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

[jira] [Updated] (AMBARI-19618) Make cohost components configurable in metainfo.xml instead of hardcoding in UI

[Yao Lei (JIRA)]

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

Yao Lei updated AMBARI-19618:
-
Fix Version/s: (was: 2.5.0)
   (was: trunk)
   3.0.0

> Make cohost components configurable in metainfo.xml instead of hardcoding in 
> UI
> ---
>
> Key: AMBARI-19618
> URL: https://issues.apache.org/jira/browse/AMBARI-19618
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Yao Lei
> Fix For: 3.0.0
>
>
> Cohost components information now is hardcoded in stack_service_component.js  
> as following:
> App.StackServiceComponent.coHost = {
>   'WEBHCAT_SERVER': 'HIVE_SERVER'
> };
> It's better to move them from javascript to metainfom.xml by adding tag 
> in stack like following:
> 
>   WEBHCAT_SERVER
>   WebHCat Server
>   MASTER
>   1
>   true
>   true
>   HIVE_SERVER
> 
> 
>RANGER_USERSYNC
>Ranger Usersync
>MASTER
>1
>true
>RANGER_ADMIN
> 



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

[jira] [Commented] (AMBARI-19637) No baseURL field on Register Version page if repoinfo.xml contains only one baseurl

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19637:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #765 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/765/])
AMBARI-19637 - No baseURL field on Register Version page if repoinfo.xml 
(rzang: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a03389c750e88ade0325011ccc09b539983dd974])
* (edit) ambari-admin/src/main/resources/ui/admin-web/app/styles/main.css
* (edit) 
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsEditCtrl.js
* (edit) 
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsCreateCtrl.js


> No baseURL field on Register Version page if repoinfo.xml contains only one 
> baseurl
> ---
>
> Key: AMBARI-19637
> URL: https://issues.apache.org/jira/browse/AMBARI-19637
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
>Priority: Critical
> Attachments: AMBARI-19637.patch
>
>
> The issue here is that if repoinfo.xml declares only one repo url per os 
> family, then UI fails  with list index out bounds error
> *repoinfo.xml*
> {code}
>   
> 
>   http://foo
>   PERF-1.0
>   PERF
>   true
> 
>   
> {code}
> errors in console 
> {code}TypeError: Cannot read property 'Repositories' of undefined
> at 
> http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4560:44
> at Array.forEach (native)
> at Scope.$scope.setVersionSelected 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4557:42)
> at 
> http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4669:16
> at wrappedCallback 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:23340:81)
> at 
> http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:23426:26
> at Scope.$eval 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24469:28)
> at Scope.$digest 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24281:31)
> at Scope.$apply 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24573:24)
> at done 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:20146:45)(anonymous
>  function) @ vendor.js:21839
> 6vendor.js:21839 TypeError: Cannot read property 'Repositories' of undefined
> at 
> http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4560:44
> at Array.forEach (native)
> at Scope.$scope.setVersionSelected 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4557:42)
> at Scope.$scope.onStackIdChange 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4578:12)
> at 
> http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:22614:21
> at callback 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:30903:17)
> at Scope.$eval 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24469:28)
> at Scope.$apply 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24567:23)
> at HTMLLIElement. 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:30908:23)
> at HTMLLIElement.jQuery.event.dispatch 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:4737:27){code}
> The hardcoded index is here:
> {code}response.updateObj.operating_systems.forEach(function(os) {
>   $scope.defaulfOSRepos[os.OperatingSystems.os_type] = {
> defaultBaseUrl: os.repositories[0].Repositories.base_url,
> defaultUtilsUrl: os.repositories[1].Repositories.base_url
>   };
> });{code}



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

[jira] [Commented] (AMBARI-19639) Remove the hardcoding for LLAP app name and read it from config 'llap_app_name'.

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19639:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #765 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/765/])
AMBARI-19639. Remove the hardcoding for LLAP app name and read it from 
(sshridhar: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ccd10f67539e6acc32af373e815e430d19aad21f])
* (edit) ambari-server/src/test/python/stacks/2.5/configs/hsi_default.json
* (edit) 
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py
* (edit) 
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py
* (edit) ambari-server/src/test/python/stacks/2.5/configs/hsi_ha.json


> Remove the hardcoding for LLAP app name and read it from config 
> 'llap_app_name'.
> 
>
> Key: AMBARI-19639
> URL: https://issues.apache.org/jira/browse/AMBARI-19639
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19639.patch
>
>




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

[jira] [Commented] (AMBARI-19601) Warnings on ambari server upgrade related to HDF paths

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19601:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #765 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/765/])
AMBARI-19601: Warnings on ambari server upgrade related to HDF paths (jluniya: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9dc0e75e0f3886730e2d64b855d37dc459c13642])
* (edit) ambari-server/src/main/package/deb/control/preinst
* (edit) ambari-server/src/main/package/rpm/preinstall.sh


> Warnings on ambari server upgrade related to HDF paths
> --
>
> Key: AMBARI-19601
> URL: https://issues.apache.org/jira/browse/AMBARI-19601
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.2
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.5.0
>
> Attachments: AMBARI-19601.patch
>
>
> Ambari 2.4.1.0 and HDF 2.0.1.0 was upgraded to Ambari 2.4.2.0 and HDF 2.1 
> mpack
> Saw the following warnings on ambari-server upgrade
> {code}
> [root@arpit-hdf-eu-5 ~]# ambari-server upgrade
> Using python  /usr/bin/python
> Upgrading ambari-server
> Updating properties in ambari.properties ...
> WARNING: Original file ambari-env.sh kept
> WARNING: Original file krb5JAASLogin.conf kept
> File krb5JAASLogin.conf updated.
> Fixing database objects owner
> Ambari Server configured for MySQL. Confirm you have made a backup of the 
> Ambari Server database [y/n] (y)?
> Upgrading database schema
> Adjusting ambari-server permissions and ownership...
> WARNING: Command chown  -R -L root /var/lib/ambari-server returned exit code 
> /var/lib/ambari-server with message: chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/repos': 
> No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/properties':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/metainfo.xml':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/ZOOKEEPER':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/LOGSEARCH':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/KAFKA':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/stack_advisor.py':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/AMBARI_INFRA':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/STORM':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/AMBARI_METRICS':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/KERBEROS':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/NIFI':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/RANGER':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/widgets.json':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/kerberos.json':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/configuration':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/role_command_order.json':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/hooks': 
> No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/common-services_21_11_16_21_33.old/NIFI/1.0.0':
>  No such file or directory
> Ambari Server 'upgrade' completed successfully.
> {code}



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

[jira] [Updated] (AMBARI-19413) Support Ceph for Ambari Service

[Gavin (JIRA)]

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

Gavin updated AMBARI-19413:
---
Status: Open  (was: Patch Available)

> Support Ceph for Ambari Service
> ---
>
> Key: AMBARI-19413
> URL: https://issues.apache.org/jira/browse/AMBARI-19413
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Affects Versions: 2.2.1
> Environment: CentOS 6
>Reporter: Gavin
>  Labels: ambari, ceph
> Fix For: 2.2.1
>
> Attachments: 0001-Support-Ceph-for-Ambari-Service.patch
>
>
> Allow Ceph to be installed via Ambari
> I'm trying to do
> ceph-repo addr: http://archive.redoop.com/crh4/redhat/6/x86_64/crh/4.9/



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

[jira] [Updated] (AMBARI-19640) Hue - Ambari Migration is not working in Kerberized envirionment

[Ishan Bhatt (JIRA)]

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

Ishan Bhatt updated AMBARI-19640:
-
Status: Patch Available  (was: Open)

> Hue - Ambari Migration is not working in Kerberized envirionment
> 
>
> Key: AMBARI-19640
> URL: https://issues.apache.org/jira/browse/AMBARI-19640
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
> Fix For: trunk
>
> Attachments: AMBARI-19640.patch
>
>
> Steps to reproduce:-
> 1. Create a cluster with kerberized  environment
> 2. Set the Kerborized parameter in while creating the view
> 3. Migrate the artifacts using Hue-Amabari . 
> It failed with below errors:-
> {code}
> 12 Jan 2017 13:31:38,125  WARN [Thread-69] ViewContextImpl:497 - Error during 
> parsing 'http://172.22.104.166:8080/#' parameter. Leaving original value.
> 12 Jan 2017 13:31:38,126  WARN [Thread-69] ViewContextImpl:497 - Error during 
> parsing 'http://172.22.104.166:8080/#' parameter. Leaving original value.
> 12 Jan 2017 13:31:38,171  WARN [Thread-69] UserGroupInformation:1551 - 
> PriviledgedActionException as:hdfs (auth:PROXY) via ambari-server-cl1 
> (auth:SIMPLE) 
> cause:org.apache.hadoop.ipc.RemoteException(java.lang.SecurityException): 
> Failed to obtain user group information: java.io.IOException: Usernames not 
> matched: name=admin != expected=ambari-server-cl1
> 12 Jan 2017 13:31:38,171 ERROR [Thread-69] 
> HiveHistoryQueryMigrationImplementation:493 - Exception in Webhdfs
> org.apache.hadoop.ipc.RemoteException(java.lang.SecurityException): Failed to 
> obtain user group information: java.io.IOException: Usernames not matched: 
> name=admin != expected=ambari-server-cl1
>   at 
> org.apache.hadoop.hdfs.web.JsonUtil.toRemoteException(JsonUtil.java:157)
>   at 
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem.validateResponse(WebHdfsFileSystem.java:318)
>   at 
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem.access$700(WebHdfsFileSystem.java:105)
>   at 
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem$AbstractRunner.getResponse(WebHdfsFileSystem.java:628)
>   at 
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem$AbstractRunner.run(WebHdfsFileSystem.java:535)
>   at 
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem.run(WebHdfsFileSystem.java:424)
>   at 
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem.getDelegationToken(WebHdfsFileSystem.java:953)
>   at 
> org.apache.hadoop.hdfs.web.TokenAspect.ensureTokenInitialized(TokenAspect.java:143)
>   at 
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem.getDelegationToken(WebHdfsFileSystem.java:227)
>   at 
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem.getAuthParameters(WebHdfsFileSystem.java:381)
>   at 
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem.toUrl(WebHdfsFileSystem.java:402)
>   at 
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem$FsPathRunner.getUrl(WebHdfsFileSystem.java:652)
>   at 
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem$AbstractRunner.init(WebHdfsFileSystem.java:485)
>   at 
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem$AbstractRunner.run(WebHdfsFileSystem.java:531)
>   at 
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem.run(WebHdfsFileSystem.java:424)
>   at 
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem.mkdirs(WebHdfsFileSystem.java:704)
>   at org.apache.hadoop.fs.FileSystem.mkdirs(FileSystem.java:1816)
>   at 
> org.apache.ambari.view.huetoambarimigration.migration.hive.historyquery.HiveHistoryQueryMigrationImplementation$2.run(HiveHistoryQueryMigrationImplementation.java:488)
>   at 
> org.apache.ambari.view.huetoambarimigration.migration.hive.historyquery.HiveHistoryQueryMigrationImplementation$2.run(HiveHistoryQueryMigrationImplementation.java:482)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:422)
>   at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1548)
>   at 
> org.apache.ambari.view.huetoambarimigration.migration.hive.historyquery.HiveHistoryQueryMigrationImplementation.createDirKerberorisedSecured(HiveHistoryQueryMigrationImplementation.java:482)
>   at 
> org.apache.ambari.view.huetoambarimigration.migration.hive.historyquery.HiveHistoryMigrationUtility.hiveHistoryQueryMigration(HiveHistoryMigrationUtility.java:200)
>   at 
> org.apache.ambari.view.huetoambarimigration.migration.hive.historyquery.HiveHistoryStartJob.run(HiveHistoryStartJob.java:65)
> {code} 



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

[jira] [Updated] (AMBARI-19640) Hue - Ambari Migration is not working in Kerberized envirionment

[Ishan Bhatt (JIRA)]

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

Ishan Bhatt updated AMBARI-19640:
-
Attachment: AMBARI-19640.patch

> Hue - Ambari Migration is not working in Kerberized envirionment
> 
>
> Key: AMBARI-19640
> URL: https://issues.apache.org/jira/browse/AMBARI-19640
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
> Fix For: trunk
>
> Attachments: AMBARI-19640.patch
>
>
> Steps to reproduce:-
> 1. Create a cluster with kerberized  environment
> 2. Set the Kerborized parameter in while creating the view
> 3. Migrate the artifacts using Hue-Amabari . 
> It failed with below errors:-
> {code}
> 12 Jan 2017 13:31:38,125  WARN [Thread-69] ViewContextImpl:497 - Error during 
> parsing 'http://172.22.104.166:8080/#' parameter. Leaving original value.
> 12 Jan 2017 13:31:38,126  WARN [Thread-69] ViewContextImpl:497 - Error during 
> parsing 'http://172.22.104.166:8080/#' parameter. Leaving original value.
> 12 Jan 2017 13:31:38,171  WARN [Thread-69] UserGroupInformation:1551 - 
> PriviledgedActionException as:hdfs (auth:PROXY) via ambari-server-cl1 
> (auth:SIMPLE) 
> cause:org.apache.hadoop.ipc.RemoteException(java.lang.SecurityException): 
> Failed to obtain user group information: java.io.IOException: Usernames not 
> matched: name=admin != expected=ambari-server-cl1
> 12 Jan 2017 13:31:38,171 ERROR [Thread-69] 
> HiveHistoryQueryMigrationImplementation:493 - Exception in Webhdfs
> org.apache.hadoop.ipc.RemoteException(java.lang.SecurityException): Failed to 
> obtain user group information: java.io.IOException: Usernames not matched: 
> name=admin != expected=ambari-server-cl1
>   at 
> org.apache.hadoop.hdfs.web.JsonUtil.toRemoteException(JsonUtil.java:157)
>   at 
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem.validateResponse(WebHdfsFileSystem.java:318)
>   at 
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem.access$700(WebHdfsFileSystem.java:105)
>   at 
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem$AbstractRunner.getResponse(WebHdfsFileSystem.java:628)
>   at 
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem$AbstractRunner.run(WebHdfsFileSystem.java:535)
>   at 
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem.run(WebHdfsFileSystem.java:424)
>   at 
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem.getDelegationToken(WebHdfsFileSystem.java:953)
>   at 
> org.apache.hadoop.hdfs.web.TokenAspect.ensureTokenInitialized(TokenAspect.java:143)
>   at 
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem.getDelegationToken(WebHdfsFileSystem.java:227)
>   at 
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem.getAuthParameters(WebHdfsFileSystem.java:381)
>   at 
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem.toUrl(WebHdfsFileSystem.java:402)
>   at 
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem$FsPathRunner.getUrl(WebHdfsFileSystem.java:652)
>   at 
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem$AbstractRunner.init(WebHdfsFileSystem.java:485)
>   at 
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem$AbstractRunner.run(WebHdfsFileSystem.java:531)
>   at 
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem.run(WebHdfsFileSystem.java:424)
>   at 
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem.mkdirs(WebHdfsFileSystem.java:704)
>   at org.apache.hadoop.fs.FileSystem.mkdirs(FileSystem.java:1816)
>   at 
> org.apache.ambari.view.huetoambarimigration.migration.hive.historyquery.HiveHistoryQueryMigrationImplementation$2.run(HiveHistoryQueryMigrationImplementation.java:488)
>   at 
> org.apache.ambari.view.huetoambarimigration.migration.hive.historyquery.HiveHistoryQueryMigrationImplementation$2.run(HiveHistoryQueryMigrationImplementation.java:482)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:422)
>   at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1548)
>   at 
> org.apache.ambari.view.huetoambarimigration.migration.hive.historyquery.HiveHistoryQueryMigrationImplementation.createDirKerberorisedSecured(HiveHistoryQueryMigrationImplementation.java:482)
>   at 
> org.apache.ambari.view.huetoambarimigration.migration.hive.historyquery.HiveHistoryMigrationUtility.hiveHistoryQueryMigration(HiveHistoryMigrationUtility.java:200)
>   at 
> org.apache.ambari.view.huetoambarimigration.migration.hive.historyquery.HiveHistoryStartJob.run(HiveHistoryStartJob.java:65)
> {code} 



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

[jira] [Commented] (AMBARI-19639) Remove the hardcoding for LLAP app name and read it from config 'llap_app_name'.

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19639:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6498 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6498/])
AMBARI-19639. Remove the hardcoding for LLAP app name and read it from 
(sshridhar: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ac907ced86bbec35f3cf068b4764c23789cf3a17])
* (edit) 
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py
* (edit) 
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py
* (edit) ambari-server/src/test/python/stacks/2.5/configs/hsi_ha.json
* (edit) ambari-server/src/test/python/stacks/2.5/configs/hsi_default.json


> Remove the hardcoding for LLAP app name and read it from config 
> 'llap_app_name'.
> 
>
> Key: AMBARI-19639
> URL: https://issues.apache.org/jira/browse/AMBARI-19639
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19639.patch
>
>




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

[jira] [Commented] (AMBARI-19623) Atlas startup failed with ZkTimeoutException exception, zookeeper timeout values are very low.

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19623:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6498 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6498/])
AMBARI-19623. Atlas startup failed with ZkTimeoutException exception, 
(afernandez: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=bbacefd44a52bfd0a82c6067f9974944623cfdec])
* (edit) 
ambari-server/src/main/resources/common-services/ATLAS/0.7.0.2.5/configuration/application-properties.xml
* (edit) 
ambari-server/src/main/resources/common-services/ZOOKEEPER/3.4.5/configuration/zoo.cfg.xml
* (edit) 
ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/configuration/application-properties.xml


> Atlas startup failed with ZkTimeoutException exception, zookeeper timeout 
> values are very low.
> --
>
> Key: AMBARI-19623
> URL: https://issues.apache.org/jira/browse/AMBARI-19623
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Ayub Khan
>Assignee: Ayub Khan
>Priority: Critical
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19623.patch
>
>
> Currently zookeeper connect/session timeout values for atlas are set to 
> 200/400 ms respectively which are very low and not practical/recommended 
> values. Due to this atlas startup fails more frequently.
> The jira is set recommended values for zookeeper timeout configuration.
> {noformat}
> atlas.kafka.zookeeper.connection.timeout.ms=3
> atlas.kafka.zookeeper.session.timeout.ms=6
> atlas.audit.zookeeper.session.timeout.ms=6
> {noformat} 



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

[jira] [Commented] (AMBARI-19638) Improve delete logging for topology artifacts

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19638:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6498 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6498/])
AMBARI-19638. Improve delete logging for topology artifacts. (swagle) (swagle: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ddcc13b40902f7fc9144bcaa2af5b54d85442dfa])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostResourceProvider.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/Clusters.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ConfigGroupResourceProvider.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClustersImpl.java


> Improve delete logging for topology artifacts
> -
>
> Key: AMBARI-19638
> URL: https://issues.apache.org/jira/browse/AMBARI-19638
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
> Fix For: 2.5.0
>
> Attachments: AMBARI-19638.patch
>
>
> Very hard to find from Ambari log when a SCH was deleted. We print so much 
> log for all kinds of this, at a minimum all deleted need to be logged.
> Scope: SC, SCH and Host. Make sure we have INFO level log for these.



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

[jira] [Created] (AMBARI-19640) Hue - Ambari Migration is not working in Kerberized envirionment

[Ishan Bhatt (JIRA)]

Ishan Bhatt created AMBARI-19640:


 Summary: Hue - Ambari Migration is not working in Kerberized 
envirionment
 Key: AMBARI-19640
 URL: https://issues.apache.org/jira/browse/AMBARI-19640
 Project: Ambari
  Issue Type: Bug
  Components: ambari-views
Reporter: Ishan Bhatt
Assignee: Ishan Bhatt
 Fix For: trunk


Steps to reproduce:-

1. Create a cluster with kerberized  environment
2. Set the Kerborized parameter in while creating the view
3. Migrate the artifacts using Hue-Amabari . 

It failed with below errors:-

{code}
12 Jan 2017 13:31:38,125  WARN [Thread-69] ViewContextImpl:497 - Error during 
parsing 'http://172.22.104.166:8080/#' parameter. Leaving original value.
12 Jan 2017 13:31:38,126  WARN [Thread-69] ViewContextImpl:497 - Error during 
parsing 'http://172.22.104.166:8080/#' parameter. Leaving original value.
12 Jan 2017 13:31:38,171  WARN [Thread-69] UserGroupInformation:1551 - 
PriviledgedActionException as:hdfs (auth:PROXY) via ambari-server-cl1 
(auth:SIMPLE) 
cause:org.apache.hadoop.ipc.RemoteException(java.lang.SecurityException): 
Failed to obtain user group information: java.io.IOException: Usernames not 
matched: name=admin != expected=ambari-server-cl1
12 Jan 2017 13:31:38,171 ERROR [Thread-69] 
HiveHistoryQueryMigrationImplementation:493 - Exception in Webhdfs
org.apache.hadoop.ipc.RemoteException(java.lang.SecurityException): Failed to 
obtain user group information: java.io.IOException: Usernames not matched: 
name=admin != expected=ambari-server-cl1
at 
org.apache.hadoop.hdfs.web.JsonUtil.toRemoteException(JsonUtil.java:157)
at 
org.apache.hadoop.hdfs.web.WebHdfsFileSystem.validateResponse(WebHdfsFileSystem.java:318)
at 
org.apache.hadoop.hdfs.web.WebHdfsFileSystem.access$700(WebHdfsFileSystem.java:105)
at 
org.apache.hadoop.hdfs.web.WebHdfsFileSystem$AbstractRunner.getResponse(WebHdfsFileSystem.java:628)
at 
org.apache.hadoop.hdfs.web.WebHdfsFileSystem$AbstractRunner.run(WebHdfsFileSystem.java:535)
at 
org.apache.hadoop.hdfs.web.WebHdfsFileSystem.run(WebHdfsFileSystem.java:424)
at 
org.apache.hadoop.hdfs.web.WebHdfsFileSystem.getDelegationToken(WebHdfsFileSystem.java:953)
at 
org.apache.hadoop.hdfs.web.TokenAspect.ensureTokenInitialized(TokenAspect.java:143)
at 
org.apache.hadoop.hdfs.web.WebHdfsFileSystem.getDelegationToken(WebHdfsFileSystem.java:227)
at 
org.apache.hadoop.hdfs.web.WebHdfsFileSystem.getAuthParameters(WebHdfsFileSystem.java:381)
at 
org.apache.hadoop.hdfs.web.WebHdfsFileSystem.toUrl(WebHdfsFileSystem.java:402)
at 
org.apache.hadoop.hdfs.web.WebHdfsFileSystem$FsPathRunner.getUrl(WebHdfsFileSystem.java:652)
at 
org.apache.hadoop.hdfs.web.WebHdfsFileSystem$AbstractRunner.init(WebHdfsFileSystem.java:485)
at 
org.apache.hadoop.hdfs.web.WebHdfsFileSystem$AbstractRunner.run(WebHdfsFileSystem.java:531)
at 
org.apache.hadoop.hdfs.web.WebHdfsFileSystem.run(WebHdfsFileSystem.java:424)
at 
org.apache.hadoop.hdfs.web.WebHdfsFileSystem.mkdirs(WebHdfsFileSystem.java:704)
at org.apache.hadoop.fs.FileSystem.mkdirs(FileSystem.java:1816)
at 
org.apache.ambari.view.huetoambarimigration.migration.hive.historyquery.HiveHistoryQueryMigrationImplementation$2.run(HiveHistoryQueryMigrationImplementation.java:488)
at 
org.apache.ambari.view.huetoambarimigration.migration.hive.historyquery.HiveHistoryQueryMigrationImplementation$2.run(HiveHistoryQueryMigrationImplementation.java:482)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at 
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1548)
at 
org.apache.ambari.view.huetoambarimigration.migration.hive.historyquery.HiveHistoryQueryMigrationImplementation.createDirKerberorisedSecured(HiveHistoryQueryMigrationImplementation.java:482)
at 
org.apache.ambari.view.huetoambarimigration.migration.hive.historyquery.HiveHistoryMigrationUtility.hiveHistoryQueryMigration(HiveHistoryMigrationUtility.java:200)
at 
org.apache.ambari.view.huetoambarimigration.migration.hive.historyquery.HiveHistoryStartJob.run(HiveHistoryStartJob.java:65)
{code} 




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

[jira] [Commented] (AMBARI-19637) No baseURL field on Register Version page if repoinfo.xml contains only one baseurl

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19637:


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

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

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

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

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

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

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

This message is automatically generated.

> No baseURL field on Register Version page if repoinfo.xml contains only one 
> baseurl
> ---
>
> Key: AMBARI-19637
> URL: https://issues.apache.org/jira/browse/AMBARI-19637
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
>Priority: Critical
> Attachments: AMBARI-19637.patch
>
>
> The issue here is that if repoinfo.xml declares only one repo url per os 
> family, then UI fails  with list index out bounds error
> *repoinfo.xml*
> {code}
>   
> 
>   http://foo
>   PERF-1.0
>   PERF
>   true
> 
>   
> {code}
> errors in console 
> {code}TypeError: Cannot read property 'Repositories' of undefined
> at 
> http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4560:44
> at Array.forEach (native)
> at Scope.$scope.setVersionSelected 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4557:42)
> at 
> http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4669:16
> at wrappedCallback 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:23340:81)
> at 
> http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:23426:26
> at Scope.$eval 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24469:28)
> at Scope.$digest 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24281:31)
> at Scope.$apply 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24573:24)
> at done 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:20146:45)(anonymous
>  function) @ vendor.js:21839
> 6vendor.js:21839 TypeError: Cannot read property 'Repositories' of undefined
> at 
> http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4560:44
> at Array.forEach (native)
> at Scope.$scope.setVersionSelected 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4557:42)
> at Scope.$scope.onStackIdChange 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4578:12)
> at 
> http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:22614:21
> at callback 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:30903:17)
> at Scope.$eval 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24469:28)
> at Scope.$apply 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24567:23)
> at HTMLLIElement. 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:30908:23)
> at HTMLLIElement.jQuery.event.dispatch 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:4737:27){code}
> The hardcoded index is here:
> {code}response.updateObj.operating_systems.forEach(function(os) {
>   $scope.defaulfOSRepos[os.OperatingSystems.os_type] = {
> defaultBaseUrl: os.repositories[0].Repositories.base_url,
> defaultUtilsUrl: os.repositories[1].Repositories.base_url
>   };
> });{code}



--
This message was 

[jira] [Updated] (AMBARI-19601) Warnings on ambari server upgrade related to HDF paths

[Jayush Luniya (JIRA)]

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

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

> Warnings on ambari server upgrade related to HDF paths
> --
>
> Key: AMBARI-19601
> URL: https://issues.apache.org/jira/browse/AMBARI-19601
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.2
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.5.0
>
> Attachments: AMBARI-19601.patch
>
>
> Ambari 2.4.1.0 and HDF 2.0.1.0 was upgraded to Ambari 2.4.2.0 and HDF 2.1 
> mpack
> Saw the following warnings on ambari-server upgrade
> {code}
> [root@arpit-hdf-eu-5 ~]# ambari-server upgrade
> Using python  /usr/bin/python
> Upgrading ambari-server
> Updating properties in ambari.properties ...
> WARNING: Original file ambari-env.sh kept
> WARNING: Original file krb5JAASLogin.conf kept
> File krb5JAASLogin.conf updated.
> Fixing database objects owner
> Ambari Server configured for MySQL. Confirm you have made a backup of the 
> Ambari Server database [y/n] (y)?
> Upgrading database schema
> Adjusting ambari-server permissions and ownership...
> WARNING: Command chown  -R -L root /var/lib/ambari-server returned exit code 
> /var/lib/ambari-server with message: chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/repos': 
> No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/properties':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/metainfo.xml':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/ZOOKEEPER':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/LOGSEARCH':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/KAFKA':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/stack_advisor.py':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/AMBARI_INFRA':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/STORM':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/AMBARI_METRICS':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/KERBEROS':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/NIFI':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/RANGER':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/widgets.json':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/kerberos.json':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/configuration':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/role_command_order.json':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/hooks': 
> No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/common-services_21_11_16_21_33.old/NIFI/1.0.0':
>  No such file or directory
> Ambari Server 'upgrade' completed successfully.
> {code}



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

[jira] [Commented] (AMBARI-19601) Warnings on ambari server upgrade related to HDF paths

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-19601:


Trunk
commit 77b5776617bb448019250d7785c103dbde4ecd24
Author: Jayush Luniya 
Date:   Thu Jan 19 17:52:21 2017 -0800

AMBARI-19601: Warnings on ambari server upgrade related to HDF paths 
(jluniya)

branch-2.5
commit 9dc0e75e0f3886730e2d64b855d37dc459c13642
Author: Jayush Luniya 
Date:   Thu Jan 19 17:52:21 2017 -0800

AMBARI-19601: Warnings on ambari server upgrade related to HDF paths 
(jluniya)

> Warnings on ambari server upgrade related to HDF paths
> --
>
> Key: AMBARI-19601
> URL: https://issues.apache.org/jira/browse/AMBARI-19601
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.2
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.5.0
>
> Attachments: AMBARI-19601.patch
>
>
> Ambari 2.4.1.0 and HDF 2.0.1.0 was upgraded to Ambari 2.4.2.0 and HDF 2.1 
> mpack
> Saw the following warnings on ambari-server upgrade
> {code}
> [root@arpit-hdf-eu-5 ~]# ambari-server upgrade
> Using python  /usr/bin/python
> Upgrading ambari-server
> Updating properties in ambari.properties ...
> WARNING: Original file ambari-env.sh kept
> WARNING: Original file krb5JAASLogin.conf kept
> File krb5JAASLogin.conf updated.
> Fixing database objects owner
> Ambari Server configured for MySQL. Confirm you have made a backup of the 
> Ambari Server database [y/n] (y)?
> Upgrading database schema
> Adjusting ambari-server permissions and ownership...
> WARNING: Command chown  -R -L root /var/lib/ambari-server returned exit code 
> /var/lib/ambari-server with message: chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/repos': 
> No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/properties':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/metainfo.xml':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/ZOOKEEPER':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/LOGSEARCH':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/KAFKA':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/stack_advisor.py':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/AMBARI_INFRA':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/STORM':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/AMBARI_METRICS':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/KERBEROS':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/NIFI':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/services/RANGER':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/widgets.json':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/kerberos.json':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/configuration':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/role_command_order.json':
>  No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/stacks_21_11_16_21_33.old/HDF/2.0/hooks': 
> No such file or directory
> chown: cannot dereference 
> `/var/lib/ambari-server/resources/common-services_21_11_16_21_33.old/NIFI/1.0.0':
>  No such file or directory
> Ambari Server 'upgrade' completed successfully.
> {code}



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

[jira] [Commented] (AMBARI-19638) Improve delete logging for topology artifacts

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19638:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #764 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/764/])
AMBARI-19638. Improve delete logging for topology artifacts. (swagle) (swagle: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d760b22624c00958173f8eea8ca8a9cc1e4f0102])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostResourceProvider.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ConfigGroupResourceProvider.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClustersImpl.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/Clusters.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java


> Improve delete logging for topology artifacts
> -
>
> Key: AMBARI-19638
> URL: https://issues.apache.org/jira/browse/AMBARI-19638
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
> Fix For: 2.5.0
>
> Attachments: AMBARI-19638.patch
>
>
> Very hard to find from Ambari log when a SCH was deleted. We print so much 
> log for all kinds of this, at a minimum all deleted need to be logged.
> Scope: SC, SCH and Host. Make sure we have INFO level log for these.



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

[jira] [Commented] (AMBARI-19623) Atlas startup failed with ZkTimeoutException exception, zookeeper timeout values are very low.

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19623:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #764 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/764/])
AMBARI-19623. Atlas startup failed with ZkTimeoutException exception, 
(afernandez: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9142e2d6c06ad50dfa01dc4d2f1ef06b834141d9])
* (edit) 
ambari-server/src/main/resources/common-services/ZOOKEEPER/3.4.5/configuration/zoo.cfg.xml
* (edit) 
ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/configuration/application-properties.xml
* (edit) 
ambari-server/src/main/resources/common-services/ATLAS/0.7.0.2.5/configuration/application-properties.xml


> Atlas startup failed with ZkTimeoutException exception, zookeeper timeout 
> values are very low.
> --
>
> Key: AMBARI-19623
> URL: https://issues.apache.org/jira/browse/AMBARI-19623
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Ayub Khan
>Assignee: Ayub Khan
>Priority: Critical
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19623.patch
>
>
> Currently zookeeper connect/session timeout values for atlas are set to 
> 200/400 ms respectively which are very low and not practical/recommended 
> values. Due to this atlas startup fails more frequently.
> The jira is set recommended values for zookeeper timeout configuration.
> {noformat}
> atlas.kafka.zookeeper.connection.timeout.ms=3
> atlas.kafka.zookeeper.session.timeout.ms=6
> atlas.audit.zookeeper.session.timeout.ms=6
> {noformat} 



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

[jira] [Commented] (AMBARI-19639) Remove the hardcoding for LLAP app name and read it from config 'llap_app_name'.

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar commented on AMBARI-19639:
--

commits


trunk:

{code}
commit ac907ced86bbec35f3cf068b4764c23789cf3a17
Author: Swapan Shridhar 
Date:   Thu Jan 19 17:11:06 2017 -0800

AMBARI-19639. Remove the hardcoding for LLAP app name and read it from 
config 'llap_app_name'.
{code}


branch-2.5:

{code}
commit ccd10f67539e6acc32af373e815e430d19aad21f
Author: Swapan Shridhar 
Date:   Thu Jan 19 17:11:06 2017 -0800

AMBARI-19639. Remove the hardcoding for LLAP app name and read it from 
config 'llap_app_name'.
{code}

> Remove the hardcoding for LLAP app name and read it from config 
> 'llap_app_name'.
> 
>
> Key: AMBARI-19639
> URL: https://issues.apache.org/jira/browse/AMBARI-19639
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19639.patch
>
>




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

[jira] [Resolved] (AMBARI-19639) Remove the hardcoding for LLAP app name and read it from config 'llap_app_name'.

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar resolved AMBARI-19639.
--
Resolution: Fixed

> Remove the hardcoding for LLAP app name and read it from config 
> 'llap_app_name'.
> 
>
> Key: AMBARI-19639
> URL: https://issues.apache.org/jira/browse/AMBARI-19639
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19639.patch
>
>




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

[jira] [Updated] (AMBARI-19639) Remove the hardcoding for LLAP app name and read it from config 'llap_app_name'.

[Swapan Shridhar (JIRA)]

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

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

> Remove the hardcoding for LLAP app name and read it from config 
> 'llap_app_name'.
> 
>
> Key: AMBARI-19639
> URL: https://issues.apache.org/jira/browse/AMBARI-19639
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19639.patch
>
>




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

[jira] [Updated] (AMBARI-19639) Remove the hardcoding for LLAP app name and read it from config 'llap_app_name'.

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar updated AMBARI-19639:
-
Status: Open  (was: Patch Available)

> Remove the hardcoding for LLAP app name and read it from config 
> 'llap_app_name'.
> 
>
> Key: AMBARI-19639
> URL: https://issues.apache.org/jira/browse/AMBARI-19639
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19639.patch
>
>




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

[jira] [Updated] (AMBARI-19639) Remove the hardcoding for LLAP app name and read it from config 'llap_app_name'.

[Swapan Shridhar (JIRA)]

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

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

> Remove the hardcoding for LLAP app name and read it from config 
> 'llap_app_name'.
> 
>
> Key: AMBARI-19639
> URL: https://issues.apache.org/jira/browse/AMBARI-19639
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
>




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

[jira] [Updated] (AMBARI-19639) Remove the hardcoding for LLAP app name and read it from config 'llap_app_name'.

[Swapan Shridhar (JIRA)]

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

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

> Remove the hardcoding for LLAP app name and read it from config 
> 'llap_app_name'.
> 
>
> Key: AMBARI-19639
> URL: https://issues.apache.org/jira/browse/AMBARI-19639
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19639.patch
>
>




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

[jira] [Updated] (AMBARI-19639) Remove the hardcoding for LLAP app name and read it from config 'llap_app_name'.

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar updated AMBARI-19639:
-
Status: Patch Available  (was: Open)

> Remove the hardcoding for LLAP app name and read it from config 
> 'llap_app_name'.
> 
>
> Key: AMBARI-19639
> URL: https://issues.apache.org/jira/browse/AMBARI-19639
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19639.patch
>
>




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

[jira] [Created] (AMBARI-19639) Remove the hardcoding for LLAP app name and read it from config 'llap_app_name'.

[Swapan Shridhar (JIRA)]

Swapan Shridhar created AMBARI-19639:


 Summary: Remove the hardcoding for LLAP app name and read it from 
config 'llap_app_name'.
 Key: AMBARI-19639
 URL: https://issues.apache.org/jira/browse/AMBARI-19639
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.4.2
Reporter: Swapan Shridhar
Assignee: Swapan Shridhar
 Fix For: 2.5.0






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

[jira] [Commented] (AMBARI-19597) Blueprint installation should accept quick link profile

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19597:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6497 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6497/])
AMBARI-19597. Blueprint installation should accept quick link profile. 
(stoader: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=de8bf601918efbeb66ef68d25364aaed4b672172])
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/QuickLinkArtifactResourceProviderTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/quicklinksprofile/Filter.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/quicklinksprofile/QuickLinksProfile.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterResourceProvider.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/quicklinksprofile/AcceptAllFilter.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/quicklinksprofile/QuickLinksProfileParser.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/quicklinksprofile/QuickLinksProfileEvaluationException.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/quicklinksprofile/Component.java
* (add) 
ambari-server/src/test/java/org/apache/ambari/server/state/quicklinksprofile/QuickLinksProfileBuilderTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/quicklinksprofile/Service.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/topology/TopologyManager.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ProvisionClusterRequest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/topology/TopologyManagerTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ProvisionClusterRequestTest.java
* (add) 
ambari-server/src/main/java/org/apache/ambari/server/state/quicklinksprofile/QuickLinksProfileBuilder.java


> Blueprint installation should accept quick link profile
> ---
>
> Key: AMBARI-19597
> URL: https://issues.apache.org/jira/browse/AMBARI-19597
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: trunk, 2.5.0
>Reporter: Balázs Bence Sári
>Assignee: Balázs Bence Sári
>Priority: Critical
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19597-QLP-BluePrint_25_v1.patch, 
> AMBARI-19597-QLP-BluePrint_trunk_v3.patch
>
>
> Specifying the quick links profile should be supported in blueprint based 
> cluster installation. First implementation will address the possibility of 
> adding the profile to the cluster creation template. See below a cluster 
> creation template that contains and embedded quick links profile:
> {code}
> {
>   "blueprint" : "wp",
>   "host_groups" :[
> {
>   "name" : "group1",
>   "hosts" : [
> {
>   "fqdn" : "ambari-agent-1.node.dc1.consul"
> }
>   ]
> }
>   ],
>   "quicklinks_profile": {
> "filters": [
>   {
> "link_attribute": "sso",
> "visible": true
>   }
> ],
> "services": []
>   }  
> }
> {code}



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

[jira] [Commented] (AMBARI-19617) Restarting Some Components During a Suspended Upgrade Fails Due To Missing Upgrade Parameters

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19617:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6497 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6497/])
AMBARI-19617 - Restarting Some Components During a Suspended Upgrade (jhurley: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d540f943da59d196b377a9e15fcd2e6dcb50483b])
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/KerberosHelperTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariCustomCommandExecutionHelper.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ClusterEffectiveVersionTest.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/state/Cluster.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ActiveWidgetLayoutResourceProviderTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/state/UpgradeHelperTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariActionExecutionHelper.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UserResourceProviderTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/UpgradeContextFactory.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/state/stack/upgrade/StageWrapperBuilderTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/UpgradeContext.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/agent/AgentResourceTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UserAuthorizationResourceProviderTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/state/ConfigHelperTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java


> Restarting Some Components During a Suspended Upgrade Fails Due To Missing 
> Upgrade Parameters
> -
>
> Key: AMBARI-19617
> URL: https://issues.apache.org/jira/browse/AMBARI-19617
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19617.patch
>
>
> While attempting to restart a component that has complicated upgrade logic, 
> the upgrade parameters are not sent to the agents. This can cause some 
> components to fails during a suspended upgrade restart. 
> Example:
> - Begin express upgrade from {{2.3.6.0-3796}} to {{2.5.3.0-37}}
> - {{HIVE_METASTORE}} couldn't start b/c of a missing Kerberos property:
> {code}
> resource_management.core.exceptions.Fail: Configuration parameter 
> 'hive.server2.authentication.kerberos.principal' was not found in 
> configurations dictionary!
> {code}
> - Chose to {{Ignore and Proceed}} which means that none of the Metastore SQL 
> files ran. 
> - Paused the upgrade (presumably at Finalize) and try to start Metastore. It 
> fails to start because the new HDP 2.5 bits are using a non-upgraded 
> database. That causes the {{-info}} option to fail and makes Ambari think it 
> needs to run {{-initSchema}}. 
> RCA: Metastore failed to start during upgrade and the admin chose to skip it. 
> This caused schema upgrade logic not to run. Ambari can examine the 
> {{upgrade_suspended}} property to determine if we need to run upgrade 
> commands while restarting Metastore during an upgrade. 
> However, it might be more prudent to simply send along the suspended upgrade 
> properties so that any actions which might need to happen (such as invoking 
> an upgrade script during the restart) can happen when the upgrade is 
> suspended.



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

[jira] [Commented] (AMBARI-19475) Workflow Manager View: Start record set to 1 even when there are no records

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19475:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6497 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6497/])
AMBARI-19475: Workflow Manager View: Start record set to 1 even when 
(sangeetar: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4531f733742d933b85d9437b68cc2dc7b24befce])
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/routes/design/dashboardtab.js


> Workflow Manager View: Start record set to 1 even when there are no records
> ---
>
> Key: AMBARI-19475
> URL: https://issues.apache.org/jira/browse/AMBARI-19475
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19475_final.patch, AMBARI-19475.patch, 
> WorkflowManagerDashboard.jpg
>
>
> 1. In the Workflow Manager View, when there are no co-ordinator or bundle 
> records, the dashboard message says "Showing 1 to 0 of 0 records". This is 
> because the start record is set to 1 by default.



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

[jira] [Commented] (AMBARI-19633) accordion classname missed on configs page

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19633:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6497 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6497/])
AMBARI-19633. accordion classname missed on configs page (akovalenko) 
(akovalenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2200dda431842c2efe5c27b7db1cf1bee43a289a])
* (edit) ambari-web/app/views/common/configs/config_category_container_view.js


> accordion classname missed on configs page
> --
>
> Key: AMBARI-19633
> URL: https://issues.apache.org/jira/browse/AMBARI-19633
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19633.patch
>
>




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

[jira] [Commented] (AMBARI-19636) Provide default values for Kafka nofile and nproc limit properties

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19636:


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

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

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

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

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

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

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

This message is automatically generated.

> Provide default values for Kafka nofile and nproc limit properties
> --
>
> Key: AMBARI-19636
> URL: https://issues.apache.org/jira/browse/AMBARI-19636
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-19636.patch
>
>
> Provide default values for Kafka nofile and nproc limit properties



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

[jira] [Updated] (AMBARI-19623) Atlas startup failed with ZkTimeoutException exception, zookeeper timeout values are very low.

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-19623:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Pushed to trunk, commit bbacefd44a52bfd0a82c6067f9974944623cfdec
branch-2.5, commit 9142e2d6c06ad50dfa01dc4d2f1ef06b834141d9

> Atlas startup failed with ZkTimeoutException exception, zookeeper timeout 
> values are very low.
> --
>
> Key: AMBARI-19623
> URL: https://issues.apache.org/jira/browse/AMBARI-19623
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Ayub Khan
>Assignee: Ayub Khan
>Priority: Critical
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19623.patch
>
>
> Currently zookeeper connect/session timeout values for atlas are set to 
> 200/400 ms respectively which are very low and not practical/recommended 
> values. Due to this atlas startup fails more frequently.
> The jira is set recommended values for zookeeper timeout configuration.
> {noformat}
> atlas.kafka.zookeeper.connection.timeout.ms=3
> atlas.kafka.zookeeper.session.timeout.ms=6
> atlas.audit.zookeeper.session.timeout.ms=6
> {noformat} 



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

[jira] [Commented] (AMBARI-19623) Atlas startup failed with ZkTimeoutException exception, zookeeper timeout values are very low.

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez commented on AMBARI-19623:
--

+1 for [^AMBARI-19623.patch]

Please create another Jira for changing these values during RU/EU to HDP 2.6

> Atlas startup failed with ZkTimeoutException exception, zookeeper timeout 
> values are very low.
> --
>
> Key: AMBARI-19623
> URL: https://issues.apache.org/jira/browse/AMBARI-19623
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Ayub Khan
>Assignee: Ayub Khan
>Priority: Critical
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19623.patch
>
>
> Currently zookeeper connect/session timeout values for atlas are set to 
> 200/400 ms respectively which are very low and not practical/recommended 
> values. Due to this atlas startup fails more frequently.
> The jira is set recommended values for zookeeper timeout configuration.
> {noformat}
> atlas.kafka.zookeeper.connection.timeout.ms=3
> atlas.kafka.zookeeper.session.timeout.ms=6
> atlas.audit.zookeeper.session.timeout.ms=6
> {noformat} 



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

[jira] [Updated] (AMBARI-19638) Improve delete logging for topology artifacts

[Siddharth Wagle (JIRA)]

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

Siddharth Wagle updated AMBARI-19638:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Pushed to 2.5 and trunk.

> Improve delete logging for topology artifacts
> -
>
> Key: AMBARI-19638
> URL: https://issues.apache.org/jira/browse/AMBARI-19638
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
> Fix For: 2.5.0
>
> Attachments: AMBARI-19638.patch
>
>
> Very hard to find from Ambari log when a SCH was deleted. We print so much 
> log for all kinds of this, at a minimum all deleted need to be logged.
> Scope: SC, SCH and Host. Make sure we have INFO level log for these.



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

[jira] [Updated] (AMBARI-19638) Improve delete logging for topology artifacts

[Siddharth Wagle (JIRA)]

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

Siddharth Wagle updated AMBARI-19638:
-
Status: Patch Available  (was: Open)

> Improve delete logging for topology artifacts
> -
>
> Key: AMBARI-19638
> URL: https://issues.apache.org/jira/browse/AMBARI-19638
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
> Fix For: 2.5.0
>
> Attachments: AMBARI-19638.patch
>
>
> Very hard to find from Ambari log when a SCH was deleted. We print so much 
> log for all kinds of this, at a minimum all deleted need to be logged.
> Scope: SC, SCH and Host. Make sure we have INFO level log for these.



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

[jira] [Updated] (AMBARI-19638) Improve delete logging for topology artifacts

[Siddharth Wagle (JIRA)]

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

Siddharth Wagle updated AMBARI-19638:
-
Attachment: AMBARI-19638.patch

> Improve delete logging for topology artifacts
> -
>
> Key: AMBARI-19638
> URL: https://issues.apache.org/jira/browse/AMBARI-19638
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
> Fix For: 2.5.0
>
> Attachments: AMBARI-19638.patch
>
>
> Very hard to find from Ambari log when a SCH was deleted. We print so much 
> log for all kinds of this, at a minimum all deleted need to be logged.
> Scope: SC, SCH and Host. Make sure we have INFO level log for these.



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

[jira] [Commented] (AMBARI-19630) Ambari should accept stack version in format of x.x.x.x without the build level digits

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19630:


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

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

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

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

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

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

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

This message is automatically generated.

> Ambari should accept stack version in format of x.x.x.x without the build 
> level digits
> --
>
> Key: AMBARI-19630
> URL: https://issues.apache.org/jira/browse/AMBARI-19630
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-trunk
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-19630.patch
>
>
> Ambari current requires stack version ( used in the repo) as x.x.x.x-, 
> Ambari should be flexible enough to accept both x.x.x.x- and x.x.x.x



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

[jira] [Created] (AMBARI-19638) Improve delete logging for topology artifacts

[Siddharth Wagle (JIRA)]

Siddharth Wagle created AMBARI-19638:


 Summary: Improve delete logging for topology artifacts
 Key: AMBARI-19638
 URL: https://issues.apache.org/jira/browse/AMBARI-19638
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.0.0
Reporter: Siddharth Wagle
Assignee: Siddharth Wagle
 Fix For: 2.5.0


Very hard to find from Ambari log when a SCH was deleted. We print so much log 
for all kinds of this, at a minimum all deleted need to be logged.

Scope: SC, SCH and Host. Make sure we have INFO level log for these.




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

[jira] [Commented] (AMBARI-19597) Blueprint installation should accept quick link profile

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19597:


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

This message is automatically generated.

> Blueprint installation should accept quick link profile
> ---
>
> Key: AMBARI-19597
> URL: https://issues.apache.org/jira/browse/AMBARI-19597
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: trunk, 2.5.0
>Reporter: Balázs Bence Sári
>Assignee: Balázs Bence Sári
>Priority: Critical
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19597-QLP-BluePrint_25_v1.patch, 
> AMBARI-19597-QLP-BluePrint_trunk_v3.patch
>
>
> Specifying the quick links profile should be supported in blueprint based 
> cluster installation. First implementation will address the possibility of 
> adding the profile to the cluster creation template. See below a cluster 
> creation template that contains and embedded quick links profile:
> {code}
> {
>   "blueprint" : "wp",
>   "host_groups" :[
> {
>   "name" : "group1",
>   "hosts" : [
> {
>   "fqdn" : "ambari-agent-1.node.dc1.consul"
> }
>   ]
> }
>   ],
>   "quicklinks_profile": {
> "filters": [
>   {
> "link_attribute": "sso",
> "visible": true
>   }
> ],
> "services": []
>   }  
> }
> {code}



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

[jira] [Commented] (AMBARI-19616) Hive Server Interactive : (1). Set 'metaspacesize' based on LLAP daemon size and (2). Fix for using "--slider-placement" argument only for HDP 2.6 and onwards.

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19616:


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

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

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

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

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

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

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

This message is automatically generated.

> Hive Server Interactive : (1). Set 'metaspacesize' based on LLAP daemon size 
> and (2). Fix for using "--slider-placement" argument only for HDP 2.6 and 
> onwards.
> ---
>
> Key: AMBARI-19616
> URL: https://issues.apache.org/jira/browse/AMBARI-19616
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19616.patch
>
>
> (1). Set 'metaspacesize' based on LLAP daemon size
> If LLAP DamoneSize <= 4GB
>  ---> Don't set metaspacesize
> else if LLAP DaemonsSize <=32GB
>  ---> Set to 256m
> else 
>  ---> Set to 1024m (current value)
> (2). Fix for using "--slider-placement" argument only for HDP 2.6 and onwards.
> - Current code add it irrespective of HDP version '--slider-placement' is not 
> valid for option for HDP version less than 2.6.



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

[jira] [Updated] (AMBARI-19637) No baseURL field on Register Version page if repoinfo.xml contains only one baseurl

[Richard Zang (JIRA)]

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

Richard Zang updated AMBARI-19637:
--
Status: Patch Available  (was: Open)

> No baseURL field on Register Version page if repoinfo.xml contains only one 
> baseurl
> ---
>
> Key: AMBARI-19637
> URL: https://issues.apache.org/jira/browse/AMBARI-19637
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
>Priority: Critical
> Attachments: AMBARI-19637.patch
>
>
> The issue here is that if repoinfo.xml declares only one repo url per os 
> family, then UI fails  with list index out bounds error
> *repoinfo.xml*
> {code}
>   
> 
>   http://foo
>   PERF-1.0
>   PERF
>   true
> 
>   
> {code}
> errors in console 
> {code}TypeError: Cannot read property 'Repositories' of undefined
> at 
> http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4560:44
> at Array.forEach (native)
> at Scope.$scope.setVersionSelected 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4557:42)
> at 
> http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4669:16
> at wrappedCallback 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:23340:81)
> at 
> http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:23426:26
> at Scope.$eval 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24469:28)
> at Scope.$digest 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24281:31)
> at Scope.$apply 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24573:24)
> at done 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:20146:45)(anonymous
>  function) @ vendor.js:21839
> 6vendor.js:21839 TypeError: Cannot read property 'Repositories' of undefined
> at 
> http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4560:44
> at Array.forEach (native)
> at Scope.$scope.setVersionSelected 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4557:42)
> at Scope.$scope.onStackIdChange 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4578:12)
> at 
> http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:22614:21
> at callback 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:30903:17)
> at Scope.$eval 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24469:28)
> at Scope.$apply 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24567:23)
> at HTMLLIElement. 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:30908:23)
> at HTMLLIElement.jQuery.event.dispatch 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:4737:27){code}
> The hardcoded index is here:
> {code}response.updateObj.operating_systems.forEach(function(os) {
>   $scope.defaulfOSRepos[os.OperatingSystems.os_type] = {
> defaultBaseUrl: os.repositories[0].Repositories.base_url,
> defaultUtilsUrl: os.repositories[1].Repositories.base_url
>   };
> });{code}



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

[jira] [Updated] (AMBARI-19637) No baseURL field on Register Version page if repoinfo.xml contains only one baseurl

[Richard Zang (JIRA)]

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

Richard Zang updated AMBARI-19637:
--
Attachment: AMBARI-19637.patch

> No baseURL field on Register Version page if repoinfo.xml contains only one 
> baseurl
> ---
>
> Key: AMBARI-19637
> URL: https://issues.apache.org/jira/browse/AMBARI-19637
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
>Priority: Critical
> Attachments: AMBARI-19637.patch
>
>
> The issue here is that if repoinfo.xml declares only one repo url per os 
> family, then UI fails  with list index out bounds error
> *repoinfo.xml*
> {code}
>   
> 
>   http://foo
>   PERF-1.0
>   PERF
>   true
> 
>   
> {code}
> errors in console 
> {code}TypeError: Cannot read property 'Repositories' of undefined
> at 
> http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4560:44
> at Array.forEach (native)
> at Scope.$scope.setVersionSelected 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4557:42)
> at 
> http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4669:16
> at wrappedCallback 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:23340:81)
> at 
> http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:23426:26
> at Scope.$eval 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24469:28)
> at Scope.$digest 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24281:31)
> at Scope.$apply 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24573:24)
> at done 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:20146:45)(anonymous
>  function) @ vendor.js:21839
> 6vendor.js:21839 TypeError: Cannot read property 'Repositories' of undefined
> at 
> http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4560:44
> at Array.forEach (native)
> at Scope.$scope.setVersionSelected 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4557:42)
> at Scope.$scope.onStackIdChange 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4578:12)
> at 
> http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:22614:21
> at callback 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:30903:17)
> at Scope.$eval 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24469:28)
> at Scope.$apply 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24567:23)
> at HTMLLIElement. 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:30908:23)
> at HTMLLIElement.jQuery.event.dispatch 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:4737:27){code}
> The hardcoded index is here:
> {code}response.updateObj.operating_systems.forEach(function(os) {
>   $scope.defaulfOSRepos[os.OperatingSystems.os_type] = {
> defaultBaseUrl: os.repositories[0].Repositories.base_url,
> defaultUtilsUrl: os.repositories[1].Repositories.base_url
>   };
> });{code}



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

[jira] [Commented] (AMBARI-19475) Workflow Manager View: Start record set to 1 even when there are no records

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19475:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #763 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/763/])
AMBARI-19475: Workflow Manager View: Start record set to 1 even when 
(sangeetar: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4179186a0bdf9694b6c9bd9da75ac13af288fad9])
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/routes/design/dashboardtab.js


> Workflow Manager View: Start record set to 1 even when there are no records
> ---
>
> Key: AMBARI-19475
> URL: https://issues.apache.org/jira/browse/AMBARI-19475
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19475_final.patch, AMBARI-19475.patch, 
> WorkflowManagerDashboard.jpg
>
>
> 1. In the Workflow Manager View, when there are no co-ordinator or bundle 
> records, the dashboard message says "Showing 1 to 0 of 0 records". This is 
> because the start record is set to 1 by default.



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

[jira] [Created] (AMBARI-19637) No baseURL field on Register Version page if repoinfo.xml contains only one baseurl

[Richard Zang (JIRA)]

Richard Zang created AMBARI-19637:
-

 Summary: No baseURL field on Register Version page if repoinfo.xml 
contains only one baseurl
 Key: AMBARI-19637
 URL: https://issues.apache.org/jira/browse/AMBARI-19637
 Project: Ambari
  Issue Type: Bug
  Components: ambari-admin
Affects Versions: 2.5.0
Reporter: Richard Zang
Assignee: Richard Zang


The issue here is that if repoinfo.xml declares only one repo url per os 
family, then UI fails  with list index out bounds error

*repoinfo.xml*
{code}
  

  http://foo
  PERF-1.0
  PERF
  true

  
{code}

errors in console 
{code}TypeError: Cannot read property 'Repositories' of undefined
at 
http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4560:44
at Array.forEach (native)
at Scope.$scope.setVersionSelected 
(http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4557:42)
at 
http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4669:16
at wrappedCallback 
(http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:23340:81)
at 
http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:23426:26
at Scope.$eval 
(http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24469:28)
at Scope.$digest 
(http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24281:31)
at Scope.$apply 
(http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24573:24)
at done 
(http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:20146:45)(anonymous
 function) @ vendor.js:21839
6vendor.js:21839 TypeError: Cannot read property 'Repositories' of undefined
at 
http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4560:44
at Array.forEach (native)
at Scope.$scope.setVersionSelected 
(http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4557:42)
at Scope.$scope.onStackIdChange 
(http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4578:12)
at 
http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:22614:21
at callback 
(http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:30903:17)
at Scope.$eval 
(http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24469:28)
at Scope.$apply 
(http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24567:23)
at HTMLLIElement. 
(http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:30908:23)
at HTMLLIElement.jQuery.event.dispatch 
(http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:4737:27){code}


The hardcoded index is here:
{code}response.updateObj.operating_systems.forEach(function(os) {
  $scope.defaulfOSRepos[os.OperatingSystems.os_type] = {
defaultBaseUrl: os.repositories[0].Repositories.base_url,
defaultUtilsUrl: os.repositories[1].Repositories.base_url
  };
});{code}



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

[jira] [Updated] (AMBARI-19637) No baseURL field on Register Version page if repoinfo.xml contains only one baseurl

[Richard Zang (JIRA)]

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

Richard Zang updated AMBARI-19637:
--
Priority: Critical  (was: Major)

> No baseURL field on Register Version page if repoinfo.xml contains only one 
> baseurl
> ---
>
> Key: AMBARI-19637
> URL: https://issues.apache.org/jira/browse/AMBARI-19637
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
>Priority: Critical
>
> The issue here is that if repoinfo.xml declares only one repo url per os 
> family, then UI fails  with list index out bounds error
> *repoinfo.xml*
> {code}
>   
> 
>   http://foo
>   PERF-1.0
>   PERF
>   true
> 
>   
> {code}
> errors in console 
> {code}TypeError: Cannot read property 'Repositories' of undefined
> at 
> http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4560:44
> at Array.forEach (native)
> at Scope.$scope.setVersionSelected 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4557:42)
> at 
> http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4669:16
> at wrappedCallback 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:23340:81)
> at 
> http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:23426:26
> at Scope.$eval 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24469:28)
> at Scope.$digest 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24281:31)
> at Scope.$apply 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24573:24)
> at done 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:20146:45)(anonymous
>  function) @ vendor.js:21839
> 6vendor.js:21839 TypeError: Cannot read property 'Repositories' of undefined
> at 
> http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4560:44
> at Array.forEach (native)
> at Scope.$scope.setVersionSelected 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4557:42)
> at Scope.$scope.onStackIdChange 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/main.js:4578:12)
> at 
> http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:22614:21
> at callback 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:30903:17)
> at Scope.$eval 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24469:28)
> at Scope.$apply 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:24567:23)
> at HTMLLIElement. 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:30908:23)
> at HTMLLIElement.jQuery.event.dispatch 
> (http://c6401.ambari.apache.org:8080/views/ADMIN_VIEW/2.5.0.0/INSTANCE/scripts/vendor.js:4737:27){code}
> The hardcoded index is here:
> {code}response.updateObj.operating_systems.forEach(function(os) {
>   $scope.defaulfOSRepos[os.OperatingSystems.os_type] = {
> defaultBaseUrl: os.repositories[0].Repositories.base_url,
> defaultUtilsUrl: os.repositories[1].Repositories.base_url
>   };
> });{code}



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

[jira] [Updated] (AMBARI-19475) Workflow Manager View: Start record set to 1 even when there are no records

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-19475:

   Resolution: Fixed
Fix Version/s: trunk
   Status: Resolved  (was: Patch Available)

Commited to branch-2.5 as

commit 4179186a0bdf9694b6c9bd9da75ac13af288fad9
Author: Sangeeta Ravindran 
Date:   Thu Jan 19 14:20:07 2017 -0800

AMBARI-19475: Workflow Manager View: Start record set to 1 even when there are 
no records (sangeetar)

Commited to trunk as

commit 4531f733742d933b85d9437b68cc2dc7b24befce
Author: Sangeeta Ravindran 
Date:   Thu Jan 19 14:55:53 2017 -0800

AMBARI-19475: Workflow Manager View: Start record set to 1 even when there are 
no records (sangeetar)


> Workflow Manager View: Start record set to 1 even when there are no records
> ---
>
> Key: AMBARI-19475
> URL: https://issues.apache.org/jira/browse/AMBARI-19475
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19475_final.patch, AMBARI-19475.patch, 
> WorkflowManagerDashboard.jpg
>
>
> 1. In the Workflow Manager View, when there are no co-ordinator or bundle 
> records, the dashboard message says "Showing 1 to 0 of 0 records". This is 
> because the start record is set to 1 by default.



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

[jira] [Updated] (AMBARI-19475) Workflow Manager View: Start record set to 1 even when there are no records

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-19475:

Attachment: AMBARI-19475_final.patch

> Workflow Manager View: Start record set to 1 even when there are no records
> ---
>
> Key: AMBARI-19475
> URL: https://issues.apache.org/jira/browse/AMBARI-19475
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: 2.5.0
>
> Attachments: AMBARI-19475_final.patch, AMBARI-19475.patch, 
> WorkflowManagerDashboard.jpg
>
>
> 1. In the Workflow Manager View, when there are no co-ordinator or bundle 
> records, the dashboard message says "Showing 1 to 0 of 0 records". This is 
> because the start record is set to 1 by default.



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

[jira] [Commented] (AMBARI-19631) Hive View 2.0: Show the table accesses in the authorization sceen

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19631:


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

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

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

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

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

{color:red}-1 core tests{color}.  The test build failed in 
contrib/views/hive20 

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

This message is automatically generated.

> Hive View 2.0: Show the table accesses in the authorization sceen
> -
>
> Key: AMBARI-19631
> URL: https://issues.apache.org/jira/browse/AMBARI-19631
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.5.0
>
> Attachments: AMBARI-19631.branch-2.5.patch
>
>
> User should be able to see what all accesses the user/groups have on the 
> table.



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

[jira] [Updated] (AMBARI-19616) Hive Server Interactive : (1). Set 'metaspacesize' based on LLAP daemon size and (2). Fix for using "--slider-placement" argument only for HDP 2.6 and onwards.

[Swapan Shridhar (JIRA)]

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

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

> Hive Server Interactive : (1). Set 'metaspacesize' based on LLAP daemon size 
> and (2). Fix for using "--slider-placement" argument only for HDP 2.6 and 
> onwards.
> ---
>
> Key: AMBARI-19616
> URL: https://issues.apache.org/jira/browse/AMBARI-19616
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19616.patch
>
>
> (1). Set 'metaspacesize' based on LLAP daemon size
> If LLAP DamoneSize <= 4GB
>  ---> Don't set metaspacesize
> else if LLAP DaemonsSize <=32GB
>  ---> Set to 256m
> else 
>  ---> Set to 1024m (current value)
> (2). Fix for using "--slider-placement" argument only for HDP 2.6 and onwards.
> - Current code add it irrespective of HDP version '--slider-placement' is not 
> valid for option for HDP version less than 2.6.



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

[jira] [Commented] (AMBARI-19597) Blueprint installation should accept quick link profile

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19597:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #762 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/762/])
AMBARI-19597. Blueprint installation should accept quick link profile. 
(stoader: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=99bb988406184aa12c4d3d0b12e39b83025b7385])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/quicklinksprofile/Service.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/topology/TopologyManager.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ProvisionClusterRequestTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterResourceProvider.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ProvisionClusterRequest.java
* (add) 
ambari-server/src/test/java/org/apache/ambari/server/state/quicklinksprofile/QuickLinksProfileBuilderTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/quicklinksprofile/AcceptAllFilter.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/quicklinksprofile/Component.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/QuickLinkArtifactResourceProviderTest.java
* (add) 
ambari-server/src/main/java/org/apache/ambari/server/state/quicklinksprofile/QuickLinksProfileBuilder.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/topology/TopologyManagerTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/quicklinksprofile/QuickLinksProfile.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/quicklinksprofile/QuickLinksProfileEvaluationException.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/quicklinksprofile/Filter.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/quicklinksprofile/QuickLinksProfileParser.java


> Blueprint installation should accept quick link profile
> ---
>
> Key: AMBARI-19597
> URL: https://issues.apache.org/jira/browse/AMBARI-19597
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: trunk, 2.5.0
>Reporter: Balázs Bence Sári
>Assignee: Balázs Bence Sári
>Priority: Critical
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19597-QLP-BluePrint_25_v1.patch, 
> AMBARI-19597-QLP-BluePrint_trunk_v3.patch
>
>
> Specifying the quick links profile should be supported in blueprint based 
> cluster installation. First implementation will address the possibility of 
> adding the profile to the cluster creation template. See below a cluster 
> creation template that contains and embedded quick links profile:
> {code}
> {
>   "blueprint" : "wp",
>   "host_groups" :[
> {
>   "name" : "group1",
>   "hosts" : [
> {
>   "fqdn" : "ambari-agent-1.node.dc1.consul"
> }
>   ]
> }
>   ],
>   "quicklinks_profile": {
> "filters": [
>   {
> "link_attribute": "sso",
> "visible": true
>   }
> ],
> "services": []
>   }  
> }
> {code}



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

[jira] [Updated] (AMBARI-19616) Hive Server Interactive : (1). Set 'metaspacesize' based on LLAP daemon size and (2). Fix for using "--slider-placement" argument only for HDP 2.6 and onwards.

[Swapan Shridhar (JIRA)]

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

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

> Hive Server Interactive : (1). Set 'metaspacesize' based on LLAP daemon size 
> and (2). Fix for using "--slider-placement" argument only for HDP 2.6 and 
> onwards.
> ---
>
> Key: AMBARI-19616
> URL: https://issues.apache.org/jira/browse/AMBARI-19616
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
>
> (1). Set 'metaspacesize' based on LLAP daemon size
> If LLAP DamoneSize <= 4GB
>  ---> Don't set metaspacesize
> else if LLAP DaemonsSize <=32GB
>  ---> Set to 256m
> else 
>  ---> Set to 1024m (current value)
> (2). Fix for using "--slider-placement" argument only for HDP 2.6 and onwards.
> - Current code add it irrespective of HDP version '--slider-placement' is not 
> valid for option for HDP version less than 2.6.



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

[jira] [Commented] (AMBARI-19617) Restarting Some Components During a Suspended Upgrade Fails Due To Missing Upgrade Parameters

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19617:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #762 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/762/])
AMBARI-19617 - Restarting Some Components During a Suspended Upgrade (jhurley: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=49185423989e7cea3dfff4f629bd64c37762b792])
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/state/ConfigHelperTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UserAuthorizationResourceProviderTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/KerberosHelperTest.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/state/Cluster.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariActionExecutionHelper.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/UpgradeContextFactory.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/state/stack/upgrade/StageWrapperBuilderTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/agent/AgentResourceTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ClusterEffectiveVersionTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariCustomCommandExecutionHelper.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ActiveWidgetLayoutResourceProviderTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UserResourceProviderTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/state/UpgradeHelperTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/UpgradeContext.java


> Restarting Some Components During a Suspended Upgrade Fails Due To Missing 
> Upgrade Parameters
> -
>
> Key: AMBARI-19617
> URL: https://issues.apache.org/jira/browse/AMBARI-19617
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19617.patch
>
>
> While attempting to restart a component that has complicated upgrade logic, 
> the upgrade parameters are not sent to the agents. This can cause some 
> components to fails during a suspended upgrade restart. 
> Example:
> - Begin express upgrade from {{2.3.6.0-3796}} to {{2.5.3.0-37}}
> - {{HIVE_METASTORE}} couldn't start b/c of a missing Kerberos property:
> {code}
> resource_management.core.exceptions.Fail: Configuration parameter 
> 'hive.server2.authentication.kerberos.principal' was not found in 
> configurations dictionary!
> {code}
> - Chose to {{Ignore and Proceed}} which means that none of the Metastore SQL 
> files ran. 
> - Paused the upgrade (presumably at Finalize) and try to start Metastore. It 
> fails to start because the new HDP 2.5 bits are using a non-upgraded 
> database. That causes the {{-info}} option to fail and makes Ambari think it 
> needs to run {{-initSchema}}. 
> RCA: Metastore failed to start during upgrade and the admin chose to skip it. 
> This caused schema upgrade logic not to run. Ambari can examine the 
> {{upgrade_suspended}} property to determine if we need to run upgrade 
> commands while restarting Metastore during an upgrade. 
> However, it might be more prudent to simply send along the suspended upgrade 
> properties so that any actions which might need to happen (such as invoking 
> an upgrade script during the restart) can happen when the upgrade is 
> suspended.



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

[jira] [Updated] (AMBARI-19629) Move schemaTool invocation out of configure() to hive_metastore start()

[Doroszlai, Attila (JIRA)]

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

Doroszlai, Attila updated AMBARI-19629:
---
Fix Version/s: 2.5.0

> Move schemaTool invocation out of configure() to hive_metastore start()
> ---
>
> Key: AMBARI-19629
> URL: https://issues.apache.org/jira/browse/AMBARI-19629
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19629-branch-2.5.patch, AMBARI-19629-trunk.patch
>
>
> The {{schemaTool}} invocation should not be part of the {{configure}} method 
> as generally the {{configure}} method should be callable from {{install}} as 
> well and {{schemaTool}}  requires a running database to be available which is 
> not true if the default {{mysql}} database server shipped with {{hive}} is 
> used.
> Also since only one component can {{configure}} method at a time on the same 
> host in order to avoid overwriting common shared configs the {{configure}} 
> methods are synchronized across all components on a host. Having the 
> {{schemaTool}} lengthy operation in the {{configure}} method will delay the 
> execution of {{configure}} methods of the other components in case of 
> parallel command execution.



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

[jira] [Commented] (AMBARI-19597) Blueprint installation should accept quick link profile

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19597:


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

This message is automatically generated.

> Blueprint installation should accept quick link profile
> ---
>
> Key: AMBARI-19597
> URL: https://issues.apache.org/jira/browse/AMBARI-19597
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: trunk, 2.5.0
>Reporter: Balázs Bence Sári
>Assignee: Balázs Bence Sári
>Priority: Critical
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19597-QLP-BluePrint_25_v1.patch, 
> AMBARI-19597-QLP-BluePrint_trunk_v3.patch
>
>
> Specifying the quick links profile should be supported in blueprint based 
> cluster installation. First implementation will address the possibility of 
> adding the profile to the cluster creation template. See below a cluster 
> creation template that contains and embedded quick links profile:
> {code}
> {
>   "blueprint" : "wp",
>   "host_groups" :[
> {
>   "name" : "group1",
>   "hosts" : [
> {
>   "fqdn" : "ambari-agent-1.node.dc1.consul"
> }
>   ]
> }
>   ],
>   "quicklinks_profile": {
> "filters": [
>   {
> "link_attribute": "sso",
> "visible": true
>   }
> ],
> "services": []
>   }  
> }
> {code}



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

[jira] [Commented] (AMBARI-19633) accordion classname missed on configs page

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko commented on AMBARI-19633:
--

committed to trunk

> accordion classname missed on configs page
> --
>
> Key: AMBARI-19633
> URL: https://issues.apache.org/jira/browse/AMBARI-19633
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19633.patch
>
>




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

[jira] [Updated] (AMBARI-19630) Ambari should accept stack version in format of x.x.x.x without the build level digits

[Di Li (JIRA)]

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

Di Li updated AMBARI-19630:
---
Status: Patch Available  (was: Open)

> Ambari should accept stack version in format of x.x.x.x without the build 
> level digits
> --
>
> Key: AMBARI-19630
> URL: https://issues.apache.org/jira/browse/AMBARI-19630
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-trunk
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-19630.patch
>
>
> Ambari current requires stack version ( used in the repo) as x.x.x.x-, 
> Ambari should be flexible enough to accept both x.x.x.x- and x.x.x.x



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

[jira] [Updated] (AMBARI-19630) Ambari should accept stack version in format of x.x.x.x without the build level digits

[Di Li (JIRA)]

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

Di Li updated AMBARI-19630:
---
Attachment: AMBARI-19630.patch

> Ambari should accept stack version in format of x.x.x.x without the build 
> level digits
> --
>
> Key: AMBARI-19630
> URL: https://issues.apache.org/jira/browse/AMBARI-19630
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-trunk
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-19630.patch
>
>
> Ambari current requires stack version ( used in the repo) as x.x.x.x-, 
> Ambari should be flexible enough to accept both x.x.x.x- and x.x.x.x



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

[jira] [Updated] (AMBARI-19617) Restarting Some Components During a Suspended Upgrade Fails Due To Missing Upgrade Parameters

[Jonathan Hurley (JIRA)]

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

Jonathan Hurley updated AMBARI-19617:
-
Status: Patch Available  (was: Open)

> Restarting Some Components During a Suspended Upgrade Fails Due To Missing 
> Upgrade Parameters
> -
>
> Key: AMBARI-19617
> URL: https://issues.apache.org/jira/browse/AMBARI-19617
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19617.patch
>
>
> While attempting to restart a component that has complicated upgrade logic, 
> the upgrade parameters are not sent to the agents. This can cause some 
> components to fails during a suspended upgrade restart. 
> Example:
> - Begin express upgrade from {{2.3.6.0-3796}} to {{2.5.3.0-37}}
> - {{HIVE_METASTORE}} couldn't start b/c of a missing Kerberos property:
> {code}
> resource_management.core.exceptions.Fail: Configuration parameter 
> 'hive.server2.authentication.kerberos.principal' was not found in 
> configurations dictionary!
> {code}
> - Chose to {{Ignore and Proceed}} which means that none of the Metastore SQL 
> files ran. 
> - Paused the upgrade (presumably at Finalize) and try to start Metastore. It 
> fails to start because the new HDP 2.5 bits are using a non-upgraded 
> database. That causes the {{-info}} option to fail and makes Ambari think it 
> needs to run {{-initSchema}}. 
> RCA: Metastore failed to start during upgrade and the admin chose to skip it. 
> This caused schema upgrade logic not to run. Ambari can examine the 
> {{upgrade_suspended}} property to determine if we need to run upgrade 
> commands while restarting Metastore during an upgrade. 
> However, it might be more prudent to simply send along the suspended upgrade 
> properties so that any actions which might need to happen (such as invoking 
> an upgrade script during the restart) can happen when the upgrade is 
> suspended.



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

[jira] [Updated] (AMBARI-19617) Restarting Some Components During a Suspended Upgrade Fails Due To Missing Upgrade Parameters

[Jonathan Hurley (JIRA)]

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

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

> Restarting Some Components During a Suspended Upgrade Fails Due To Missing 
> Upgrade Parameters
> -
>
> Key: AMBARI-19617
> URL: https://issues.apache.org/jira/browse/AMBARI-19617
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19617.patch
>
>
> While attempting to restart a component that has complicated upgrade logic, 
> the upgrade parameters are not sent to the agents. This can cause some 
> components to fails during a suspended upgrade restart. 
> Example:
> - Begin express upgrade from {{2.3.6.0-3796}} to {{2.5.3.0-37}}
> - {{HIVE_METASTORE}} couldn't start b/c of a missing Kerberos property:
> {code}
> resource_management.core.exceptions.Fail: Configuration parameter 
> 'hive.server2.authentication.kerberos.principal' was not found in 
> configurations dictionary!
> {code}
> - Chose to {{Ignore and Proceed}} which means that none of the Metastore SQL 
> files ran. 
> - Paused the upgrade (presumably at Finalize) and try to start Metastore. It 
> fails to start because the new HDP 2.5 bits are using a non-upgraded 
> database. That causes the {{-info}} option to fail and makes Ambari think it 
> needs to run {{-initSchema}}. 
> RCA: Metastore failed to start during upgrade and the admin chose to skip it. 
> This caused schema upgrade logic not to run. Ambari can examine the 
> {{upgrade_suspended}} property to determine if we need to run upgrade 
> commands while restarting Metastore during an upgrade. 
> However, it might be more prudent to simply send along the suspended upgrade 
> properties so that any actions which might need to happen (such as invoking 
> an upgrade script during the restart) can happen when the upgrade is 
> suspended.



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

[jira] [Updated] (AMBARI-19617) Restarting Some Components During a Suspended Upgrade Fails Due To Missing Upgrade Parameters

[Jonathan Hurley (JIRA)]

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

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

> Restarting Some Components During a Suspended Upgrade Fails Due To Missing 
> Upgrade Parameters
> -
>
> Key: AMBARI-19617
> URL: https://issues.apache.org/jira/browse/AMBARI-19617
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19617.patch
>
>
> While attempting to restart a component that has complicated upgrade logic, 
> the upgrade parameters are not sent to the agents. This can cause some 
> components to fails during a suspended upgrade restart. 
> Example:
> - Begin express upgrade from {{2.3.6.0-3796}} to {{2.5.3.0-37}}
> - {{HIVE_METASTORE}} couldn't start b/c of a missing Kerberos property:
> {code}
> resource_management.core.exceptions.Fail: Configuration parameter 
> 'hive.server2.authentication.kerberos.principal' was not found in 
> configurations dictionary!
> {code}
> - Chose to {{Ignore and Proceed}} which means that none of the Metastore SQL 
> files ran. 
> - Paused the upgrade (presumably at Finalize) and try to start Metastore. It 
> fails to start because the new HDP 2.5 bits are using a non-upgraded 
> database. That causes the {{-info}} option to fail and makes Ambari think it 
> needs to run {{-initSchema}}. 
> RCA: Metastore failed to start during upgrade and the admin chose to skip it. 
> This caused schema upgrade logic not to run. Ambari can examine the 
> {{upgrade_suspended}} property to determine if we need to run upgrade 
> commands while restarting Metastore during an upgrade. 
> However, it might be more prudent to simply send along the suspended upgrade 
> properties so that any actions which might need to happen (such as invoking 
> an upgrade script during the restart) can happen when the upgrade is 
> suspended.



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

[jira] [Updated] (AMBARI-19597) Blueprint installation should accept quick link profile

[JIRA]

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

Balázs Bence Sári updated AMBARI-19597:
---
Attachment: AMBARI-19597-QLP-BluePrint_25_v1.patch

> Blueprint installation should accept quick link profile
> ---
>
> Key: AMBARI-19597
> URL: https://issues.apache.org/jira/browse/AMBARI-19597
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: trunk, 2.5.0
>Reporter: Balázs Bence Sári
>Assignee: Balázs Bence Sári
>Priority: Critical
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19597-QLP-BluePrint_25_v1.patch, 
> AMBARI-19597-QLP-BluePrint_trunk_v3.patch
>
>
> Specifying the quick links profile should be supported in blueprint based 
> cluster installation. First implementation will address the possibility of 
> adding the profile to the cluster creation template. See below a cluster 
> creation template that contains and embedded quick links profile:
> {code}
> {
>   "blueprint" : "wp",
>   "host_groups" :[
> {
>   "name" : "group1",
>   "hosts" : [
> {
>   "fqdn" : "ambari-agent-1.node.dc1.consul"
> }
>   ]
> }
>   ],
>   "quicklinks_profile": {
> "filters": [
>   {
> "link_attribute": "sso",
> "visible": true
>   }
> ],
> "services": []
>   }  
> }
> {code}



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

[jira] [Updated] (AMBARI-19636) Provide default values for Kafka nofile and nproc limit properties

[Di Li (JIRA)]

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

Di Li updated AMBARI-19636:
---
Description: Provide default values for Kafka nofile and nproc limit 
properties

> Provide default values for Kafka nofile and nproc limit properties
> --
>
> Key: AMBARI-19636
> URL: https://issues.apache.org/jira/browse/AMBARI-19636
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-19636.patch
>
>
> Provide default values for Kafka nofile and nproc limit properties



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

[jira] [Updated] (AMBARI-19636) Provide default values for Kafka nofile and nproc limit properties

[Di Li (JIRA)]

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

Di Li updated AMBARI-19636:
---
Attachment: AMBARI-19636.patch

> Provide default values for Kafka nofile and nproc limit properties
> --
>
> Key: AMBARI-19636
> URL: https://issues.apache.org/jira/browse/AMBARI-19636
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-19636.patch
>
>




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

[jira] [Updated] (AMBARI-19636) Provide default values for Kafka nofile and nproc limit properties

[Di Li (JIRA)]

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

Di Li updated AMBARI-19636:
---
Status: Patch Available  (was: Open)

> Provide default values for Kafka nofile and nproc limit properties
> --
>
> Key: AMBARI-19636
> URL: https://issues.apache.org/jira/browse/AMBARI-19636
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-19636.patch
>
>




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

[jira] [Created] (AMBARI-19636) Provide default values for Kafka nofile and nproc limit properties

[Di Li (JIRA)]

Di Li created AMBARI-19636:
--

 Summary: Provide default values for Kafka nofile and nproc limit 
properties
 Key: AMBARI-19636
 URL: https://issues.apache.org/jira/browse/AMBARI-19636
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: trunk
Reporter: Di Li
Assignee: Di Li
Priority: Minor
 Fix For: trunk






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

[jira] [Created] (AMBARI-19635) Provide default values for Kafka nofile and nproc limit properties

[Di Li (JIRA)]

Di Li created AMBARI-19635:
--

 Summary: Provide default values for Kafka nofile and nproc limit 
properties
 Key: AMBARI-19635
 URL: https://issues.apache.org/jira/browse/AMBARI-19635
 Project: Ambari
  Issue Type: Bug
  Components: ambari-sever
Affects Versions: trunk
Reporter: Di Li
Assignee: Di Li
Priority: Minor
 Fix For: trunk






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

[jira] [Updated] (AMBARI-19634) Log Search UI: Add description about Snapshot feature

[JIRA]

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

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

> Log Search UI: Add description about Snapshot feature
> -
>
> Key: AMBARI-19634
> URL: https://issues.apache.org/jira/browse/AMBARI-19634
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-19634.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>




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

[jira] [Created] (AMBARI-19634) Log Search UI: Add description about Snapshot feature

[JIRA]

Olivér Szabó created AMBARI-19634:
-

 Summary: Log Search UI: Add description about Snapshot feature
 Key: AMBARI-19634
 URL: https://issues.apache.org/jira/browse/AMBARI-19634
 Project: Ambari
  Issue Type: Bug
  Components: ambari-logsearch
Affects Versions: 2.4.0
Reporter: Olivér Szabó
Assignee: Olivér Szabó
 Fix For: 2.5.0






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

[jira] [Commented] (AMBARI-19623) Atlas startup failed with ZkTimeoutException exception, zookeeper timeout values are very low.

[Mahadev konar (JIRA)]

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

Mahadev konar commented on AMBARI-19623:


+1 for the patch.

> Atlas startup failed with ZkTimeoutException exception, zookeeper timeout 
> values are very low.
> --
>
> Key: AMBARI-19623
> URL: https://issues.apache.org/jira/browse/AMBARI-19623
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Ayub Khan
>Assignee: Ayub Khan
>Priority: Critical
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19623.patch
>
>
> Currently zookeeper connect/session timeout values for atlas are set to 
> 200/400 ms respectively which are very low and not practical/recommended 
> values. Due to this atlas startup fails more frequently.
> The jira is set recommended values for zookeeper timeout configuration.
> {noformat}
> atlas.kafka.zookeeper.connection.timeout.ms=3
> atlas.kafka.zookeeper.session.timeout.ms=6
> atlas.audit.zookeeper.session.timeout.ms=6
> {noformat} 



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

[jira] [Updated] (AMBARI-19633) accordion classname missed on configs page

[Aleksandr Kovalenko (JIRA)]

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

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

> accordion classname missed on configs page
> --
>
> Key: AMBARI-19633
> URL: https://issues.apache.org/jira/browse/AMBARI-19633
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19633.patch
>
>




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

[jira] [Updated] (AMBARI-19633) accordion classname missed on configs page

[Aleksandr Kovalenko (JIRA)]

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

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

> accordion classname missed on configs page
> --
>
> Key: AMBARI-19633
> URL: https://issues.apache.org/jira/browse/AMBARI-19633
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19633.patch
>
>




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

[jira] [Created] (AMBARI-19633) accordion classname missed on configs page

[Aleksandr Kovalenko (JIRA)]

Aleksandr Kovalenko created AMBARI-19633:


 Summary: accordion classname missed on configs page
 Key: AMBARI-19633
 URL: https://issues.apache.org/jira/browse/AMBARI-19633
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.5.0
Reporter: Aleksandr Kovalenko
Assignee: Aleksandr Kovalenko
Priority: Critical
 Fix For: 2.5.0






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

[jira] [Updated] (AMBARI-19546) Add support for call context to the stack advisor

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-19546:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to trunk and branch-2.5

> Add support for call context to the stack advisor
> -
>
> Key: AMBARI-19546
> URL: https://issues.apache.org/jira/browse/AMBARI-19546
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19546.patch
>
>
> Add support for call context to stack advisor.
> Stack advisor coding will be simpler if the calls are aware of the context 
> with which calls are being made.
> Some of the context are:
> * Fresh install
> * Config editing (landing on a config page)
> * Compute attributes
> * Add service
> * Delete service
> * Enable kerberos
> * Enable HA
> The plan is to add some context fields that can be populated by the caller of 
> stack recommendation APIs and consumed by the stack advisor code.



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

[jira] [Created] (AMBARI-19632) Ldap sync fails when there are special characters in distinguished names

[Robert Levas (JIRA)]

Robert Levas created AMBARI-19632:
-

 Summary: Ldap sync fails when there are special characters in 
distinguished names
 Key: AMBARI-19632
 URL: https://issues.apache.org/jira/browse/AMBARI-19632
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.4.0
Reporter: Robert Levas
Assignee: Robert Levas
Priority: Critical
 Fix For: 2.5.0


Ldap sync fails when there are special characters in distinguished names. 

For example if there was a user with the distinguished name of 
{{OU=test/test,OU=users,DC=EXAMPLE,DC=COM}} and that user was a member of a 
synced group, then the lookup of the user using the membership attribute in the 
group would fail due to the special character.  

The error would look something like
{noformat}
REASON: Caught exception running LDAP sync. Uncategorized exception occured 
during LDAP processing; nested exception is javax.naming.NamingException: 
[LDAP: error code 1 - 20D6: SvcErr: DSID-031007DB, problem 5012 
(DIR_ERROR), data 0
]; remaining name 'OU=test/test,OU=users,DC=EXAMPLE,DC=COM'
{noformat}

*Solution*
Update the library versionf for Spring LDAP 
* {{org.springframework.security/spring-security-ldap}} to {{4.0.4.RELEASE}}
* {{org.springframework.ldap/spring-ldap-core}} to {{2.0.4.RELEASE}}

Then use {{LdapUtils.newLdapName}} to convert a String representing a DN into a 
{{javax.naming.ldap.LdapName}} and use that object in the search facility 
executed in 
{{org.apache.ambari.server.security.ldap.AmbariLdapDataPopulator#getFilteredLdapUsers(java.lang.String,
 org.springframework.ldap.filter.Filter)}}. 




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

[jira] [Commented] (AMBARI-19613) ZKFC Zookeper connection is not secure

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19613:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12848323/AMBARI-19613.v1.b-2.5.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/10152//console

This message is automatically generated.

> ZKFC Zookeper connection is not secure
> --
>
> Key: AMBARI-19613
> URL: https://issues.apache.org/jira/browse/AMBARI-19613
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent, ambari-server
>Affects Versions: 2.5.0
>Reporter: Laszlo Puskas
>Assignee: Laszlo Puskas
> Fix For: 2.5.0
>
> Attachments: AMBARI-19613.v1.b-2.5.patch, AMBARI-19613.v4.trunk.patch
>
>
> On secure namenode HA clusters the ZKFC component needs to access the 
> zookeeper securely.
> On enabling security appropriate settings are configured to secure this 
> connection. 



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

[jira] [Updated] (AMBARI-19597) Blueprint installation should accept quick link profile

[JIRA]

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

Balázs Bence Sári updated AMBARI-19597:
---
Status: Patch Available  (was: Open)

> Blueprint installation should accept quick link profile
> ---
>
> Key: AMBARI-19597
> URL: https://issues.apache.org/jira/browse/AMBARI-19597
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: trunk, 2.5.0
>Reporter: Balázs Bence Sári
>Assignee: Balázs Bence Sári
>Priority: Critical
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19597-QLP-BluePrint_trunk_v3.patch
>
>
> Specifying the quick links profile should be supported in blueprint based 
> cluster installation. First implementation will address the possibility of 
> adding the profile to the cluster creation template. See below a cluster 
> creation template that contains and embedded quick links profile:
> {code}
> {
>   "blueprint" : "wp",
>   "host_groups" :[
> {
>   "name" : "group1",
>   "hosts" : [
> {
>   "fqdn" : "ambari-agent-1.node.dc1.consul"
> }
>   ]
> }
>   ],
>   "quicklinks_profile": {
> "filters": [
>   {
> "link_attribute": "sso",
> "visible": true
>   }
> ],
> "services": []
>   }  
> }
> {code}



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