[jira] [Assigned] (AMBARI-22079) Upgrade Yarn version for Logsearch Web
[ https://issues.apache.org/jira/browse/AMBARI-22079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó reassigned AMBARI-22079: - Assignee: Istvan Tobias > Upgrade Yarn version for Logsearch Web > -- > > Key: AMBARI-22079 > URL: https://issues.apache.org/jira/browse/AMBARI-22079 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22088) A couple of merge fixes for branch-3.0-perf
[ https://issues.apache.org/jira/browse/AMBARI-22088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-22088: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-3.0-perf > A couple of merge fixes for branch-3.0-perf > --- > > Key: AMBARI-22088 > URL: https://issues.apache.org/jira/browse/AMBARI-22088 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0 > > Attachments: AMBARI-22088.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-13852) Can't access the stack admin interface [Error 500]
[
https://issues.apache.org/jira/browse/AMBARI-13852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16185653#comment-16185653
]
Yao Lei commented on AMBARI-13852:
--
I find one solution, it works for me but i think it is not recommended.
Comment one line code in
AmbariHandlerList#getHandler(org.apache.ambari.server.orm.entities.ViewInstanceEntity)
like following:
{code:java}
//webAppContext.addFilter(new FilterHolder(springSecurityFilter), "/*",
AmbariServer.DISPATCHER_TYPES);
{code}
> Can't access the stack admin interface [Error 500]
> --
>
> Key: AMBARI-13852
> URL: https://issues.apache.org/jira/browse/AMBARI-13852
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.1.2
>Reporter: Loïc C. Chanel
>Priority: Blocker
> Labels: ambari-server, stacktrace
>
> As I click on Stack & Version and then on the Manage Version button in the
> Versions tab, I get an HTTP 500 Error, with the following stack :
> HTTP ERROR 500
> Problem accessing /views/ADMIN_VIEW/2.1.2/INSTANCE/. Reason:
> Server Error
> Caused by:
> java.lang.IllegalStateException: No WebApplicationContext found: no
> ContextLoaderListener registered?
> at
> org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:159)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1467)
> at
> org.apache.ambari.server.api.AmbariPersistFilter.doFilter(AmbariPersistFilter.java:47)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1467)
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:501)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:557)
> at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)
> at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:429)
> at
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
> at
> org.apache.ambari.server.controller.AmbariHandlerList.processHandlers(AmbariHandlerList.java:209)
> at
> org.apache.ambari.server.controller.AmbariHandlerList.processHandlers(AmbariHandlerList.java:197)
> at
> org.apache.ambari.server.controller.AmbariHandlerList.handle(AmbariHandlerList.java:132)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
> at org.eclipse.jetty.server.Server.handle(Server.java:370)
> at
> org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:494)
> at
> org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:971)
> at
> org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1033)
> at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644)
> at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)
> at
> org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
> at
> org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:696)
> at
> org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:53)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
> at java.lang.Thread.run(Thread.java:744)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22092) Blueprint Created Cluster Is Throwing Constant Exceptions
Doroszlai, Attila created AMBARI-22092:
--
Summary: Blueprint Created Cluster Is Throwing Constant Exceptions
Key: AMBARI-22092
URL: https://issues.apache.org/jira/browse/AMBARI-22092
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.2.0
Reporter: Doroszlai, Attila
Assignee: Doroszlai, Attila
Fix For: 2.6.0
During the creation of a cluster, Ambari server is spitting out the following
exception every second until all host groups have the required number of hosts.
{code}
2017-09-26 11:08:56,221 INFO [pool-4-thread-1] (AsyncCallableService.java:115)
taskCompleted() - Exception during task execution:
java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException:
TopologyManager.ConfigureClusterTask - prerequisites for config request
processing not yet satisfied
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:206)
at
org.apache.ambari.server.topology.AsyncCallableService.taskCompleted(AsyncCallableService.java:106)
at
org.apache.ambari.server.topology.AsyncCallableService.call(AsyncCallableService.java:77)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalArgumentException:
TopologyManager.ConfigureClusterTask - prerequisites for config request
processing not yet satisfied
at
org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:64)
at
org.apache.ambari.server.security.authorization.internal.InternalAuthenticationInterceptor.invoke(InternalAuthenticationInterceptor.java:45)
at
org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:1)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
{code}
Logging in {{ConfigureClusterTask}} and {{AsyncCallableService}} should be
refined and clarified.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22092) Blueprint Created Cluster Is Throwing Constant Exceptions
[
https://issues.apache.org/jira/browse/AMBARI-22092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-22092:
---
Status: Patch Available (was: In Progress)
> Blueprint Created Cluster Is Throwing Constant Exceptions
> -
>
> Key: AMBARI-22092
> URL: https://issues.apache.org/jira/browse/AMBARI-22092
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 2.6.0
>
> Attachments: AMBARI-22092.patch
>
>
> During the creation of a cluster, Ambari server is spitting out the following
> exception every second until all host groups have the required number of
> hosts.
> {code}
> 2017-09-26 11:08:56,221 INFO [pool-4-thread-1]
> (AsyncCallableService.java:115) taskCompleted() - Exception during task
> execution:
> java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException:
> TopologyManager.ConfigureClusterTask - prerequisites for config request
> processing not yet satisfied
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at
> org.apache.ambari.server.topology.AsyncCallableService.taskCompleted(AsyncCallableService.java:106)
> at
> org.apache.ambari.server.topology.AsyncCallableService.call(AsyncCallableService.java:77)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException:
> TopologyManager.ConfigureClusterTask - prerequisites for config request
> processing not yet satisfied
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:64)
> at
> org.apache.ambari.server.security.authorization.internal.InternalAuthenticationInterceptor.invoke(InternalAuthenticationInterceptor.java:45)
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> {code}
> Logging in {{ConfigureClusterTask}} and {{AsyncCallableService}} should be
> refined and clarified.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22092) Blueprint Created Cluster Is Throwing Constant Exceptions
[
https://issues.apache.org/jira/browse/AMBARI-22092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-22092:
---
Attachment: AMBARI-22092.patch
> Blueprint Created Cluster Is Throwing Constant Exceptions
> -
>
> Key: AMBARI-22092
> URL: https://issues.apache.org/jira/browse/AMBARI-22092
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 2.6.0
>
> Attachments: AMBARI-22092.patch
>
>
> During the creation of a cluster, Ambari server is spitting out the following
> exception every second until all host groups have the required number of
> hosts.
> {code}
> 2017-09-26 11:08:56,221 INFO [pool-4-thread-1]
> (AsyncCallableService.java:115) taskCompleted() - Exception during task
> execution:
> java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException:
> TopologyManager.ConfigureClusterTask - prerequisites for config request
> processing not yet satisfied
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at
> org.apache.ambari.server.topology.AsyncCallableService.taskCompleted(AsyncCallableService.java:106)
> at
> org.apache.ambari.server.topology.AsyncCallableService.call(AsyncCallableService.java:77)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException:
> TopologyManager.ConfigureClusterTask - prerequisites for config request
> processing not yet satisfied
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:64)
> at
> org.apache.ambari.server.security.authorization.internal.InternalAuthenticationInterceptor.invoke(InternalAuthenticationInterceptor.java:45)
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> {code}
> Logging in {{ConfigureClusterTask}} and {{AsyncCallableService}} should be
> refined and clarified.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22092) Blueprint Created Cluster Is Throwing Constant Exceptions
[
https://issues.apache.org/jira/browse/AMBARI-22092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-22092:
---
Status: Open (was: Patch Available)
> Blueprint Created Cluster Is Throwing Constant Exceptions
> -
>
> Key: AMBARI-22092
> URL: https://issues.apache.org/jira/browse/AMBARI-22092
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 2.6.0
>
> Attachments: AMBARI-22092.patch
>
>
> During the creation of a cluster, Ambari server is spitting out the following
> exception every second until all host groups have the required number of
> hosts.
> {code}
> 2017-09-26 11:08:56,221 INFO [pool-4-thread-1]
> (AsyncCallableService.java:115) taskCompleted() - Exception during task
> execution:
> java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException:
> TopologyManager.ConfigureClusterTask - prerequisites for config request
> processing not yet satisfied
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at
> org.apache.ambari.server.topology.AsyncCallableService.taskCompleted(AsyncCallableService.java:106)
> at
> org.apache.ambari.server.topology.AsyncCallableService.call(AsyncCallableService.java:77)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException:
> TopologyManager.ConfigureClusterTask - prerequisites for config request
> processing not yet satisfied
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:64)
> at
> org.apache.ambari.server.security.authorization.internal.InternalAuthenticationInterceptor.invoke(InternalAuthenticationInterceptor.java:45)
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> {code}
> Logging in {{ConfigureClusterTask}} and {{AsyncCallableService}} should be
> refined and clarified.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22092) Blueprint Created Cluster Is Throwing Constant Exceptions
[
https://issues.apache.org/jira/browse/AMBARI-22092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-22092:
---
Attachment: (was: AMBARI-22092.patch)
> Blueprint Created Cluster Is Throwing Constant Exceptions
> -
>
> Key: AMBARI-22092
> URL: https://issues.apache.org/jira/browse/AMBARI-22092
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 2.6.0
>
> Attachments: AMBARI-22092.patch
>
>
> During the creation of a cluster, Ambari server is spitting out the following
> exception every second until all host groups have the required number of
> hosts.
> {code}
> 2017-09-26 11:08:56,221 INFO [pool-4-thread-1]
> (AsyncCallableService.java:115) taskCompleted() - Exception during task
> execution:
> java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException:
> TopologyManager.ConfigureClusterTask - prerequisites for config request
> processing not yet satisfied
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at
> org.apache.ambari.server.topology.AsyncCallableService.taskCompleted(AsyncCallableService.java:106)
> at
> org.apache.ambari.server.topology.AsyncCallableService.call(AsyncCallableService.java:77)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException:
> TopologyManager.ConfigureClusterTask - prerequisites for config request
> processing not yet satisfied
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:64)
> at
> org.apache.ambari.server.security.authorization.internal.InternalAuthenticationInterceptor.invoke(InternalAuthenticationInterceptor.java:45)
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> {code}
> Logging in {{ConfigureClusterTask}} and {{AsyncCallableService}} should be
> refined and clarified.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22092) Blueprint Created Cluster Is Throwing Constant Exceptions
[
https://issues.apache.org/jira/browse/AMBARI-22092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-22092:
---
Attachment: AMBARI-22092.patch
> Blueprint Created Cluster Is Throwing Constant Exceptions
> -
>
> Key: AMBARI-22092
> URL: https://issues.apache.org/jira/browse/AMBARI-22092
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 2.6.0
>
> Attachments: AMBARI-22092.patch
>
>
> During the creation of a cluster, Ambari server is spitting out the following
> exception every second until all host groups have the required number of
> hosts.
> {code}
> 2017-09-26 11:08:56,221 INFO [pool-4-thread-1]
> (AsyncCallableService.java:115) taskCompleted() - Exception during task
> execution:
> java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException:
> TopologyManager.ConfigureClusterTask - prerequisites for config request
> processing not yet satisfied
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at
> org.apache.ambari.server.topology.AsyncCallableService.taskCompleted(AsyncCallableService.java:106)
> at
> org.apache.ambari.server.topology.AsyncCallableService.call(AsyncCallableService.java:77)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException:
> TopologyManager.ConfigureClusterTask - prerequisites for config request
> processing not yet satisfied
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:64)
> at
> org.apache.ambari.server.security.authorization.internal.InternalAuthenticationInterceptor.invoke(InternalAuthenticationInterceptor.java:45)
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> {code}
> Logging in {{ConfigureClusterTask}} and {{AsyncCallableService}} should be
> refined and clarified.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22092) Blueprint Created Cluster Is Throwing Constant Exceptions
[
https://issues.apache.org/jira/browse/AMBARI-22092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-22092:
---
Status: Patch Available (was: Open)
> Blueprint Created Cluster Is Throwing Constant Exceptions
> -
>
> Key: AMBARI-22092
> URL: https://issues.apache.org/jira/browse/AMBARI-22092
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 2.6.0
>
> Attachments: AMBARI-22092.patch
>
>
> During the creation of a cluster, Ambari server is spitting out the following
> exception every second until all host groups have the required number of
> hosts.
> {code}
> 2017-09-26 11:08:56,221 INFO [pool-4-thread-1]
> (AsyncCallableService.java:115) taskCompleted() - Exception during task
> execution:
> java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException:
> TopologyManager.ConfigureClusterTask - prerequisites for config request
> processing not yet satisfied
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at
> org.apache.ambari.server.topology.AsyncCallableService.taskCompleted(AsyncCallableService.java:106)
> at
> org.apache.ambari.server.topology.AsyncCallableService.call(AsyncCallableService.java:77)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException:
> TopologyManager.ConfigureClusterTask - prerequisites for config request
> processing not yet satisfied
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:64)
> at
> org.apache.ambari.server.security.authorization.internal.InternalAuthenticationInterceptor.invoke(InternalAuthenticationInterceptor.java:45)
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> {code}
> Logging in {{ConfigureClusterTask}} and {{AsyncCallableService}} should be
> refined and clarified.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22093) Log Search UI: implement service logs actions functionality
Andrii Babiichuk created AMBARI-22093: - Summary: Log Search UI: implement service logs actions functionality Key: AMBARI-22093 URL: https://issues.apache.org/jira/browse/AMBARI-22093 Project: Ambari Issue Type: Task Components: ambari-logsearch Affects Versions: 3.0.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Fix For: 3.0.0 Implement Copy, Open Log and Context actions for logs list entries. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22093) Log Search UI: implement service logs actions functionality
[ https://issues.apache.org/jira/browse/AMBARI-22093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-22093: -- Status: Patch Available (was: Open) > Log Search UI: implement service logs actions functionality > --- > > Key: AMBARI-22093 > URL: https://issues.apache.org/jira/browse/AMBARI-22093 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-22093.patch > > > Implement Copy, Open Log and Context actions for logs list entries. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22093) Log Search UI: implement service logs actions functionality
[ https://issues.apache.org/jira/browse/AMBARI-22093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-22093: -- Attachment: AMBARI-22093.patch > Log Search UI: implement service logs actions functionality > --- > > Key: AMBARI-22093 > URL: https://issues.apache.org/jira/browse/AMBARI-22093 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-22093.patch > > > Implement Copy, Open Log and Context actions for logs list entries. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22092) Blueprint Created Cluster Is Throwing Constant Exceptions
[
https://issues.apache.org/jira/browse/AMBARI-22092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-22092:
---
Attachment: AMBARI-22092_branch-2.6.patch
> Blueprint Created Cluster Is Throwing Constant Exceptions
> -
>
> Key: AMBARI-22092
> URL: https://issues.apache.org/jira/browse/AMBARI-22092
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 2.6.0
>
> Attachments: AMBARI-22092_branch-2.6.patch, AMBARI-22092.patch
>
>
> During the creation of a cluster, Ambari server is spitting out the following
> exception every second until all host groups have the required number of
> hosts.
> {code}
> 2017-09-26 11:08:56,221 INFO [pool-4-thread-1]
> (AsyncCallableService.java:115) taskCompleted() - Exception during task
> execution:
> java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException:
> TopologyManager.ConfigureClusterTask - prerequisites for config request
> processing not yet satisfied
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at
> org.apache.ambari.server.topology.AsyncCallableService.taskCompleted(AsyncCallableService.java:106)
> at
> org.apache.ambari.server.topology.AsyncCallableService.call(AsyncCallableService.java:77)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException:
> TopologyManager.ConfigureClusterTask - prerequisites for config request
> processing not yet satisfied
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:64)
> at
> org.apache.ambari.server.security.authorization.internal.InternalAuthenticationInterceptor.invoke(InternalAuthenticationInterceptor.java:45)
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> {code}
> Logging in {{ConfigureClusterTask}} and {{AsyncCallableService}} should be
> refined and clarified.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22094) Install Wizard: refactor stack versions step
Andrii Tkach created AMBARI-22094: - Summary: Install Wizard: refactor stack versions step Key: AMBARI-22094 URL: https://issues.apache.org/jira/browse/AMBARI-22094 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 3.0.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 3.0.0 Request to fetch stack versions made on each step of Install Wizard. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22093) Log Search UI: implement service logs actions functionality
[
https://issues.apache.org/jira/browse/AMBARI-22093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16185813#comment-16185813
]
Hadoop QA commented on AMBARI-22093:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12889684/AMBARI-22093.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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-logsearch/ambari-logsearch-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12381//console
This message is automatically generated.
> Log Search UI: implement service logs actions functionality
> ---
>
> Key: AMBARI-22093
> URL: https://issues.apache.org/jira/browse/AMBARI-22093
> Project: Ambari
> Issue Type: Task
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-22093.patch
>
>
> Implement Copy, Open Log and Context actions for logs list entries.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22094) Install Wizard: refactor stack versions step
[ https://issues.apache.org/jira/browse/AMBARI-22094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22094: -- Attachment: AMBARI-22094.patch > Install Wizard: refactor stack versions step > > > Key: AMBARI-22094 > URL: https://issues.apache.org/jira/browse/AMBARI-22094 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22094.patch > > > Request to fetch stack versions made on each step of Install Wizard. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22094) Install Wizard: refactor stack versions step
[ https://issues.apache.org/jira/browse/AMBARI-22094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22094: -- Status: Patch Available (was: Open) > Install Wizard: refactor stack versions step > > > Key: AMBARI-22094 > URL: https://issues.apache.org/jira/browse/AMBARI-22094 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22094.patch > > > Request to fetch stack versions made on each step of Install Wizard. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22094) Install Wizard: refactor stack versions step
[ https://issues.apache.org/jira/browse/AMBARI-22094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16185823#comment-16185823 ] Andrii Tkach commented on AMBARI-22094: --- 21353 passing (27s) 128 pending > Install Wizard: refactor stack versions step > > > Key: AMBARI-22094 > URL: https://issues.apache.org/jira/browse/AMBARI-22094 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22094.patch > > > Request to fetch stack versions made on each step of Install Wizard. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22093) Log Search UI: implement service logs actions functionality
[ https://issues.apache.org/jira/browse/AMBARI-22093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-22093: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > Log Search UI: implement service logs actions functionality > --- > > Key: AMBARI-22093 > URL: https://issues.apache.org/jira/browse/AMBARI-22093 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-22093.patch > > > Implement Copy, Open Log and Context actions for logs list entries. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21803) Implement STOMP endpoint to provide alert definitions
[ https://issues.apache.org/jira/browse/AMBARI-21803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-21803: --- Attachment: (was: AMBARI-21803.patch) > Implement STOMP endpoint to provide alert definitions > - > > Key: AMBARI-21803 > URL: https://issues.apache.org/jira/browse/AMBARI-21803 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila >Priority: Critical > Fix For: 3.0.0 > > > Add endpoint in Ambari Server for agent to query / subscribe to alert > definitions. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21803) Implement STOMP endpoint to provide alert definitions
[ https://issues.apache.org/jira/browse/AMBARI-21803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-21803: --- Attachment: AMBARI-21803.patch > Implement STOMP endpoint to provide alert definitions > - > > Key: AMBARI-21803 > URL: https://issues.apache.org/jira/browse/AMBARI-21803 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-21803.patch > > > Add endpoint in Ambari Server for agent to query / subscribe to alert > definitions. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22079) Upgrade Yarn version for Logsearch Web
[
https://issues.apache.org/jira/browse/AMBARI-22079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16185862#comment-16185862
]
Olivér Szabó commented on AMBARI-22079:
---
committed to trunk:
{code:java}
commit 504094e5bc697373b233683e0697de63872ce101
Author: Istvan Tobias
Date: Fri Sep 29 15:50:20 2017 +0200
AMBARI-22079. Upgrade Yarn version for Logsearch Web (Istvan Tobias via
oleewere)
{code}
> Upgrade Yarn version for Logsearch Web
> --
>
> Key: AMBARI-22079
> URL: https://issues.apache.org/jira/browse/AMBARI-22079
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
> Fix For: 3.0.0
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-22079) Upgrade Yarn version for Logsearch Web
[ https://issues.apache.org/jira/browse/AMBARI-22079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-22079. --- Resolution: Fixed > Upgrade Yarn version for Logsearch Web > -- > > Key: AMBARI-22079 > URL: https://issues.apache.org/jira/browse/AMBARI-22079 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22093) Log Search UI: implement service logs actions functionality
[ https://issues.apache.org/jira/browse/AMBARI-22093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16185868#comment-16185868 ] Hudson commented on AMBARI-22093: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8167 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8167/]) AMBARI-22093 Log Search UI: implement service logs actions (ababiichuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8852edd2f5458a22109bc0931fd6e91341d0523f]) * (edit) ambari-logsearch/ambari-logsearch-web/src/app/models/store.model.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/component-actions.service.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/dropdown-list/dropdown-list.component.html * (add) ambari-logsearch/ambari-logsearch-web/src/app/classes/service-log-context-entry.class.ts * (add) ambari-logsearch/ambari-logsearch-web/src/app/components/log-file-entry/log-file-entry.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/logs-container/logs-container.component.spec.ts * (add) ambari-logsearch/ambari-logsearch-web/src/app/components/log-context/log-context.component.html * (add) ambari-logsearch/ambari-logsearch-web/src/app/components/log-file-entry/log-file-entry.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/storage/reducers.service.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/logs-container.service.ts * (add) ambari-logsearch/ambari-logsearch-web/src/app/components/log-context/log-context.component.less * (add) ambari-logsearch/ambari-logsearch-web/src/app/components/log-file-entry/log-file-entry.component.html * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/logs-list/logs-list.component.html * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/timezone-picker/timezone-picker.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/logs-container/logs-container.component.html * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/main-container/main-container.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/dropdown-list/dropdown-list.component.spec.ts * (add) ambari-logsearch/ambari-logsearch-web/src/app/components/log-file-entry/log-file-entry.component.less * (edit) ambari-logsearch/ambari-logsearch-web/src/app/models/app-state.model.ts * (add) ambari-logsearch/ambari-logsearch-web/src/app/classes/queries/service-logs-truncated-query-params.class.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/logs-list/logs-list.component.less * (add) ambari-logsearch/ambari-logsearch-web/src/app/components/log-context/log-context.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/classes/queries/audit-logs-query-params.class.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/dropdown-list/dropdown-list.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/filter-button/filter-button.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/filter-dropdown/filter-dropdown.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/menu-button/menu-button.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/main-container/main-container.component.less * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/http-client.service.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/dropdown-button/dropdown-button.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/app.module.ts * (add) ambari-logsearch/ambari-logsearch-web/src/app/components/log-context/log-context.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/logs-list/logs-list.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/variables.less * (edit) ambari-logsearch/ambari-logsearch-web/src/app/models/graph.model.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/filters-panel/filters-panel.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/logs-container.service.spec.ts * (add) ambari-logsearch/ambari-logsearch-web/src/app/services/storage/service-logs-truncated.service.ts * (add) ambari-logsearch/ambari-logsearch-web/src/app/classes/active-service-log-entry.class.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/component-actions.service.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/classes/list-item.class.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/dropdown-button/dropdown-button.component.html * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/main-container/main-container.component.ts * (edit) ambari-logsearc
[jira] [Commented] (AMBARI-22094) Install Wizard: refactor stack versions step
[
https://issues.apache.org/jira/browse/AMBARI-22094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16185872#comment-16185872
]
Hadoop QA commented on AMBARI-22094:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12889690/AMBARI-22094.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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12382//console
This message is automatically generated.
> Install Wizard: refactor stack versions step
>
>
> Key: AMBARI-22094
> URL: https://issues.apache.org/jira/browse/AMBARI-22094
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-22094.patch
>
>
> Request to fetch stack versions made on each step of Install Wizard.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22092) Blueprint Created Cluster Is Throwing Constant Exceptions
[
https://issues.apache.org/jira/browse/AMBARI-22092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-22092:
---
Attachment: (was: AMBARI-22092.patch)
> Blueprint Created Cluster Is Throwing Constant Exceptions
> -
>
> Key: AMBARI-22092
> URL: https://issues.apache.org/jira/browse/AMBARI-22092
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 2.6.0
>
> Attachments: AMBARI-22092_branch-2.6.patch, AMBARI-22092.patch
>
>
> During the creation of a cluster, Ambari server is spitting out the following
> exception every second until all host groups have the required number of
> hosts.
> {code}
> 2017-09-26 11:08:56,221 INFO [pool-4-thread-1]
> (AsyncCallableService.java:115) taskCompleted() - Exception during task
> execution:
> java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException:
> TopologyManager.ConfigureClusterTask - prerequisites for config request
> processing not yet satisfied
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at
> org.apache.ambari.server.topology.AsyncCallableService.taskCompleted(AsyncCallableService.java:106)
> at
> org.apache.ambari.server.topology.AsyncCallableService.call(AsyncCallableService.java:77)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException:
> TopologyManager.ConfigureClusterTask - prerequisites for config request
> processing not yet satisfied
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:64)
> at
> org.apache.ambari.server.security.authorization.internal.InternalAuthenticationInterceptor.invoke(InternalAuthenticationInterceptor.java:45)
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> {code}
> Logging in {{ConfigureClusterTask}} and {{AsyncCallableService}} should be
> refined and clarified.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22092) Blueprint Created Cluster Is Throwing Constant Exceptions
[
https://issues.apache.org/jira/browse/AMBARI-22092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-22092:
---
Attachment: (was: AMBARI-22092_branch-2.6.patch)
> Blueprint Created Cluster Is Throwing Constant Exceptions
> -
>
> Key: AMBARI-22092
> URL: https://issues.apache.org/jira/browse/AMBARI-22092
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 2.6.0
>
> Attachments: AMBARI-22092_branch-2.6.patch, AMBARI-22092.patch
>
>
> During the creation of a cluster, Ambari server is spitting out the following
> exception every second until all host groups have the required number of
> hosts.
> {code}
> 2017-09-26 11:08:56,221 INFO [pool-4-thread-1]
> (AsyncCallableService.java:115) taskCompleted() - Exception during task
> execution:
> java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException:
> TopologyManager.ConfigureClusterTask - prerequisites for config request
> processing not yet satisfied
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at
> org.apache.ambari.server.topology.AsyncCallableService.taskCompleted(AsyncCallableService.java:106)
> at
> org.apache.ambari.server.topology.AsyncCallableService.call(AsyncCallableService.java:77)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException:
> TopologyManager.ConfigureClusterTask - prerequisites for config request
> processing not yet satisfied
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:64)
> at
> org.apache.ambari.server.security.authorization.internal.InternalAuthenticationInterceptor.invoke(InternalAuthenticationInterceptor.java:45)
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> {code}
> Logging in {{ConfigureClusterTask}} and {{AsyncCallableService}} should be
> refined and clarified.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22092) Blueprint Created Cluster Is Throwing Constant Exceptions
[
https://issues.apache.org/jira/browse/AMBARI-22092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-22092:
---
Attachment: AMBARI-22092.patch
> Blueprint Created Cluster Is Throwing Constant Exceptions
> -
>
> Key: AMBARI-22092
> URL: https://issues.apache.org/jira/browse/AMBARI-22092
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 2.6.0
>
> Attachments: AMBARI-22092_branch-2.6.patch, AMBARI-22092.patch
>
>
> During the creation of a cluster, Ambari server is spitting out the following
> exception every second until all host groups have the required number of
> hosts.
> {code}
> 2017-09-26 11:08:56,221 INFO [pool-4-thread-1]
> (AsyncCallableService.java:115) taskCompleted() - Exception during task
> execution:
> java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException:
> TopologyManager.ConfigureClusterTask - prerequisites for config request
> processing not yet satisfied
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at
> org.apache.ambari.server.topology.AsyncCallableService.taskCompleted(AsyncCallableService.java:106)
> at
> org.apache.ambari.server.topology.AsyncCallableService.call(AsyncCallableService.java:77)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException:
> TopologyManager.ConfigureClusterTask - prerequisites for config request
> processing not yet satisfied
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:64)
> at
> org.apache.ambari.server.security.authorization.internal.InternalAuthenticationInterceptor.invoke(InternalAuthenticationInterceptor.java:45)
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> {code}
> Logging in {{ConfigureClusterTask}} and {{AsyncCallableService}} should be
> refined and clarified.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22092) Blueprint Created Cluster Is Throwing Constant Exceptions
[
https://issues.apache.org/jira/browse/AMBARI-22092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-22092:
---
Attachment: AMBARI-22092_branch-2.6.patch
> Blueprint Created Cluster Is Throwing Constant Exceptions
> -
>
> Key: AMBARI-22092
> URL: https://issues.apache.org/jira/browse/AMBARI-22092
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 2.6.0
>
> Attachments: AMBARI-22092_branch-2.6.patch, AMBARI-22092.patch
>
>
> During the creation of a cluster, Ambari server is spitting out the following
> exception every second until all host groups have the required number of
> hosts.
> {code}
> 2017-09-26 11:08:56,221 INFO [pool-4-thread-1]
> (AsyncCallableService.java:115) taskCompleted() - Exception during task
> execution:
> java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException:
> TopologyManager.ConfigureClusterTask - prerequisites for config request
> processing not yet satisfied
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at
> org.apache.ambari.server.topology.AsyncCallableService.taskCompleted(AsyncCallableService.java:106)
> at
> org.apache.ambari.server.topology.AsyncCallableService.call(AsyncCallableService.java:77)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException:
> TopologyManager.ConfigureClusterTask - prerequisites for config request
> processing not yet satisfied
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:64)
> at
> org.apache.ambari.server.security.authorization.internal.InternalAuthenticationInterceptor.invoke(InternalAuthenticationInterceptor.java:45)
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> {code}
> Logging in {{ConfigureClusterTask}} and {{AsyncCallableService}} should be
> refined and clarified.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22017) stack advisor recommends all components on single host for HDP-2.6 Ambari trunk build
[ https://issues.apache.org/jira/browse/AMBARI-22017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-22017: Resolution: Fixed Status: Resolved (was: Patch Available) > stack advisor recommends all components on single host for HDP-2.6 Ambari > trunk build > - > > Key: AMBARI-22017 > URL: https://issues.apache.org/jira/browse/AMBARI-22017 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: trunk, 3.0.0 > > Attachments: AMBARI-22017_2.patch, AMBARI-22017.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22094) Install Wizard: refactor stack versions step
[
https://issues.apache.org/jira/browse/AMBARI-22094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16185917#comment-16185917
]
Hadoop QA commented on AMBARI-22094:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12889690/AMBARI-22094.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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12383//console
This message is automatically generated.
> Install Wizard: refactor stack versions step
>
>
> Key: AMBARI-22094
> URL: https://issues.apache.org/jira/browse/AMBARI-22094
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-22094.patch
>
>
> Request to fetch stack versions made on each step of Install Wizard.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22092) Blueprint Created Cluster Is Throwing Constant Exceptions
[
https://issues.apache.org/jira/browse/AMBARI-22092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16185920#comment-16185920
]
Hadoop QA commented on AMBARI-22092:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12889699/AMBARI-22092_branch-2.6.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/12384//console
This message is automatically generated.
> Blueprint Created Cluster Is Throwing Constant Exceptions
> -
>
> Key: AMBARI-22092
> URL: https://issues.apache.org/jira/browse/AMBARI-22092
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 2.6.0
>
> Attachments: AMBARI-22092_branch-2.6.patch, AMBARI-22092.patch
>
>
> During the creation of a cluster, Ambari server is spitting out the following
> exception every second until all host groups have the required number of
> hosts.
> {code}
> 2017-09-26 11:08:56,221 INFO [pool-4-thread-1]
> (AsyncCallableService.java:115) taskCompleted() - Exception during task
> execution:
> java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException:
> TopologyManager.ConfigureClusterTask - prerequisites for config request
> processing not yet satisfied
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at
> org.apache.ambari.server.topology.AsyncCallableService.taskCompleted(AsyncCallableService.java:106)
> at
> org.apache.ambari.server.topology.AsyncCallableService.call(AsyncCallableService.java:77)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException:
> TopologyManager.ConfigureClusterTask - prerequisites for config request
> processing not yet satisfied
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:64)
> at
> org.apache.ambari.server.security.authorization.internal.InternalAuthenticationInterceptor.invoke(InternalAuthenticationInterceptor.java:45)
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> {code}
> Logging in {{ConfigureClusterTask}} and {{AsyncCallableService}} should be
> refined and clarified.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22095) Make hooks stack agnostic
Dmytro Sen created AMBARI-22095: --- Summary: Make hooks stack agnostic Key: AMBARI-22095 URL: https://issues.apache.org/jira/browse/AMBARI-22095 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Priority: Critical Fix For: 3.0.0 - At present hooks are located inside stacks - For all HDP stacks, we use https://github.com/apache/ambari/tree/trunk/ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks - Similarly for all HDF stacks, we use https://github.com/hortonworks/hdf_ambari_mp/tree/master/hdf-ambari-mpack/src/main/resources/stacks/HDF/2.0/hooks - Any time the HDP hooks are updated, the changes have to be ported to HDF branch. This is a maintenance overhead - In Ambari 3.0 when we move to mpack based operations model, this will be a maint nightmare. *Requirements* # We should look into making hooks stack agnostic. # Hooks should be moved from resources/stacks/HDP/2.0.6/hooks to resources/stack-hooks # Hooks should be entirely config driven # There should be no HDP or HDF specific logic in the hooks (hdp-select, conf-select, hdf-select, hdfconf-select) # There should be no service specific logic in the hooks (for example: hardcoded service user to service group mapping etc. this should be stack driven see: AMBARI-20034). # Any service specific logic that doesn't make sense should be removed and refactored into respective service definitions. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22094) Install Wizard: refactor stack versions step
[ https://issues.apache.org/jira/browse/AMBARI-22094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16185923#comment-16185923 ] Aleksandr Kovalenko commented on AMBARI-22094: -- +1 for the patch > Install Wizard: refactor stack versions step > > > Key: AMBARI-22094 > URL: https://issues.apache.org/jira/browse/AMBARI-22094 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22094.patch > > > Request to fetch stack versions made on each step of Install Wizard. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22094) Install Wizard: refactor stack versions step
[ https://issues.apache.org/jira/browse/AMBARI-22094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16185929#comment-16185929 ] Andrii Tkach commented on AMBARI-22094: --- committed to trunk > Install Wizard: refactor stack versions step > > > Key: AMBARI-22094 > URL: https://issues.apache.org/jira/browse/AMBARI-22094 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22094.patch > > > Request to fetch stack versions made on each step of Install Wizard. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22094) Install Wizard: refactor stack versions step
[ https://issues.apache.org/jira/browse/AMBARI-22094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22094: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Install Wizard: refactor stack versions step > > > Key: AMBARI-22094 > URL: https://issues.apache.org/jira/browse/AMBARI-22094 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22094.patch > > > Request to fetch stack versions made on each step of Install Wizard. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22079) Upgrade Yarn version for Logsearch Web
[ https://issues.apache.org/jira/browse/AMBARI-22079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16185933#comment-16185933 ] Hudson commented on AMBARI-22079: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8168 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8168/]) AMBARI-22079. Upgrade Yarn version for Logsearch Web (Istvan Tobias via (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=504094e5bc697373b233683e0697de63872ce101]) * (edit) ambari-logsearch/ambari-logsearch-web/yarn.lock * (edit) ambari-logsearch/ambari-logsearch-web/pom.xml * (edit) ambari-logsearch/ambari-logsearch-web/package.json > Upgrade Yarn version for Logsearch Web > -- > > Key: AMBARI-22079 > URL: https://issues.apache.org/jira/browse/AMBARI-22079 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22091) Hive view2.0 Jobs worksheets doesn't have hyperlink whereas view1.5 History worksheets had hyperlinks pointing to fetched results
[
https://issues.apache.org/jira/browse/AMBARI-22091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16185941#comment-16185941
]
Hadoop QA commented on AMBARI-22091:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12889642/AMBARI-22091.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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in
[contrib/views/hive20|https://builds.apache.org/job/Ambari-trunk-test-patch/12385//artifact/patch-work/testrun_hive20.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12385//console
This message is automatically generated.
> Hive view2.0 Jobs worksheets doesn't have hyperlink whereas view1.5 History
> worksheets had hyperlinks pointing to fetched results
> -
>
> Key: AMBARI-22091
> URL: https://issues.apache.org/jira/browse/AMBARI-22091
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.6.0
>Reporter: venkat
>Assignee: venkat
> Fix For: 2.6.0
>
> Attachments: AMBARI-22091.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22092) Blueprint Created Cluster Is Throwing Constant Exceptions
[
https://issues.apache.org/jira/browse/AMBARI-22092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16185943#comment-16185943
]
Hadoop QA commented on AMBARI-22092:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12889699/AMBARI-22092_branch-2.6.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/12386//console
This message is automatically generated.
> Blueprint Created Cluster Is Throwing Constant Exceptions
> -
>
> Key: AMBARI-22092
> URL: https://issues.apache.org/jira/browse/AMBARI-22092
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 2.6.0
>
> Attachments: AMBARI-22092_branch-2.6.patch, AMBARI-22092.patch
>
>
> During the creation of a cluster, Ambari server is spitting out the following
> exception every second until all host groups have the required number of
> hosts.
> {code}
> 2017-09-26 11:08:56,221 INFO [pool-4-thread-1]
> (AsyncCallableService.java:115) taskCompleted() - Exception during task
> execution:
> java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException:
> TopologyManager.ConfigureClusterTask - prerequisites for config request
> processing not yet satisfied
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at
> org.apache.ambari.server.topology.AsyncCallableService.taskCompleted(AsyncCallableService.java:106)
> at
> org.apache.ambari.server.topology.AsyncCallableService.call(AsyncCallableService.java:77)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException:
> TopologyManager.ConfigureClusterTask - prerequisites for config request
> processing not yet satisfied
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:64)
> at
> org.apache.ambari.server.security.authorization.internal.InternalAuthenticationInterceptor.invoke(InternalAuthenticationInterceptor.java:45)
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> {code}
> Logging in {{ConfigureClusterTask}} and {{AsyncCallableService}} should be
> refined and clarified.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22095) Make hooks stack agnostic
[ https://issues.apache.org/jira/browse/AMBARI-22095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-22095: Attachment: AMBARI-22095.patch > Make hooks stack agnostic > - > > Key: AMBARI-22095 > URL: https://issues.apache.org/jira/browse/AMBARI-22095 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-22095.patch > > > - At present hooks are located inside stacks > - For all HDP stacks, we use > https://github.com/apache/ambari/tree/trunk/ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks > - Similarly for all HDF stacks, we use > https://github.com/hortonworks/hdf_ambari_mp/tree/master/hdf-ambari-mpack/src/main/resources/stacks/HDF/2.0/hooks > - Any time the HDP hooks are updated, the changes have to be ported to HDF > branch. This is a maintenance overhead > - In Ambari 3.0 when we move to mpack based operations model, this will be a > maint nightmare. > *Requirements* > # We should look into making hooks stack agnostic. > # Hooks should be moved from resources/stacks/HDP/2.0.6/hooks to > resources/stack-hooks > # Hooks should be entirely config driven > # There should be no HDP or HDF specific logic in the hooks (hdp-select, > conf-select, hdf-select, hdfconf-select) > # There should be no service specific logic in the hooks (for example: > hardcoded service user to service group mapping etc. this should be stack > driven see: AMBARI-20034). > # Any service specific logic that doesn't make sense should be removed and > refactored into respective service definitions. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22095) Make hooks stack agnostic
[ https://issues.apache.org/jira/browse/AMBARI-22095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-22095: Status: Patch Available (was: In Progress) > Make hooks stack agnostic > - > > Key: AMBARI-22095 > URL: https://issues.apache.org/jira/browse/AMBARI-22095 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-22095.patch > > > - At present hooks are located inside stacks > - For all HDP stacks, we use > https://github.com/apache/ambari/tree/trunk/ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks > - Similarly for all HDF stacks, we use > https://github.com/hortonworks/hdf_ambari_mp/tree/master/hdf-ambari-mpack/src/main/resources/stacks/HDF/2.0/hooks > - Any time the HDP hooks are updated, the changes have to be ported to HDF > branch. This is a maintenance overhead > - In Ambari 3.0 when we move to mpack based operations model, this will be a > maint nightmare. > *Requirements* > # We should look into making hooks stack agnostic. > # Hooks should be moved from resources/stacks/HDP/2.0.6/hooks to > resources/stack-hooks > # Hooks should be entirely config driven > # There should be no HDP or HDF specific logic in the hooks (hdp-select, > conf-select, hdf-select, hdfconf-select) > # There should be no service specific logic in the hooks (for example: > hardcoded service user to service group mapping etc. this should be stack > driven see: AMBARI-20034). > # Any service specific logic that doesn't make sense should be removed and > refactored into respective service definitions. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22083) Wrong Hadoop Home Directory Is Being Picked Up on MAINT/PATCH Upgraded Clusters
[
https://issues.apache.org/jira/browse/AMBARI-22083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-22083:
-
Status: Patch Available (was: Open)
> Wrong Hadoop Home Directory Is Being Picked Up on MAINT/PATCH Upgraded
> Clusters
> ---
>
> Key: AMBARI-22083
> URL: https://issues.apache.org/jira/browse/AMBARI-22083
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-22083.patch
>
>
> STR:
> - Install HDP 2.6.0.0 with HDFS and YARN/MapR
> - Perform a MAINT upgrade of HDFS to 2.6.3.0
> - Stop all services
> - Restart all services
> The following is observed:
> - {{/usr/hdp/current/hadoop-client -> /usr/hdp/2.6.0.0/hadoop}}
> - HDFS picks up 2.6.0.0
> - YARN/MapR pick up 2.6.0.0
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22083) Wrong Hadoop Home Directory Is Being Picked Up on MAINT/PATCH Upgraded Clusters
[
https://issues.apache.org/jira/browse/AMBARI-22083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-22083:
-
Attachment: AMBARI-22083.patch
> Wrong Hadoop Home Directory Is Being Picked Up on MAINT/PATCH Upgraded
> Clusters
> ---
>
> Key: AMBARI-22083
> URL: https://issues.apache.org/jira/browse/AMBARI-22083
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-22083.patch
>
>
> STR:
> - Install HDP 2.6.0.0 with HDFS and YARN/MapR
> - Perform a MAINT upgrade of HDFS to 2.6.3.0
> - Stop all services
> - Restart all services
> The following is observed:
> - {{/usr/hdp/current/hadoop-client -> /usr/hdp/2.6.0.0/hadoop}}
> - HDFS picks up 2.6.0.0
> - YARN/MapR pick up 2.6.0.0
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22083) Wrong Hadoop Home Directory Is Being Picked Up on MAINT/PATCH Upgraded Clusters
[
https://issues.apache.org/jira/browse/AMBARI-22083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16185977#comment-16185977
]
Hadoop QA commented on AMBARI-22083:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12889708/AMBARI-22083.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/12387//console
This message is automatically generated.
> Wrong Hadoop Home Directory Is Being Picked Up on MAINT/PATCH Upgraded
> Clusters
> ---
>
> Key: AMBARI-22083
> URL: https://issues.apache.org/jira/browse/AMBARI-22083
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-22083.patch
>
>
> STR:
> - Install HDP 2.6.0.0 with HDFS and YARN/MapR
> - Perform a MAINT upgrade of HDFS to 2.6.3.0
> - Stop all services
> - Restart all services
> The following is observed:
> - {{/usr/hdp/current/hadoop-client -> /usr/hdp/2.6.0.0/hadoop}}
> - HDFS picks up 2.6.0.0
> - YARN/MapR pick up 2.6.0.0
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22095) Make hooks stack agnostic
[
https://issues.apache.org/jira/browse/AMBARI-22095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16185981#comment-16185981
]
Hadoop QA commented on AMBARI-22095:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12889704/AMBARI-22095.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/12388//console
This message is automatically generated.
> Make hooks stack agnostic
> -
>
> Key: AMBARI-22095
> URL: https://issues.apache.org/jira/browse/AMBARI-22095
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-22095.patch
>
>
> - At present hooks are located inside stacks
> - For all HDP stacks, we use
> https://github.com/apache/ambari/tree/trunk/ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks
> - Similarly for all HDF stacks, we use
> https://github.com/hortonworks/hdf_ambari_mp/tree/master/hdf-ambari-mpack/src/main/resources/stacks/HDF/2.0/hooks
> - Any time the HDP hooks are updated, the changes have to be ported to HDF
> branch. This is a maintenance overhead
> - In Ambari 3.0 when we move to mpack based operations model, this will be a
> maint nightmare.
> *Requirements*
> # We should look into making hooks stack agnostic.
> # Hooks should be moved from resources/stacks/HDP/2.0.6/hooks to
> resources/stack-hooks
> # Hooks should be entirely config driven
> # There should be no HDP or HDF specific logic in the hooks (hdp-select,
> conf-select, hdf-select, hdfconf-select)
> # There should be no service specific logic in the hooks (for example:
> hardcoded service user to service group mapping etc. this should be stack
> driven see: AMBARI-20034).
> # Any service specific logic that doesn't make sense should be removed and
> refactored into respective service definitions.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22090) INCORROUT in Hive SELECT-JOIN query using Hive View 2.0
[
https://issues.apache.org/jira/browse/AMBARI-22090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pallav Kulshreshtha updated AMBARI-22090:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
code committed to trunk.
> INCORROUT in Hive SELECT-JOIN query using Hive View 2.0
> ---
>
> Key: AMBARI-22090
> URL: https://issues.apache.org/jira/browse/AMBARI-22090
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Reporter: Pallav Kulshreshtha
>Assignee: Pallav Kulshreshtha
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-22090_branch-trunk.patch
>
>
> TESTCASE:
> DROP TABLE IF EXISTS mydim;
> DROP TABLE IF EXISTS staging;
> CREATE TABLE mydim (
> key int,
> value string,
> status string)
> PARTITIONED BY (last_updated timestamp)
> CLUSTERED BY (key) INTO 5 BUCKETS
> STORED AS ORC TBLPROPERTIES ('transactional'='true');
> INSERT INTO mydim PARTITION(last_updated) VALUES
> (1, 'value1', 'original value', '2017-01-01'),
> (2, 'value2', 'original value', '2017-01-01'),
> (3, 'value3', 'original value', '2017-01-01'),
> (4, 'value4', 'original value', '2017-01-01'),
> (5, 'value5', 'original value', '2017-01-01');
> CREATE TABLE staging(
> key int,
> value string)
> STORED AS ORC;
> INSERT INTO staging VALUES
> (0, 'value0'),
> (1, 'value1_new');
> – INCORROUT: 1value1_new original value 2017-01-01 00:00:00.0
> 1 value1_new
> – EXPECTED: 1 value1 original value 2017-01-01 00:00:00.0 1
> value1_new
> SELECT *
> FROM mydim,staging
> WHERE mydim.key = staging.key;
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22089) Hive View 2.0 - Unable to update existing saved queries, view creates new records under saved queries tab
[ https://issues.apache.org/jira/browse/AMBARI-22089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-22089: - Resolution: Fixed Status: Resolved (was: Patch Available) code committed to trunk. > Hive View 2.0 - Unable to update existing saved queries, view creates new > records under saved queries tab > - > > Key: AMBARI-22089 > URL: https://issues.apache.org/jira/browse/AMBARI-22089 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha >Priority: Blocker > Fix For: 2.6.0 > > Attachments: AMBARI-22089_branch-trunk.patch > > > Under the "Saved Queries" section in Ambari, there exist multiple entries for > the query - all entries have the same query name, that is - when changes are > made to a query and subsequently saved, an entry gets created. > However, all entries have the same name - after a while it is not possible to > know which is the latest version. > The "Saved Queries" view does not include a timestamp nor does it > automatically append a version name to the query - thus making it hard for > the user to figure out which is the latest query > Review the screenshot in attached adobe pdf > Issue: In Hive view2.0 - when query is saved it gets saved with the provided > name say "test-query1" - now go to "Saved queries" tab and click on > "test-query1" and modify the query and then do save as again - in this case > instead of overriding (updating) the saved query it creates one more copy > with same name. this is creating a confusion which one is the latest one as > there is no timestamps. > One more thing is - while saving the query - if I give existing saved query > name then also it is creating one more copy with same name. > In Hive view1.5 - it overrides the query name with note saying as "Saving > will overwrite previously saved query" . -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22094) Install Wizard: refactor stack versions step
[ https://issues.apache.org/jira/browse/AMBARI-22094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16185993#comment-16185993 ] Hudson commented on AMBARI-22094: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8169 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8169/]) AMBARI-22094 Install Wizard: refactor stack versions step. (atkach) (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f5f888cd7e7297e514537ce4754397590a0dc62f]) * (edit) ambari-web/app/controllers/installer.js * (edit) ambari-web/app/styles/stack_versions.less * (edit) ambari-web/test/controllers/installer_test.js > Install Wizard: refactor stack versions step > > > Key: AMBARI-22094 > URL: https://issues.apache.org/jira/browse/AMBARI-22094 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22094.patch > > > Request to fetch stack versions made on each step of Install Wizard. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22083) Wrong Hadoop Home Directory Is Being Picked Up on MAINT/PATCH Upgraded Clusters
[
https://issues.apache.org/jira/browse/AMBARI-22083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-22083:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Wrong Hadoop Home Directory Is Being Picked Up on MAINT/PATCH Upgraded
> Clusters
> ---
>
> Key: AMBARI-22083
> URL: https://issues.apache.org/jira/browse/AMBARI-22083
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-22083.patch
>
>
> STR:
> - Install HDP 2.6.0.0 with HDFS and YARN/MapR
> - Perform a MAINT upgrade of HDFS to 2.6.3.0
> - Stop all services
> - Restart all services
> The following is observed:
> - {{/usr/hdp/current/hadoop-client -> /usr/hdp/2.6.0.0/hadoop}}
> - HDFS picks up 2.6.0.0
> - YARN/MapR pick up 2.6.0.0
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22083) Wrong Hadoop Home Directory Is Being Picked Up on MAINT/PATCH Upgraded Clusters
[ https://issues.apache.org/jira/browse/AMBARI-22083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16186017#comment-16186017 ] Hudson commented on AMBARI-22083: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #306 (See [https://builds.apache.org/job/Ambari-branch-2.6/306/]) AMBARI-22083 - Wrong Hadoop Home Directory Is Being Picked Up on (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=5433e479260dc9e13aacae1ea9edb9c29d6b96cb]) * (edit) ambari-server/src/test/python/stacks/2.5/SPARK/test_spark_livy.py * (edit) ambari-server/src/test/python/stacks/2.3/SPARK/test_spark_thrift_server.py * (edit) ambari-server/src/test/python/stacks/2.5/configs/ranger-kms-secured.json * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/HeartbeatMonitor.java * (edit) ambari-common/src/main/python/resource_management/libraries/functions/component_version.py * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/status_params.py * (edit) ambari-server/src/test/python/stacks/2.5/RANGER_KMS/test_kms_server.py * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.0/hooks/before-START/scripts/params.py * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.0/hooks/before-ANY/scripts/params.py * (edit) ambari-server/src/test/python/stacks/2.0.6/HIVE/test_hive_service_check.py * (edit) ambari-server/src/test/python/stacks/2.0.6/hooks/before-ANY/test_before_any.py * (edit) ambari-server/src/test/python/stacks/2.0.6/HBASE/test_phoenix_queryserver.py * (edit) ambari-server/src/test/python/stacks/2.0.6/YARN/test_mapreduce2_client.py * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.0/hooks/after-INSTALL/scripts/params.py * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2.5/hooks/after-INSTALL/scripts/params.py * (edit) ambari-server/src/test/python/stacks/2.2/PIG/test_pig_service_check.py * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_upgrade.py * (edit) ambari-common/src/main/python/resource_management/libraries/functions/conf_select.py * (edit) ambari-server/src/test/python/stacks/2.0.6/HBASE/test_hbase_master.py * (edit) ambari-server/src/test/python/stacks/2.0.6/OOZIE/test_oozie_server.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-ANY/scripts/params.py * (edit) ambari-server/src/test/python/stacks/2.0.6/HIVE/test_webhcat_server.py * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2.5/hooks/before-ANY/scripts/params.py * (edit) ambari-server/src/test/python/stacks/2.0.6/HIVE/test_hive_server.py * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.3.ECS/services/ECS/package/scripts/params.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/params.py * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/webhcat.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-ANY/scripts/shared_initialization.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py * (edit) ambari-server/src/test/python/stacks/2.3/MAHOUT/test_mahout_service_check.py * (edit) ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py * (edit) ambari-server/src/test/python/stacks/2.6/SPARK2/test_spark_livy2.py * (edit) ambari-server/src/test/python/stacks/2.0.6/hooks/after-INSTALL/test_after_install.py * (edit) ambari-server/src/test/python/stacks/2.3/MAHOUT/test_mahout_client.py * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2.5/hooks/before-START/scripts/params.py * (edit) ambari-server/src/test/python/stacks/2.0.6/HDFS/test_datanode.py * (edit) ambari-server/src/test/python/stacks/2.0.6/HIVE/test_hive_metastore.py * (edit) ambari-common/src/main/python/resource_management/libraries/functions/stack_select.py * (edit) ambari-server/src/test/python/stacks/2.0.6/YARN/test_historyserver.py * (edit) ambari-server/src/test/python/stacks/2.6/DRUID/test_druid.py * (edit) ambari-server/src/test/python/stacks/2.1/HIVE/test_hive_metastore.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/StatusCommand.java * (edit) ambari-server/src/test/python/stacks/2.0.6/HBASE/test_hbase_client.py * (edit) ambari-server/src/test/python/stacks/2.0.6/OOZIE/test_oozie_service_check.py * (edit) ambari-server/src/test/python/stacks/2.2/SPARK/test_job_history_server.py * (edit) ambari-server/src/test/python/stacks/2.1/FALCON/test_falcon_server.py > Wrong Hadoop Home Directory Is Being Picked Up on MAINT/PATCH Upgraded > Clusters > --- > > Key: AMBARI-22083 > URL: https://
[jira] [Created] (AMBARI-22096) Entries related to hive query are found in RM UI after killing or stopping the execution of the query.
venkat created AMBARI-22096: --- Summary: Entries related to hive query are found in RM UI after killing or stopping the execution of the query. Key: AMBARI-22096 URL: https://issues.apache.org/jira/browse/AMBARI-22096 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.6.0 Reporter: venkat Assignee: venkat Fix For: 2.6.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22089) Hive View 2.0 - Unable to update existing saved queries, view creates new records under saved queries tab
[ https://issues.apache.org/jira/browse/AMBARI-22089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16186030#comment-16186030 ] Hudson commented on AMBARI-22089: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8170 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8170/]) AMBARI-22089. Hive View 2.0 - Unable to update existing saved queries, (pallavkul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d3b67eeab455b01f8f921039b50818a6ded32839]) * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/queries/query.js * (edit) contrib/views/hive20/src/main/resources/ui/yarn.lock * (edit) contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/resources/savedQueries/SavedQueryResourceManager.java > Hive View 2.0 - Unable to update existing saved queries, view creates new > records under saved queries tab > - > > Key: AMBARI-22089 > URL: https://issues.apache.org/jira/browse/AMBARI-22089 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha >Priority: Blocker > Fix For: 2.6.0 > > Attachments: AMBARI-22089_branch-trunk.patch > > > Under the "Saved Queries" section in Ambari, there exist multiple entries for > the query - all entries have the same query name, that is - when changes are > made to a query and subsequently saved, an entry gets created. > However, all entries have the same name - after a while it is not possible to > know which is the latest version. > The "Saved Queries" view does not include a timestamp nor does it > automatically append a version name to the query - thus making it hard for > the user to figure out which is the latest query > Review the screenshot in attached adobe pdf > Issue: In Hive view2.0 - when query is saved it gets saved with the provided > name say "test-query1" - now go to "Saved queries" tab and click on > "test-query1" and modify the query and then do save as again - in this case > instead of overriding (updating) the saved query it creates one more copy > with same name. this is creating a confusion which one is the latest one as > there is no timestamps. > One more thing is - while saving the query - if I give existing saved query > name then also it is creating one more copy with same name. > In Hive view1.5 - it overrides the query name with note saying as "Saving > will overwrite previously saved query" . -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22090) INCORROUT in Hive SELECT-JOIN query using Hive View 2.0
[
https://issues.apache.org/jira/browse/AMBARI-22090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16186031#comment-16186031
]
Hudson commented on AMBARI-22090:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8170 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8170/])
AMBARI-22090. INCORROUT in Hive SELECT-JOIN query using Hive View 2.0
(pallavkul:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=045fc072588632429bc53f6b6a1ee0e0a83179d0])
* (edit)
contrib/views/hive20/src/main/resources/ui/app/components/query-result-table.js
> INCORROUT in Hive SELECT-JOIN query using Hive View 2.0
> ---
>
> Key: AMBARI-22090
> URL: https://issues.apache.org/jira/browse/AMBARI-22090
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Reporter: Pallav Kulshreshtha
>Assignee: Pallav Kulshreshtha
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-22090_branch-trunk.patch
>
>
> TESTCASE:
> DROP TABLE IF EXISTS mydim;
> DROP TABLE IF EXISTS staging;
> CREATE TABLE mydim (
> key int,
> value string,
> status string)
> PARTITIONED BY (last_updated timestamp)
> CLUSTERED BY (key) INTO 5 BUCKETS
> STORED AS ORC TBLPROPERTIES ('transactional'='true');
> INSERT INTO mydim PARTITION(last_updated) VALUES
> (1, 'value1', 'original value', '2017-01-01'),
> (2, 'value2', 'original value', '2017-01-01'),
> (3, 'value3', 'original value', '2017-01-01'),
> (4, 'value4', 'original value', '2017-01-01'),
> (5, 'value5', 'original value', '2017-01-01');
> CREATE TABLE staging(
> key int,
> value string)
> STORED AS ORC;
> INSERT INTO staging VALUES
> (0, 'value0'),
> (1, 'value1_new');
> – INCORROUT: 1value1_new original value 2017-01-01 00:00:00.0
> 1 value1_new
> – EXPECTED: 1 value1 original value 2017-01-01 00:00:00.0 1
> value1_new
> SELECT *
> FROM mydim,staging
> WHERE mydim.key = staging.key;
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22097) Revert option is missing when MAINT type PU is done
Antonenko Alexander created AMBARI-22097: Summary: Revert option is missing when MAINT type PU is done Key: AMBARI-22097 URL: https://issues.apache.org/jira/browse/AMBARI-22097 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.6.0 Reporter: Antonenko Alexander Priority: Critical Fix For: 2.6.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22097) Revert option is missing when MAINT type PU is done
[ https://issues.apache.org/jira/browse/AMBARI-22097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16186075#comment-16186075 ] Antonenko Alexander commented on AMBARI-22097: -- Task is actual only for 2.6 version. Manually tested > Revert option is missing when MAINT type PU is done > --- > > Key: AMBARI-22097 > URL: https://issues.apache.org/jira/browse/AMBARI-22097 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22097.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22097) Revert option is missing when MAINT type PU is done
[ https://issues.apache.org/jira/browse/AMBARI-22097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22097: - Attachment: AMBARI-22097.patch > Revert option is missing when MAINT type PU is done > --- > > Key: AMBARI-22097 > URL: https://issues.apache.org/jira/browse/AMBARI-22097 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22097.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22097) Revert option is missing when MAINT type PU is done
[ https://issues.apache.org/jira/browse/AMBARI-22097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22097: - Assignee: Antonenko Alexander Status: Patch Available (was: Open) > Revert option is missing when MAINT type PU is done > --- > > Key: AMBARI-22097 > URL: https://issues.apache.org/jira/browse/AMBARI-22097 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22097.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22096) Entries related to hive query are found in RM UI after killing or stopping the execution of the query.
[ https://issues.apache.org/jira/browse/AMBARI-22096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-22096: Attachment: AMBARI-22096-trunk.patch > Entries related to hive query are found in RM UI after killing or stopping > the execution of the query. > -- > > Key: AMBARI-22096 > URL: https://issues.apache.org/jira/browse/AMBARI-22096 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.6.0 > > Attachments: AMBARI-22096-trunk.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22097) Revert option is missing when MAINT type PU is done
[ https://issues.apache.org/jira/browse/AMBARI-22097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16186090#comment-16186090 ] Aleksandr Kovalenko commented on AMBARI-22097: -- +1 for the patch > Revert option is missing when MAINT type PU is done > --- > > Key: AMBARI-22097 > URL: https://issues.apache.org/jira/browse/AMBARI-22097 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22097.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22097) Revert option is missing when MAINT type PU is done
[ https://issues.apache.org/jira/browse/AMBARI-22097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22097: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.6 > Revert option is missing when MAINT type PU is done > --- > > Key: AMBARI-22097 > URL: https://issues.apache.org/jira/browse/AMBARI-22097 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22097.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22097) Revert option is missing when MAINT type PU is done
[ https://issues.apache.org/jira/browse/AMBARI-22097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16186137#comment-16186137 ] Hudson commented on AMBARI-22097: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #307 (See [https://builds.apache.org/job/Ambari-branch-2.6/307/]) AMBARI-22097. Revert option is missing when MAINT type PU is done (aantonenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=312baa26ddbb9b405dd2f317d8534c805adf0af2]) * (edit) ambari-web/test/views/main/admin/stack_upgrade/upgrade_version_box_view_test.js * (edit) ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_box_view.js > Revert option is missing when MAINT type PU is done > --- > > Key: AMBARI-22097 > URL: https://issues.apache.org/jira/browse/AMBARI-22097 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22097.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22098) UI Change: Rename "Rerun Checks" button to "Rerun Pre-Upgrade Checks"
Antonenko Alexander created AMBARI-22098: Summary: UI Change: Rename "Rerun Checks" button to "Rerun Pre-Upgrade Checks" Key: AMBARI-22098 URL: https://issues.apache.org/jira/browse/AMBARI-22098 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.6.0 Reporter: Antonenko Alexander Priority: Critical Fix For: 2.6.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-22098) UI Change: Rename "Rerun Checks" button to "Rerun Pre-Upgrade Checks"
[ https://issues.apache.org/jira/browse/AMBARI-22098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-22098: Assignee: Antonenko Alexander > UI Change: Rename "Rerun Checks" button to "Rerun Pre-Upgrade Checks" > - > > Key: AMBARI-22098 > URL: https://issues.apache.org/jira/browse/AMBARI-22098 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22098.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22098) UI Change: Rename "Rerun Checks" button to "Rerun Pre-Upgrade Checks"
[ https://issues.apache.org/jira/browse/AMBARI-22098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22098: - Attachment: AMBARI-22098.patch > UI Change: Rename "Rerun Checks" button to "Rerun Pre-Upgrade Checks" > - > > Key: AMBARI-22098 > URL: https://issues.apache.org/jira/browse/AMBARI-22098 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22098.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22098) UI Change: Rename "Rerun Checks" button to "Rerun Pre-Upgrade Checks"
[ https://issues.apache.org/jira/browse/AMBARI-22098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22098: - Status: Patch Available (was: Open) > UI Change: Rename "Rerun Checks" button to "Rerun Pre-Upgrade Checks" > - > > Key: AMBARI-22098 > URL: https://issues.apache.org/jira/browse/AMBARI-22098 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22098.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22098) UI Change: Rename "Rerun Checks" button to "Rerun Pre-Upgrade Checks"
[
https://issues.apache.org/jira/browse/AMBARI-22098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16186156#comment-16186156
]
Hadoop QA commented on AMBARI-22098:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12889730/AMBARI-22098.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/12389//console
This message is automatically generated.
> UI Change: Rename "Rerun Checks" button to "Rerun Pre-Upgrade Checks"
> -
>
> Key: AMBARI-22098
> URL: https://issues.apache.org/jira/browse/AMBARI-22098
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-22098.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22098) UI Change: Rename "Rerun Checks" button to "Rerun Pre-Upgrade Checks"
[ https://issues.apache.org/jira/browse/AMBARI-22098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16186161#comment-16186161 ] Aleksandr Kovalenko commented on AMBARI-22098: -- +1 for the patch > UI Change: Rename "Rerun Checks" button to "Rerun Pre-Upgrade Checks" > - > > Key: AMBARI-22098 > URL: https://issues.apache.org/jira/browse/AMBARI-22098 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22098.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22098) UI Change: Rename "Rerun Checks" button to "Rerun Pre-Upgrade Checks"
[ https://issues.apache.org/jira/browse/AMBARI-22098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22098: - Status: In Progress (was: Patch Available) > UI Change: Rename "Rerun Checks" button to "Rerun Pre-Upgrade Checks" > - > > Key: AMBARI-22098 > URL: https://issues.apache.org/jira/browse/AMBARI-22098 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22098.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22098) UI Change: Rename "Rerun Checks" button to "Rerun Pre-Upgrade Checks"
[ https://issues.apache.org/jira/browse/AMBARI-22098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22098: - Attachment: AMBARI-22098.patch > UI Change: Rename "Rerun Checks" button to "Rerun Pre-Upgrade Checks" > - > > Key: AMBARI-22098 > URL: https://issues.apache.org/jira/browse/AMBARI-22098 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22098.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22098) UI Change: Rename "Rerun Checks" button to "Rerun Pre-Upgrade Checks"
[ https://issues.apache.org/jira/browse/AMBARI-22098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22098: - Attachment: (was: AMBARI-22098.patch) > UI Change: Rename "Rerun Checks" button to "Rerun Pre-Upgrade Checks" > - > > Key: AMBARI-22098 > URL: https://issues.apache.org/jira/browse/AMBARI-22098 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22098.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22098) UI Change: Rename "Rerun Checks" button to "Rerun Pre-Upgrade Checks"
[ https://issues.apache.org/jira/browse/AMBARI-22098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22098: - Attachment: AMBARI-22098.patch > UI Change: Rename "Rerun Checks" button to "Rerun Pre-Upgrade Checks" > - > > Key: AMBARI-22098 > URL: https://issues.apache.org/jira/browse/AMBARI-22098 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22098.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22098) UI Change: Rename "Rerun Checks" button to "Rerun Pre-Upgrade Checks"
[ https://issues.apache.org/jira/browse/AMBARI-22098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22098: - Attachment: (was: AMBARI-22098.patch) > UI Change: Rename "Rerun Checks" button to "Rerun Pre-Upgrade Checks" > - > > Key: AMBARI-22098 > URL: https://issues.apache.org/jira/browse/AMBARI-22098 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22098.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (AMBARI-22098) UI Change: Rename "Rerun Checks" button to "Rerun Pre-Upgrade Checks"
[ https://issues.apache.org/jira/browse/AMBARI-22098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16186181#comment-16186181 ] Antonenko Alexander edited comment on AMBARI-22098 at 9/29/17 6:19 PM: --- Manually tested. Committed to branch-2.6 and trunk was (Author: aantonenko): Committed to branch-2.6 and trunk > UI Change: Rename "Rerun Checks" button to "Rerun Pre-Upgrade Checks" > - > > Key: AMBARI-22098 > URL: https://issues.apache.org/jira/browse/AMBARI-22098 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22098.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-22098) UI Change: Rename "Rerun Checks" button to "Rerun Pre-Upgrade Checks"
[ https://issues.apache.org/jira/browse/AMBARI-22098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander resolved AMBARI-22098. -- Resolution: Fixed Committed to branch-2.6 and trunk > UI Change: Rename "Rerun Checks" button to "Rerun Pre-Upgrade Checks" > - > > Key: AMBARI-22098 > URL: https://issues.apache.org/jira/browse/AMBARI-22098 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22098.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22099) Patch Upgrade UI Change: Exclamation Icon's Center shouldn't be transparent
Antonenko Alexander created AMBARI-22099: Summary: Patch Upgrade UI Change: Exclamation Icon's Center shouldn't be transparent Key: AMBARI-22099 URL: https://issues.apache.org/jira/browse/AMBARI-22099 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.6.0 Reporter: Antonenko Alexander Priority: Critical Fix For: 2.6.0 The exclamation icon we use has a transparent center, need to use white bg. Otherwise the background page elements show through and make it look odd. Also we need to double check the placement in some modals as the placement of the icon is off. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-22099) Patch Upgrade UI Change: Exclamation Icon's Center shouldn't be transparent
[ https://issues.apache.org/jira/browse/AMBARI-22099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-22099: Assignee: Antonenko Alexander > Patch Upgrade UI Change: Exclamation Icon's Center shouldn't be transparent > --- > > Key: AMBARI-22099 > URL: https://issues.apache.org/jira/browse/AMBARI-22099 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > > The exclamation icon we use has a transparent center, need to use white bg. > Otherwise the background page elements show through and make it look odd. > Also we need to double check the placement in some modals as the placement of > the icon is off. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22099) Patch Upgrade UI Change: Exclamation Icon's Center shouldn't be transparent
[ https://issues.apache.org/jira/browse/AMBARI-22099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22099: - Attachment: AMBARI-22099.patch > Patch Upgrade UI Change: Exclamation Icon's Center shouldn't be transparent > --- > > Key: AMBARI-22099 > URL: https://issues.apache.org/jira/browse/AMBARI-22099 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22099.patch > > > The exclamation icon we use has a transparent center, need to use white bg. > Otherwise the background page elements show through and make it look odd. > Also we need to double check the placement in some modals as the placement of > the icon is off. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22099) Patch Upgrade UI Change: Exclamation Icon's Center shouldn't be transparent
[ https://issues.apache.org/jira/browse/AMBARI-22099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16186210#comment-16186210 ] Aleksandr Kovalenko commented on AMBARI-22099: -- +1 for the patch > Patch Upgrade UI Change: Exclamation Icon's Center shouldn't be transparent > --- > > Key: AMBARI-22099 > URL: https://issues.apache.org/jira/browse/AMBARI-22099 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22099.patch, AMBARI-22099_trunk.patch > > > The exclamation icon we use has a transparent center, need to use white bg. > Otherwise the background page elements show through and make it look odd. > Also we need to double check the placement in some modals as the placement of > the icon is off. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22099) Patch Upgrade UI Change: Exclamation Icon's Center shouldn't be transparent
[ https://issues.apache.org/jira/browse/AMBARI-22099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22099: - Attachment: AMBARI-22099_trunk.patch > Patch Upgrade UI Change: Exclamation Icon's Center shouldn't be transparent > --- > > Key: AMBARI-22099 > URL: https://issues.apache.org/jira/browse/AMBARI-22099 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22099.patch, AMBARI-22099_trunk.patch > > > The exclamation icon we use has a transparent center, need to use white bg. > Otherwise the background page elements show through and make it look odd. > Also we need to double check the placement in some modals as the placement of > the icon is off. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22099) Patch Upgrade UI Change: Exclamation Icon's Center shouldn't be transparent
[ https://issues.apache.org/jira/browse/AMBARI-22099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22099: - Attachment: (was: AMBARI-22099_trunk.patch) > Patch Upgrade UI Change: Exclamation Icon's Center shouldn't be transparent > --- > > Key: AMBARI-22099 > URL: https://issues.apache.org/jira/browse/AMBARI-22099 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22099.patch > > > The exclamation icon we use has a transparent center, need to use white bg. > Otherwise the background page elements show through and make it look odd. > Also we need to double check the placement in some modals as the placement of > the icon is off. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22099) Patch Upgrade UI Change: Exclamation Icon's Center shouldn't be transparent
[ https://issues.apache.org/jira/browse/AMBARI-22099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16186216#comment-16186216 ] Antonenko Alexander commented on AMBARI-22099: -- Patches are for styling only, manually tested > Patch Upgrade UI Change: Exclamation Icon's Center shouldn't be transparent > --- > > Key: AMBARI-22099 > URL: https://issues.apache.org/jira/browse/AMBARI-22099 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22099.patch, AMBARI-22099_trunk.patch > > > The exclamation icon we use has a transparent center, need to use white bg. > Otherwise the background page elements show through and make it look odd. > Also we need to double check the placement in some modals as the placement of > the icon is off. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22099) Patch Upgrade UI Change: Exclamation Icon's Center shouldn't be transparent
[ https://issues.apache.org/jira/browse/AMBARI-22099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22099: - Attachment: AMBARI-22099_trunk.patch > Patch Upgrade UI Change: Exclamation Icon's Center shouldn't be transparent > --- > > Key: AMBARI-22099 > URL: https://issues.apache.org/jira/browse/AMBARI-22099 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22099.patch, AMBARI-22099_trunk.patch > > > The exclamation icon we use has a transparent center, need to use white bg. > Otherwise the background page elements show through and make it look odd. > Also we need to double check the placement in some modals as the placement of > the icon is off. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-22099) Patch Upgrade UI Change: Exclamation Icon's Center shouldn't be transparent
[ https://issues.apache.org/jira/browse/AMBARI-22099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander resolved AMBARI-22099. -- Resolution: Fixed Committed to branch-2.6 and trunk > Patch Upgrade UI Change: Exclamation Icon's Center shouldn't be transparent > --- > > Key: AMBARI-22099 > URL: https://issues.apache.org/jira/browse/AMBARI-22099 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22099.patch, AMBARI-22099_trunk.patch > > > The exclamation icon we use has a transparent center, need to use white bg. > Otherwise the background page elements show through and make it look odd. > Also we need to double check the placement in some modals as the placement of > the icon is off. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22098) UI Change: Rename "Rerun Checks" button to "Rerun Pre-Upgrade Checks"
[ https://issues.apache.org/jira/browse/AMBARI-22098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16186232#comment-16186232 ] Hudson commented on AMBARI-22098: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #308 (See [https://builds.apache.org/job/Ambari-branch-2.6/308/]) AMBARI-22098. UI Change: Rename 'Rerun Checks' button to 'Rerun (aantonenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=91f1d523f9022bbfc5fee8b198e270f24b8674ea]) * (edit) ambari-web/app/messages.js > UI Change: Rename "Rerun Checks" button to "Rerun Pre-Upgrade Checks" > - > > Key: AMBARI-22098 > URL: https://issues.apache.org/jira/browse/AMBARI-22098 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22098.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22098) UI Change: Rename "Rerun Checks" button to "Rerun Pre-Upgrade Checks"
[ https://issues.apache.org/jira/browse/AMBARI-22098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16186238#comment-16186238 ] Hudson commented on AMBARI-22098: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8171 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8171/]) AMBARI-22098. UI Change: Rename 'Rerun Checks' button to 'Rerun (aantonenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=510a2620db12e47741e7a00022d66d6bceb283b5]) * (edit) ambari-web/app/messages.js > UI Change: Rename "Rerun Checks" button to "Rerun Pre-Upgrade Checks" > - > > Key: AMBARI-22098 > URL: https://issues.apache.org/jira/browse/AMBARI-22098 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22098.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22099) Patch Upgrade UI Change: Exclamation Icon's Center shouldn't be transparent
[ https://issues.apache.org/jira/browse/AMBARI-22099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16186269#comment-16186269 ] Hudson commented on AMBARI-22099: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #309 (See [https://builds.apache.org/job/Ambari-branch-2.6/309/]) AMBARI-22099. Patch Upgrade UI Change: Exclamation Icon's Center (aantonenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4cd607e8fddaf140f362903bb01280f45ee9f762]) * (edit) ambari-web/app/styles/stack_versions.less > Patch Upgrade UI Change: Exclamation Icon's Center shouldn't be transparent > --- > > Key: AMBARI-22099 > URL: https://issues.apache.org/jira/browse/AMBARI-22099 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22099.patch, AMBARI-22099_trunk.patch > > > The exclamation icon we use has a transparent center, need to use white bg. > Otherwise the background page elements show through and make it look odd. > Also we need to double check the placement in some modals as the placement of > the icon is off. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22099) Patch Upgrade UI Change: Exclamation Icon's Center shouldn't be transparent
[ https://issues.apache.org/jira/browse/AMBARI-22099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16186276#comment-16186276 ] Hudson commented on AMBARI-22099: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8172 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8172/]) AMBARI-22099. Patch Upgrade UI Change: Exclamation Icon's Center (aantonenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f69ccd890bdfd0e4df78fc8c52f8799d7a61b03b]) * (edit) ambari-web/app/styles/stack_versions.less > Patch Upgrade UI Change: Exclamation Icon's Center shouldn't be transparent > --- > > Key: AMBARI-22099 > URL: https://issues.apache.org/jira/browse/AMBARI-22099 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22099.patch, AMBARI-22099_trunk.patch > > > The exclamation icon we use has a transparent center, need to use white bg. > Otherwise the background page elements show through and make it look odd. > Also we need to double check the placement in some modals as the placement of > the icon is off. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22095) Make hooks stack agnostic
[ https://issues.apache.org/jira/browse/AMBARI-22095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-22095: --- Description: - At present hooks are located inside stacks - For all HDP stacks, we use https://github.com/apache/ambari/tree/trunk/ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks - Similarly for all HDF stacks, we use https://github.com/apache/ambari/tree/trunk/contrib/management-packs/hdf-ambari-mpack/src/main/resources/stacks/HDF/2.0/hooks - Any time the HDP hooks are updated, the changes have to be ported to HDF branch. This is a maintenance overhead - In Ambari 3.0 when we move to mpack based operations model, this will be a maint nightmare. *Requirements* # We should look into making hooks stack agnostic. # Hooks should be moved from resources/stacks/HDP/2.0.6/hooks to resources/stack-hooks # Hooks should be entirely config driven # There should be no HDP or HDF specific logic in the hooks (hdp-select, conf-select, hdf-select, hdfconf-select) # There should be no service specific logic in the hooks (for example: hardcoded service user to service group mapping etc. this should be stack driven see: AMBARI-20034). # Any service specific logic that doesn't make sense should be removed and refactored into respective service definitions. was: - At present hooks are located inside stacks - For all HDP stacks, we use https://github.com/apache/ambari/tree/trunk/ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks - Similarly for all HDF stacks, we use https://github.com/hortonworks/hdf_ambari_mp/tree/master/hdf-ambari-mpack/src/main/resources/stacks/HDF/2.0/hooks - Any time the HDP hooks are updated, the changes have to be ported to HDF branch. This is a maintenance overhead - In Ambari 3.0 when we move to mpack based operations model, this will be a maint nightmare. *Requirements* # We should look into making hooks stack agnostic. # Hooks should be moved from resources/stacks/HDP/2.0.6/hooks to resources/stack-hooks # Hooks should be entirely config driven # There should be no HDP or HDF specific logic in the hooks (hdp-select, conf-select, hdf-select, hdfconf-select) # There should be no service specific logic in the hooks (for example: hardcoded service user to service group mapping etc. this should be stack driven see: AMBARI-20034). # Any service specific logic that doesn't make sense should be removed and refactored into respective service definitions. > Make hooks stack agnostic > - > > Key: AMBARI-22095 > URL: https://issues.apache.org/jira/browse/AMBARI-22095 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-22095.patch > > > - At present hooks are located inside stacks > - For all HDP stacks, we use > https://github.com/apache/ambari/tree/trunk/ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks > - Similarly for all HDF stacks, we use > https://github.com/apache/ambari/tree/trunk/contrib/management-packs/hdf-ambari-mpack/src/main/resources/stacks/HDF/2.0/hooks > - Any time the HDP hooks are updated, the changes have to be ported to HDF > branch. This is a maintenance overhead > - In Ambari 3.0 when we move to mpack based operations model, this will be a > maint nightmare. > *Requirements* > # We should look into making hooks stack agnostic. > # Hooks should be moved from resources/stacks/HDP/2.0.6/hooks to > resources/stack-hooks > # Hooks should be entirely config driven > # There should be no HDP or HDF specific logic in the hooks (hdp-select, > conf-select, hdf-select, hdfconf-select) > # There should be no service specific logic in the hooks (for example: > hardcoded service user to service group mapping etc. this should be stack > driven see: AMBARI-20034). > # Any service specific logic that doesn't make sense should be removed and > refactored into respective service definitions. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22068) Remove user to group hardcoded logic in hooks
[ https://issues.apache.org/jira/browse/AMBARI-22068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16186323#comment-16186323 ] Hudson commented on AMBARI-22068: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8173 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8173/]) AMBARI-22068. Additional Fix.Remove user to group hardcoded logic in (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=18fd04f2e3c59b3c741ac0d32083a70739203f70]) * (edit) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-ANY/scripts/params.py > Remove user to group hardcoded logic in hooks > - > > Key: AMBARI-22068 > URL: https://issues.apache.org/jira/browse/AMBARI-22068 > Project: Ambari > Issue Type: Bug > Components: ambari-agent, ambari-server >Affects Versions: 2.5.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi > Fix For: 3.0.0 > > Attachments: AMBARI-22068.patch > > > We added feature to tag a user property with corresponding user-group > properties to which a user should be added. We no longer should need the > hardcoded logic in the hooks adding users to groups. This can be entirely > stack driven after we update the user config properties for all services. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22076) Use A Scoped Repo When Installing stack-tools
[
https://issues.apache.org/jira/browse/AMBARI-22076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16186348#comment-16186348
]
Hudson commented on AMBARI-22076:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #310 (See
[https://builds.apache.org/job/Ambari-branch-2.6/310/])
AMBARI-22076 - Use A Scoped Repo When Installing stack-tools (unit test
(jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=eb89ef0482c55a8de9b67b86bc16074ff4a1e505])
* (edit) ambari-agent/src/test/python/resource_management/TestPackageResource.py
> Use A Scoped Repo When Installing stack-tools
> -
>
> Key: AMBARI-22076
> URL: https://issues.apache.org/jira/browse/AMBARI-22076
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-22076.patch
>
>
> Ambari does not write out repositories with a "priority" attribute since this
> is a plugin and is not guaranteed to be installed. Also, when installing
> packages with versions "in the middle" of two other installed stacks,
> priority would be incorrect as the most recent stack-tools should always be
> used.
> The following is seen when trying to distribute a stack for a patch upgrade:
> {code}
> 2017-09-26 16:28:58,652 - Package Manager failed to install packages. Error:
> Execution of '/usr/bin/yum -d 0 -e 0 -y install hive_2_6_3_1_1' returned 1.
> Error: Package: hadoop_2_6_3_1_1-2.7.3.2.6.3.1-1.x86_64 (HDP-2.6-repo-2)
>Requires: hdp-select >= 2.6.3.1-1
>Installed: hdp-select-2.6.3.0-122.noarch (@HDP-2.6.3.0-122)
>hdp-select = 2.6.3.0-122
> {code}
> The cause of this seems to be that the repository for HDP-2.6-repo-2 does not
> take priority over the existing installed repository for {{hdp-select}}.
> That's actually good - it shouldn't take priority over it arbitrarily.
> However, this means that the {{hdp-select}} which is installed did not get
> taken from {{HDP-2.6-repo-2}}. So, when installing {{hdp-select}}, we should
> scope the install to the repo we are trying to calculate the version for.
> This works because the stack-select tools do not have their package names
> versioned ({{hdp-select}} as opposed to {{hdp-select_x_y_z}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22083) Wrong Hadoop Home Directory Is Being Picked Up on MAINT/PATCH Upgraded Clusters
[ https://issues.apache.org/jira/browse/AMBARI-22083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16186401#comment-16186401 ] Hudson commented on AMBARI-22083: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8174 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8174/]) AMBARI-22083 - Wrong Hadoop Home Directory Is Being Picked Up on (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=31344fff2ddd94923f053d6c9c6b945c299bd5d5]) * (edit) ambari-server/src/test/python/stacks/2.0.6/YARN/test_historyserver.py * (edit) ambari-server/src/test/python/stacks/2.6/ZEPPELIN/test_zeppelin_070.py * (edit) ambari-server/src/test/python/stacks/2.0.6/HBASE/test_hbase_client.py * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_upgrade.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/StatusCommand.java * (edit) ambari-server/src/test/python/stacks/2.6/SPARK2/test_spark_livy2.py * (edit) ambari-server/src/test/python/stacks/2.2/SPARK/test_job_history_server.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/params.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.3.ECS/services/ECS/package/scripts/params.py * (edit) ambari-server/src/test/python/stacks/2.5/ZEPPELIN/test_zeppelin_060.py * (edit) ambari-server/src/test/python/stacks/2.0.6/hooks/before-ANY/test_before_any.py * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py * (edit) ambari-common/src/main/python/resource_management/libraries/functions/stack_select.py * (edit) ambari-server/src/test/python/stacks/2.3/MAHOUT/test_mahout_client.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-ANY/scripts/shared_initialization.py * (edit) ambari-server/src/test/python/stacks/2.1/HIVE/test_hive_metastore.py * (edit) ambari-server/src/test/python/stacks/2.3/SPARK/test_spark_thrift_server.py * (edit) ambari-server/src/test/python/stacks/2.0.6/HIVE/test_hive_metastore.py * (edit) ambari-server/src/test/python/stacks/2.0.6/HIVE/test_webhcat_server.py * (edit) ambari-server/src/test/python/stacks/2.0.6/OOZIE/test_oozie_service_check.py * (edit) ambari-server/src/test/python/stacks/2.2/PIG/test_pig_service_check.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-ANY/scripts/params.py * (edit) ambari-server/src/test/python/stacks/2.1/FALCON/test_falcon_server.py * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/webhcat.py * (edit) ambari-server/src/test/python/stacks/2.3/MAHOUT/test_mahout_service_check.py * (edit) ambari-common/src/main/python/resource_management/libraries/functions/component_version.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py * (edit) ambari-server/src/test/python/stacks/2.0.6/HDFS/test_datanode.py * (edit) ambari-server/src/test/python/stacks/2.0.6/HBASE/test_hbase_master.py * (edit) ambari-server/src/test/python/stacks/2.5/SPARK/test_spark_livy.py * (edit) ambari-server/src/test/python/stacks/2.0.6/YARN/test_mapreduce2_client.py * (edit) ambari-server/src/test/python/stacks/2.0.6/HBASE/test_phoenix_queryserver.py * (edit) ambari-server/src/test/python/stacks/2.0.6/HIVE/test_hive_service_check.py * (edit) ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py * (edit) ambari-server/src/test/python/stacks/2.0.6/OOZIE/test_oozie_server.py * (edit) ambari-common/src/main/python/resource_management/libraries/functions/conf_select.py * (edit) ambari-server/src/test/python/stacks/2.0.6/HIVE/test_hive_server.py * (edit) ambari-server/src/test/python/stacks/2.0.6/hooks/after-INSTALL/test_after_install.py * (edit) ambari-server/src/test/python/stacks/2.5/RANGER_KMS/test_kms_server.py * (edit) ambari-server/src/test/python/stacks/2.6/DRUID/test_druid.py * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/status_params.py * (edit) ambari-server/src/test/python/stacks/2.5/configs/ranger-kms-secured.json AMBARI-22083 - Wrong Hadoop Home Directory Is Being Picked Up on (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b84cbbe7e9a3afffab07da534541b4eb6076d50c]) * (edit) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-ANY/scripts/params.py * (edit) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/after-INSTALL/scripts/params.py * (edit) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-START/scripts/params.py > Wrong Hadoop Home Directory Is Being Picked Up on MAINT/PATCH Upgraded > Clusters > --- > > Key: AMBARI-22083 > URL: https://issues.apache.org/jira/browse/AMBARI-22083 > Project: Ambari >
[jira] [Commented] (AMBARI-22076) Use A Scoped Repo When Installing stack-tools
[
https://issues.apache.org/jira/browse/AMBARI-22076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16186402#comment-16186402
]
Hudson commented on AMBARI-22076:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8174 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8174/])
AMBARI-22076 - Use A Scoped Repo When Installing stack-tools (unit test
(jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d19f0bb7661404ccc72099621e9c2d7c97609d2a])
* (edit) ambari-agent/src/test/python/resource_management/TestPackageResource.py
> Use A Scoped Repo When Installing stack-tools
> -
>
> Key: AMBARI-22076
> URL: https://issues.apache.org/jira/browse/AMBARI-22076
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-22076.patch
>
>
> Ambari does not write out repositories with a "priority" attribute since this
> is a plugin and is not guaranteed to be installed. Also, when installing
> packages with versions "in the middle" of two other installed stacks,
> priority would be incorrect as the most recent stack-tools should always be
> used.
> The following is seen when trying to distribute a stack for a patch upgrade:
> {code}
> 2017-09-26 16:28:58,652 - Package Manager failed to install packages. Error:
> Execution of '/usr/bin/yum -d 0 -e 0 -y install hive_2_6_3_1_1' returned 1.
> Error: Package: hadoop_2_6_3_1_1-2.7.3.2.6.3.1-1.x86_64 (HDP-2.6-repo-2)
>Requires: hdp-select >= 2.6.3.1-1
>Installed: hdp-select-2.6.3.0-122.noarch (@HDP-2.6.3.0-122)
>hdp-select = 2.6.3.0-122
> {code}
> The cause of this seems to be that the repository for HDP-2.6-repo-2 does not
> take priority over the existing installed repository for {{hdp-select}}.
> That's actually good - it shouldn't take priority over it arbitrarily.
> However, this means that the {{hdp-select}} which is installed did not get
> taken from {{HDP-2.6-repo-2}}. So, when installing {{hdp-select}}, we should
> scope the install to the repo we are trying to calculate the version for.
> This works because the stack-select tools do not have their package names
> versioned ({{hdp-select}} as opposed to {{hdp-select_x_y_z}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22100) Devdeploy: HiveServer2 Interactive Start failed
Madhuvanthi Radhakrishnan created AMBARI-22100:
--
Summary: Devdeploy: HiveServer2 Interactive Start failed
Key: AMBARI-22100
URL: https://issues.apache.org/jira/browse/AMBARI-22100
Project: Ambari
Issue Type: Bug
Affects Versions: 2.6.0
Reporter: Madhuvanthi Radhakrishnan
Assignee: Madhuvanthi Radhakrishnan
Fix For: 2.6.0
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py",
line 612, in
HiveServerInteractive().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 325, in execute
method(env)
File
"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py",
line 103, in start
import params
File
"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/params.py",
line 27, in
from params_linux import *
File
"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py",
line 240, in
raise Exception("hadoop.security.credential.provider.path property should
be set")
Exception: hadoop.security.credential.provider.path property should be set
Due to same temp paths for service components.
Change /var/lib/ambari-agent/cred/ to
/var/lib/ambari-agent/cred/
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22101) After enabling NameNode HA, Yarn and MapReduce2 shows stale configs
Ishan Bhatt created AMBARI-22101: Summary: After enabling NameNode HA, Yarn and MapReduce2 shows stale configs Key: AMBARI-22101 URL: https://issues.apache.org/jira/browse/AMBARI-22101 Project: Ambari Issue Type: Bug Components: ambari-web Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: trunk, 2.6.0 It seems "Stop Required services" for NameNode HA wizard is not stopping all services instead just HDFS service. This looks to be undesired behavior -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22101) After enabling NameNode HA, Yarn and MapReduce2 shows stale configs
[ https://issues.apache.org/jira/browse/AMBARI-22101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-22101: - Attachment: AMBARI-22101_branch-2.6.patch > After enabling NameNode HA, Yarn and MapReduce2 shows stale configs > --- > > Key: AMBARI-22101 > URL: https://issues.apache.org/jira/browse/AMBARI-22101 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-22101_branch-2.6.patch > > > It seems "Stop Required services" for NameNode HA wizard is not stopping all > services instead just HDFS service. > This looks to be undesired behavior -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22101) After enabling NameNode HA, Yarn and MapReduce2 shows stale configs
[ https://issues.apache.org/jira/browse/AMBARI-22101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-22101: - Attachment: AMBARI-22101.patch > After enabling NameNode HA, Yarn and MapReduce2 shows stale configs > --- > > Key: AMBARI-22101 > URL: https://issues.apache.org/jira/browse/AMBARI-22101 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-22101_branch-2.6.patch, AMBARI-22101.patch > > > It seems "Stop Required services" for NameNode HA wizard is not stopping all > services instead just HDFS service. > This looks to be undesired behavior -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22100) Devdeploy: HiveServer2 Interactive Start failed
[
https://issues.apache.org/jira/browse/AMBARI-22100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhuvanthi Radhakrishnan updated AMBARI-22100:
---
Attachment: AMBARI-22100.patch
> Devdeploy: HiveServer2 Interactive Start failed
> ---
>
> Key: AMBARI-22100
> URL: https://issues.apache.org/jira/browse/AMBARI-22100
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
> Fix For: 2.6.0
>
> Attachments: AMBARI-22100.patch
>
>
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py",
> line 612, in
> HiveServerInteractive().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 325, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py",
> line 103, in start
> import params
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/params.py",
> line 27, in
> from params_linux import *
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py",
> line 240, in
> raise Exception("hadoop.security.credential.provider.path property should
> be set")
> Exception: hadoop.security.credential.provider.path property should be set
> Due to same temp paths for service components.
> Change /var/lib/ambari-agent/cred/ to
> /var/lib/ambari-agent/cred/
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21430) Allow Multiple Versions of Stack Tools to Co-Exist
[
https://issues.apache.org/jira/browse/AMBARI-21430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16186800#comment-16186800
]
Hudson commented on AMBARI-21430:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.6 #311 (See
[https://builds.apache.org/job/Ambari-branch-2.6/311/])
AMBARI-21430 - Allow Multiple Versions of Stack Tools to Co-Exist (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=27efa3f1abe7fd8968d3c7b8e103dcc327e9f1ad])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProvider.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProviderTest.java
> Allow Multiple Versions of Stack Tools to Co-Exist
> --
>
> Key: AMBARI-21430
> URL: https://issues.apache.org/jira/browse/AMBARI-21430
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21430.patch
>
>
> Currently, the stack tools:
> - {{cluster-env/stack_features}}
> - {{cluster-env/stack_tools}}
> - {{cluster-env/stack_root}}
> Are bound to the {{cluster-env}} without any sort of scoping. This prevents 2
> sets of stack tools from co-existing. Although Ambari doesn't support more
> than a single stack in 2.x, we do support upgrades from one stack vendor to
> another. Therefore, we need this support to send the right tools on the
> commands.
> This will involve the following work:
> - Changing the existing stack tools/features/root to have a stack name as the
> key in the JSON
> - Altering the existing {{cluster-env}} tools on upgrade
> - Ensuring that the stack tools/features for a repository's stack exist when
> distributing that stack
> - Changing any Python code which references the stack tools (stack_tools.py,
> alerts, etc)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22091) Hive view2.0 Jobs worksheets doesn't have hyperlink whereas view1.5 History worksheets had hyperlinks pointing to fetched results
[ https://issues.apache.org/jira/browse/AMBARI-22091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16186877#comment-16186877 ] Hudson commented on AMBARI-22091: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.6 #312 (See [https://builds.apache.org/job/Ambari-branch-2.6/312/]) AMBARI-22091.Hive view2.0 Jobs worksheets doesn't have hyperlink whereas (venkatasairam.lanka: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9e34f40009cd60fd8ca3ffdcc992bda4352170ae]) * (edit) contrib/views/hive20/src/main/resources/ui/app/templates/components/jobs-browser.hbs * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/queries/query.js * (edit) contrib/views/hive20/src/main/resources/ui/app/templates/jobs.hbs * (edit) contrib/views/hive20/src/main/resources/ui/app/components/jobs-browser.js * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/queries/new.js * (edit) contrib/views/hive20/src/main/resources/ui/app/components/job-item.js * (edit) contrib/views/hive20/src/main/resources/ui/app/styles/app.scss * (edit) contrib/views/hive20/src/main/resources/ui/app/templates/components/job-item.hbs * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/jobs.js > Hive view2.0 Jobs worksheets doesn't have hyperlink whereas view1.5 History > worksheets had hyperlinks pointing to fetched results > - > > Key: AMBARI-22091 > URL: https://issues.apache.org/jira/browse/AMBARI-22091 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.6.0 > > Attachments: AMBARI-22091.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
