[jira] [Updated] (AMBARI-18842) Provide support for removing an mpack on the command line
[ https://issues.apache.org/jira/browse/AMBARI-18842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18842: --- Status: Open (was: Patch Available) > Provide support for removing an mpack on the command line > - > > Key: AMBARI-18842 > URL: https://issues.apache.org/jira/browse/AMBARI-18842 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: 2.5.0 > > Attachments: AMBARI-18842.3.patch > > > # Provide command line support to remove a management pack. > # Removal should work for add-on service mpacks. > # Removal command should remove all versions the mpack to be removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18842) Provide support for removing an mpack on the command line
[ https://issues.apache.org/jira/browse/AMBARI-18842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18842: --- Attachment: (was: AMBARI-18842.patch) > Provide support for removing an mpack on the command line > - > > Key: AMBARI-18842 > URL: https://issues.apache.org/jira/browse/AMBARI-18842 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: 2.5.0 > > Attachments: AMBARI-18842.3.patch > > > # Provide command line support to remove a management pack. > # Removal should work for add-on service mpacks. > # Removal command should remove all versions the mpack to be removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18842) Provide support for removing an mpack on the command line
[ https://issues.apache.org/jira/browse/AMBARI-18842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18842: --- Status: Patch Available (was: Open) > Provide support for removing an mpack on the command line > - > > Key: AMBARI-18842 > URL: https://issues.apache.org/jira/browse/AMBARI-18842 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: 2.5.0 > > Attachments: AMBARI-18842.3.patch > > > # Provide command line support to remove a management pack. > # Removal should work for add-on service mpacks. > # Removal command should remove all versions the mpack to be removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18842) Provide support for removing an mpack on the command line
[ https://issues.apache.org/jira/browse/AMBARI-18842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18842: --- Attachment: AMBARI-18842.3.patch > Provide support for removing an mpack on the command line > - > > Key: AMBARI-18842 > URL: https://issues.apache.org/jira/browse/AMBARI-18842 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: 2.5.0 > > Attachments: AMBARI-18842.3.patch > > > # Provide command line support to remove a management pack. > # Removal should work for add-on service mpacks. > # Removal command should remove all versions the mpack to be removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-18836) Remove group readable from hdfs headless keytab
[
https://issues.apache.org/jira/browse/AMBARI-18836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila reopened AMBARI-18836:
This causes python unit test failure.
{noformat}
Failed tests:
FAIL: test_start_secured (test_webhcat_server.TestWebHCatServer)
--
Traceback (most recent call last):
File
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-common/src/test/python/mock/mock.py",
line 1199, in patched
return func(*args, **keywargs)
File
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-server/src/test/python/stacks/2.0.6/HIVE/test_webhcat_server.py",
line 134, in test_start_secured
self.assert_configure_secured()
File
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-server/src/test/python/stacks/2.0.6/HIVE/test_webhcat_server.py",
line 257, in assert_configure_secured
user = 'hcat',
File
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
line 280, in assertResourceCalled
self.assertEquals(resource_type, resource.__class__.__name__)
AssertionError: 'Execute' != 'XmlConfig'
--
Total run:1166
Total errors:0
Total failures:1
{noformat}
> Remove group readable from hdfs headless keytab
> ---
>
> Key: AMBARI-18836
> URL: https://issues.apache.org/jira/browse/AMBARI-18836
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Shi Wang
>Assignee: Shi Wang
> Fix For: trunk
>
> Attachments:
> 0001-AMBARI-18836-Remove-group-readable-from-hdfs-headles.patch
>
>
> The Smoke and “Headless” Service users are used by Ambari to perform service
> “smoke” checks and run alert health checks.
> The permission for hdfs.headless.keytab is 440. But it will cause security
> concern to allow other service user in hadoop group to kinit hdfs headless
> principal using hdfs.headless.keytab. In this way, other service user could
> "pretend" to be hdfs user and be granted hdfs user's authorities.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18836) Remove group readable from hdfs headless keytab
[ https://issues.apache.org/jira/browse/AMBARI-18836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-18836: --- Attachment: AMBARI-18836-test_failure.patch > Remove group readable from hdfs headless keytab > --- > > Key: AMBARI-18836 > URL: https://issues.apache.org/jira/browse/AMBARI-18836 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: Shi Wang >Assignee: Shi Wang > Fix For: trunk > > Attachments: > 0001-AMBARI-18836-Remove-group-readable-from-hdfs-headles.patch, > AMBARI-18836-test_failure.patch > > > The Smoke and “Headless” Service users are used by Ambari to perform service > “smoke” checks and run alert health checks. > The permission for hdfs.headless.keytab is 440. But it will cause security > concern to allow other service user in hadoop group to kinit hdfs headless > principal using hdfs.headless.keytab. In this way, other service user could > "pretend" to be hdfs user and be granted hdfs user's authorities. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18836) Remove group readable from hdfs headless keytab
[
https://issues.apache.org/jira/browse/AMBARI-18836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15689389#comment-15689389
]
Doroszlai, Attila commented on AMBARI-18836:
[~rlevas] could you please commit [^AMBARI-18836-test_failure.patch], too?
{noformat}
Total run:1166
Total errors:0
Total failures:0
{noformat}
> Remove group readable from hdfs headless keytab
> ---
>
> Key: AMBARI-18836
> URL: https://issues.apache.org/jira/browse/AMBARI-18836
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Shi Wang
>Assignee: Shi Wang
> Fix For: trunk
>
> Attachments:
> 0001-AMBARI-18836-Remove-group-readable-from-hdfs-headles.patch,
> AMBARI-18836-test_failure.patch
>
>
> The Smoke and “Headless” Service users are used by Ambari to perform service
> “smoke” checks and run alert health checks.
> The permission for hdfs.headless.keytab is 440. But it will cause security
> concern to allow other service user in hadoop group to kinit hdfs headless
> principal using hdfs.headless.keytab. In this way, other service user could
> "pretend" to be hdfs user and be granted hdfs user's authorities.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18966) Add check to ensure we do not have @Transactional annotations on private methods
[
https://issues.apache.org/jira/browse/AMBARI-18966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15689413#comment-15689413
]
Doroszlai, Attila commented on AMBARI-18966:
{noformat}
Failed tests:
FAIL: test_start_secured (test_webhcat_server.TestWebHCatServer)
{noformat}
is not related to this patch, caused by AMBARI-18836.
> Add check to ensure we do not have @Transactional annotations on private
> methods
>
>
> Key: AMBARI-18966
> URL: https://issues.apache.org/jira/browse/AMBARI-18966
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18966.patch
>
>
> {{@Transactional}} methods [must not be
> {{private}}|https://github.com/google/guice/wiki/Transactions#method-level-transactional].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18781) ambari server StackOverflowError in IBM PPC64
[ https://issues.apache.org/jira/browse/AMBARI-18781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18781: Status: Patch Available (was: Reopened) > ambari server StackOverflowError in IBM PPC64 > - > > Key: AMBARI-18781 > URL: https://issues.apache.org/jira/browse/AMBARI-18781 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: wuhui > Fix For: trunk > > Attachments: AMBARI-18781.patch > > > 02 Nov 2016 09:27:22,301 INFO [qtp-client-85] PersistKeyValueService:82 - > Looking for keyName CLUSTER_CURRENT_STATUS > 02 Nov 2016 09:27:25,360 INFO [qtp-client-125] PersistKeyValueService:82 - > Looking for keyName CLUSTER_CURRENT_STATUS > 02 Nov 2016 09:28:32,681 WARN [qtp-client-85] ServletHandler:538 - > javax.servlet.ServletException: java.lang.StackOverflowError > at > com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:420) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:540) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:715) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) > at > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1496) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330) > at > org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118) > at > org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:103) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:54) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:45) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.apache.ambari.server.security.authorization.AmbariAuthorizationFilter.doFilter(AmbariAuthorizationFilter.java:182) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:150) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-18781) ambari server StackOverflowError in IBM PPC64
[ https://issues.apache.org/jira/browse/AMBARI-18781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin reopened AMBARI-18781: - > ambari server StackOverflowError in IBM PPC64 > - > > Key: AMBARI-18781 > URL: https://issues.apache.org/jira/browse/AMBARI-18781 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: wuhui > Fix For: trunk > > Attachments: AMBARI-18781.patch > > > 02 Nov 2016 09:27:22,301 INFO [qtp-client-85] PersistKeyValueService:82 - > Looking for keyName CLUSTER_CURRENT_STATUS > 02 Nov 2016 09:27:25,360 INFO [qtp-client-125] PersistKeyValueService:82 - > Looking for keyName CLUSTER_CURRENT_STATUS > 02 Nov 2016 09:28:32,681 WARN [qtp-client-85] ServletHandler:538 - > javax.servlet.ServletException: java.lang.StackOverflowError > at > com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:420) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:540) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:715) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) > at > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1496) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330) > at > org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118) > at > org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:103) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:54) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:45) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.apache.ambari.server.security.authorization.AmbariAuthorizationFilter.doFilter(AmbariAuthorizationFilter.java:182) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:150) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18948) hive metrics : support hs2 with remote metastore
[ https://issues.apache.org/jira/browse/AMBARI-18948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18948: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > hive metrics : support hs2 with remote metastore > > > Key: AMBARI-18948 > URL: https://issues.apache.org/jira/browse/AMBARI-18948 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.0 > > Attachments: AMBARI-18948.patch > > > Currently, the only "enable" config param we set on hive to enable metrics > logging from hive is "hive.metastore.metrics.enabled". This parameter winds up > enabling the metrics system for both the metastore as well as HS2 (since HS2 > typically runs with embedded metastore, and the metrics we log for HS2 include > these api calls up front and center in Grafana). > However, this is an issue in that we're not enabling/tracking metrics for HS2 > instances that run with a remote metastore, since that is enabled by a > different flag, called "hive.server2.metrics.enabled". This flag also needs to > be set when metrics is enabled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18971) Populate Ranger LDAP group configs under LDAP category used for authentication
Mugdha Varadkar created AMBARI-18971: Summary: Populate Ranger LDAP group configs under LDAP category used for authentication Key: AMBARI-18971 URL: https://issues.apache.org/jira/browse/AMBARI-18971 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0, 2.2.2, 2.4.1, 2.4.2 Reporter: Mugdha Varadkar Assignee: Mugdha Varadkar Priority: Critical Fix For: 2.5.0 There are two properties under advanced ranger-admin-site called "Group Search Base" and "Group Search Filter" which are auto populated with the ones from Ranger User Info Group config. These are used during ldap authentication. It is little confusing as they are hidden somewhere below and user is not aware of these config while configuring other authentication properties -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-18641) When the value "Audit to DB/Audit to Solr/Audit to HDFS" is turned to ON, Ambari should automatically set ranger.audit.source.type to the right value
[ https://issues.apache.org/jira/browse/AMBARI-18641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar reassigned AMBARI-18641: Assignee: Mugdha Varadkar > When the value "Audit to DB/Audit to Solr/Audit to HDFS" is turned to ON, > Ambari should automatically set ranger.audit.source.type to the right value > - > > Key: AMBARI-18641 > URL: https://issues.apache.org/jira/browse/AMBARI-18641 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Chun Tam >Assignee: Mugdha Varadkar > > PROBLEM: When the value "Audit to DB/Audit to Solr/Audit to HDFS" is turned > to ON, Ambari should automatically set ranger.audit.source.type to the right > value. Either one of the properties should be deprecated > BUSINESS IMPACT: This is confusing > Reproduced on Ambari 2.2.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-18641) When the value "Audit to DB/Audit to Solr/Audit to HDFS" is turned to ON, Ambari should automatically set ranger.audit.source.type to the right value
[ https://issues.apache.org/jira/browse/AMBARI-18641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar resolved AMBARI-18641. -- Resolution: Fixed [~ctam] fix is handled in AMBARI-14562 and is available from Ambari 2.4.0 > When the value "Audit to DB/Audit to Solr/Audit to HDFS" is turned to ON, > Ambari should automatically set ranger.audit.source.type to the right value > - > > Key: AMBARI-18641 > URL: https://issues.apache.org/jira/browse/AMBARI-18641 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Chun Tam >Assignee: Mugdha Varadkar > > PROBLEM: When the value "Audit to DB/Audit to Solr/Audit to HDFS" is turned > to ON, Ambari should automatically set ranger.audit.source.type to the right > value. Either one of the properties should be deprecated > BUSINESS IMPACT: This is confusing > Reproduced on Ambari 2.2.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18948) hive metrics : support hs2 with remote metastore
[ https://issues.apache.org/jira/browse/AMBARI-18948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15689586#comment-15689586 ] Hudson commented on AMBARI-18948: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6071 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6071/]) AMBARI-18948. hive metrics : support hs2 with remote metastore (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=292d27987f7c0fa0265ba9d2f6c47f69cb9827c9]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/hivemetastore-site.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/hiveserver2-interactive-site.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/hiveserver2-site.xml > hive metrics : support hs2 with remote metastore > > > Key: AMBARI-18948 > URL: https://issues.apache.org/jira/browse/AMBARI-18948 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.0 > > Attachments: AMBARI-18948.patch > > > Currently, the only "enable" config param we set on hive to enable metrics > logging from hive is "hive.metastore.metrics.enabled". This parameter winds up > enabling the metrics system for both the metastore as well as HS2 (since HS2 > typically runs with embedded metastore, and the metrics we log for HS2 include > these api calls up front and center in Grafana). > However, this is an issue in that we're not enabling/tracking metrics for HS2 > instances that run with a remote metastore, since that is enabled by a > different flag, called "hive.server2.metrics.enabled". This flag also needs to > be set when metrics is enabled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18971) Populate Ranger LDAP group configs under LDAP category used for authentication
[ https://issues.apache.org/jira/browse/AMBARI-18971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-18971: - Attachment: AMBARI-18971.patch > Populate Ranger LDAP group configs under LDAP category used for authentication > -- > > Key: AMBARI-18971 > URL: https://issues.apache.org/jira/browse/AMBARI-18971 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0, 2.2.2, 2.4.1, 2.4.2 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18971.patch > > > There are two properties under advanced ranger-admin-site called "Group > Search Base" and "Group Search Filter" which are auto populated with the ones > from Ranger User Info Group config. These are used during ldap authentication. > It is little confusing as they are hidden somewhere below and user is not > aware of these config while configuring other authentication properties -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18781) ambari server StackOverflowError in IBM PPC64
[
https://issues.apache.org/jira/browse/AMBARI-18781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15689653#comment-15689653
]
Hadoop QA commented on AMBARI-18781:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836704/AMBARI-18781.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9366//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9366//console
This message is automatically generated.
> ambari server StackOverflowError in IBM PPC64
> -
>
> Key: AMBARI-18781
> URL: https://issues.apache.org/jira/browse/AMBARI-18781
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: wuhui
> Fix For: trunk
>
> Attachments: AMBARI-18781.patch
>
>
> 02 Nov 2016 09:27:22,301 INFO [qtp-client-85] PersistKeyValueService:82 -
> Looking for keyName CLUSTER_CURRENT_STATUS
> 02 Nov 2016 09:27:25,360 INFO [qtp-client-125] PersistKeyValueService:82 -
> Looking for keyName CLUSTER_CURRENT_STATUS
> 02 Nov 2016 09:28:32,681 WARN [qtp-client-85] ServletHandler:538 -
> javax.servlet.ServletException: java.lang.StackOverflowError
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:420)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:540)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:715)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
> at
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1496)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
> at
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118)
> at
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:103)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:54)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:45)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.apache.ambari.server.security.authorization.AmbariAuthorizationFilter.doFilter(AmbariAuthorizationFilter.java:182)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:150)
> at
> org.springframework.security.web.FilterChainP
[jira] [Updated] (AMBARI-18971) Populate Ranger LDAP group configs under LDAP category used for authentication
[ https://issues.apache.org/jira/browse/AMBARI-18971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-18971: - Status: Patch Available (was: In Progress) > Populate Ranger LDAP group configs under LDAP category used for authentication > -- > > Key: AMBARI-18971 > URL: https://issues.apache.org/jira/browse/AMBARI-18971 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0, 2.2.2, 2.4.1, 2.4.2 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18971.patch > > > There are two properties under advanced ranger-admin-site called "Group > Search Base" and "Group Search Filter" which are auto populated with the ones > from Ranger User Info Group config. These are used during ldap authentication. > It is little confusing as they are hidden somewhere below and user is not > aware of these config while configuring other authentication properties -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18966) Add check to ensure we do not have @Transactional annotations on private methods
[
https://issues.apache.org/jira/browse/AMBARI-18966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15689704#comment-15689704
]
Hadoop QA commented on AMBARI-18966:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12840151/AMBARI-18966.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9367//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9367//console
This message is automatically generated.
> Add check to ensure we do not have @Transactional annotations on private
> methods
>
>
> Key: AMBARI-18966
> URL: https://issues.apache.org/jira/browse/AMBARI-18966
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18966.patch
>
>
> {{@Transactional}} methods [must not be
> {{private}}|https://github.com/google/guice/wiki/Transactions#method-level-transactional].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (AMBARI-18912) Implement Create Alerts: step 1 select alert type
[ https://issues.apache.org/jira/browse/AMBARI-18912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko reopened AMBARI-18912: > Implement Create Alerts: step 1 select alert type > - > > Key: AMBARI-18912 > URL: https://issues.apache.org/jira/browse/AMBARI-18912 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 2.5.0 > > Attachments: AMBARI-18912-branch-2.5.patch, AMBARI-18912.patch, > AMBARI-18912.patch, Screen Shot 2016-11-16 at 6.13.51 PM.png, Screen Shot > 2016-11-17 at 5.59.59 PM.png > > Original Estimate: 24h > Remaining Estimate: 24h > > This is a FE task to implement the "Create Alerts Wizard " based on the > design attached. > In this task, should implement the step 1 in the design. All available alert > types should be displayed as options with icon, type and description. Make > sure that on clicking a type use would jump to next step. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18972) Remove redundant css (part 4)
Oleg Nechiporenko created AMBARI-18972: -- Summary: Remove redundant css (part 4) Key: AMBARI-18972 URL: https://issues.apache.org/jira/browse/AMBARI-18972 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 3.0.0 Reporter: Oleg Nechiporenko Assignee: Oleg Nechiporenko Fix For: 3.0.0 * Fix racks markup * Fix assign masters markup -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18972) Remove redundant css (part 4)
[ https://issues.apache.org/jira/browse/AMBARI-18972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-18972: --- Status: Patch Available (was: Open) +1 by [~atkach] on the review board > Remove redundant css (part 4) > - > > Key: AMBARI-18972 > URL: https://issues.apache.org/jira/browse/AMBARI-18972 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > > * Fix racks markup > * Fix assign masters markup -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18842) Provide support for removing an mpack on the command line
[
https://issues.apache.org/jira/browse/AMBARI-18842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15689757#comment-15689757
]
Hadoop QA commented on AMBARI-18842:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12840218/AMBARI-18842.3.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/9368//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9368//console
This message is automatically generated.
> Provide support for removing an mpack on the command line
> -
>
> Key: AMBARI-18842
> URL: https://issues.apache.org/jira/browse/AMBARI-18842
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.5.0
>
> Attachments: AMBARI-18842.3.patch
>
>
> # Provide command line support to remove a management pack.
> # Removal should work for add-on service mpacks.
> # Removal command should remove all versions the mpack to be removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18970) Unable to load Grafana Graphs in IE11
[
https://issues.apache.org/jira/browse/AMBARI-18970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15689806#comment-15689806
]
Hadoop QA commented on AMBARI-18970:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12840185/AMBARI-18970.v0.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 .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9369//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9369//console
This message is automatically generated.
> Unable to load Grafana Graphs in IE11
> -
>
> Key: AMBARI-18970
> URL: https://issues.apache.org/jira/browse/AMBARI-18970
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.4.0
> Environment: Windows 8.1
> Internet Explorer 11
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-18970.v0.patch
>
>
> Getting JS error in IE11 that prevents any graph from loading.
> JS Error
> +++
> Error Message:Unable to get property 'lastIndexOf' of undefined or null
> reference
> Stack trace:
> TypeError: Unable to get property 'lastIndexOf' of undefined or null reference
> at AmbariMetricsDatasource.prototype.query
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18965) Investigate and reduce AMS HA dependency on Zookeeper.
[
https://issues.apache.org/jira/browse/AMBARI-18965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15689874#comment-15689874
]
Hadoop QA commented on AMBARI-18965:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12840181/AMBARI-18965.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 3 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/9370//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9370//console
This message is automatically generated.
> Investigate and reduce AMS HA dependency on Zookeeper.
> --
>
> Key: AMBARI-18965
> URL: https://issues.apache.org/jira/browse/AMBARI-18965
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18965.patch
>
>
> In AMS embedded mode or distributed mode single collector deployments, we
> should try and reduce sink dependency on Zookeeper. In general, we should
> investigate how to reduce Zk fallback on single and multi-collector
> deployments.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18973) Service Auto Start: discard popup appears even when no changes were made
Andrii Tkach created AMBARI-18973: - Summary: Service Auto Start: discard popup appears even when no changes were made Key: AMBARI-18973 URL: https://issues.apache.org/jira/browse/AMBARI-18973 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 3.0.0 Discard popup appears even when no changes were made. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18973) Service Auto Start: discard popup appears even when no changes were made
[ https://issues.apache.org/jira/browse/AMBARI-18973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-18973: -- Attachment: AMBARI-18973.patch > Service Auto Start: discard popup appears even when no changes were made > > > Key: AMBARI-18973 > URL: https://issues.apache.org/jira/browse/AMBARI-18973 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-18973.patch > > > Discard popup appears even when no changes were made. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18973) Service Auto Start: discard popup appears even when no changes were made
[ https://issues.apache.org/jira/browse/AMBARI-18973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15689916#comment-15689916 ] Andrii Tkach commented on AMBARI-18973: --- 19850 tests complete (26 seconds) 156 tests pending > Service Auto Start: discard popup appears even when no changes were made > > > Key: AMBARI-18973 > URL: https://issues.apache.org/jira/browse/AMBARI-18973 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-18973.patch > > > Discard popup appears even when no changes were made. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18973) Service Auto Start: discard popup appears even when no changes were made
[ https://issues.apache.org/jira/browse/AMBARI-18973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-18973: -- Status: Patch Available (was: Open) > Service Auto Start: discard popup appears even when no changes were made > > > Key: AMBARI-18973 > URL: https://issues.apache.org/jira/browse/AMBARI-18973 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-18973.patch > > > Discard popup appears even when no changes were made. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18969) Add support to provide additional slider specific parameters to llap
[
https://issues.apache.org/jira/browse/AMBARI-18969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15689924#comment-15689924
]
Hadoop QA commented on AMBARI-18969:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12840180/AMBARI-18969.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9371//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9371//console
This message is automatically generated.
> Add support to provide additional slider specific parameters to llap
>
>
> Key: AMBARI-18969
> URL: https://issues.apache.org/jira/browse/AMBARI-18969
> 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-18969.patch
>
>
> Parameters need to be provided to the
> slider --service llap script, to restrict the range of ports.
> The range of ports needs to be taken as input from the user.
> Ambari could either add this as a port list field, or a more generic
> slider.global-conf entry list.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18968) Ambari Server Unit Test failure: org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs
[
https://issues.apache.org/jira/browse/AMBARI-18968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15689968#comment-15689968
]
Hadoop QA commented on AMBARI-18968:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12840169/AMBARI-18968.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9372//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9372//console
This message is automatically generated.
> Ambari Server Unit Test failure:
> org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs
> -
>
> Key: AMBARI-18968
> URL: https://issues.apache.org/jira/browse/AMBARI-18968
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
> Attachments: AMBARI-18968.patch
>
>
> {noformat}
> Error Message
> File
> /home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/target/test-classes/TestAmbaryServer.samples/../../../src/main/resources/stacks/PERF/1.0/services/YARN/configuration/yarn-site.xml
> didn't pass the validation. Error message is : cvc-complex-type.2.3: Element
> 'configuration' cannot have character [children], because the type's content
> type is element-only.
> {noformat}
> The file is malformed and has an extraneous property name outside of a
> field.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18967) Use max-AM percentage for a queue selected, instead of reading from top level common.
[
https://issues.apache.org/jira/browse/AMBARI-18967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15689974#comment-15689974
]
Hadoop QA commented on AMBARI-18967:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12840170/AMBARI-18967.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/9373//console
This message is automatically generated.
> Use max-AM percentage for a queue selected, instead of reading from top level
> common.
> -
>
> Key: AMBARI-18967
> URL: https://issues.apache.org/jira/browse/AMBARI-18967
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18967.patch
>
>
> *Current:*
> - We are reading the top level max-AM percent value for non 'llap' named
> queue at root level.
> Eg: yarn.scheduler.capacity.maximum-am-resource-percent=1
> *Required:*
> AM Percent value should be read as:
> - Fetch the 'AM Percent' value for queue in consideration, if exists, else
> - Return default value as 0.1.
> *Eg:*
> Say queue in consideration is named: 'xyz' and is at depth 3. Thus, the
> expected 'key' config to be read is :
> {noformat}
> yarn.scheduler.capacity.root.abc.xyz.maximum-am-resource-percent=
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18972) Remove redundant css (part 4)
[
https://issues.apache.org/jira/browse/AMBARI-18972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15689975#comment-15689975
]
Hadoop QA commented on AMBARI-18972:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org
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/9374//console
This message is automatically generated.
> Remove redundant css (part 4)
> -
>
> Key: AMBARI-18972
> URL: https://issues.apache.org/jira/browse/AMBARI-18972
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
>
> * Fix racks markup
> * Fix assign masters markup
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18972) Remove redundant css (part 4)
[
https://issues.apache.org/jira/browse/AMBARI-18972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690032#comment-15690032
]
Hadoop QA commented on AMBARI-18972:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org
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/9375//console
This message is automatically generated.
> Remove redundant css (part 4)
> -
>
> Key: AMBARI-18972
> URL: https://issues.apache.org/jira/browse/AMBARI-18972
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
>
> * Fix racks markup
> * Fix assign masters markup
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18972) Remove redundant css (part 4)
[ https://issues.apache.org/jira/browse/AMBARI-18972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690047#comment-15690047 ] Oleg Nechiporenko commented on AMBARI-18972: Committed to trunk > Remove redundant css (part 4) > - > > Key: AMBARI-18972 > URL: https://issues.apache.org/jira/browse/AMBARI-18972 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > > * Fix racks markup > * Fix assign masters markup -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18972) Remove redundant css (part 4)
[ https://issues.apache.org/jira/browse/AMBARI-18972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690045#comment-15690045 ] Oleg Nechiporenko commented on AMBARI-18972: Build failed not because of this patch > Remove redundant css (part 4) > - > > Key: AMBARI-18972 > URL: https://issues.apache.org/jira/browse/AMBARI-18972 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > > * Fix racks markup > * Fix assign masters markup -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18929) Yarn service check fails when either resource manager is down in HA enabled cluster
[
https://issues.apache.org/jira/browse/AMBARI-18929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690127#comment-15690127
]
Di Li commented on AMBARI-18929:
[~cheersyang] Principal-wise the two service checks seem to fail for the same
reason, they both fail prematurely when the logic hits a dead node.
Implementation-wise they are different. Yarn has the following logic ( also
with a very short timeout in my opinion). As you can see, it assumes both RM
are online, it should also handle curl exit code for better error handling.
for rm_webapp_address in params.rm_webapp_addresses_list:
info_app_url = params.scheme + "://" + rm_webapp_address +
"/ws/v1/cluster/apps/" + application_name
get_app_info_cmd = "curl --negotiate -u : -ks --location-trusted
--connect-timeout " + CURL_CONNECTION_TIMEOUT + " " + info_app_url
return_code, stdout, _ = get_user_call_output(get_app_info_cmd,
user=params.smokeuser,
path='/usr/sbin:/sbin:/usr/local/bin:/bin:/usr/bin',
)
# Handle HDP<2.2.8.1 where RM doesn't do automatic redirection from
standby to active
if stdout.startswith("This is standby RM. Redirecting to the current
active RM:"):
Logger.info(format("Skipped checking of {rm_webapp_address} since
returned '{stdout}'"))
continue
For HDFS, it's a two-path approach, I haven't run it but I suspect it'd be the
second part that fails on checkWebUI.py logic? If so, it'd be the same
suggestion, better error handling to continue with the check until all hosts
are pinged.
> Yarn service check fails when either resource manager is down in HA enabled
> cluster
> ---
>
> Key: AMBARI-18929
> URL: https://issues.apache.org/jira/browse/AMBARI-18929
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Weiwei Yang
>
> When HA is enabled, yarn service_check.py fails if one of RM is down, even
> the other one is active. This gives user the wrong impression the yarn
> cluster is not healthy. Instead, service check should pass, or at least pass
> with warning that lets user know there is one RM down.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18929) Yarn service check fails when either resource manager is down in HA enabled cluster
[ https://issues.apache.org/jira/browse/AMBARI-18929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690130#comment-15690130 ] Di Li commented on AMBARI-18929: [~cheersyang], Could you submit a patch for this issue please ? > Yarn service check fails when either resource manager is down in HA enabled > cluster > --- > > Key: AMBARI-18929 > URL: https://issues.apache.org/jira/browse/AMBARI-18929 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Weiwei Yang > > When HA is enabled, yarn service_check.py fails if one of RM is down, even > the other one is active. This gives user the wrong impression the yarn > cluster is not healthy. Instead, service check should pass, or at least pass > with warning that lets user know there is one RM down. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18972) Remove redundant css (part 4)
[ https://issues.apache.org/jira/browse/AMBARI-18972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690144#comment-15690144 ] Hudson commented on AMBARI-18972: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6072 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6072/]) AMBARI-18972. Remove redundant css (part 4) (onechiporenko) (onechiporenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6088c17906b784f57adca36af224d63135a49b9a]) * (edit) ambari-web/app/views/common/assign_master_components_view.js * (edit) ambari-web/app/templates/common/assign_master_components.hbs * (edit) ambari-web/app/templates/wizard/step3.hbs * (edit) ambari-web/app/styles/application.less * (edit) ambari-web/app/templates/main/service/info/heatmap_dropdown.hbs * (edit) ambari-web/app/templates/wizard/step9/step9HostTasksLogPopup.hbs * (edit) ambari-web/app/templates/wizard/step3/step3_host_warnings_popup.hbs * (edit) ambari-web/app/templates/main/charts/heatmap_dropdown.hbs * (edit) ambari-web/app/templates/main/charts/heatmap/heatmap_host_detail.hbs * (edit) ambari-web/app/views/main/charts/heatmap/heatmap_rack.js * (edit) ambari-web/app/templates/common/host_progress_popup.hbs * (edit) ambari-web/app/templates/main/charts/heatmap/heatmap_rack.hbs * (edit) ambari-web/app/controllers/main/charts/heatmap.js * (edit) ambari-web/app/templates/main/host/details/deleteComponentPopup.hbs * (edit) ambari-web/app/templates/main/host/details/doDeleteHostPopup.hbs * (edit) ambari-web/app/templates/common/form/check_db_connection.hbs * (edit) ambari-web/test/controllers/main/alerts/add_alert_definition/step1_controller_test.js * (edit) ambari-web/app/templates/main/host/details/raiseDeleteComponentErrorPopup.hbs * (edit) ambari-web/app/styles/wizard.less > Remove redundant css (part 4) > - > > Key: AMBARI-18972 > URL: https://issues.apache.org/jira/browse/AMBARI-18972 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > > * Fix racks markup > * Fix assign masters markup -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18973) Service Auto Start: discard popup appears even when no changes were made
[
https://issues.apache.org/jira/browse/AMBARI-18973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690146#comment-15690146
]
Hadoop QA commented on AMBARI-18973:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12840240/AMBARI-18973.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 4 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9376//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9376//console
This message is automatically generated.
> Service Auto Start: discard popup appears even when no changes were made
>
>
> Key: AMBARI-18973
> URL: https://issues.apache.org/jira/browse/AMBARI-18973
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-18973.patch
>
>
> Discard popup appears even when no changes were made.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18973) Service Auto Start: discard popup appears even when no changes were made
[ https://issues.apache.org/jira/browse/AMBARI-18973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690154#comment-15690154 ] Andrii Tkach commented on AMBARI-18973: --- committed to trunk > Service Auto Start: discard popup appears even when no changes were made > > > Key: AMBARI-18973 > URL: https://issues.apache.org/jira/browse/AMBARI-18973 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-18973.patch > > > Discard popup appears even when no changes were made. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18973) Service Auto Start: discard popup appears even when no changes were made
[ https://issues.apache.org/jira/browse/AMBARI-18973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-18973: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Service Auto Start: discard popup appears even when no changes were made > > > Key: AMBARI-18973 > URL: https://issues.apache.org/jira/browse/AMBARI-18973 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-18973.patch > > > Discard popup appears even when no changes were made. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18973) Service Auto Start: discard popup appears even when no changes were made
[
https://issues.apache.org/jira/browse/AMBARI-18973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690199#comment-15690199
]
Hadoop QA commented on AMBARI-18973:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12840240/AMBARI-18973.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 4 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9377//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9377//console
This message is automatically generated.
> Service Auto Start: discard popup appears even when no changes were made
>
>
> Key: AMBARI-18973
> URL: https://issues.apache.org/jira/browse/AMBARI-18973
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-18973.patch
>
>
> Discard popup appears even when no changes were made.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18971) Populate Ranger LDAP group configs under LDAP category used for authentication
[
https://issues.apache.org/jira/browse/AMBARI-18971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690204#comment-15690204
]
Hadoop QA commented on AMBARI-18971:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12840228/AMBARI-18971.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/9378//console
This message is automatically generated.
> Populate Ranger LDAP group configs under LDAP category used for authentication
> --
>
> Key: AMBARI-18971
> URL: https://issues.apache.org/jira/browse/AMBARI-18971
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0, 2.2.2, 2.4.1, 2.4.2
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18971.patch
>
>
> There are two properties under advanced ranger-admin-site called "Group
> Search Base" and "Group Search Filter" which are auto populated with the ones
> from Ranger User Info Group config. These are used during ldap authentication.
> It is little confusing as they are hidden somewhere below and user is not
> aware of these config while configuring other authentication properties
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-8840) Keytabs need to be created to include the encryption type of AES256 CTS mode with HMAC SHA1-96
[
https://issues.apache.org/jira/browse/AMBARI-8840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690227#comment-15690227
]
Robert Levas commented on AMBARI-8840:
--
[~forestsissi],
In Ambari 1.7, the keytab files were created manually. So it is possible they
were never created with an AES256 keytab entry. After Ambari 2.0, Ambari will
create the keytab files (if configured to do so) and will include the AES256
keytabs entry if:
* the correct unlimited key JCE policy is installed
* the configured encryption types do not exclude it - by default it is not
excluded
> Keytabs need to be created to include the encryption type of AES256 CTS mode
> with HMAC SHA1-96
> --
>
> Key: AMBARI-8840
> URL: https://issues.apache.org/jira/browse/AMBARI-8840
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.0.0, 2.1.0
> Environment: Red Hat Enterprise Linux Server release 6.6 (Santiago)
> [root@hdtest253 etc]# java -version
> java version "1.7.0_79"
> OpenJDK Runtime Environment (rhel-2.5.5.3.el6_6-x86_64 u79-b14)
> OpenJDK 64-Bit Server VM (build 24.79-b02, mixed mode)
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: kerberos, keytabs
> Fix For: 2.1.0
>
> Attachments: hadoop-hdfs-journalnode-hdtest253.svl.ibm.com.log
>
>
> During automated keytab generation, an entry with the following encryption
> type must be added else certain services will fail to start up or properly
> when Kerberos is enabled:
> {code}AES256 CTS mode with HMAC SHA1-96{code}
> For example, NAMENODE will fail with the following errors:
> {code}
> 2014-12-19 21:45:56,101 WARN server.AuthenticationFilter
> (AuthenticationFilter.java:doFilter(551)) - Authentication exception:
> GSSException: Failure unspecified at GSS-API level (Mechanism level: Invalid
> argument (400) - Cannot find key of appropriate type to decrypt AP REP -
> AES256 CTS mode with HMAC SHA1-96)
> org.apache.hadoop.security.authentication.client.AuthenticationException:
> GSSException: Failure unspecified at GSS-API level (Mechanism level: Invalid
> argument (400) - Cannot find key of appropriate type to decrypt AP REP -
> AES256 CTS mode with HMAC SHA1-96)
> at
> org.apache.hadoop.security.authentication.server.KerberosAuthenticationHandler.authenticate(KerberosAuthenticationHandler.java:399)
> at
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:507)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at
> org.apache.hadoop.http.HttpServer2$QuotingInputFilter.doFilter(HttpServer2.java:1224)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at org.apache.hadoop.http.NoCacheFilter.doFilter(NoCacheFilter.java:45)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at org.apache.hadoop.http.NoCacheFilter.doFilter(NoCacheFilter.java:45)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)
> at
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> at
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
> at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
> at
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
> at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
> at org.mortbay.jetty.Server.handle(Server.java:326)
> at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
> at
> org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
> at
> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
> at
> org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
> Caused by: GSSException: Failure unspecified at GSS-API level (Mechanism
> level: Invalid argument (400) - Cannot find key of appropriate type to
> decrypt AP REP - AES256 CTS mode with HMAC SHA1-96)
> at
> sun.security.jgss.krb5.Krb5Context.acceptS
[jira] [Updated] (AMBARI-18974) A number of Ambari Server Unit Test failures on branch-2.5
[ https://issues.apache.org/jira/browse/AMBARI-18974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-18974: Status: Patch Available (was: Open) > A number of Ambari Server Unit Test failures on branch-2.5 > -- > > Key: AMBARI-18974 > URL: https://issues.apache.org/jira/browse/AMBARI-18974 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko > Attachments: AMBARI-18974.patch > > > See https://builds.apache.org/job/Ambari-branch-2.5/374/#showFailuresLink > There are about 10 failures. > One of which (validatePropertySchemaOfServiceXMLs) seems like a dup of > BUG-69341: > org.apache.ambari.server.state.cluster.ClusterDeadlockTest.testDeadlockWhileRestartingComponents > org.apache.ambari.server.controller.internal.StackDefinedPropertyProviderTest.testStackDefinedPropertyProviderAsClusterAdministrator > org.apache.ambari.server.controller.internal.StackDefinedPropertyProviderTest.testStackDefinedPropertyProviderAsAdministrator > org.apache.ambari.server.controller.internal.StackDefinedPropertyProviderTest.testStackDefinedPropertyProviderAsServiceAdministrator > org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testRestMetricsPropertyProviderAsViewUser > org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testRestMetricsPropertyProviderAsClusterAdministrator > org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testRestMetricsPropertyProviderAsAdministrator > org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testRestMetricsPropertyProviderAsServiceAdministrator > org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testResolvePort > org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18974) A number of Ambari Server Unit Test failures on branch-2.5
[ https://issues.apache.org/jira/browse/AMBARI-18974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-18974: Attachment: AMBARI-18974.patch > A number of Ambari Server Unit Test failures on branch-2.5 > -- > > Key: AMBARI-18974 > URL: https://issues.apache.org/jira/browse/AMBARI-18974 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko > Attachments: AMBARI-18974.patch > > > See https://builds.apache.org/job/Ambari-branch-2.5/374/#showFailuresLink > There are about 10 failures. > One of which (validatePropertySchemaOfServiceXMLs) seems like a dup of > BUG-69341: > org.apache.ambari.server.state.cluster.ClusterDeadlockTest.testDeadlockWhileRestartingComponents > org.apache.ambari.server.controller.internal.StackDefinedPropertyProviderTest.testStackDefinedPropertyProviderAsClusterAdministrator > org.apache.ambari.server.controller.internal.StackDefinedPropertyProviderTest.testStackDefinedPropertyProviderAsAdministrator > org.apache.ambari.server.controller.internal.StackDefinedPropertyProviderTest.testStackDefinedPropertyProviderAsServiceAdministrator > org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testRestMetricsPropertyProviderAsViewUser > org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testRestMetricsPropertyProviderAsClusterAdministrator > org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testRestMetricsPropertyProviderAsAdministrator > org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testRestMetricsPropertyProviderAsServiceAdministrator > org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testResolvePort > org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18974) A number of Ambari Server Unit Test failures on branch-2.5
[ https://issues.apache.org/jira/browse/AMBARI-18974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-18974: Component/s: ambari-server > A number of Ambari Server Unit Test failures on branch-2.5 > -- > > Key: AMBARI-18974 > URL: https://issues.apache.org/jira/browse/AMBARI-18974 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko > Attachments: AMBARI-18974.patch > > > See https://builds.apache.org/job/Ambari-branch-2.5/374/#showFailuresLink > There are about 10 failures. > One of which (validatePropertySchemaOfServiceXMLs) seems like a dup of > BUG-69341: > org.apache.ambari.server.state.cluster.ClusterDeadlockTest.testDeadlockWhileRestartingComponents > org.apache.ambari.server.controller.internal.StackDefinedPropertyProviderTest.testStackDefinedPropertyProviderAsClusterAdministrator > org.apache.ambari.server.controller.internal.StackDefinedPropertyProviderTest.testStackDefinedPropertyProviderAsAdministrator > org.apache.ambari.server.controller.internal.StackDefinedPropertyProviderTest.testStackDefinedPropertyProviderAsServiceAdministrator > org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testRestMetricsPropertyProviderAsViewUser > org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testRestMetricsPropertyProviderAsClusterAdministrator > org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testRestMetricsPropertyProviderAsAdministrator > org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testRestMetricsPropertyProviderAsServiceAdministrator > org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testResolvePort > org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18974) A number of Ambari Server Unit Test failures on branch-2.5
Dmitry Lysnichenko created AMBARI-18974: --- Summary: A number of Ambari Server Unit Test failures on branch-2.5 Key: AMBARI-18974 URL: https://issues.apache.org/jira/browse/AMBARI-18974 Project: Ambari Issue Type: Bug Reporter: Dmitry Lysnichenko Assignee: Dmitry Lysnichenko Attachments: AMBARI-18974.patch See https://builds.apache.org/job/Ambari-branch-2.5/374/#showFailuresLink There are about 10 failures. One of which (validatePropertySchemaOfServiceXMLs) seems like a dup of BUG-69341: org.apache.ambari.server.state.cluster.ClusterDeadlockTest.testDeadlockWhileRestartingComponents org.apache.ambari.server.controller.internal.StackDefinedPropertyProviderTest.testStackDefinedPropertyProviderAsClusterAdministrator org.apache.ambari.server.controller.internal.StackDefinedPropertyProviderTest.testStackDefinedPropertyProviderAsAdministrator org.apache.ambari.server.controller.internal.StackDefinedPropertyProviderTest.testStackDefinedPropertyProviderAsServiceAdministrator org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testRestMetricsPropertyProviderAsViewUser org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testRestMetricsPropertyProviderAsClusterAdministrator org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testRestMetricsPropertyProviderAsAdministrator org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testRestMetricsPropertyProviderAsServiceAdministrator org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testResolvePort org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-8840) Keytabs need to be created to include the encryption type of AES256 CTS mode with HMAC SHA1-96
[
https://issues.apache.org/jira/browse/AMBARI-8840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690227#comment-15690227
]
Robert Levas edited comment on AMBARI-8840 at 11/23/16 2:24 PM:
[~forestsissi],
In Ambari 1.7, the keytab files were created manually. So it is possible they
were never created with an AES256 keytab entry. After Ambari 2.0, Ambari will
create the keytab files (if configured to do so) and will include the AES256
keytabs entry if:
* the correct unlimited key JCE policy is installed
* the configured encryption types do not exclude it - by default it is not
excluded
Possibly check out https://community.hortonworks.com for help with this issue.
was (Author: rlevas):
[~forestsissi],
In Ambari 1.7, the keytab files were created manually. So it is possible they
were never created with an AES256 keytab entry. After Ambari 2.0, Ambari will
create the keytab files (if configured to do so) and will include the AES256
keytabs entry if:
* the correct unlimited key JCE policy is installed
* the configured encryption types do not exclude it - by default it is not
excluded
> Keytabs need to be created to include the encryption type of AES256 CTS mode
> with HMAC SHA1-96
> --
>
> Key: AMBARI-8840
> URL: https://issues.apache.org/jira/browse/AMBARI-8840
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.0.0, 2.1.0
> Environment: Red Hat Enterprise Linux Server release 6.6 (Santiago)
> [root@hdtest253 etc]# java -version
> java version "1.7.0_79"
> OpenJDK Runtime Environment (rhel-2.5.5.3.el6_6-x86_64 u79-b14)
> OpenJDK 64-Bit Server VM (build 24.79-b02, mixed mode)
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: kerberos, keytabs
> Fix For: 2.1.0
>
> Attachments: hadoop-hdfs-journalnode-hdtest253.svl.ibm.com.log
>
>
> During automated keytab generation, an entry with the following encryption
> type must be added else certain services will fail to start up or properly
> when Kerberos is enabled:
> {code}AES256 CTS mode with HMAC SHA1-96{code}
> For example, NAMENODE will fail with the following errors:
> {code}
> 2014-12-19 21:45:56,101 WARN server.AuthenticationFilter
> (AuthenticationFilter.java:doFilter(551)) - Authentication exception:
> GSSException: Failure unspecified at GSS-API level (Mechanism level: Invalid
> argument (400) - Cannot find key of appropriate type to decrypt AP REP -
> AES256 CTS mode with HMAC SHA1-96)
> org.apache.hadoop.security.authentication.client.AuthenticationException:
> GSSException: Failure unspecified at GSS-API level (Mechanism level: Invalid
> argument (400) - Cannot find key of appropriate type to decrypt AP REP -
> AES256 CTS mode with HMAC SHA1-96)
> at
> org.apache.hadoop.security.authentication.server.KerberosAuthenticationHandler.authenticate(KerberosAuthenticationHandler.java:399)
> at
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:507)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at
> org.apache.hadoop.http.HttpServer2$QuotingInputFilter.doFilter(HttpServer2.java:1224)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at org.apache.hadoop.http.NoCacheFilter.doFilter(NoCacheFilter.java:45)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at org.apache.hadoop.http.NoCacheFilter.doFilter(NoCacheFilter.java:45)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)
> at
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> at
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
> at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
> at
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
> at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
> at org.mortbay.jetty.Server.handle(Server.java:326)
> at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
> at
> org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
> at org.mortbay.jetty.H
[jira] [Comment Edited] (AMBARI-8840) Keytabs need to be created to include the encryption type of AES256 CTS mode with HMAC SHA1-96
[
https://issues.apache.org/jira/browse/AMBARI-8840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690227#comment-15690227
]
Robert Levas edited comment on AMBARI-8840 at 11/23/16 2:26 PM:
[~forestsissi],
In Ambari 1.7, the keytab files were created manually. So it is possible they
were never created with an AES256 keytab entry. After Ambari 2.0, Ambari will
create the keytab files (if configured to do so) and will include the AES256
keytabs entry if:
* the correct unlimited key JCE policy is installed
* the configured encryption types do not exclude it - by default it is not
excluded
Possibly check out https://community.hortonworks.com for help with this issue.
UPDATE: I see you found
https://community.hortonworks.com/articles/49542/getting-the-error-cannot-find-key-of-appropriate-t.html.
was (Author: rlevas):
[~forestsissi],
In Ambari 1.7, the keytab files were created manually. So it is possible they
were never created with an AES256 keytab entry. After Ambari 2.0, Ambari will
create the keytab files (if configured to do so) and will include the AES256
keytabs entry if:
* the correct unlimited key JCE policy is installed
* the configured encryption types do not exclude it - by default it is not
excluded
Possibly check out https://community.hortonworks.com for help with this issue.
> Keytabs need to be created to include the encryption type of AES256 CTS mode
> with HMAC SHA1-96
> --
>
> Key: AMBARI-8840
> URL: https://issues.apache.org/jira/browse/AMBARI-8840
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.0.0, 2.1.0
> Environment: Red Hat Enterprise Linux Server release 6.6 (Santiago)
> [root@hdtest253 etc]# java -version
> java version "1.7.0_79"
> OpenJDK Runtime Environment (rhel-2.5.5.3.el6_6-x86_64 u79-b14)
> OpenJDK 64-Bit Server VM (build 24.79-b02, mixed mode)
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: kerberos, keytabs
> Fix For: 2.1.0
>
> Attachments: hadoop-hdfs-journalnode-hdtest253.svl.ibm.com.log
>
>
> During automated keytab generation, an entry with the following encryption
> type must be added else certain services will fail to start up or properly
> when Kerberos is enabled:
> {code}AES256 CTS mode with HMAC SHA1-96{code}
> For example, NAMENODE will fail with the following errors:
> {code}
> 2014-12-19 21:45:56,101 WARN server.AuthenticationFilter
> (AuthenticationFilter.java:doFilter(551)) - Authentication exception:
> GSSException: Failure unspecified at GSS-API level (Mechanism level: Invalid
> argument (400) - Cannot find key of appropriate type to decrypt AP REP -
> AES256 CTS mode with HMAC SHA1-96)
> org.apache.hadoop.security.authentication.client.AuthenticationException:
> GSSException: Failure unspecified at GSS-API level (Mechanism level: Invalid
> argument (400) - Cannot find key of appropriate type to decrypt AP REP -
> AES256 CTS mode with HMAC SHA1-96)
> at
> org.apache.hadoop.security.authentication.server.KerberosAuthenticationHandler.authenticate(KerberosAuthenticationHandler.java:399)
> at
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:507)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at
> org.apache.hadoop.http.HttpServer2$QuotingInputFilter.doFilter(HttpServer2.java:1224)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at org.apache.hadoop.http.NoCacheFilter.doFilter(NoCacheFilter.java:45)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at org.apache.hadoop.http.NoCacheFilter.doFilter(NoCacheFilter.java:45)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)
> at
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> at
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
> at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
> at
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
> at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
> at org.mortbay.jetty.Server.handle(Server.java:326)
> at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.j
[jira] [Commented] (AMBARI-18973) Service Auto Start: discard popup appears even when no changes were made
[ https://issues.apache.org/jira/browse/AMBARI-18973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690246#comment-15690246 ] Hudson commented on AMBARI-18973: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6073 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6073/]) AMBARI-18973 Service Auto Start: discard popup appears even when no (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=29db2273e77b8fd4f36c15a2001495a08099250a]) * (add) ambari-web/test/controllers/main/admin/service_auto_start_test.js * (edit) ambari-web/app/assets/test/tests.js * (edit) ambari-web/app/controllers/main/admin/service_auto_start.js * (edit) ambari-web/app/templates/main/admin/service_auto_start.hbs * (add) ambari-web/test/views/main/admin/service_auto_start_test.js * (add) ambari-web/test/views/main/admin/service_auto_start/component_auto_start_test.js * (edit) ambari-web/app/templates/main/admin/service_auto_start/component_auto_start.hbs * (edit) ambari-web/app/views/main/admin/service_auto_start.js * (edit) ambari-web/app/views/main/admin/service_auto_start/component_auto_start.js > Service Auto Start: discard popup appears even when no changes were made > > > Key: AMBARI-18973 > URL: https://issues.apache.org/jira/browse/AMBARI-18973 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-18973.patch > > > Discard popup appears even when no changes were made. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18836) Remove group readable from hdfs headless keytab
[ https://issues.apache.org/jira/browse/AMBARI-18836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690250#comment-15690250 ] Robert Levas commented on AMBARI-18836: --- [~adoroszlai], Lets revert this patch and have [~Wancy], apply your fix to the existing patch.. then I will commit it. > Remove group readable from hdfs headless keytab > --- > > Key: AMBARI-18836 > URL: https://issues.apache.org/jira/browse/AMBARI-18836 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: Shi Wang >Assignee: Shi Wang > Fix For: trunk > > Attachments: > 0001-AMBARI-18836-Remove-group-readable-from-hdfs-headles.patch, > AMBARI-18836-test_failure.patch > > > The Smoke and “Headless” Service users are used by Ambari to perform service > “smoke” checks and run alert health checks. > The permission for hdfs.headless.keytab is 440. But it will cause security > concern to allow other service user in hadoop group to kinit hdfs headless > principal using hdfs.headless.keytab. In this way, other service user could > "pretend" to be hdfs user and be granted hdfs user's authorities. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18974) A number of Ambari Server Unit Test failures on branch-2.5
[ https://issues.apache.org/jira/browse/AMBARI-18974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-18974: Fix Version/s: 2.5.0 > A number of Ambari Server Unit Test failures on branch-2.5 > -- > > Key: AMBARI-18974 > URL: https://issues.apache.org/jira/browse/AMBARI-18974 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko > Fix For: 2.5.0 > > Attachments: AMBARI-18974.patch > > > See https://builds.apache.org/job/Ambari-branch-2.5/374/#showFailuresLink > There are about 10 failures. > One of which (validatePropertySchemaOfServiceXMLs) seems like a dup of > BUG-69341: > org.apache.ambari.server.state.cluster.ClusterDeadlockTest.testDeadlockWhileRestartingComponents > org.apache.ambari.server.controller.internal.StackDefinedPropertyProviderTest.testStackDefinedPropertyProviderAsClusterAdministrator > org.apache.ambari.server.controller.internal.StackDefinedPropertyProviderTest.testStackDefinedPropertyProviderAsAdministrator > org.apache.ambari.server.controller.internal.StackDefinedPropertyProviderTest.testStackDefinedPropertyProviderAsServiceAdministrator > org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testRestMetricsPropertyProviderAsViewUser > org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testRestMetricsPropertyProviderAsClusterAdministrator > org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testRestMetricsPropertyProviderAsAdministrator > org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testRestMetricsPropertyProviderAsServiceAdministrator > org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testResolvePort > org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18836) Remove group readable from hdfs headless keytab
[
https://issues.apache.org/jira/browse/AMBARI-18836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690258#comment-15690258
]
Robert Levas commented on AMBARI-18836:
---
[~Wancy]
Reverted 38076327525986b780942f33eff01d2de4a70ce2 on trunk:
{noformat}
commit 4551c9f9cbc3e1723a331b038dfee954098f3b44
Author: Robert Levas
Date: Wed Nov 23 09:32:37 2016 -0500
{noformat}
CC: [~adoroszlai]
> Remove group readable from hdfs headless keytab
> ---
>
> Key: AMBARI-18836
> URL: https://issues.apache.org/jira/browse/AMBARI-18836
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Shi Wang
>Assignee: Shi Wang
> Fix For: trunk
>
> Attachments:
> 0001-AMBARI-18836-Remove-group-readable-from-hdfs-headles.patch,
> AMBARI-18836-test_failure.patch
>
>
> The Smoke and “Headless” Service users are used by Ambari to perform service
> “smoke” checks and run alert health checks.
> The permission for hdfs.headless.keytab is 440. But it will cause security
> concern to allow other service user in hadoop group to kinit hdfs headless
> principal using hdfs.headless.keytab. In this way, other service user could
> "pretend" to be hdfs user and be granted hdfs user's authorities.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18974) A number of Ambari Server Unit Test failures on branch-2.5
[ https://issues.apache.org/jira/browse/AMBARI-18974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-18974: Affects Version/s: 2.5.0 > A number of Ambari Server Unit Test failures on branch-2.5 > -- > > Key: AMBARI-18974 > URL: https://issues.apache.org/jira/browse/AMBARI-18974 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko > Fix For: 2.5.0 > > Attachments: AMBARI-18974.patch > > > See https://builds.apache.org/job/Ambari-branch-2.5/374/#showFailuresLink > There are about 10 failures. > One of which (validatePropertySchemaOfServiceXMLs) seems like a dup of > BUG-69341: > org.apache.ambari.server.state.cluster.ClusterDeadlockTest.testDeadlockWhileRestartingComponents > org.apache.ambari.server.controller.internal.StackDefinedPropertyProviderTest.testStackDefinedPropertyProviderAsClusterAdministrator > org.apache.ambari.server.controller.internal.StackDefinedPropertyProviderTest.testStackDefinedPropertyProviderAsAdministrator > org.apache.ambari.server.controller.internal.StackDefinedPropertyProviderTest.testStackDefinedPropertyProviderAsServiceAdministrator > org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testRestMetricsPropertyProviderAsViewUser > org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testRestMetricsPropertyProviderAsClusterAdministrator > org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testRestMetricsPropertyProviderAsAdministrator > org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testRestMetricsPropertyProviderAsServiceAdministrator > org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testResolvePort > org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17847) ambari-agent register failed with HostNotFoundException: Host not found, hostname=
[
https://issues.apache.org/jira/browse/AMBARI-17847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-17847:
-
Description:
At the 'Confirm Hosts' step , ambari-agent install successed but register
failed.
20 Jul 2016 17:24:47,710 INFO [Thread-130] BSRunner:220 - Host=
gmjk-bdc-b21,gmjk-bdc-b22,gmjk-bdc-b12,gmjk-bdc-b13,gmjk-bdc-b14,gmjk-bdc-b15,gmjk-bdc-b16,gmjk-bdc-b17,gmjk-bdc-b30,gmjk-bdc-b31,gmjk-bdc-b32,gmjk-bdc-b33,gmjk-bdc-b34,gmjk-bdc-b35,gmjk-bdc-b36
bs=/usr/lib/python2.6/site-packages/ambari_server/bootstrap.py
requestDir=/var/run/ambari-server/bootstrap/4 user=root
keyfile=/var/run/ambari-server/bootstrap/4/sshKey passwordFile null
server=gmjk-bdc-b22 version=2.2.1.0 serverPort=8080 userRunAs=root
20 Jul 2016 17:24:57,710 INFO [pool-11-thread-1] BSHostStatusCollector:55 -
Request directory /var/run/ambari-server/bootstrap/4
20 Jul 2016 17:24:57,711 INFO [pool-11-thread-1] BSHostStatusCollector:62 -
HostList for polling on [gmjk-bdc-b21, gmjk-bdc-b22, gmjk-bdc-b12,
gmjk-bdc-b13, gmjk-bdc-b14, gmjk-bdc-b15, gmjk-bdc-b16, gmjk-bdc-b17,
gmjk-bdc-b30, gmjk-bdc-b31, gmjk-bdc-b32, gmjk-bdc-b33, gmjk-bdc-b34,
gmjk-bdc-b35, gmjk-bdc-b36]
20 Jul 2016 17:25:07,714 INFO [pool-11-thread-1] BSHostStatusCollector:55 -
Request directory /var/run/ambari-server/bootstrap/4
20 Jul 2016 17:25:07,714 INFO [pool-11-thread-1] BSHostStatusCollector:62 -
HostList for polling on [gmjk-bdc-b21, gmjk-bdc-b22, gmjk-bdc-b12,
gmjk-bdc-b13, gmjk-bdc-b14, gmjk-bdc-b15, gmjk-bdc-b16, gmjk-bdc-b17,
gmjk-bdc-b30, gmjk-bdc-b31, gmjk-bdc-b32, gmjk-bdc-b33, gmjk-bdc-b34,
gmjk-bdc-b35, gmjk-bdc-b36]
20 Jul 2016 17:25:10,023 INFO [Thread-130] BSRunner:264 - Bootstrap output,
log=/var/run/ambari-server/bootstrap/4/bootstrap.err
/var/run/ambari-server/bootstrap/4/bootstrap.out at gmjk-bdc-b22
20 Jul 2016 17:25:10,026 INFO [Thread-130] BSRunner:275 - Script log Mesg
INFO:root:BootStrapping hosts ['gmjk-bdc-b21',
'gmjk-bdc-b22',
'gmjk-bdc-b12',
'gmjk-bdc-b13',
'gmjk-bdc-b14',
'gmjk-bdc-b15',
'gmjk-bdc-b16',
'gmjk-bdc-b17',
'gmjk-bdc-b30',
'gmjk-bdc-b31',
'gmjk-bdc-b32',
'gmjk-bdc-b33',
'gmjk-bdc-b34',
'gmjk-bdc-b35',
'gmjk-bdc-b36'] using /usr/lib/python2.6/site-packages/ambari_server cluster
primary OS: redhat6 with user 'root' sshKey File
/var/run/ambari-server/bootstrap/4/sshKey password File null using tmp dir
/var/run/ambari-server/bootstrap/4 ambari: gmjk-bdc-b22; server_port: 8080;
ambari version: 2.2.1.0; user_run_as: root
INFO:root:Executing parallel bootstrap
ERROR:root:ERROR: Bootstrap of host gmjk-bdc-b21 fails because previous action
finished with non-zero exit code (255)
ERROR MESSAGE: tcgetattr: Invalid argument
Connection to gmjk-bdc-b21 closed.
STDOUT: tput: unknown terminal "unknown"
tput: unknown terminal "unknown"
('WARNING 2016-07-20 16:05:46,843 NetUtil.py:89 - Failed to connect to
https://gmjk-bdc-b21:8440/ca due to [Errno 111] Connection refused \nWARNING
2016-07-20 16:05:46,843 NetUtil.py:112 - Server at https://gmjk-bdc-b21:8440 is
not reachable, sleeping for 10 seconds...\nINFO 2016-07-20 16:05:56,843
NetUtil.py:60 - Connecting to https://gmjk-bdc-b21:8440/ca\nWARNING 2016-07-20
16:05:56,844 NetUtil.py:89 - Failed to connect to https://gmjk-bdc-b21:8440/ca
due to [Errno 111] Connection refused \nWARNING 2016-07-20 16:05:56,844
NetUtil.py:112 - Server at https://gmjk-bdc-b21:8440 is not reachable, sleeping
for 10
tcgetattr: Invalid argument
Connection to gmjk-bdc-b21 closed.
INFO:root:Finished parallel bootstrap
20 Jul 2016 17:25:10,027 INFO [pool-11-thread-1] BSHostStatusCollector:55 -
Request directory /var/run/ambari-server/bootstrap/4
20 Jul 2016 17:25:10,027 INFO [pool-11-thread-1] BSHostStatusCollector:62 -
HostList for polling on [gmjk-bdc-b21, gmjk-bdc-b22, gmjk-bdc-b12,
gmjk-bdc-b13, gmjk-bdc-b14, gmjk-bdc-b15, gmjk-bdc-b16, gmjk-bdc-b17,
gmjk-bdc-b30, gmjk-bdc-b31, gmjk-bdc-b32, gmjk-bdc-b33, gmjk-bdc-b34,
gmjk-bdc-b35, gmjk-bdc-b36]
20 Jul 2016 17:27:18,328 ERROR [qtp-ambari-client-170]
AbstractResourceProvider:280 - Caught AmbariException when creating a resource
org.apache.ambari.server.HostNotFoundException: Host not found, hostname=
at
org.apache.ambari.server.state.cluster.ClustersImpl.getHost(ClustersImpl.java:370)
at
org.apache.ambari.server.state.ConfigHelper.getEffectiveDesiredTags(ConfigHelper.java:107)
at
org.apache.ambari.server.controller.AmbariManagementControllerImpl.findConfigurationTagsWithOverrides(AmbariManagementControllerImpl.java:1876)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
was:
At the 'Confirm Hosts' step , ambari-agent install successed but register
failed.
20 Jul 2016 17:24:47,710 INFO [Thread-130] BSRunner:220 - Host=
gmjk-bdc-b21,gmjk-bdc-b22,gmjk-bdc-b1
[jira] [Commented] (AMBARI-18929) Yarn service check fails when either resource manager is down in HA enabled cluster
[ https://issues.apache.org/jira/browse/AMBARI-18929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690265#comment-15690265 ] Weiwei Yang commented on AMBARI-18929: -- Thanks [~dili], I'll try to submit a patch. > Yarn service check fails when either resource manager is down in HA enabled > cluster > --- > > Key: AMBARI-18929 > URL: https://issues.apache.org/jira/browse/AMBARI-18929 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Weiwei Yang > > When HA is enabled, yarn service_check.py fails if one of RM is down, even > the other one is active. This gives user the wrong impression the yarn > cluster is not healthy. Instead, service check should pass, or at least pass > with warning that lets user know there is one RM down. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18972) Remove redundant css (part 4)
[
https://issues.apache.org/jira/browse/AMBARI-18972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690274#comment-15690274
]
Oleg Nechiporenko commented on AMBARI-18972:
Build failed not because of this patch
{noformat}
[INFO] Ambari Web . SUCCESS [02:35 min]
[INFO] Ambari Server .. FAILURE [14:51 min]
{noformat}
> Remove redundant css (part 4)
> -
>
> Key: AMBARI-18972
> URL: https://issues.apache.org/jira/browse/AMBARI-18972
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
>
> * Fix racks markup
> * Fix assign masters markup
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18972) Remove redundant css (part 4)
[ https://issues.apache.org/jira/browse/AMBARI-18972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-18972: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Remove redundant css (part 4) > - > > Key: AMBARI-18972 > URL: https://issues.apache.org/jira/browse/AMBARI-18972 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > > * Fix racks markup > * Fix assign masters markup -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18836) Remove group readable from hdfs headless keytab
[ https://issues.apache.org/jira/browse/AMBARI-18836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690328#comment-15690328 ] Hudson commented on AMBARI-18836: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6074 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6074/]) Revert "AMBARI-18836. Remove group readable from hdfs headless keytab (rlevas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4551c9f9cbc3e1723a331b038dfee954098f3b44]) * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/kerberos.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/HDFS/kerberos.json * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/webhcat.py > Remove group readable from hdfs headless keytab > --- > > Key: AMBARI-18836 > URL: https://issues.apache.org/jira/browse/AMBARI-18836 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: Shi Wang >Assignee: Shi Wang > Fix For: trunk > > Attachments: > 0001-AMBARI-18836-Remove-group-readable-from-hdfs-headles.patch, > AMBARI-18836-test_failure.patch > > > The Smoke and “Headless” Service users are used by Ambari to perform service > “smoke” checks and run alert health checks. > The permission for hdfs.headless.keytab is 440. But it will cause security > concern to allow other service user in hadoop group to kinit hdfs headless > principal using hdfs.headless.keytab. In this way, other service user could > "pretend" to be hdfs user and be granted hdfs user's authorities. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18947) Infinite spinner displayed instead of some Flume Agent graphs
[ https://issues.apache.org/jira/browse/AMBARI-18947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-18947: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.5 > Infinite spinner displayed instead of some Flume Agent graphs > - > > Key: AMBARI-18947 > URL: https://issues.apache.org/jira/browse/AMBARI-18947 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18947.patch > > > ChannelSize, EventPutSuccessCount and EventTakeSuccessCount graphs aren't > displayed. > At the same time, JS error is thrown after selecting a host from the table: > Uncaught TypeError: Cannot read property '1' of undefined at app.js:178829. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18381) Kafka alerts fail if more than one listener is configured
[
https://issues.apache.org/jira/browse/AMBARI-18381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690365#comment-15690365
]
kevin.chen commented on AMBARI-18381:
-
can I work on this issue?
> Kafka alerts fail if more than one listener is configured
> -
>
> Key: AMBARI-18381
> URL: https://issues.apache.org/jira/browse/AMBARI-18381
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Carson Gaspar
>Priority: Minor
>
> If more than one kafka listener is configured (e.g.
> PLAINTEXTSASL://localhost:6667, PLAINTEXT://127.0.0.1:6668), the alert
> definition configures a PORT test with the whole string, which appears to get
> parsed with the first hostname and the last port. This causes the test to
> fail. If there's a way to modify {{kafka-broker/listeners}} so that it splits
> on the first comma, or some other workaround, I can't figure it out.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18975) Remove Zeppelin View from Ambari
Renjith Kamath created AMBARI-18975: --- Summary: Remove Zeppelin View from Ambari Key: AMBARI-18975 URL: https://issues.apache.org/jira/browse/AMBARI-18975 Project: Ambari Issue Type: Improvement Reporter: Renjith Kamath Assignee: Renjith Kamath Fix For: 2.5.0 Currently Zeppelin view is an iframe loading Zeppelin UI. There are no advantages of loading the UI of a service in an iframe and also limits the ux of Zeppelin due to fixed iframe width in Ambari. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18975) Remove Zeppelin View from Ambari
[ https://issues.apache.org/jira/browse/AMBARI-18975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Renjith Kamath updated AMBARI-18975: Status: Patch Available (was: Open) > Remove Zeppelin View from Ambari > > > Key: AMBARI-18975 > URL: https://issues.apache.org/jira/browse/AMBARI-18975 > Project: Ambari > Issue Type: Improvement >Reporter: Renjith Kamath >Assignee: Renjith Kamath > Fix For: 2.5.0 > > Attachments: AMBARI-18975-branch-2.5-v1.patch > > > Currently Zeppelin view is an iframe loading Zeppelin UI. There are no > advantages of loading the UI of a service in an iframe and also limits the ux > of Zeppelin due to fixed iframe width in Ambari. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18975) Remove Zeppelin View from Ambari
[ https://issues.apache.org/jira/browse/AMBARI-18975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Renjith Kamath updated AMBARI-18975: Attachment: AMBARI-18975-branch-2.5-v1.patch > Remove Zeppelin View from Ambari > > > Key: AMBARI-18975 > URL: https://issues.apache.org/jira/browse/AMBARI-18975 > Project: Ambari > Issue Type: Improvement >Reporter: Renjith Kamath >Assignee: Renjith Kamath > Fix For: 2.5.0 > > Attachments: AMBARI-18975-branch-2.5-v1.patch > > > Currently Zeppelin view is an iframe loading Zeppelin UI. There are no > advantages of loading the UI of a service in an iframe and also limits the ux > of Zeppelin due to fixed iframe width in Ambari. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18974) A number of Ambari Server Unit Test failures on branch-2.5
[
https://issues.apache.org/jira/browse/AMBARI-18974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690429#comment-15690429
]
Hadoop QA commented on AMBARI-18974:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12840251/AMBARI-18974.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.state.ServicePropertiesTest
org.apache.ambari.server.controller.internal.UpgradeResourceProviderTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9379//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9379//console
This message is automatically generated.
> A number of Ambari Server Unit Test failures on branch-2.5
> --
>
> Key: AMBARI-18974
> URL: https://issues.apache.org/jira/browse/AMBARI-18974
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.5.0
>
> Attachments: AMBARI-18974.patch
>
>
> See https://builds.apache.org/job/Ambari-branch-2.5/374/#showFailuresLink
> There are about 10 failures.
> One of which (validatePropertySchemaOfServiceXMLs) seems like a dup of
> BUG-69341:
> org.apache.ambari.server.state.cluster.ClusterDeadlockTest.testDeadlockWhileRestartingComponents
> org.apache.ambari.server.controller.internal.StackDefinedPropertyProviderTest.testStackDefinedPropertyProviderAsClusterAdministrator
> org.apache.ambari.server.controller.internal.StackDefinedPropertyProviderTest.testStackDefinedPropertyProviderAsAdministrator
> org.apache.ambari.server.controller.internal.StackDefinedPropertyProviderTest.testStackDefinedPropertyProviderAsServiceAdministrator
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testRestMetricsPropertyProviderAsViewUser
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testRestMetricsPropertyProviderAsClusterAdministrator
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testRestMetricsPropertyProviderAsAdministrator
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testRestMetricsPropertyProviderAsServiceAdministrator
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testResolvePort
> org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18966) Add check to ensure we do not have @Transactional annotations on private methods
[
https://issues.apache.org/jira/browse/AMBARI-18966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-18966:
---
Attachment: (was: AMBARI-18966.patch)
> Add check to ensure we do not have @Transactional annotations on private
> methods
>
>
> Key: AMBARI-18966
> URL: https://issues.apache.org/jira/browse/AMBARI-18966
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18966.patch
>
>
> {{@Transactional}} methods [must not be
> {{private}}|https://github.com/google/guice/wiki/Transactions#method-level-transactional].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18947) Infinite spinner displayed instead of some Flume Agent graphs
[ https://issues.apache.org/jira/browse/AMBARI-18947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690492#comment-15690492 ] Hudson commented on AMBARI-18947: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #381 (See [https://builds.apache.org/job/Ambari-branch-2.5/381/]) AMBARI-18947 Infinite spinner displayed instead of some Flume Agent (dsen: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=213804975156220d0daa2b1b0d34f45e061894de]) * (edit) ambari-server/src/main/resources/common-services/FLUME/1.4.0.2.0/metrics.json > Infinite spinner displayed instead of some Flume Agent graphs > - > > Key: AMBARI-18947 > URL: https://issues.apache.org/jira/browse/AMBARI-18947 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18947.patch > > > ChannelSize, EventPutSuccessCount and EventTakeSuccessCount graphs aren't > displayed. > At the same time, JS error is thrown after selecting a host from the table: > Uncaught TypeError: Cannot read property '1' of undefined at app.js:178829. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18966) Add check to ensure we do not have @Transactional annotations on private methods
[
https://issues.apache.org/jira/browse/AMBARI-18966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-18966:
---
Attachment: AMBARI-18966.patch
* Added unit test for {{AvoidTransactionalOnPrivateMethodsCheck}}
* Added ability to skip Checkstyle run by setting {{-Dcheckstyle.skip}}
(similar to {{-Drat.skip}})
* Moved plugin config to parent POM ({{ambari-project/pom.xml}}) to avoid
duplication
> Add check to ensure we do not have @Transactional annotations on private
> methods
>
>
> Key: AMBARI-18966
> URL: https://issues.apache.org/jira/browse/AMBARI-18966
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18966.patch, AMBARI-18966.patch
>
>
> {{@Transactional}} methods [must not be
> {{private}}|https://github.com/google/guice/wiki/Transactions#method-level-transactional].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18929) Yarn service check fails when either resource manager is down in HA enabled cluster
[ https://issues.apache.org/jira/browse/AMBARI-18929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690568#comment-15690568 ] Tim Thorpe commented on AMBARI-18929: - Assuming the python issues are fixed with HDFS and YARN, the status of the service should be properly reported at least since 2.4 https://issues.apache.org/jira/browse/AMBARI-14496 > Yarn service check fails when either resource manager is down in HA enabled > cluster > --- > > Key: AMBARI-18929 > URL: https://issues.apache.org/jira/browse/AMBARI-18929 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Weiwei Yang > > When HA is enabled, yarn service_check.py fails if one of RM is down, even > the other one is active. This gives user the wrong impression the yarn > cluster is not healthy. Instead, service check should pass, or at least pass > with warning that lets user know there is one RM down. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18947) Infinite spinner displayed instead of some Flume Agent graphs
[ https://issues.apache.org/jira/browse/AMBARI-18947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690614#comment-15690614 ] Dmytro Sen commented on AMBARI-18947: - Failed tests aren't related to this jira > Infinite spinner displayed instead of some Flume Agent graphs > - > > Key: AMBARI-18947 > URL: https://issues.apache.org/jira/browse/AMBARI-18947 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18947.patch > > > ChannelSize, EventPutSuccessCount and EventTakeSuccessCount graphs aren't > displayed. > At the same time, JS error is thrown after selecting a host from the table: > Uncaught TypeError: Cannot read property '1' of undefined at app.js:178829. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-18713) use exclude list of mount device types on docker containers
[ https://issues.apache.org/jira/browse/AMBARI-18713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen reassigned AMBARI-18713: --- Assignee: Dmytro Sen (was: Andrew Onischuk) > use exclude list of mount device types on docker containers > --- > > Key: AMBARI-18713 > URL: https://issues.apache.org/jira/browse/AMBARI-18713 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Dmytro Grinenko >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18713-2.5.patch, AMBARI-18713.patch, > AMBARI-18713.patch.1 > > > * Remove logic from UI that picks a single host to represent the entire > cluster > * Have each host report their mount devices and how much space is available > in each one, so Ambari can store this in the DB (this will affect new > installs only or newly registered hosts) > * Move logic to Stack Advisor > * Use exclude list -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-18713) use exclude list of mount device types on docker containers
[ https://issues.apache.org/jira/browse/AMBARI-18713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen reopened AMBARI-18713: - > use exclude list of mount device types on docker containers > --- > > Key: AMBARI-18713 > URL: https://issues.apache.org/jira/browse/AMBARI-18713 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Dmytro Grinenko >Assignee: Andrew Onischuk >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18713-2.5.patch, AMBARI-18713.patch, > AMBARI-18713.patch.1 > > > * Remove logic from UI that picks a single host to represent the entire > cluster > * Have each host report their mount devices and how much space is available > in each one, so Ambari can store this in the DB (this will affect new > installs only or newly registered hosts) > * Move logic to Stack Advisor > * Use exclude list -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-18959) Remove outdated properties and and add fsType exclusions to StackAdviser recommendations
[ https://issues.apache.org/jira/browse/AMBARI-18959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko resolved AMBARI-18959. -- Resolution: Duplicate > Remove outdated properties and and add fsType exclusions to StackAdviser > recommendations > > > Key: AMBARI-18959 > URL: https://issues.apache.org/jira/browse/AMBARI-18959 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Dmytro Grinenko >Priority: Blocker > Fix For: trunk, 2.5.0 > > > Properties to be removed: fs.checkpoint.dir, dfs.name.dir, dfs.data.dir > fsType to be added to exclude list: devtmpfs, tmpfs, vboxsf, CDFS > Mount point to be ignored: /etc/resolv.conf, /etc/hostname, /etc/hosts, > /boot, /mnt, tmp -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18713) use exclude list of mount device types on docker containers
[ https://issues.apache.org/jira/browse/AMBARI-18713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690679#comment-15690679 ] Dmytro Sen commented on AMBARI-18713: - Reverted from trunk and branch-2.5 > use exclude list of mount device types on docker containers > --- > > Key: AMBARI-18713 > URL: https://issues.apache.org/jira/browse/AMBARI-18713 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Dmytro Grinenko >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18713-2.5.patch, AMBARI-18713.patch, > AMBARI-18713.patch.1 > > > * Remove logic from UI that picks a single host to represent the entire > cluster > * Have each host report their mount devices and how much space is available > in each one, so Ambari can store this in the DB (this will affect new > installs only or newly registered hosts) > * Move logic to Stack Advisor > * Use exclude list -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18976) Config History request execution time depends on config versions count
Myroslav Papirkovskyi created AMBARI-18976:
--
Summary: Config History request execution time depends on config
versions count
Key: AMBARI-18976
URL: https://issues.apache.org/jira/browse/AMBARI-18976
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.4.0
Reporter: Myroslav Papirkovskyi
Assignee: Myroslav Papirkovskyi
Priority: Critical
Fix For: 2.5.0
Request:
{{/api/v1/clusters/tdk/configurations/service_config_versions?fields=group_id,user&minimal_response=true&from=0&page_size=10}}
Response always contains 10 records or less (if there are less than 10 service
configs versions). Each record has only two fields ({{group_id}}, {{user}}).
Request execution time depends on overall count of service config versions in
the DB.
Example:
|| Items Total in the DB || Response Time ||
|2 |~140 ms|
|100|900+ ms|
|290|3+ s|
|750|9+ s|
|1000 |15+ s|
|3000 |30+ s|
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18713) use exclude list of mount device types on docker containers
[ https://issues.apache.org/jira/browse/AMBARI-18713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690754#comment-15690754 ] Hudson commented on AMBARI-18713: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #382 (See [https://builds.apache.org/job/Ambari-branch-2.5/382/]) Revert "AMBARI-18713 use exclude list of mount device types on docker (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a4665bb37f9b49d5f13dd19533a1ec69054d751f]) * (edit) ambari-web/test/utils/ajax/ajax_test.js * (edit) ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py * (edit) ambari-server/src/test/python/stacks/2.0.6/common/test_stack_advisor.py * (delete) ambari-server/src/test/python/stacks/test_stack_adviser.py * (add) ambari-web/app/utils/configs/mount_points_based_initializer_mixin.js * (edit) ambari-server/src/main/resources/scripts/stack_advisor.py * (edit) ambari-web/app/mixins.js * (edit) ambari-web/test/utils/configs/config_initializer_test.js * (edit) ambari-server/src/main/resources/stacks/stack_advisor.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/configuration/cluster-env.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.1/services/stack_advisor.py * (edit) ambari-server/src/test/python/stacks/2.1/common/test_stack_advisor.py * (edit) ambari-web/app/utils/configs/config_initializer.js * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py > use exclude list of mount device types on docker containers > --- > > Key: AMBARI-18713 > URL: https://issues.apache.org/jira/browse/AMBARI-18713 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Dmytro Grinenko >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18713-2.5.patch, AMBARI-18713.patch, > AMBARI-18713.patch.1 > > > * Remove logic from UI that picks a single host to represent the entire > cluster > * Have each host report their mount devices and how much space is available > in each one, so Ambari can store this in the DB (this will affect new > installs only or newly registered hosts) > * Move logic to Stack Advisor > * Use exclude list -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18977) Quick link profiles contain rules to control the visibility of quicklinks.
Balázs Bence Sári created AMBARI-18977: -- Summary: Quick link profiles contain rules to control the visibility of quicklinks. Key: AMBARI-18977 URL: https://issues.apache.org/jira/browse/AMBARI-18977 Project: Ambari Issue Type: Epic Reporter: Balázs Bence Sári Quick link profiles contain rules to control the visibility of quicklinks. Rules will be based on: - the name of the link (e.g. show namenode_ui), or - a feature of the link (e.g. is it SSO enabled?) or - general rules (e.g. show all links for HDFS) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18978) Create Quick link profile data model and json parser
Balázs Bence Sári created AMBARI-18978: -- Summary: Create Quick link profile data model and json parser Key: AMBARI-18978 URL: https://issues.apache.org/jira/browse/AMBARI-18978 Project: Ambari Issue Type: Epic Affects Versions: 2.5.0 Reporter: Balázs Bence Sári Assignee: Balázs Bence Sári Fix For: 2.5.0 Create the data model and JSON parser for quick link profiles. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18977) Quick link profiles contain rules to control the visibility of quicklinks.
[ https://issues.apache.org/jira/browse/AMBARI-18977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-18977: --- Fix Version/s: 2.5.0 > Quick link profiles contain rules to control the visibility of quicklinks. > -- > > Key: AMBARI-18977 > URL: https://issues.apache.org/jira/browse/AMBARI-18977 > Project: Ambari > Issue Type: Epic >Reporter: Balázs Bence Sári > Fix For: 2.5.0 > > > Quick link profiles contain rules to control the visibility of quicklinks. > Rules will be based on: > - the name of the link (e.g. show namenode_ui), or > - a feature of the link (e.g. is it SSO enabled?) or > - general rules (e.g. show all links for HDFS) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18978) Create Quick link profile data model and json parser
[ https://issues.apache.org/jira/browse/AMBARI-18978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-18978: --- Issue Type: Task (was: Epic) > Create Quick link profile data model and json parser > > > Key: AMBARI-18978 > URL: https://issues.apache.org/jira/browse/AMBARI-18978 > Project: Ambari > Issue Type: Task >Affects Versions: 2.5.0 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári > Fix For: 2.5.0 > > > Create the data model and JSON parser for quick link profiles. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18977) Quick link profiles to control the visibility of quicklinks.
[ https://issues.apache.org/jira/browse/AMBARI-18977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-18977: --- Summary: Quick link profiles to control the visibility of quicklinks. (was: Quick link profiles contain rules to control the visibility of quicklinks.) > Quick link profiles to control the visibility of quicklinks. > > > Key: AMBARI-18977 > URL: https://issues.apache.org/jira/browse/AMBARI-18977 > Project: Ambari > Issue Type: Epic >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári > Fix For: 2.5.0 > > > Quick link profiles contain rules to control the visibility of quicklinks. > Rules will be based on: > - the name of the link (e.g. show namenode_ui), or > - a feature of the link (e.g. is it SSO enabled?) or > - general rules (e.g. show all links for HDFS) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-18977) Quick link profiles contain rules to control the visibility of quicklinks.
[ https://issues.apache.org/jira/browse/AMBARI-18977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári reassigned AMBARI-18977: -- Assignee: Balázs Bence Sári > Quick link profiles contain rules to control the visibility of quicklinks. > -- > > Key: AMBARI-18977 > URL: https://issues.apache.org/jira/browse/AMBARI-18977 > Project: Ambari > Issue Type: Epic >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári > Fix For: 2.5.0 > > > Quick link profiles contain rules to control the visibility of quicklinks. > Rules will be based on: > - the name of the link (e.g. show namenode_ui), or > - a feature of the link (e.g. is it SSO enabled?) or > - general rules (e.g. show all links for HDFS) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18979) Optimize loading of views in cloud environments
Laszlo Puskas created AMBARI-18979: -- Summary: Optimize loading of views in cloud environments Key: AMBARI-18979 URL: https://issues.apache.org/jira/browse/AMBARI-18979 Project: Ambari Issue Type: Bug Reporter: Laszlo Puskas Assignee: Laszlo Puskas On cloud environments loading views can take a long time having the side effect of delaying the ambari-server to be available. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18979) Optimize loading of views in cloud environments
[ https://issues.apache.org/jira/browse/AMBARI-18979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laszlo Puskas updated AMBARI-18979: --- Affects Version/s: 2.4.1 Fix Version/s: 2.5.0 Component/s: ambari-server > Optimize loading of views in cloud environments > --- > > Key: AMBARI-18979 > URL: https://issues.apache.org/jira/browse/AMBARI-18979 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Laszlo Puskas >Assignee: Laszlo Puskas > Fix For: 2.5.0 > > Original Estimate: 72h > Remaining Estimate: 72h > > On cloud environments loading views can take a long time having the side > effect of delaying the ambari-server to be available. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18970) Unable to load Grafana Graphs in IE11
[ https://issues.apache.org/jira/browse/AMBARI-18970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-18970: -- Resolution: Fixed Status: Resolved (was: Patch Available) +1 received on reviewboard. Patch committed to trunk and branch-2.5 > Unable to load Grafana Graphs in IE11 > - > > Key: AMBARI-18970 > URL: https://issues.apache.org/jira/browse/AMBARI-18970 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 > Environment: Windows 8.1 > Internet Explorer 11 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-18970.v0.patch > > > Getting JS error in IE11 that prevents any graph from loading. > JS Error > +++ > Error Message:Unable to get property 'lastIndexOf' of undefined or null > reference > Stack trace: > TypeError: Unable to get property 'lastIndexOf' of undefined or null reference > at AmbariMetricsDatasource.prototype.query -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18961) Ambari HiveView does not create or upload script in UTF-8 format
[
https://issues.apache.org/jira/browse/AMBARI-18961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaimin Jetly updated AMBARI-18961:
--
Fix Version/s: 2.5.0
> Ambari HiveView does not create or upload script in UTF-8 format
>
>
> Key: AMBARI-18961
> URL: https://issues.apache.org/jira/browse/AMBARI-18961
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.4.1
> Environment: All
>Reporter: JaySenSharma
>Assignee: JaySenSharma
> Fix For: 2.5.0
>
> Attachments: AMBARI-18961.patch
>
>
> - When we run an insert query with some special character in the Hive
> (Hive-next) View then we see that the values are not being reflected
> properly. The special characters are being replaced with "?"
> Example:
> {code}
> CREATE table test (id int, name string);
> insert into test values (100, "€");
> insert into test values (200, "$");
> insert into test values (300, "£");
> insert into test values (400, "₡");
> SELECT * FROM test LIMIT 100;
> {code}
> - Once the above script is executed then we will see the output something
> like "HiveView_UTF-8_Issue.png" (attached)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18966) Add check to ensure we do not have @Transactional annotations on private methods
[
https://issues.apache.org/jira/browse/AMBARI-18966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690877#comment-15690877
]
Hadoop QA commented on AMBARI-18966:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12840268/AMBARI-18966.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in utility
ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9380//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9380//console
This message is automatically generated.
> Add check to ensure we do not have @Transactional annotations on private
> methods
>
>
> Key: AMBARI-18966
> URL: https://issues.apache.org/jira/browse/AMBARI-18966
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18966.patch
>
>
> {{@Transactional}} methods [must not be
> {{private}}|https://github.com/google/guice/wiki/Transactions#method-level-transactional].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18975) Remove Zeppelin View from Ambari
[
https://issues.apache.org/jira/browse/AMBARI-18975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690881#comment-15690881
]
Hadoop QA commented on AMBARI-18975:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12840267/AMBARI-18975-branch-2.5-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/9381//console
This message is automatically generated.
> Remove Zeppelin View from Ambari
>
>
> Key: AMBARI-18975
> URL: https://issues.apache.org/jira/browse/AMBARI-18975
> Project: Ambari
> Issue Type: Improvement
>Reporter: Renjith Kamath
>Assignee: Renjith Kamath
> Fix For: 2.5.0
>
> Attachments: AMBARI-18975-branch-2.5-v1.patch
>
>
> Currently Zeppelin view is an iframe loading Zeppelin UI. There are no
> advantages of loading the UI of a service in an iframe and also limits the ux
> of Zeppelin due to fixed iframe width in Ambari.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18970) Unable to load Grafana Graphs in IE11
[ https://issues.apache.org/jira/browse/AMBARI-18970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690898#comment-15690898 ] Hudson commented on AMBARI-18970: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #383 (See [https://builds.apache.org/job/Ambari-branch-2.5/383/]) AMBARI-18970. Unable to load Grafana Graphs in IE11. (Vivek Subramanian (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=3344786c3c9643b7bc88679221843c91456b0a2a]) * (edit) ambari-metrics/ambari-metrics-grafana/ambari-metrics/datasource.js > Unable to load Grafana Graphs in IE11 > - > > Key: AMBARI-18970 > URL: https://issues.apache.org/jira/browse/AMBARI-18970 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 > Environment: Windows 8.1 > Internet Explorer 11 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-18970.v0.patch > > > Getting JS error in IE11 that prevents any graph from loading. > JS Error > +++ > Error Message:Unable to get property 'lastIndexOf' of undefined or null > reference > Stack trace: > TypeError: Unable to get property 'lastIndexOf' of undefined or null reference > at AmbariMetricsDatasource.prototype.query -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18836) Remove group readable from hdfs headless keytab
[ https://issues.apache.org/jira/browse/AMBARI-18836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shi Wang updated AMBARI-18836: -- Attachment: (was: 0001-AMBARI-18836-Remove-group-readable-from-hdfs-headles.patch) > Remove group readable from hdfs headless keytab > --- > > Key: AMBARI-18836 > URL: https://issues.apache.org/jira/browse/AMBARI-18836 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: Shi Wang >Assignee: Shi Wang > Fix For: trunk > > Attachments: AMBARI-18836-test_failure.patch > > > The Smoke and “Headless” Service users are used by Ambari to perform service > “smoke” checks and run alert health checks. > The permission for hdfs.headless.keytab is 440. But it will cause security > concern to allow other service user in hadoop group to kinit hdfs headless > principal using hdfs.headless.keytab. In this way, other service user could > "pretend" to be hdfs user and be granted hdfs user's authorities. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18836) Remove group readable from hdfs headless keytab
[ https://issues.apache.org/jira/browse/AMBARI-18836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shi Wang updated AMBARI-18836: -- Attachment: 0001-AMBARI-18836-Remove-group-readable-from-hdfs-headles.patch > Remove group readable from hdfs headless keytab > --- > > Key: AMBARI-18836 > URL: https://issues.apache.org/jira/browse/AMBARI-18836 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: Shi Wang >Assignee: Shi Wang > Fix For: trunk > > Attachments: > 0001-AMBARI-18836-Remove-group-readable-from-hdfs-headles.patch, > AMBARI-18836-test_failure.patch > > > The Smoke and “Headless” Service users are used by Ambari to perform service > “smoke” checks and run alert health checks. > The permission for hdfs.headless.keytab is 440. But it will cause security > concern to allow other service user in hadoop group to kinit hdfs headless > principal using hdfs.headless.keytab. In this way, other service user could > "pretend" to be hdfs user and be granted hdfs user's authorities. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18836) Remove group readable from hdfs headless keytab
[ https://issues.apache.org/jira/browse/AMBARI-18836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shi Wang updated AMBARI-18836: -- Status: Patch Available (was: Reopened) > Remove group readable from hdfs headless keytab > --- > > Key: AMBARI-18836 > URL: https://issues.apache.org/jira/browse/AMBARI-18836 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: Shi Wang >Assignee: Shi Wang > Fix For: trunk > > Attachments: > 0001-AMBARI-18836-Remove-group-readable-from-hdfs-headles.patch, > AMBARI-18836-test_failure.patch > > > The Smoke and “Headless” Service users are used by Ambari to perform service > “smoke” checks and run alert health checks. > The permission for hdfs.headless.keytab is 440. But it will cause security > concern to allow other service user in hadoop group to kinit hdfs headless > principal using hdfs.headless.keytab. In this way, other service user could > "pretend" to be hdfs user and be granted hdfs user's authorities. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18842) Provide support for removing an mpack on the command line
[
https://issues.apache.org/jira/browse/AMBARI-18842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690972#comment-15690972
]
Jayush Luniya commented on AMBARI-18842:
Hadoop QA test failure is not related to this patch.
{code}
--
Failed tests:
FAIL: test_start_secured (test_webhcat_server.TestWebHCatServer)
--
Traceback (most recent call last):
File
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-common/src/test/python/mock/mock.py",
line 1199, in patched
return func(*args, **keywargs)
File
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-server/src/test/python/stacks/2.0.6/HIVE/test_webhcat_server.py",
line 134, in test_start_secured
self.assert_configure_secured()
File
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-server/src/test/python/stacks/2.0.6/HIVE/test_webhcat_server.py",
line 257, in assert_configure_secured
user = 'hcat',
File
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
line 280, in assertResourceCalled
self.assertEquals(resource_type, resource.__class__.__name__)
AssertionError: 'Execute' != 'XmlConfig'
--
{code}
> Provide support for removing an mpack on the command line
> -
>
> Key: AMBARI-18842
> URL: https://issues.apache.org/jira/browse/AMBARI-18842
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.5.0
>
> Attachments: AMBARI-18842.3.patch
>
>
> # Provide command line support to remove a management pack.
> # Removal should work for add-on service mpacks.
> # Removal command should remove all versions the mpack to be removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18842) Provide support for removing an mpack on the command line
[ https://issues.apache.org/jira/browse/AMBARI-18842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690977#comment-15690977 ] Jayush Luniya commented on AMBARI-18842: Trunk commit bd2cd4ab61798a44a670797a9348b6e818b7701b Author: Jayush Luniya Date: Wed Nov 23 10:30:00 2016 -0800 AMBARI-18842: Provide support for removing an mpack on the command line (jluniya) Branch-2.5 commit d5337a5a3baf21516471b1070edcb52e2fe254d8 Author: Jayush Luniya Date: Wed Nov 23 10:30:00 2016 -0800 AMBARI-18842: Provide support for removing an mpack on the command line (jluniya) > Provide support for removing an mpack on the command line > - > > Key: AMBARI-18842 > URL: https://issues.apache.org/jira/browse/AMBARI-18842 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: 2.5.0 > > Attachments: AMBARI-18842.3.patch > > > # Provide command line support to remove a management pack. > # Removal should work for add-on service mpacks. > # Removal command should remove all versions the mpack to be removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18842) Provide support for removing an mpack on the command line
[ https://issues.apache.org/jira/browse/AMBARI-18842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18842: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Provide support for removing an mpack on the command line > - > > Key: AMBARI-18842 > URL: https://issues.apache.org/jira/browse/AMBARI-18842 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: 2.5.0 > > Attachments: AMBARI-18842.3.patch > > > # Provide command line support to remove a management pack. > # Removal should work for add-on service mpacks. > # Removal command should remove all versions the mpack to be removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18979) Optimize loading of views in cloud environments
[ https://issues.apache.org/jira/browse/AMBARI-18979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-18979: Attachment: AMBARI-18979.patch > Optimize loading of views in cloud environments > --- > > Key: AMBARI-18979 > URL: https://issues.apache.org/jira/browse/AMBARI-18979 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Laszlo Puskas >Assignee: Laszlo Puskas > Fix For: 2.5.0 > > Attachments: AMBARI-18979.patch > > Original Estimate: 72h > Remaining Estimate: 72h > > On cloud environments loading views can take a long time having the side > effect of delaying the ambari-server to be available. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18979) Optimize loading of views in cloud environments
[ https://issues.apache.org/jira/browse/AMBARI-18979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-18979: Status: Patch Available (was: Open) > Optimize loading of views in cloud environments > --- > > Key: AMBARI-18979 > URL: https://issues.apache.org/jira/browse/AMBARI-18979 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Laszlo Puskas >Assignee: Laszlo Puskas > Fix For: 2.5.0 > > Attachments: AMBARI-18979.patch > > Original Estimate: 72h > Remaining Estimate: 72h > > On cloud environments loading views can take a long time having the side > effect of delaying the ambari-server to be available. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18968) Ambari Server Unit Test failure: org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs
[
https://issues.apache.org/jira/browse/AMBARI-18968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-18968:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to trunk, commit b59dc1dd0daff5da65622c8237cd9ecfba605734
branch-2.5, commit e36dc9c6d0f091ebe9e5f6a0fcadca3da377cea4
> Ambari Server Unit Test failure:
> org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs
> -
>
> Key: AMBARI-18968
> URL: https://issues.apache.org/jira/browse/AMBARI-18968
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
> Attachments: AMBARI-18968.patch
>
>
> {noformat}
> Error Message
> File
> /home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/target/test-classes/TestAmbaryServer.samples/../../../src/main/resources/stacks/PERF/1.0/services/YARN/configuration/yarn-site.xml
> didn't pass the validation. Error message is : cvc-complex-type.2.3: Element
> 'configuration' cannot have character [children], because the type's content
> type is element-only.
> {noformat}
> The file is malformed and has an extraneous property name outside of a
> field.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
