[jira] [Commented] (AMBARI-22505) Kafka service check fails when using a non-root user in kerberized environment
[
https://issues.apache.org/jira/browse/AMBARI-22505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16263638#comment-16263638
]
Hadoop QA commented on AMBARI-22505:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898964/AMBARI-22505_branch2.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/12726//console
This message is automatically generated.
> Kafka service check fails when using a non-root user in kerberized environment
> --
>
> Key: AMBARI-22505
> URL: https://issues.apache.org/jira/browse/AMBARI-22505
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.6.0
>Reporter: Yolanda M. Davis
>Assignee: Yolanda M. Davis
> Attachments: AMBARI-22505.patch, AMBARI-22505_branch2.6.patch
>
>
> When Ambari agents are configured to run with a non-root user, if kerberos is
> enabled, Kafka service check experiences errors in the logs which indicate
> that the check is attempting to create a topic that already exists. However
> the true failure, which isn't in the logs but captured in an error variable,
> demonstrates the culprit (see below):
> [2017-11-22 05:12:57,029] WARN SASL configuration failed:
> javax.security.auth.login.LoginException: No password provided Will continue
> connection to Zookeeper server without SASL authentication, if Zookeeper
> server allows it. (org.apache.zookeeper.ClientCnxn)
> Exception in thread "main"
> org.I0Itec.zkclient.exception.ZkAuthFailedException: Authentication failure
> at org.I0Itec.zkclient.ZkClient.waitForKeeperState(ZkClient.java:947)
> at org.I0Itec.zkclient.ZkClient.waitUntilConnected(ZkClient.java:924)
> at org.I0Itec.zkclient.ZkClient.connect(ZkClient.java:1231)
> at org.I0Itec.zkclient.ZkClient.(ZkClient.java:157)
> at org.I0Itec.zkclient.ZkClient.(ZkClient.java:131)
> at kafka.utils.ZkUtils$.createZkClientAndConnection(ZkUtils.scala:115)
> at kafka.utils.ZkUtils$.apply(ZkUtils.scala:97)
> at kafka.admin.TopicCommand$.main(TopicCommand.scala:56)
> at kafka.admin.TopicCommand.main(TopicCommand.scala)
> This occurs because a prior check to see if the topic exists is not executed
> as the kafka user. A subsequent call to create the topic does execute as that
> user. The first check should also execute as the kakfa user. Also Ambari
> should immediately raise a failure if an error occurs during the topic check
> and show that error in the logs.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22503) Log Search UI: refine time range picker
[
https://issues.apache.org/jira/browse/AMBARI-22503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16263486#comment-16263486
]
Hadoop QA commented on AMBARI-22503:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898903/AMBARI-22503.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/12724//console
This message is automatically generated.
> Log Search UI: refine time range picker
> ---
>
> Key: AMBARI-22503
> URL: https://issues.apache.org/jira/browse/AMBARI-22503
> 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-22503.patch
>
>
> # Values of time picker inputs should be synced with the selected time range.
> # Label of toggle button should contain 'Custom' text when custom range is
> specified with the time pickers.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22485) Allow Ambari to support non-kerberos SASL mechanisms for Kafka
[
https://issues.apache.org/jira/browse/AMBARI-22485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16263220#comment-16263220
]
Hadoop QA commented on AMBARI-22485:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898922/AMBARI-22485.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12723//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12723//console
This message is automatically generated.
> Allow Ambari to support non-kerberos SASL mechanisms for Kafka
> --
>
> Key: AMBARI-22485
> URL: https://issues.apache.org/jira/browse/AMBARI-22485
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.6.0
>Reporter: Yolanda M. Davis
>Assignee: Yolanda M. Davis
> Attachments: AMBARI-22485.patch, AMBARI-22485_branch-2.6.patch
>
>
> Currently AMBARI support's SASL and SSL as the security options for Kafka.
> Within SASL Ambari only supports GSSAPI(kerberos) only. Kafka supports other
> mechanisms such as plain, md5 etc.. This allows users to plug in their LDAP
> system into Kafka.
> Also another important option is SASL_SSL.
> We need to expose necessary configs in Ambari to enable these mechanisms for
> users.
> Ambari should allow users to not only configure Kafka for non-kerberos based
> SASL mechanisms, but also ensure that jaas configuration files are written
> when these options are provided (as opposed to only writing those files when
> kerberos has been enabled)..
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22503) Log Search UI: refine time range picker
[
https://issues.apache.org/jira/browse/AMBARI-22503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16263090#comment-16263090
]
Hadoop QA commented on AMBARI-22503:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898903/AMBARI-22503.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12722//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12722//console
This message is automatically generated.
> Log Search UI: refine time range picker
> ---
>
> Key: AMBARI-22503
> URL: https://issues.apache.org/jira/browse/AMBARI-22503
> 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-22503.patch
>
>
> # Values of time picker inputs should be synced with the selected time range.
> # Label of toggle button should contain 'Custom' text when custom range is
> specified with the time pickers.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22503) Log Search UI: refine time range picker
[
https://issues.apache.org/jira/browse/AMBARI-22503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16263072#comment-16263072
]
Hadoop QA commented on AMBARI-22503:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898903/AMBARI-22503.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12721//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12721//console
This message is automatically generated.
> Log Search UI: refine time range picker
> ---
>
> Key: AMBARI-22503
> URL: https://issues.apache.org/jira/browse/AMBARI-22503
> 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-22503.patch
>
>
> # Values of time picker inputs should be synced with the selected time range.
> # Label of toggle button should contain 'Custom' text when custom range is
> specified with the time pickers.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22503) Log Search UI: refine time range picker
[
https://issues.apache.org/jira/browse/AMBARI-22503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16263046#comment-16263046
]
Hadoop QA commented on AMBARI-22503:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898903/AMBARI-22503.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12720//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12720//console
This message is automatically generated.
> Log Search UI: refine time range picker
> ---
>
> Key: AMBARI-22503
> URL: https://issues.apache.org/jira/browse/AMBARI-22503
> 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-22503.patch
>
>
> # Values of time picker inputs should be synced with the selected time range.
> # Label of toggle button should contain 'Custom' text when custom range is
> specified with the time pickers.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22502) Workflow Manager View - FS node will overwrite internal commands and replace them with blank "move" commands when reopening the node
[
https://issues.apache.org/jira/browse/AMBARI-22502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16263030#comment-16263030
]
Hadoop QA commented on AMBARI-22502:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898897/AMBARI-22502-trunk.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12719//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12719//console
This message is automatically generated.
> Workflow Manager View - FS node will overwrite internal commands and replace
> them with blank "move" commands when reopening the node
>
>
> Key: AMBARI-22502
> URL: https://issues.apache.org/jira/browse/AMBARI-22502
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Reporter: venkat
>Assignee: venkat
> Fix For: 2.6.1
>
> Attachments: AMBARI-22502-trunk.patch
>
>
> STEPS TO REPRODUCE:
> 1. Create workflow with FS node
> 2. Add a HDFS "Move" command
> 3. Save
> 4. Exit the browser, clear cache and log back in
> 5. Select Recent
> 6. Select Saved workflow
> 7. Open workflow and check FS node
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22501) stack advisor error while adding Druid service
[
https://issues.apache.org/jira/browse/AMBARI-22501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16263019#comment-16263019
]
Hadoop QA commented on AMBARI-22501:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898884/AMBARI-22501_trunk.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12718//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12718//console
This message is automatically generated.
> stack advisor error while adding Druid service
> --
>
> Key: AMBARI-22501
> URL: https://issues.apache.org/jira/browse/AMBARI-22501
> Project: Ambari
> Issue Type: Bug
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.6.1
>
> Attachments: AMBARI-22501.patch, AMBARI-22501_trunk.patch
>
>
> On adding Druid service via Ambari below exception was thrown
> {code}
> 14 Nov 2017 05:48:06,083 ERROR [ambari-client-thread-44539]
> BaseManagementHandler:61 - Caught a system exception while attempting to
> create a resource: Stack Advisor reported an error: UnboundLocalError: local
> variable 'host' referenced before assignment
> StdOut file: /var/run/ambari-server/stack-recommendations/44/stackadvisor.out
> StdErr file: /var/run/ambari-server/stack-recommendations/44/stackadvisor.err
> org.apache.ambari.server.controller.spi.SystemException: Stack Advisor
> reported an error: UnboundLocalError: local variable 'host' referenced before
> assignment
> StdOut file: /var/run/ambari-server/stack-recommendations/44/stackadvisor.out
> StdErr file: /var/run/ambari-server/stack-recommendations/44/stackadvisor.err
> at
> org.apache.ambari.server.controller.internal.RecommendationResourceProvider.createResources(RecommendationResourceProvider.java:98)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298)
> at
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
> at
> org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37)
> at
> org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
> at
> org.apache.ambari.server.api.services.RecommendationService.getRecommendation(RecommendationService.java:59)
> at sun.reflect.GeneratedMethodAccessor1179.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
> at
>
[jira] [Commented] (AMBARI-22501) stack advisor error while adding Druid service
[
https://issues.apache.org/jira/browse/AMBARI-22501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262980#comment-16262980
]
Hadoop QA commented on AMBARI-22501:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898884/AMBARI-22501_trunk.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12717//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12717//console
This message is automatically generated.
> stack advisor error while adding Druid service
> --
>
> Key: AMBARI-22501
> URL: https://issues.apache.org/jira/browse/AMBARI-22501
> Project: Ambari
> Issue Type: Bug
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.6.1
>
> Attachments: AMBARI-22501.patch, AMBARI-22501_trunk.patch
>
>
> On adding Druid service via Ambari below exception was thrown
> {code}
> 14 Nov 2017 05:48:06,083 ERROR [ambari-client-thread-44539]
> BaseManagementHandler:61 - Caught a system exception while attempting to
> create a resource: Stack Advisor reported an error: UnboundLocalError: local
> variable 'host' referenced before assignment
> StdOut file: /var/run/ambari-server/stack-recommendations/44/stackadvisor.out
> StdErr file: /var/run/ambari-server/stack-recommendations/44/stackadvisor.err
> org.apache.ambari.server.controller.spi.SystemException: Stack Advisor
> reported an error: UnboundLocalError: local variable 'host' referenced before
> assignment
> StdOut file: /var/run/ambari-server/stack-recommendations/44/stackadvisor.out
> StdErr file: /var/run/ambari-server/stack-recommendations/44/stackadvisor.err
> at
> org.apache.ambari.server.controller.internal.RecommendationResourceProvider.createResources(RecommendationResourceProvider.java:98)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298)
> at
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
> at
> org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37)
> at
> org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
> at
> org.apache.ambari.server.api.services.RecommendationService.getRecommendation(RecommendationService.java:59)
> at sun.reflect.GeneratedMethodAccessor1179.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
> at
>
[jira] [Commented] (AMBARI-22501) stack advisor error while adding Druid service
[
https://issues.apache.org/jira/browse/AMBARI-22501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262901#comment-16262901
]
Hadoop QA commented on AMBARI-22501:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898884/AMBARI-22501_trunk.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12716//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12716//console
This message is automatically generated.
> stack advisor error while adding Druid service
> --
>
> Key: AMBARI-22501
> URL: https://issues.apache.org/jira/browse/AMBARI-22501
> Project: Ambari
> Issue Type: Bug
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.6.1
>
> Attachments: AMBARI-22501.patch, AMBARI-22501_trunk.patch
>
>
> On adding Druid service via Ambari below exception was thrown
> {code}
> 14 Nov 2017 05:48:06,083 ERROR [ambari-client-thread-44539]
> BaseManagementHandler:61 - Caught a system exception while attempting to
> create a resource: Stack Advisor reported an error: UnboundLocalError: local
> variable 'host' referenced before assignment
> StdOut file: /var/run/ambari-server/stack-recommendations/44/stackadvisor.out
> StdErr file: /var/run/ambari-server/stack-recommendations/44/stackadvisor.err
> org.apache.ambari.server.controller.spi.SystemException: Stack Advisor
> reported an error: UnboundLocalError: local variable 'host' referenced before
> assignment
> StdOut file: /var/run/ambari-server/stack-recommendations/44/stackadvisor.out
> StdErr file: /var/run/ambari-server/stack-recommendations/44/stackadvisor.err
> at
> org.apache.ambari.server.controller.internal.RecommendationResourceProvider.createResources(RecommendationResourceProvider.java:98)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298)
> at
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
> at
> org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37)
> at
> org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
> at
> org.apache.ambari.server.api.services.RecommendationService.getRecommendation(RecommendationService.java:59)
> at sun.reflect.GeneratedMethodAccessor1179.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
> at
>
[jira] [Commented] (AMBARI-22493) Fix build for test classes in feature branch
[
https://issues.apache.org/jira/browse/AMBARI-22493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262764#comment-16262764
]
Hadoop QA commented on AMBARI-22493:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898871/AMBARI-22493.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/12714//console
This message is automatically generated.
> Fix build for test classes in feature branch
>
>
> Key: AMBARI-22493
> URL: https://issues.apache.org/jira/browse/AMBARI-22493
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-22493.patch
>
>
> First step, we need to fix build process for test classes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22499) Ambari server becomes unusable if numeric value is specified as long
[
https://issues.apache.org/jira/browse/AMBARI-22499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262570#comment-16262570
]
Hadoop QA commented on AMBARI-22499:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898849/AMBARI-22499.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12713//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12713//console
This message is automatically generated.
> Ambari server becomes unusable if numeric value is specified as long
>
>
> Key: AMBARI-22499
> URL: https://issues.apache.org/jira/browse/AMBARI-22499
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: AMBARI-22499.patch
>
>
> Configure numeric property (eg. {{hive.compactor.worker.timeout}}) with value
> specified as {{long}} (eg. {{86400L}}). Ambari UI becomes unresponsive due
> to being flooded of the following exception:
> {noformat}
> 17 Nov 2017 13:32:29,464 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:130
> - Exception received
> java.lang.NumberFormatException: For input string: "86400L"
> at
> sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:2043)
> at sun.misc.FloatingDecimal.parseDouble(FloatingDecimal.java:110)
> at java.lang.Double.parseDouble(Double.java:538)
> at
> org.apache.ambari.server.state.ConfigHelper.valuesAreEqual(ConfigHelper.java:1515)
> at
> org.apache.ambari.server.state.ConfigHelper.findChangedKeys(ConfigHelper.java:1497)
> at
> org.apache.ambari.server.state.ConfigHelper.calculateIsStaleConfigs(ConfigHelper.java:1352)
> at
> org.apache.ambari.server.state.ConfigHelper.isStaleConfigs(ConfigHelper.java:476)
> at
> org.apache.ambari.server.state.ConfigHelper.isStaleConfigs(ConfigHelper.java:470)
> at
> org.apache.ambari.server.agent.HeartbeatMonitor.createStatusCommand(HeartbeatMonitor.java:317)
> at
> org.apache.ambari.server.agent.HeartbeatMonitor.generateStatusCommands(HeartbeatMonitor.java:225)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22500) Modify AMBARI-22387 to Check for LZO + No Opt-in
[
https://issues.apache.org/jira/browse/AMBARI-22500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262553#comment-16262553
]
Hadoop QA commented on AMBARI-22500:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898861/AMBARI-22500.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12712//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12712//console
This message is automatically generated.
> Modify AMBARI-22387 to Check for LZO + No Opt-in
>
>
> Key: AMBARI-22500
> URL: https://issues.apache.org/jira/browse/AMBARI-22500
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Attachments: AMBARI-22500.patch
>
>
> The work for AMBARI-22387 was initially created to warn the user before
> performing an upgrade that LZO was enabled and would need to be managed on
> their own. However, with AMBARI-22457, we now support LZO when a user opts-in
> to installed GPL-licensed code.
> The warning in AMBARI-22387 should be changed to check for LZO being enabled
> but the user _NOT_ opt-ing in
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22493) Fix build for test classes in feature branch
[
https://issues.apache.org/jira/browse/AMBARI-22493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262366#comment-16262366
]
Hadoop QA commented on AMBARI-22493:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898745/AMBARI-22493.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/12711//console
This message is automatically generated.
> Fix build for test classes in feature branch
>
>
> Key: AMBARI-22493
> URL: https://issues.apache.org/jira/browse/AMBARI-22493
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-22493.patch
>
>
> First step, we need to fix build process for test classes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22485) Allow Ambari to support non-kerberos SASL mechanisms for Kafka
[
https://issues.apache.org/jira/browse/AMBARI-22485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262365#comment-16262365
]
Hadoop QA commented on AMBARI-22485:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898782/AMBARI-22485_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/12710//console
This message is automatically generated.
> Allow Ambari to support non-kerberos SASL mechanisms for Kafka
> --
>
> Key: AMBARI-22485
> URL: https://issues.apache.org/jira/browse/AMBARI-22485
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.6.0
>Reporter: Yolanda M. Davis
>Assignee: Yolanda M. Davis
> Attachments: AMBARI-22485.patch, AMBARI-22485_branch-2.6.patch
>
>
> Currently AMBARI support's SASL and SSL as the security options for Kafka.
> Within SASL Ambari only supports GSSAPI(kerberos) only. Kafka supports other
> mechanisms such as plain, md5 etc.. This allows users to plug in their LDAP
> system into Kafka.
> Also another important option is SASL_SSL.
> We need to expose necessary configs in Ambari to enable these mechanisms for
> users.
> Ambari should allow users to not only configure Kafka for non-kerberos based
> SASL mechanisms, but also ensure that jaas configuration files are written
> when these options are provided (as opposed to only writing those files when
> kerberos has been enabled)..
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22495) Installer - Select Version page should show HDP-GPL repo if necessary
[
https://issues.apache.org/jira/browse/AMBARI-22495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262362#comment-16262362
]
Hadoop QA commented on AMBARI-22495:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898775/AMBARI-22495.v1.br-feature.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/12709//console
This message is automatically generated.
> Installer - Select Version page should show HDP-GPL repo if necessary
> -
>
> Key: AMBARI-22495
> URL: https://issues.apache.org/jira/browse/AMBARI-22495
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.6.1
>
> Attachments: AMBARI-22495.v0.br-feature.patch,
> AMBARI-22495.v1.br-feature.patch
>
>
> Display HDP-GPL repo field under Repositories in Select Version step of
> Installer only if user agrees to gpl license agreement
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22496) Admin View - Manage Versions page should show HDP-GPL repo if necessary
[
https://issues.apache.org/jira/browse/AMBARI-22496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262358#comment-16262358
]
Hadoop QA commented on AMBARI-22496:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898786/AMBARI-22496.v0.br-feature.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/12708//console
This message is automatically generated.
> Admin View - Manage Versions page should show HDP-GPL repo if necessary
> ---
>
> Key: AMBARI-22496
> URL: https://issues.apache.org/jira/browse/AMBARI-22496
> Project: Ambari
> Issue Type: Task
> Components: ambari-admin
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.6.1
>
> Attachments: AMBARI-22496.v0.br-feature.patch
>
>
> Display HDP-GPL repo field under Repositories in Manage Versions of Admin
> View only if the user agreed to the GPL license agreement during
> ambari-server setup
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22494) Unable to install the cluster
[
https://issues.apache.org/jira/browse/AMBARI-22494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262354#comment-16262354
]
Hadoop QA commented on AMBARI-22494:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898834/AMBARI-22494_trunk.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12707//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12707//console
This message is automatically generated.
> Unable to install the cluster
> -
>
> Key: AMBARI-22494
> URL: https://issues.apache.org/jira/browse/AMBARI-22494
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: amarnath reddy pappu
>Assignee: Andrii Tkach
> Attachments: AMBARI-22494.patch, AMBARI-22494_trunk.patch
>
>
> Customer has installed Ambari 2.6 and trying to install the cluster. in the
> hosts page it keeps loading for hostcheck results and never loads/enables
> Next button.
> It fails out with JS error like below,
> {noformat}
> ##
> Uncaught TypeError: _hostPackagesData.installedPackages.forEach is not a
> function
> at Class. (app.js:40783)
> at Array.forEach ()
> at Class.parseHostCheckWarnings (app.js:40746)
> at Class.getHostInfoSuccessCallback (app.js:41079)
> at Class.opt.success (app.js:177567)
> at o (vendor.js:106)
> at Object.fireWith [as resolveWith] (vendor.js:106)
> at w (vendor.js:108)
> ##
> {noformat}
> If the API response is like below,
> {noformat}
> {
> "Requests" : {
> "id" : 18,
> "inputs" :
> "{\"jdk_location\":\"https://HOST:8443/resources/\",\"threshold\":\"20\",\"HAS_RESOURCE_FILTERS\":\"true\",\"check_execute_list\":\"last_agent_env_check,installed_packages,existing_repos,transparentHugePage\"};,
> "request_status" : "COMPLETED"
> },
> "tasks" : [
> {
> "Tasks" : {
> "command_detail" : "check_host ACTIONEXECUTE",
> "error_log" : "/var/lib/ambari-agent/data/errors-178.txt",
> "host_name" : "host.net",
> "id" : 178,
> "status" : "COMPLETED",
> "stderr" : "2017-11-20 15:53:40,844 - There was an unknown error
> while checking installed packages and existing repositories: list index out
> of range\nTraceback (most recent call last):\n File
> \"/var/lib/ambari-agent/cache/custom_actions/scripts/check_host.py\", line
> 170, in actionexecute\ninstalled_packages, repos =
> self.execute_existing_repos_and_installed_packages_check(config)\n File
> \"/var/lib/ambari-agent/cache/custom_actions/scripts/check_host.py\", line
> 233, in execute_existing_repos_and_installed_packages_check\n
> installedPackages = self.pkg_provider.all_installed_packages()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/package/yumrpm.py\",
> line 222, in all_installed_packages\nreturn
> self._get_installed_packages(None)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/package/yumrpm.py\",
> line 157, in _get_installed_packages\npackages =
> self._lookup_packages([AMBARI_SUDO_BINARY, \"yum\", \"list\", \"installed\"],
> \"Installed Packages\")\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/package/yumrpm.py\",
> line 191, in _lookup_packages\nif items[i + 2].find('@') ==
> 0:\nIndexError: list index out of range\nNo handlers could be found for
> logger \"ambari_agent.HostCheckReportFileHandler\"\nTraceback (most recent
> call last):\n File
> \"/usr/lib/python2.6/site-packages/ambari_agent/HostCheckReportFileHandler.py\",
> line 74, in writeHostChecksCustomActionsFile\n
> items.append(itemDetail['name'])\nTypeError: string indices must be integers,
> not str",
> "stdout" : "2017-11-20 15:53:39,422 - Host checks
> started.\n2017-11-20 15:53:39,422 - Check execute list:
> last_agent_env_check,installed_packages,existing_repos,transparentHugePage\n2017-11-20
> 15:53:39,422 - Last Agent Env check started.\n2017-11-20 15:53:39,469 - Last
> Agent Env check completed successfully.\n2017-11-20 15:53:39,469 - Installed
> packages and existing repos checks started.\n2017-11-20 15:53:40,844 - There
> was an unknown error while checking installed packages and existing
> repositories: list index out of range\nTraceback (most recent call last):\n
> File \"/var/lib/ambari-agent/cache/custom_actions/scripts/check_host.py\",
> line 170, in actionexecute\ninstalled_packages, repos =
> self.execute_existing_repos_and_installed_packages_check(config)\n File
>
[jira] [Commented] (AMBARI-22494) Unable to install the cluster
[
https://issues.apache.org/jira/browse/AMBARI-22494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262344#comment-16262344
]
Hadoop QA commented on AMBARI-22494:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898834/AMBARI-22494_trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 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/12706//console
This message is automatically generated.
> Unable to install the cluster
> -
>
> Key: AMBARI-22494
> URL: https://issues.apache.org/jira/browse/AMBARI-22494
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: amarnath reddy pappu
>Assignee: Andrii Tkach
> Attachments: AMBARI-22494.patch, AMBARI-22494_trunk.patch
>
>
> Customer has installed Ambari 2.6 and trying to install the cluster. in the
> hosts page it keeps loading for hostcheck results and never loads/enables
> Next button.
> It fails out with JS error like below,
> {noformat}
> ##
> Uncaught TypeError: _hostPackagesData.installedPackages.forEach is not a
> function
> at Class. (app.js:40783)
> at Array.forEach ()
> at Class.parseHostCheckWarnings (app.js:40746)
> at Class.getHostInfoSuccessCallback (app.js:41079)
> at Class.opt.success (app.js:177567)
> at o (vendor.js:106)
> at Object.fireWith [as resolveWith] (vendor.js:106)
> at w (vendor.js:108)
> ##
> {noformat}
> If the API response is like below,
> {noformat}
> {
> "Requests" : {
> "id" : 18,
> "inputs" :
> "{\"jdk_location\":\"https://HOST:8443/resources/\",\"threshold\":\"20\",\"HAS_RESOURCE_FILTERS\":\"true\",\"check_execute_list\":\"last_agent_env_check,installed_packages,existing_repos,transparentHugePage\"};,
> "request_status" : "COMPLETED"
> },
> "tasks" : [
> {
> "Tasks" : {
> "command_detail" : "check_host ACTIONEXECUTE",
> "error_log" : "/var/lib/ambari-agent/data/errors-178.txt",
> "host_name" : "host.net",
> "id" : 178,
> "status" : "COMPLETED",
> "stderr" : "2017-11-20 15:53:40,844 - There was an unknown error
> while checking installed packages and existing repositories: list index out
> of range\nTraceback (most recent call last):\n File
> \"/var/lib/ambari-agent/cache/custom_actions/scripts/check_host.py\", line
> 170, in actionexecute\ninstalled_packages, repos =
> self.execute_existing_repos_and_installed_packages_check(config)\n File
> \"/var/lib/ambari-agent/cache/custom_actions/scripts/check_host.py\", line
> 233, in execute_existing_repos_and_installed_packages_check\n
> installedPackages = self.pkg_provider.all_installed_packages()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/package/yumrpm.py\",
> line 222, in all_installed_packages\nreturn
> self._get_installed_packages(None)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/package/yumrpm.py\",
> line 157, in _get_installed_packages\npackages =
> self._lookup_packages([AMBARI_SUDO_BINARY, \"yum\", \"list\", \"installed\"],
> \"Installed Packages\")\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/package/yumrpm.py\",
> line 191, in _lookup_packages\nif items[i + 2].find('@') ==
> 0:\nIndexError: list index out of range\nNo handlers could be found for
> logger \"ambari_agent.HostCheckReportFileHandler\"\nTraceback (most recent
> call last):\n File
> \"/usr/lib/python2.6/site-packages/ambari_agent/HostCheckReportFileHandler.py\",
> line 74, in writeHostChecksCustomActionsFile\n
> items.append(itemDetail['name'])\nTypeError: string indices must be integers,
> not str",
> "stdout" : "2017-11-20 15:53:39,422 - Host checks
> started.\n2017-11-20 15:53:39,422 - Check execute list:
> last_agent_env_check,installed_packages,existing_repos,transparentHugePage\n2017-11-20
> 15:53:39,422 - Last Agent Env check started.\n2017-11-20 15:53:39,469 - Last
> Agent Env check completed successfully.\n2017-11-20
[jira] [Commented] (AMBARI-22494) Unable to install the cluster
[
https://issues.apache.org/jira/browse/AMBARI-22494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262285#comment-16262285
]
Hadoop QA commented on AMBARI-22494:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898834/AMBARI-22494_trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 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
[ambari-web|https://builds.apache.org/job/Ambari-trunk-test-patch/12705//artifact/patch-work/testrun_ambari-web.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12705//console
This message is automatically generated.
> Unable to install the cluster
> -
>
> Key: AMBARI-22494
> URL: https://issues.apache.org/jira/browse/AMBARI-22494
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: amarnath reddy pappu
>Assignee: Andrii Tkach
> Attachments: AMBARI-22494.patch, AMBARI-22494_trunk.patch
>
>
> Customer has installed Ambari 2.6 and trying to install the cluster. in the
> hosts page it keeps loading for hostcheck results and never loads/enables
> Next button.
> It fails out with JS error like below,
> {noformat}
> ##
> Uncaught TypeError: _hostPackagesData.installedPackages.forEach is not a
> function
> at Class. (app.js:40783)
> at Array.forEach ()
> at Class.parseHostCheckWarnings (app.js:40746)
> at Class.getHostInfoSuccessCallback (app.js:41079)
> at Class.opt.success (app.js:177567)
> at o (vendor.js:106)
> at Object.fireWith [as resolveWith] (vendor.js:106)
> at w (vendor.js:108)
> ##
> {noformat}
> If the API response is like below,
> {noformat}
> {
> "Requests" : {
> "id" : 18,
> "inputs" :
> "{\"jdk_location\":\"https://HOST:8443/resources/\",\"threshold\":\"20\",\"HAS_RESOURCE_FILTERS\":\"true\",\"check_execute_list\":\"last_agent_env_check,installed_packages,existing_repos,transparentHugePage\"};,
> "request_status" : "COMPLETED"
> },
> "tasks" : [
> {
> "Tasks" : {
> "command_detail" : "check_host ACTIONEXECUTE",
> "error_log" : "/var/lib/ambari-agent/data/errors-178.txt",
> "host_name" : "host.net",
> "id" : 178,
> "status" : "COMPLETED",
> "stderr" : "2017-11-20 15:53:40,844 - There was an unknown error
> while checking installed packages and existing repositories: list index out
> of range\nTraceback (most recent call last):\n File
> \"/var/lib/ambari-agent/cache/custom_actions/scripts/check_host.py\", line
> 170, in actionexecute\ninstalled_packages, repos =
> self.execute_existing_repos_and_installed_packages_check(config)\n File
> \"/var/lib/ambari-agent/cache/custom_actions/scripts/check_host.py\", line
> 233, in execute_existing_repos_and_installed_packages_check\n
> installedPackages = self.pkg_provider.all_installed_packages()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/package/yumrpm.py\",
> line 222, in all_installed_packages\nreturn
> self._get_installed_packages(None)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/package/yumrpm.py\",
> line 157, in _get_installed_packages\npackages =
> self._lookup_packages([AMBARI_SUDO_BINARY, \"yum\", \"list\", \"installed\"],
> \"Installed Packages\")\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/package/yumrpm.py\",
> line 191, in _lookup_packages\nif items[i + 2].find('@') ==
> 0:\nIndexError: list index out of range\nNo handlers could be found for
> logger \"ambari_agent.HostCheckReportFileHandler\"\nTraceback (most recent
> call last):\n File
> \"/usr/lib/python2.6/site-packages/ambari_agent/HostCheckReportFileHandler.py\",
> line 74, in writeHostChecksCustomActionsFile\n
> items.append(itemDetail['name'])\nTypeError: string indices must be integers,
> not str",
> "stdout" : "2017-11-20 15:53:39,422 - Host checks
> started.\n2017-11-20 15:53:39,422 - Check execute list:
> last_agent_env_check,installed_packages,existing_repos,transparentHugePage\n2017-11-20
> 15:53:39,422 - Last Agent Env check
[jira] [Commented] (AMBARI-22489) Port AMBARI-22467 to BigInsight
[
https://issues.apache.org/jira/browse/AMBARI-22489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16261139#comment-16261139
]
Hadoop QA commented on AMBARI-22489:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898646/AMBARI-22489.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/12704//console
This message is automatically generated.
> Port AMBARI-22467 to BigInsight
> ---
>
> Key: AMBARI-22489
> URL: https://issues.apache.org/jira/browse/AMBARI-22489
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.6.1
>
> Attachments: AMBARI-22489.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22491) Moving Metrics Collector Forces ZooKeeper Server Install on Target Host
[
https://issues.apache.org/jira/browse/AMBARI-22491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16261138#comment-16261138
]
Hadoop QA commented on AMBARI-22491:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898677/AMBARI-22491.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/12703//console
This message is automatically generated.
> Moving Metrics Collector Forces ZooKeeper Server Install on Target Host
> ---
>
> Key: AMBARI-22491
> URL: https://issues.apache.org/jira/browse/AMBARI-22491
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22491.patch
>
>
> When moving a Metrics Collector, a ZooKeeper Server is installed on the
> target host along with the Metrics Collector. This ZooKeeper Server is added
> and quorum can be upset in large clusters, and the customer was not intending
> to have a ZooKeeper server on the target directory.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22491) Moving Metrics Collector Forces ZooKeeper Server Install on Target Host
[
https://issues.apache.org/jira/browse/AMBARI-22491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16261037#comment-16261037
]
Hadoop QA commented on AMBARI-22491:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898677/AMBARI-22491.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/12702//console
This message is automatically generated.
> Moving Metrics Collector Forces ZooKeeper Server Install on Target Host
> ---
>
> Key: AMBARI-22491
> URL: https://issues.apache.org/jira/browse/AMBARI-22491
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22491.patch
>
>
> When moving a Metrics Collector, a ZooKeeper Server is installed on the
> target host along with the Metrics Collector. This ZooKeeper Server is added
> and quorum can be upset in large clusters, and the customer was not intending
> to have a ZooKeeper server on the target directory.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22491) Moving Metrics Collector Forces ZooKeeper Server Install on Target Host
[
https://issues.apache.org/jira/browse/AMBARI-22491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16260972#comment-16260972
]
Hadoop QA commented on AMBARI-22491:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898677/AMBARI-22491.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:red}-1 core tests{color}. The test build failed in
[ambari-web|https://builds.apache.org/job/Ambari-trunk-test-patch/12701//artifact/patch-work/testrun_ambari-web.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12701//console
This message is automatically generated.
> Moving Metrics Collector Forces ZooKeeper Server Install on Target Host
> ---
>
> Key: AMBARI-22491
> URL: https://issues.apache.org/jira/browse/AMBARI-22491
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22491.patch
>
>
> When moving a Metrics Collector, a ZooKeeper Server is installed on the
> target host along with the Metrics Collector. This ZooKeeper Server is added
> and quorum can be upset in large clusters, and the customer was not intending
> to have a ZooKeeper server on the target directory.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22489) Port AMBARI-22467 to BigInsight
[
https://issues.apache.org/jira/browse/AMBARI-22489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16260572#comment-16260572
]
Hadoop QA commented on AMBARI-22489:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898646/AMBARI-22489.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/12700//console
This message is automatically generated.
> Port AMBARI-22467 to BigInsight
> ---
>
> Key: AMBARI-22489
> URL: https://issues.apache.org/jira/browse/AMBARI-22489
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.6.1
>
> Attachments: AMBARI-22489.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22469) Ambari upgrade failed
[
https://issues.apache.org/jira/browse/AMBARI-22469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259744#comment-16259744
]
Hadoop QA commented on AMBARI-22469:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898511/AMBARI-22469.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/12699//console
This message is automatically generated.
> Ambari upgrade failed
> -
>
> Key: AMBARI-22469
> URL: https://issues.apache.org/jira/browse/AMBARI-22469
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: amarnath reddy pappu
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22469.patch
>
>
> Ambari upgrade would fail for all Ambari view servers.
> Steps to reproduce:
> 1. Install Ambari 2.5.2 and setup it as view server. (it you don't set up it
> up as view server also it fails)
> 2. now install 2.6.0
> 3. run ambari-server upgrade
> it fails out with below exception.
> {noformat}
> ERROR: Error executing schema upgrade, please check the server logs.
> ERROR: Error output from schema upgrade command:
> ERROR: Exception in thread "main" org.apache.ambari.server.AmbariException:
> Unable to find any CURRENT repositories.
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:203)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:418)
> Caused by: org.apache.ambari.server.AmbariException: Unable to find any
> CURRENT repositories.
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog260.getCurrentVersionID(UpgradeCatalog260.java:510)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog260.executeDDLUpdates(UpgradeCatalog260.java:194)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:923)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:200)
> ... 1 more
> ERROR: Ambari server upgrade failed. Please look at
> /var/log/ambari-server/ambari-server.log, for more details.
> ERROR: Exiting with exit code 11.
> REASON: Schema upgrade failed.
> {noformat}
> For some reason we are checking cluster_version table entries and throwing up
> above exception.
> {noformat}
> In UpgradeCatalog260.java
> public int getCurrentVersionID() throws AmbariException, SQLException {
> List currentVersionList =
> dbAccessor.getIntColumnValues(CLUSTER_VERSION_TABLE, REPO_VERSION_ID_COLUMN,
> new String[]{STATE_COLUMN}, new String[]{CURRENT}, false);
> if (currentVersionList.isEmpty()) {
> throw new AmbariException("Unable to find any CURRENT repositories.");
> } else if (currentVersionList.size() != 1) {
> throw new AmbariException("The following repositories were found to be
> CURRENT: ".concat(StringUtils.join(currentVersionList, ",")));
> }
> return currentVersionList.get(0);
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22479) After removing force_delete_components option hosts are not deleted
[
https://issues.apache.org/jira/browse/AMBARI-22479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259459#comment-16259459
]
Hadoop QA commented on AMBARI-22479:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898484/AMBARI-22479.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:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.controller.AmbariManagementControllerTest
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12698//console
This message is automatically generated.
> After removing force_delete_components option hosts are not deleted
> ---
>
> Key: AMBARI-22479
> URL: https://issues.apache.org/jira/browse/AMBARI-22479
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: AMBARI-22479.patch
>
>
> After removing force_delete_components from bulk host delete request BE
> returns "hosts not stopped error" even though the components have been stopped
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22393) UI changes for prompting user during registration failure for new OS family
[
https://issues.apache.org/jira/browse/AMBARI-22393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259374#comment-16259374
]
Hadoop QA commented on AMBARI-22393:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898494/AMBARI-22393.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:red}-1 core tests{color}. The test build failed in
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/12697//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12697//console
This message is automatically generated.
> UI changes for prompting user during registration failure for new OS family
> ---
>
> Key: AMBARI-22393
> URL: https://issues.apache.org/jira/browse/AMBARI-22393
> Project: Ambari
> Issue Type: Sub-task
> Components: ambari-server, ambari-web
>Reporter: Yussuf Shaikh
>Assignee: Yussuf Shaikh
> Attachments: AMBARI-22393.patch
>
>
> This task will include UI related template changes for the Ambari repository
> url prompt.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22478) Ambari 3.0: Implement new design for Admin View: Edit cluster name
[
https://issues.apache.org/jira/browse/AMBARI-22478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259322#comment-16259322
]
Hadoop QA commented on AMBARI-22478:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898489/AMBARI-22478.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-admin.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12696//console
This message is automatically generated.
> Ambari 3.0: Implement new design for Admin View: Edit cluster name
> --
>
> Key: AMBARI-22478
> URL: https://issues.apache.org/jira/browse/AMBARI-22478
> 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-22478.patch, Save Cluster Name.png
>
>
> The cluster name can be changed by interacting with the cluster name field.
> Color for the text box is: #fdfbdd.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22479) After removing force_delete_components option hosts are not deleted
[
https://issues.apache.org/jira/browse/AMBARI-22479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259240#comment-16259240
]
Hadoop QA commented on AMBARI-22479:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898485/screenshot-1.png
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/12694//console
This message is automatically generated.
> After removing force_delete_components option hosts are not deleted
> ---
>
> Key: AMBARI-22479
> URL: https://issues.apache.org/jira/browse/AMBARI-22479
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: AMBARI-22479.patch, screenshot-1.png
>
>
> After removing force_delete_components from bulk host delete request BE
> returns "hosts not stopped error" even though the components have been stopped
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22478) Ambari 3.0: Implement new design for Admin View: Edit cluster name
[
https://issues.apache.org/jira/browse/AMBARI-22478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259232#comment-16259232
]
Hadoop QA commented on AMBARI-22478:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898480/AMBARI-22478.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-admin.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12693//console
This message is automatically generated.
> Ambari 3.0: Implement new design for Admin View: Edit cluster name
> --
>
> Key: AMBARI-22478
> URL: https://issues.apache.org/jira/browse/AMBARI-22478
> 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-22478.patch, Save Cluster Name.png
>
>
> The cluster name can be changed by interacting with the cluster name field.
> Color for the text box is: #fdfbdd.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22393) UI changes for prompting user during registration failure for new OS family
[
https://issues.apache.org/jira/browse/AMBARI-22393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259199#comment-16259199
]
Hadoop QA commented on AMBARI-22393:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898444/AMBARI-22393.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:red}-1 core tests{color}. The test build failed in
[ambari-web|https://builds.apache.org/job/Ambari-trunk-test-patch/12692//artifact/patch-work/testrun_ambari-web.txt]
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/12692//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12692//console
This message is automatically generated.
> UI changes for prompting user during registration failure for new OS family
> ---
>
> Key: AMBARI-22393
> URL: https://issues.apache.org/jira/browse/AMBARI-22393
> Project: Ambari
> Issue Type: Sub-task
> Components: ambari-server, ambari-web
>Reporter: Yussuf Shaikh
>Assignee: Yussuf Shaikh
> Attachments: AMBARI-22393.patch
>
>
> This task will include UI related template changes for the Ambari repository
> url prompt.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22477) Log Search UI: implement access logs table
[
https://issues.apache.org/jira/browse/AMBARI-22477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259163#comment-16259163
]
Hadoop QA commented on AMBARI-22477:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898467/AMBARI-22477.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/12690//console
This message is automatically generated.
> Log Search UI: implement access logs table
> --
>
> Key: AMBARI-22477
> URL: https://issues.apache.org/jira/browse/AMBARI-22477
> 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-22477.patch
>
>
> Add layout for audit logs table
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22473) shell.process_executor races process exit
[
https://issues.apache.org/jira/browse/AMBARI-22473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16258829#comment-16258829
]
Hadoop QA commented on AMBARI-22473:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898369/0001-AMBARI-22473-shell.process_executor-races-process-ex.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 .
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12689//console
This message is automatically generated.
> shell.process_executor races process exit
> -
>
> Key: AMBARI-22473
> URL: https://issues.apache.org/jira/browse/AMBARI-22473
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Jonathan Matthew
> Attachments:
> 0001-AMBARI-22473-shell.process_executor-races-process-ex.patch
>
>
> By calling cmd.poll(), shell.process_executor assumes that the subcommand
> will have exited once it has finished reading from its stdout pipe. This
> isn't necessarily the case, so it should call cmd.wait() instead.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22467) YARN, MapReduce2, Hive, and Oozie Should Conditionally Install LZO
[
https://issues.apache.org/jira/browse/AMBARI-22467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257108#comment-16257108
]
Hadoop QA commented on AMBARI-22467:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898215/AMBARI-22467.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/12688//console
This message is automatically generated.
> YARN, MapReduce2, Hive, and Oozie Should Conditionally Install LZO
> --
>
> Key: AMBARI-22467
> URL: https://issues.apache.org/jira/browse/AMBARI-22467
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.6.1
>
> Attachments: AMBARI-22467.patch
>
>
> Changes Summary:
> - Do not install lzo if GPL license if not accepted, instead give out
> logger.warning and skip
> - Remove installation of lzo from metainfo.xml. Since we need to install lzo
> on restart if lzo is enabled/license accepted, we still need to do this in
> Python code. No need to duplicate.
> Clients will also use that code during install.
> - Move function get_lzo_packages to lzo_utils.py
> - Add code for Yarn, MR2, Hive to install lzo, edit existing code to install
> lzo for HDFS,Oozie to use lzo_utils.py
> Notes:
> - Impl is Patch Upgrade friendly as uses the same code to detect
> {stack_version} as all the other packages. That code (not implemented here)
> gets version depending component specific repo info not stack specific.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22466) Ambari 3.0: Implement new design for Admin View: Views page tweaks
[
https://issues.apache.org/jira/browse/AMBARI-22466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257105#comment-16257105
]
Hadoop QA commented on AMBARI-22466:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898211/AMBARI-22466.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/12687//console
This message is automatically generated.
> Ambari 3.0: Implement new design for Admin View: Views page tweaks
> --
>
> Key: AMBARI-22466
> URL: https://issues.apache.org/jira/browse/AMBARI-22466
> 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-22466.patch, View status indicator.png
>
>
> # Add view status indicator
> # Clone view should be in modal
> # Create/Clone View modal should contain properties and settings
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22467) YARN, MapReduce2, Hive, and Oozie Should Conditionally Install LZO
[
https://issues.apache.org/jira/browse/AMBARI-22467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257089#comment-16257089
]
Hadoop QA commented on AMBARI-22467:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898215/AMBARI-22467.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/12686//console
This message is automatically generated.
> YARN, MapReduce2, Hive, and Oozie Should Conditionally Install LZO
> --
>
> Key: AMBARI-22467
> URL: https://issues.apache.org/jira/browse/AMBARI-22467
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.6.1
>
> Attachments: AMBARI-22467.patch
>
>
> Changes Summary:
> - Do not install lzo if GPL license if not accepted, instead give out
> logger.warning and skip
> - Remove installation of lzo from metainfo.xml. Since we need to install lzo
> on restart if lzo is enabled/license accepted, we still need to do this in
> Python code. No need to duplicate.
> Clients will also use that code during install.
> - Move function get_lzo_packages to lzo_utils.py
> - Add code for Yarn, MR2, Hive to install lzo, edit existing code to install
> lzo for HDFS,Oozie to use lzo_utils.py
> Notes:
> - Impl is Patch Upgrade friendly as uses the same code to detect
> {stack_version} as all the other packages. That code (not implemented here)
> gets version depending component specific repo info not stack specific.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22466) Ambari 3.0: Implement new design for Admin View: Views page tweaks
[
https://issues.apache.org/jira/browse/AMBARI-22466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257087#comment-16257087
]
Hadoop QA commented on AMBARI-22466:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898211/AMBARI-22466.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-admin.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12685//console
This message is automatically generated.
> Ambari 3.0: Implement new design for Admin View: Views page tweaks
> --
>
> Key: AMBARI-22466
> URL: https://issues.apache.org/jira/browse/AMBARI-22466
> 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-22466.patch, View status indicator.png
>
>
> # Add view status indicator
> # Clone view should be in modal
> # Create/Clone View modal should contain properties and settings
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22463) Removing secure reference configs entries from stack for Ranger KMS service
[
https://issues.apache.org/jira/browse/AMBARI-22463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16256989#comment-16256989
]
Hadoop QA commented on AMBARI-22463:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898192/AMBARI-22463.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
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/12684//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12684//console
This message is automatically generated.
> Removing secure reference configs entries from stack for Ranger KMS service
> ---
>
> Key: AMBARI-22463
> URL: https://issues.apache.org/jira/browse/AMBARI-22463
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-22463.patch
>
>
> Removing below properties entries from stack.
> {noformat}
> hadoop.kms.authentication.kerberos.keytab
> hadoop.kms.authentication.kerberos.principal
> hadoop.kms.authentication.signer.secret.provider.zookeeper.kerberos.keytab
> hadoop.kms.authentication.signer.secret.provider.zookeeper.kerberos.principal
> {noformat}
> These properties will be added in secure cluster using Ranger KMS Kerberos
> descriptor.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22462) StackAdvisorCommand unable to make internal request to AmbariConfigurationProvider due to changed resource field id's
[
https://issues.apache.org/jira/browse/AMBARI-22462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16256658#comment-16256658
]
Hadoop QA commented on AMBARI-22462:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898141/AMBARI-22462.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12683//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12683//console
This message is automatically generated.
> StackAdvisorCommand unable to make internal request to
> AmbariConfigurationProvider due to changed resource field id's
> -
>
> Key: AMBARI-22462
> URL: https://issues.apache.org/jira/browse/AMBARI-22462
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: trunk
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Blocker
> Fix For: trunk
>
> Attachments: AMBARI-22462.patch
>
>
> caused by AMBARI-22347, hardcoded request need to be reworked to use new
> field id's
> {code}
> 17 Nov 2017 04:59:22,835 WARN [ambari-client-thread-86]
> StackAdvisorCommand:191 - Error occured during retrieving ldap configuration,
> status=400, response={
> "status" : 400,
> "message" : "The properties [AmbariConfiguration/type] specified in the
> request or predicate are not supported for the resource type
> AmbariConfiguration."
> }
> 17 Nov 2017 04:59:22,836 WARN [ambari-client-thread-86]
> StackAdvisorCommand:170 - Error parsing services.json file content: Error
> occured during retrieving ldap configuration, status=400, response={
> "status" : 400,
> "message" : "The properties [AmbariConfiguration/type] specified in the
> request or predicate are not supported for the resource type
> AmbariConfiguration."
> }
> org.apache.ambari.server.api.services.stackadvisor.StackAdvisorException:
> Error occured during retrieving ldap configuration, status=400, response={
> "status" : 400,
> "message" : "The properties [AmbariConfiguration/type] specified in the
> request or predicate are not supported for the resource type
> AmbariConfiguration."
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22449) Improved service/component dependency support
[
https://issues.apache.org/jira/browse/AMBARI-22449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16256648#comment-16256648
]
Hadoop QA commented on AMBARI-22449:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12898144/AMBARI-22449.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12682//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12682//console
This message is automatically generated.
> Improved service/component dependency support
> -
>
> Key: AMBARI-22449
> URL: https://issues.apache.org/jira/browse/AMBARI-22449
> Project: Ambari
> Issue Type: Task
> Components: ambari-server, ambari-web
>Affects Versions: 3.0.0
>Reporter: Attila Magyar
>Assignee: Attila Magyar
> Fix For: 3.0.0
>
> Attachments: AMBARI-22449.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22454) ambari-server upgrade to 2.6.1 should surface the GPL agreement
[
https://issues.apache.org/jira/browse/AMBARI-22454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255712#comment-16255712
]
Hadoop QA commented on AMBARI-22454:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897987/AMBARI-22454.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/12681//console
This message is automatically generated.
> ambari-server upgrade to 2.6.1 should surface the GPL agreement
> ---
>
> Key: AMBARI-22454
> URL: https://issues.apache.org/jira/browse/AMBARI-22454
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.6.1
>
> Attachments: AMBARI-22454.patch, AMBARI-22454.patch
>
>
> .
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22454) ambari-server upgrade to 2.6.1 should surface the GPL agreement
[
https://issues.apache.org/jira/browse/AMBARI-22454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255306#comment-16255306
]
Hadoop QA commented on AMBARI-22454:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897987/AMBARI-22454.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/12680//console
This message is automatically generated.
> ambari-server upgrade to 2.6.1 should surface the GPL agreement
> ---
>
> Key: AMBARI-22454
> URL: https://issues.apache.org/jira/browse/AMBARI-22454
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.6.1
>
> Attachments: AMBARI-22454.patch, AMBARI-22454.patch
>
>
> .
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22460) NFSGateway start failed
[
https://issues.apache.org/jira/browse/AMBARI-22460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255115#comment-16255115
]
Hadoop QA commented on AMBARI-22460:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897958/AMBARI-22460.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
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/12679//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12679//console
This message is automatically generated.
> NFSGateway start failed
> ---
>
> Key: AMBARI-22460
> URL: https://issues.apache.org/jira/browse/AMBARI-22460
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.6.1
>
> Attachments: AMBARI-22460.patch
>
>
> NFSGateway Start failed:
>
>
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py",
> line 83, in
> NFSGateway().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 367, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py",
> line 52, in start
> nfsgateway(action="start")
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py",
> line 74, in nfsgateway
> create_log_dir=True
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/utils.py",
> line 276, in service
> Execute(daemon_cmd, not_if=process_id_exists_command,
> environment=hadoop_env_exports)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line
> 166, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 72, in inner
> result = function(command, **kwargs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of
> 'ambari-sudo.sh -H -E /usr/hdp/2.6.4.0-25/hadoop/sbin/hadoop-daemon.sh
> --config /usr/hdp/2.6.4.0-25/hadoop/conf start nfs3' returned 1. starting
> nfs3, logging to
> /grid/0/log/hdfs/root/hadoop-cstm-hdfs-nfs3-ctr-e134-1499953498516-307402-01-05.hwx.site.out
>
> Build: Setup/644664/>
> Ambari UI:
[jira] [Commented] (AMBARI-22459) IOP/HDP migration NN HA restart post Ambari upgrade fails
[
https://issues.apache.org/jira/browse/AMBARI-22459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16254348#comment-16254348
]
Hadoop QA commented on AMBARI-22459:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897851/AMBARI-22459.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/12678//console
This message is automatically generated.
> IOP/HDP migration NN HA restart post Ambari upgrade fails
> -
>
> Key: AMBARI-22459
> URL: https://issues.apache.org/jira/browse/AMBARI-22459
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Di Li
>Assignee: Di Li
> Fix For: 2.6.1
>
> Attachments: AMBARI-22459.patch
>
>
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_select.py",
> line 109, in get_package_name
> package = get_packages(PACKAGE_SCOPE_STACK_SELECT, service_name,
> component_name)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_select.py",
> line 234, in get_packages
> raise Fail("The package {0} is not supported by this version of the
> stack-select tool.".format(package))
> resource_management.core.exceptions.Fail: The package hadoop-hdfs-zkfc is not
> supported by this version of the stack-select tool.
> Need your help in understanding expected behavior.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22424) Quicklinks for OneFS
[
https://issues.apache.org/jira/browse/AMBARI-22424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253949#comment-16253949
]
Hadoop QA commented on AMBARI-22424:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897789/AMBARI-22424.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/12676//console
This message is automatically generated.
> Quicklinks for OneFS
>
>
> Key: AMBARI-22424
> URL: https://issues.apache.org/jira/browse/AMBARI-22424
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Attila Magyar
>Assignee: Attila Magyar
> Fix For: 3.0.0
>
> Attachments: AMBARI-22424.patch
>
>
> The OneFS mpack should hava a quicklink.json. A quicklink should point to the
> OneFS web admin UI.
> Currently only master components can have quicklinks. The OneFS is a client
> only service.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22455) Ambari Logsearch Web unit tests are sometimes failing
[
https://issues.apache.org/jira/browse/AMBARI-22455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253714#comment-16253714
]
Hadoop QA commented on AMBARI-22455:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897770/AMBARI-22455.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/12675//console
This message is automatically generated.
> Ambari Logsearch Web unit tests are sometimes failing
> -
>
> Key: AMBARI-22455
> URL: https://issues.apache.org/jira/browse/AMBARI-22455
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-22455.patch
>
>
> Ambari Logsearch Web unit tests fail on CI builds:
> {code}
> [INFO] PhantomJS 2.1.1 (Linux 0.0.0) UtilsService #isEqual() undefined values
> equality FAILED
> [INFO]Expected false to be true.
> [INFO]http://localhost:9876/_karma_webpack_/main.bundle.js:9369:31
> [INFO]
> __tryOrUnsub@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55648:20
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55595:34
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55535:30
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57133:34
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57437:30
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55243:29
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:54628:35
> [INFO]http://localhost:9876/_karma_webpack_/vendor.bundle.js:415:62
> [INFO]
> __tryOrUnsub@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55648:20
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55595:34
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55535:30
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> _tryNext@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58081:30
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58068:33
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58466:38
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> observe@http://localhost:9876/_karma_webpack_/vendor.bundle.js:54715:54
> [INFO]
> dispatch@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57869:29
> [INFO]
> _execute@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58652:22
> [INFO]
> execute@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58781:26
> [INFO]
> flush@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58726:39
> [INFO]
> schedule@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58775:29
> [INFO]
> schedule@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55175:61
> [INFO]
> scheduleMessage@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57873:41
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57876:29
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55243:29
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:54628:35
> [INFO]
>
[jira] [Commented] (AMBARI-22444) Add Native Libraries To Tez Tarball
[
https://issues.apache.org/jira/browse/AMBARI-22444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253653#comment-16253653
]
Hadoop QA commented on AMBARI-22444:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897772/AMBARI-22444.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/12674//console
This message is automatically generated.
> Add Native Libraries To Tez Tarball
> ---
>
> Key: AMBARI-22444
> URL: https://issues.apache.org/jira/browse/AMBARI-22444
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22444.patch
>
>
> As part of the investigation for getting patch upgrades working in Ambari
> 2.6.1, it was determined that the Tez tarball will need to have the hadoop
> native libraries added to it so that they can be detected from the tarball.
> STR:
> - Install ZK, MapR, Tez, Yarn, Hive
> - Enable a non-LZO codec, like Snappy
> - Patch Hive to a new version
> - Change the following properties in {{tez-site}}:
> -- tez.am.launch.env = LD_LIBRARY=./tezlib/lib/native
> -- tez.task.launch.env = LD_LIBRARY=./tezlib/lib/native
> When Hive commands run, they will attempt to load the native snappy libraries
> from the Tez tarball and will fail with:
> {code}
> Caused by: java.io.IOException: Unable to get CompressorType for codec
> (org.apache.hadoop.io.compress.SnappyCodec). This is most likely due to
> missing native libraries for the codec.
> at
> org.apache.tez.runtime.library.common.sort.impl.ExternalSorter.(ExternalSorter.java:217)
> {code}
> In order to fix this, the Tez tarball should include the native hadoop
> libraries as well:
> {code}
> ├── tez
> │  ├── lib
> │  │  ├── native
> │  │  │  ├── libhadoop.a
> │  │  │  ├── libhadoop.so -> libhadoop.so.1.0.0
> │  │  │  ├── libhadoop.so.1.0.0
> │  │  │  ├── libhadooppipes.a
> │  │  │  ├── libhadooputils.a
> │  │  │  ├── libhdfs.a
> │  │  │  ├── libhdfs.so -> libhdfs.so.0.0.0
> │  │  │  ├── libhdfs.so.0.0.0
> │  │  │  ├── libsnappy.so -> libsnappy.so.1.1.4
> │  │  │  ├── libsnappy.so.1 -> libsnappy.so.1.1.4
> │  │  │  └── libsnappy.so.1.1.4
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22448) Oozie Jobs on Hive Fail With Missing Tarball
[
https://issues.apache.org/jira/browse/AMBARI-22448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253313#comment-16253313
]
Hadoop QA commented on AMBARI-22448:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897655/AMBARI-22448.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-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12673//console
This message is automatically generated.
> Oozie Jobs on Hive Fail With Missing Tarball
>
>
> Key: AMBARI-22448
> URL: https://issues.apache.org/jira/browse/AMBARI-22448
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.6 1
>
> Attachments: AMBARI-22448.patch
>
>
> STR:
> - Install an HDP 2.6.3.0 cluster with Oozie, HIve, MapR, Yarn, ZK, HDFS
> - Patch only Oozie to a new version, such as 2.6.3.1-1
> - Attempt to run an Oozie job on Hive
> The workflow job will fail with:
> {code}
> org.apache.oozie.action.ActionExecutorException: JA008: File does not exist:
> hdfs://jhurley-pu-1.openstacklocal:8020/hdp/apps/2.6.3.1-1/mapreduce/mapreduce.tar.gz
> at
> org.apache.oozie.action.ActionExecutor.convertExceptionHelper(ActionExecutor.java:457)
> at
> org.apache.oozie.action.ActionExecutor.convertException(ActionExecutor.java:441)
> at
> org.apache.oozie.action.hadoop.JavaActionExecutor.submitLauncher(JavaActionExecutor.java:1211)
> at
> org.apache.oozie.action.hadoop.JavaActionExecutor.start(JavaActionExecutor.java:1382)
> at
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:234)
> at
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:65)
> at org.apache.oozie.command.XCommand.call(XCommand.java:287)
> at
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:331)
> at
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:260)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:178)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> This is because Oozie appears to be trying to use a version of the MapReduce
> tarball which matches its version. However, since it does not ship its
> version, it cannot find it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22441) Integrate Alert Groups on Alert page with websocket events
[
https://issues.apache.org/jira/browse/AMBARI-22441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253269#comment-16253269
]
Hadoop QA commented on AMBARI-22441:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897709/AMBARI-22441.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/12672//console
This message is automatically generated.
> Integrate Alert Groups on Alert page with websocket events
> --
>
> Key: AMBARI-22441
> URL: https://issues.apache.org/jira/browse/AMBARI-22441
> 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-22441.patch
>
>
> Subscribe to /events/alert_groups topic, which will update/add/delete groups
> of alerts.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22441) Integrate Alert Groups on Alert page with websocket events
[
https://issues.apache.org/jira/browse/AMBARI-22441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253197#comment-16253197
]
Hadoop QA commented on AMBARI-22441:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897709/AMBARI-22441.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/12671//console
This message is automatically generated.
> Integrate Alert Groups on Alert page with websocket events
> --
>
> Key: AMBARI-22441
> URL: https://issues.apache.org/jira/browse/AMBARI-22441
> 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-22441.patch
>
>
> Subscribe to /events/alert_groups topic, which will update/add/delete groups
> of alerts.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22447) Ambari Infra, AMS, LogSearch are missing from list of services to be installed
[
https://issues.apache.org/jira/browse/AMBARI-22447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16252725#comment-16252725
]
Hadoop QA commented on AMBARI-22447:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897640/AMBARI-22447.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
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/12670//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12670//console
This message is automatically generated.
> Ambari Infra, AMS, LogSearch are missing from list of services to be installed
> --
>
> Key: AMBARI-22447
> URL: https://issues.apache.org/jira/browse/AMBARI-22447
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Attachments: AMBARI-22447.patch
>
>
> Ambari Infra service is missing from list of services to be installed, This
> is one of the necessary services for Atlas and Ranger, other-wise need to
> setup Solr manually.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22418) Make Ambari configuration API consistent with existing API.
[
https://issues.apache.org/jira/browse/AMBARI-22418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16252177#comment-16252177
]
Hadoop QA commented on AMBARI-22418:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897615/AMBARI-22418_trunk_01.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 15 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:red}-1 core tests{color}. The test build failed in
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/12669//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12669//console
This message is automatically generated.
> Make Ambari configuration API consistent with existing API.
> ---
>
> Key: AMBARI-22418
> URL: https://issues.apache.org/jira/browse/AMBARI-22418
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Fix For: 3.0.0
>
> Attachments: AMBARI-22418_trunk_01.patch
>
>
> Make Ambari configuration API consistent with existing API.
> The current API entry point (as of AMBARI-21307) is
> {{/api/v1/ambariconfigs}}. This should be more inline with the existing entry
> point for Ambari server related data...
> {{/api/v1/services/AMBARI/components/AMBARI_SERVER}}.
> The new API entry point for Ambari server related configuration data should
> be {{/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations}}.
> Example Rest API calls:
> *Create/Set configuration*
> Used to create a new or explicitly set properties an existing Ambari Server
> configuration
> {noformat:title=URL}
> POST /api/v1/services/AMBARI/components/AMBARI_SERVER/configurations
> {noformat}
> {code:title=Payload}
> {
> "Configuration": {
> "category" : "ldap-configuration",
> "properties": {
> "ambari.ldap.bindanonymously": "true",
> "ambari.ldap.server.port": "389",
> "ambari.ldap.base.dn": "dc=example,dc=com",
> "ambari.ldap.user.object.class":"person",
> "ambari.ldap.user.name.attribute":"uid",
> "ambari.ldap.user.search.base": "dc=example,dc=com",
> "ambari.ldap.group.object.class":"groupOfUniqueNames",
> "ambari.ldap.group.name.attribute":"cn",
> "ambari.ldap.group.member.attribute":"uniqueMember",
> "ambari.ldap.group.search.base": "dc=example,dc=com"
> }
> }
> }
> {code}
> *Update configuration*
> Used to update existing properties or add new properties to an existing
> Ambari Server configuration
> {noformat:title=URL}
> PUT
> /api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/ldap-configuration
> {noformat}
> {code:title=Payload}
> {
> "Configuration": {
> "properties": {
> "ambari.ldap.bindanonymously": "true",
> "ambari.ldap.server.port": "389",
> "ambari.ldap.base.dn": "dc=example,dc=com",
> "ambari.ldap.user.object.class":"person",
> "ambari.ldap.user.name.attribute":"uid",
> "ambari.ldap.user.search.base": "dc=example,dc=com",
> "ambari.ldap.group.object.class":"groupOfUniqueNames",
> "ambari.ldap.group.name.attribute":"cn",
> "ambari.ldap.group.member.attribute":"uniqueMember",
> "ambari.ldap.group.search.base": "dc=example,dc=com"
> }
> }
> }
> {code}
> *Delete configuration*
> Deletes an existing Ambari Server configuration
> {noformat:title=URL}
> DELETE
> /api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/ldap-configuration
> {noformat}
> *Get configurations*
> Used to retrieve a list of the existing Ambari Server configurations
> {noformat:title=URL}
> GET /api/v1/services/AMBARI/components/AMBARI_SERVER/configurations
> {noformat}
> {code:title=Response}
> {
> "href" :
> "http://c6401.ambari.apache.org:8080/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations;,
> "items" : [
> {
> "href" :
> "http://c6401.ambari.apache.org:8080/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/ldap-configuration;,
> "Configuration" : {
> "category" : "ldap-configuration",
> "component_name" : "AMBARI_SERVER",
> "service_name" : "AMBARI"
> }
> }
> ]
> }
> {code}
> *Get configuration*
> Used to retrieve a the details
[jira] [Commented] (AMBARI-22435) Hive services sets incorrect permissions on the root of HDFS while setting up replication
[
https://issues.apache.org/jira/browse/AMBARI-22435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251716#comment-16251716
]
Hadoop QA commented on AMBARI-22435:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897443/AMBARI-22435-trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 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
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/12667//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12667//console
This message is automatically generated.
> Hive services sets incorrect permissions on the root of HDFS while setting up
> replication
> -
>
> Key: AMBARI-22435
> URL: https://issues.apache.org/jira/browse/AMBARI-22435
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Deepesh Khandelwal
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-22435-trunk.patch
>
>
> While starting Hive metastore or HiveServer2 observed that the hdfs audit log
> had the following entries:
> {noformat}
> 2017-11-14 01:48:03,682 INFO FSNamesystem.audit: allowed=true ugi=hdfs
> (auth:SIMPLE) ip=/172.27.70.128 cmd=getfileinfo src=/ dst=null
> perm=null proto=webhdfs
> 2017-11-14 01:48:03,745 INFO FSNamesystem.audit: allowed=true ugi=hdfs
> (auth:SIMPLE) ip=/172.27.70.128 cmd=setPermission src=/
> dst=nullperm=hdfs:hdfs:rwxrwxrwtproto=webhdfs
> 2017-11-14 01:48:03,809 INFO FSNamesystem.audit: allowed=true ugi=hdfs
> (auth:SIMPLE) ip=/172.27.70.128 cmd=setOwnersrc=/ dst=null
> perm=hive:hadoop:rwxrwxrwt proto=webhdfs
> 2017-11-14 01:48:04,126 INFO FSNamesystem.audit: allowed=true ugi=hdfs
> (auth:SIMPLE) ip=/172.27.70.128 cmd=getfileinfo src=/ dst=null
> perm=null proto=webhdfs
> 2017-11-14 01:48:04,189 INFO FSNamesystem.audit: allowed=true ugi=hdfs
> (auth:SIMPLE) ip=/172.27.70.128 cmd=setPermission src=/
> dst=nullperm=hive:hadoop:rwx-- proto=webhdfs
> {noformat}
> The consequence of this was that for any non-hdfs user you will see the
> following error running hadoop commands:
> {noformat}
> $ hadoop fs -ls /
> ls: Permission denied: user=root, access=READ_EXECUTE,
> inode="/":hive:hadoop:drwx--
> {noformat}
> On debugging this was happening due to incomplete null/empty check on params
> hive_repl_cmrootdir and hive_repl_rootdir in
> ambari/blob/trunk/ambari-server/src/main/resources/common-services/HIVE/2.1.0.3.0/package/scripts/hive.py.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22436) zookeeper service issue
[
https://issues.apache.org/jira/browse/AMBARI-22436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251658#comment-16251658
]
Hadoop QA commented on AMBARI-22436:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897453/AMBARI-22436.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
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/12666//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12666//console
This message is automatically generated.
> zookeeper service issue
> ---
>
> Key: AMBARI-22436
> URL: https://issues.apache.org/jira/browse/AMBARI-22436
> Project: Ambari
> Issue Type: Improvement
>Affects Versions: trunk
>Reporter: zhangxiaolu
>Assignee: zhangxiaolu
> Fix For: trunk
>
> Attachments: AMBARI-22436.patch, screenshot-1.png
>
>
> amabri-qa has not permission to write zookeeper'.log in the dir of
> /var/log/zookeeper for permission is 0755.
> so should set permission is 0777 when executing service check.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22438) Disable plugins for yum on yum list command
[
https://issues.apache.org/jira/browse/AMBARI-22438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251601#comment-16251601
]
Hadoop QA commented on AMBARI-22438:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897520/AMBARI-22438.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 .
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12665//console
This message is automatically generated.
> Disable plugins for yum on yum list command
> ---
>
> Key: AMBARI-22438
> URL: https://issues.apache.org/jira/browse/AMBARI-22438
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.1
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
> Fix For: 2.6.1
>
> Attachments: AMBARI-22438.patch
>
>
> On the system with configured RedHat Satellite, yum command could produce
> additional output, which can break packages list parser.
> To avoid the issue, plugins should be disabled on calling "yum list *" command
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22439) Host check operation is being performed on all hosts during host add should not get stuck
[
https://issues.apache.org/jira/browse/AMBARI-22439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251551#comment-16251551
]
Hadoop QA commented on AMBARI-22439:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897530/AMBARI-22439.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-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12664//console
This message is automatically generated.
> Host check operation is being performed on all hosts during host add should
> not get stuck
> -
>
> Key: AMBARI-22439
> URL: https://issues.apache.org/jira/browse/AMBARI-22439
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.6.1
>
> Attachments: AMBARI-22439.patch, AMBARI-22439_branch-2.6.patch
>
>
> Steps to reproduce:
> 1. Have a cluster with 2/3 hosts
> 2. now try to add a new host from UI
> 3. Ambari initiates host check for all the hosts in the cluster instead of
> doing it for new host alone. if there is any issues with other hosts then
> host add will get hung and will not be able to proceed further.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22431) Able to add config type if EU/RU of the same stack (minor version upgrade)
[
https://issues.apache.org/jira/browse/AMBARI-22431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251500#comment-16251500
]
Hadoop QA commented on AMBARI-22431:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897563/AMBARI-22431-v3.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:red}-1 core tests{color}. The test build failed in
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/12663//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12663//console
This message is automatically generated.
> Able to add config type if EU/RU of the same stack (minor version upgrade)
> --
>
> Key: AMBARI-22431
> URL: https://issues.apache.org/jira/browse/AMBARI-22431
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Di Li
>Assignee: Di Li
> Fix For: 2.6.1
>
> Attachments: AMBARI-22431-v2.patch, AMBARI-22431-v3.patch,
> AMBARI-22431.patch
>
>
> EU/RU does not create/load default of new config types when the source stack
> and target stack is the same. This JIRA introduces a new config task type for
> creating/loading defaults of a new config type when stack does not change
> during EU/RU. This is particularly important for EU/RU of custom services
> where their stack may not change at all.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22431) Able to add config type if EU/RU of the same stack (minor version upgrade)
[
https://issues.apache.org/jira/browse/AMBARI-22431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16250435#comment-16250435
]
Hadoop QA commented on AMBARI-22431:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897376/AMBARI-22431-v2.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:red}-1 javac{color}. The patch appears to cause the [build to
fail|https://builds.apache.org/job/Ambari-trunk-test-patch/12662//artifact/patch-work/patchJavacWarnings.txt].
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12662//console
This message is automatically generated.
> Able to add config type if EU/RU of the same stack (minor version upgrade)
> --
>
> Key: AMBARI-22431
> URL: https://issues.apache.org/jira/browse/AMBARI-22431
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Di Li
>Assignee: Di Li
> Fix For: 2.6.1
>
> Attachments: AMBARI-22431-v2.patch, AMBARI-22431.patch
>
>
> EU/RU does not create/load default of new config types when the source stack
> and target stack is the same. This JIRA introduces a new config task type for
> creating/loading defaults of a new config type when stack does not change
> during EU/RU. This is particularly important for EU/RU of custom services
> where their stack may not change at all.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22425) Ambari 3.0: Implement new design for Admin View: fix checkboxes
[
https://issues.apache.org/jira/browse/AMBARI-22425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16250208#comment-16250208
]
Hadoop QA commented on AMBARI-22425:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897312/AMBARI-22425.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-admin.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12661//console
This message is automatically generated.
> Ambari 3.0: Implement new design for Admin View: fix checkboxes
> ---
>
> Key: AMBARI-22425
> URL: https://issues.apache.org/jira/browse/AMBARI-22425
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-22425.patch, no-checkbox-visible.png
>
>
> After applying new styles checkboxes disappeared.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22426) Push down Logger instances
[
https://issues.apache.org/jira/browse/AMBARI-22426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16250164#comment-16250164
]
Hadoop QA commented on AMBARI-22426:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897324/AMBARI-22426.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
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/12660//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12660//console
This message is automatically generated.
> Push down Logger instances
> --
>
> Key: AMBARI-22426
> URL: https://issues.apache.org/jira/browse/AMBARI-22426
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: AMBARI-22426.patch
>
>
> {{Logger}} prepends classname and line number to log messages. Reusing
> {{Logger}} from other classes makes it more difficult to understand where the
> log message is coming from. This includes {{Logger}} instances inherited
> from parent classes.
> {noformat:title=example}
> 13 Nov 2017 11:55:13,571 INFO [ambari-client-thread-36]
> AbstractResourceProvider:525 - Creating Cluster 'TEST' based on blueprint
> 'blue'.
> 13 Nov 2017 11:55:13,623 ERROR [ambari-client-thread-36]
> BaseManagementHandler:79 - Caught a runtime exception while attempting to
> create a resource: null
> {noformat}
> In the above example, log is written from {{ClusterResourceProvider}} and
> {{CreateHandler}}, respectively, but one needs to search the source code for
> the messages to find this out.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22427) Check if configurations used for commands are of correct version
[
https://issues.apache.org/jira/browse/AMBARI-22427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16250055#comment-16250055
]
Hadoop QA commented on AMBARI-22427:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897325/AMBARI-22427.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/12659//console
This message is automatically generated.
> Check if configurations used for commands are of correct version
>
>
> Key: AMBARI-22427
> URL: https://issues.apache.org/jira/browse/AMBARI-22427
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-22427.patch
>
>
> This was not reproduced, but theoretically race condition might occur causing
> configuration update event to be received later than the actual commands which
> needs those configs.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22429) Log Search UI: implement logout
[
https://issues.apache.org/jira/browse/AMBARI-22429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16250053#comment-16250053
]
Hadoop QA commented on AMBARI-22429:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897332/AMBARI-22429.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/12658//console
This message is automatically generated.
> Log Search UI: implement logout
> ---
>
> Key: AMBARI-22429
> URL: https://issues.apache.org/jira/browse/AMBARI-22429
> Project: Ambari
> Issue Type: Task
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Istvan Tobias
> Fix For: 3.0.0
>
> Attachments: AMBARI-22429.patch
>
>
> Logout control should be available from user menu.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22431) Able to add config type if EU/RU of the same stack (minor version upgrade)
[
https://issues.apache.org/jira/browse/AMBARI-22431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16250017#comment-16250017
]
Hadoop QA commented on AMBARI-22431:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897358/AMBARI-22431.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:red}-1 javac{color}. The patch appears to cause the [build to
fail|https://builds.apache.org/job/Ambari-trunk-test-patch/12656//artifact/patch-work/patchJavacWarnings.txt].
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12656//console
This message is automatically generated.
> Able to add config type if EU/RU of the same stack (minor version upgrade)
> --
>
> Key: AMBARI-22431
> URL: https://issues.apache.org/jira/browse/AMBARI-22431
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Di Li
>Assignee: Di Li
> Fix For: 2.6.1
>
> Attachments: AMBARI-22431.patch
>
>
> EU/RU does not create/load default of new config types when the source stack
> and target stack is the same. This JIRA introduces a new config task type for
> creating/loading defaults of a new config type when stack does not change
> during EU/RU. This is particularly important for EU/RU of custom services
> where their stack may not change at all.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22420) Enable mpack version selection
[
https://issues.apache.org/jira/browse/AMBARI-22420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16249984#comment-16249984
]
Hadoop QA commented on AMBARI-22420:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897359/AMBARI-22420.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/12655//console
This message is automatically generated.
> Enable mpack version selection
> --
>
> Key: AMBARI-22420
> URL: https://issues.apache.org/jira/browse/AMBARI-22420
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Jason Golieb
>Assignee: Jason Golieb
> Fix For: 3.0.0
>
> Attachments: AMBARI-22420.patch
>
>
> Implement the ability to change mpack version in the available mpacks list.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22429) Log Search UI: implement logout
[
https://issues.apache.org/jira/browse/AMBARI-22429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16249982#comment-16249982
]
Hadoop QA commented on AMBARI-22429:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897332/AMBARI-22429.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/12654//console
This message is automatically generated.
> Log Search UI: implement logout
> ---
>
> Key: AMBARI-22429
> URL: https://issues.apache.org/jira/browse/AMBARI-22429
> Project: Ambari
> Issue Type: Task
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Istvan Tobias
> Fix For: 3.0.0
>
> Attachments: AMBARI-22429.patch
>
>
> Logout control should be available from user menu.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22318) repositoryFile entity populating for wrong repository for RU
[
https://issues.apache.org/jira/browse/AMBARI-22318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16248211#comment-16248211
]
Hadoop QA commented on AMBARI-22318:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897141/AMBARI-22318.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/12652//console
This message is automatically generated.
> repositoryFile entity populating for wrong repository for RU
> --
>
> Key: AMBARI-22318
> URL: https://issues.apache.org/jira/browse/AMBARI-22318
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.1
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.6.1
>
> Attachments: AMBARI-22318.patch, AMBARI-22318.v1.patch,
> AMBARI-22318.v2.preview.patch
>
>
> In populating repositoryFile entity we relating to desired stack version,
> what i correct for RU, as desired state switched there exactly at upgrade
> creation time, while for RU we doing it later.
> Due to entity populating far ahead of real upgrade, for RU it populated for
> source repository version instead of target.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22420) Enable mpack version selection
[
https://issues.apache.org/jira/browse/AMBARI-22420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16248209#comment-16248209
]
Hadoop QA commented on AMBARI-22420:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897145/AMBARI-22420.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/12651//console
This message is automatically generated.
> Enable mpack version selection
> --
>
> Key: AMBARI-22420
> URL: https://issues.apache.org/jira/browse/AMBARI-22420
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Jason Golieb
>Assignee: Jason Golieb
> Fix For: 3.0.0
>
> Attachments: AMBARI-22420.patch
>
>
> Implement the ability to change mpack version in the available mpacks list.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22413) Fix tar_archive.py: 1. remove verbosity flags, 2. fix archive_dir() and archive_directory_dereference() methods
[
https://issues.apache.org/jira/browse/AMBARI-22413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16248207#comment-16248207
]
Hadoop QA commented on AMBARI-22413:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897101/AMBARI-22413-fix-tar-trunk_v1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 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-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12650//console
This message is automatically generated.
> Fix tar_archive.py: 1. remove verbosity flags, 2. fix archive_dir() and
> archive_directory_dereference() methods
> ---
>
> Key: AMBARI-22413
> URL: https://issues.apache.org/jira/browse/AMBARI-22413
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Balázs Bence Sári
>Assignee: Balázs Bence Sári
>Priority: Critical
> Attachments: AMBARI-22413-fix-tar-trunk_v1.patch
>
>
> There are two issues with tar_archive.py which caused a HDP upgrade to fail
> at a customer:
> # The verbose flag (-v) is switched on. This could result in long archival
> time and timeouts
> # The full path of the files is preserverved in the archive without the
> leading slash. This results in doubled paths when the archive is expanded.
> E.g:
> The contents of _/hadoop/falcon/_ directory is archived.
> All files are archived with full path but no leading slash:
> _hadoop/falcon//_
> After unpacking the unpacked file will look like:
> _/hadoop/falcon/hadoop/falcon//_.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22417) Ambari checks fail with FIPS mode is activated on the OS
[
https://issues.apache.org/jira/browse/AMBARI-22417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16248139#comment-16248139
]
Hadoop QA commented on AMBARI-22417:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897110/AMBARI-22417_branch-2.6_01.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 .
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12649//console
This message is automatically generated.
> Ambari checks fail with FIPS mode is activated on the OS
>
>
> Key: AMBARI-22417
> URL: https://issues.apache.org/jira/browse/AMBARI-22417
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Affects Versions: 2.5.1
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Fix For: 2.6.1
>
> Attachments: AMBARI-22417_branch-2.6_01.patch,
> AMBARI-22417_trunk_01.patch
>
>
> Ambari checks fail with FIPS mode is activated on the OS (Rhel7). FIPS mode
> disables weak ciphers (such as MD5).
> Ambari code is doing
> {code}
> ccache_file_name = _md5("
> {0}|{1}".format(principal, keytab)).hexdigest(). MD5 is disabled on the OS
> (RHEL7) so ambari throws errors.
> {code}
> - All service checks fail, Ranger KMS start fails via ambari.
> - However all the services are actually running and fine.
> - Also Ranger KMS succesfully started from command Line
> Here is the stack trace from Ambari
> {code}
> service_check
> params.kinit_path_local, False, None, params.smoke_user)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/curl_krb_request.py",
> line 109, in curl_krb_request
> ccache_file_name = _md5("{0}
> |
> {1}
> ".format(principal, keytab)).hexdigest()
> ValueError: error:060800A3:digital envelope
> routines:EVP_DigestInit_ex:disabled for fips
> {code}
> Fix:
> MD5 is disabled on the OS, Code needs to be updated to use SHA?
> This is required when FIPS mode is enabled on the RHEL OS
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22416) Log Search UI: fixes for filtering form
[
https://issues.apache.org/jira/browse/AMBARI-22416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16248035#comment-16248035
]
Hadoop QA commented on AMBARI-22416:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897107/AMBARI-22416.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/12648//console
This message is automatically generated.
> Log Search UI: fixes for filtering form
> ---
>
> Key: AMBARI-22416
> URL: https://issues.apache.org/jira/browse/AMBARI-22416
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-22416.patch
>
>
> # Checkboxes in multiselect, labels of dropdown filter buttons etc. should
> pick up currently selected value even if it's set from outside the form
> # All the tabs should have their own isolated filtering options, so that
> filters application on one tab doesn't affect other tab
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22412) Remove IPA integration from experimental status
[
https://issues.apache.org/jira/browse/AMBARI-22412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16247628#comment-16247628
]
Hadoop QA commented on AMBARI-22412:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897064/AMBARI-22412_trunk_01.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 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/12647//console
This message is automatically generated.
> Remove IPA integration from experimental status
> ---
>
> Key: AMBARI-22412
> URL: https://issues.apache.org/jira/browse/AMBARI-22412
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-22412_trunk_01.patch
>
>
> Remove IPA integration from experimental status so that users can select
> FreeIPA when enabling Kerberos via the Enable Kerberos Wizard without having
> to explicitly enable it via the Experimental page.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22390) Implement many-to-many relation between keytabs and principals
[
https://issues.apache.org/jira/browse/AMBARI-22390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16245926#comment-16245926
]
Hadoop QA commented on AMBARI-22390:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12896881/AMBARI-22390.1.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-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12644//console
This message is automatically generated.
> Implement many-to-many relation between keytabs and principals
> --
>
> Key: AMBARI-22390
> URL: https://issues.apache.org/jira/browse/AMBARI-22390
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Eugene Chekanskiy
>Assignee: Eugene Chekanskiy
> Fix For: 3.0.0
>
> Attachments: AMBARI-22390.1.patch, AMBARI-22390.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22400) Ambari 3.0: Implement new design for Admin View: Cluster Information page
[
https://issues.apache.org/jira/browse/AMBARI-22400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16245797#comment-16245797
]
Hadoop QA commented on AMBARI-22400:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12896876/AMBARI-22400.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-admin.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12643//console
This message is automatically generated.
> Ambari 3.0: Implement new design for Admin View: Cluster Information page
> -
>
> Key: AMBARI-22400
> URL: https://issues.apache.org/jira/browse/AMBARI-22400
> 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-22400.patch
>
>
> Add Cluster Information page.
> Move stack versions to a separate page Versions.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22402) PERF stack: Deploy fails due to common hooks being used instead of one specific to PERF
[
https://issues.apache.org/jira/browse/AMBARI-22402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16245758#comment-16245758
]
Hadoop QA commented on AMBARI-22402:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12896875/AMBARI-22402.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/12642//console
This message is automatically generated.
> PERF stack: Deploy fails due to common hooks being used instead of one
> specific to PERF
> ---
>
> Key: AMBARI-22402
> URL: https://issues.apache.org/jira/browse/AMBARI-22402
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-22402.patch
>
>
> Hooks location should be customizible. Because perf stack uses different hooks
> folder.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22398) Upstart is not able to stop the ambari-agent
[
https://issues.apache.org/jira/browse/AMBARI-22398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16245757#comment-16245757
]
Hadoop QA commented on AMBARI-22398:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12896874/AMBARI-22398.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
[ambari-agent|https://builds.apache.org/job/Ambari-trunk-test-patch/12641//artifact/patch-work/testrun_ambari-agent.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12641//console
This message is automatically generated.
> Upstart is not able to stop the ambari-agent
>
>
> Key: AMBARI-22398
> URL: https://issues.apache.org/jira/browse/AMBARI-22398
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-22398.patch
>
>
> While starting ambari-agent using "service ambari-agent start" it works fine
> but when we used try to check status using "start ambari-agent" (upstart
> command) facing issue. But when we start ambari agent using "start ambari-
> agent" it's works but at this time when we checked status using service
> command facing issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22390) Implement many-to-many relation between keytabs and principals
[
https://issues.apache.org/jira/browse/AMBARI-22390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16245716#comment-16245716
]
Hadoop QA commented on AMBARI-22390:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12896858/AMBARI-22390.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-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12640//console
This message is automatically generated.
> Implement many-to-many relation between keytabs and principals
> --
>
> Key: AMBARI-22390
> URL: https://issues.apache.org/jira/browse/AMBARI-22390
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Eugene Chekanskiy
>Assignee: Eugene Chekanskiy
> Fix For: 3.0.0
>
> Attachments: AMBARI-22390.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22387) Create a Pre-Upgrade Check Warning About LZO
[
https://issues.apache.org/jira/browse/AMBARI-22387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16245552#comment-16245552
]
Hadoop QA commented on AMBARI-22387:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12896836/AMBARI-22387.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 46 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:red}-1 javac{color}. The patch appears to cause the [build to
fail|https://builds.apache.org/job/Ambari-trunk-test-patch/12639//artifact/patch-work/patchJavacWarnings.txt].
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12639//console
This message is automatically generated.
> Create a Pre-Upgrade Check Warning About LZO
>
>
> Key: AMBARI-22387
> URL: https://issues.apache.org/jira/browse/AMBARI-22387
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Attachments: AMBARI-22387.patch
>
>
> Ambari has removed its native support of distributing and installing LZO when
> the LZO codecs are enabled in {{core-site}}. For existing clusters where LZO
> is enabled, this means that performing an upgrade will now require manual
> user intervention to get the LZO packages installed.
> A pre-upgrade check should be created which checks to see if LZO is enabled
> in the cluster and then produces a {{WARNING}} to the user letting them know
> that before upgrading, they'd need to distribute the appropriate LZO packages.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22388) Log Search UI: restyle logs list
[
https://issues.apache.org/jira/browse/AMBARI-22388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16245537#comment-16245537
]
Hadoop QA commented on AMBARI-22388:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12896850/AMBARI-22388.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/12638//console
This message is automatically generated.
> Log Search UI: restyle logs list
>
>
> Key: AMBARI-22388
> URL: https://issues.apache.org/jira/browse/AMBARI-22388
> Project: Ambari
> Issue Type: Task
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Istvan Tobias
> Fix For: 3.0.0
>
> Attachments: AMBARI-22388.patch
>
>
> Restyle logs list as table.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22388) Log Search UI: restyle logs list
[
https://issues.apache.org/jira/browse/AMBARI-22388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16245533#comment-16245533
]
Hadoop QA commented on AMBARI-22388:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12896850/AMBARI-22388.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/12637//console
This message is automatically generated.
> Log Search UI: restyle logs list
>
>
> Key: AMBARI-22388
> URL: https://issues.apache.org/jira/browse/AMBARI-22388
> Project: Ambari
> Issue Type: Task
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Istvan Tobias
> Fix For: 3.0.0
>
> Attachments: AMBARI-22388.patch
>
>
> Restyle logs list as table.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22249) Add service group dependencies
[
https://issues.apache.org/jira/browse/AMBARI-22249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16245262#comment-16245262
]
Hadoop QA commented on AMBARI-22249:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12896769/AMBARI-22249_part2.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/12636//console
This message is automatically generated.
> Add service group dependencies
> --
>
> Key: AMBARI-22249
> URL: https://issues.apache.org/jira/browse/AMBARI-22249
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
> Fix For: 3.0.0
>
> Attachments: AMBARI-22249.patch, AMBARI-22249_part2.patch
>
>
> Add table servicegroupdependencies
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22386) Patch Upgrades Broken For Clients Due To Versioned LD Library
[
https://issues.apache.org/jira/browse/AMBARI-22386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16244893#comment-16244893
]
Hadoop QA commented on AMBARI-22386:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12896728/AMBARI-22386.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-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12635//console
This message is automatically generated.
> Patch Upgrades Broken For Clients Due To Versioned LD Library
> -
>
> Key: AMBARI-22386
> URL: https://issues.apache.org/jira/browse/AMBARI-22386
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22386.patch
>
>
> When services are patched to different versions, jobs being run in containers
> are unable to pickup the correct JARs from the {{LD_LIBRARY_PATH}} passed in
> via the job.
> Consider the following situation:
> - Base cluster installed at 2.6.3.0-1
> - Enable some sort of codec, like snappy
> - YARN patched to 2.6.3.1-1
> - Hive patched to 2.6.3.2-1
> When Hive goes to run jobs on Tez or when jobs are run on MapR, whatever is
> sending the job is resolving the {{hdp.version}} to its own version. The box
> that the job runs on, however, might not have that specific versioned
> directory.
> The problem can only be solved externally by providing a way to ensure that
> the native libraries are on every machine which could potentially run jobs.
> We could install bits on every host, but that would defeat the space-saving
> purposes of patch upgrades.
> Another solution is to ensure that the Tez and MapR tarballs have the
> required libraries and that those libraries are added to the classpath of
> launched jobs.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22327) Allow different OS types and versions for Hybrid setup
[
https://issues.apache.org/jira/browse/AMBARI-22327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16244546#comment-16244546
]
Hadoop QA commented on AMBARI-22327:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12896658/AMBARI-22327.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-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12634//console
This message is automatically generated.
> Allow different OS types and versions for Hybrid setup
> --
>
> Key: AMBARI-22327
> URL: https://issues.apache.org/jira/browse/AMBARI-22327
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Yussuf Shaikh
>Assignee: Yussuf Shaikh
> Attachments: AMBARI-22327.patch
>
>
> For setting up Ambari hybrid cluster we need to allow different OS types for
> agent hosts as compared to the server OS type.
> The strict check during bootstrap needs to be changed in os_check_type.py
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22383) Remove Auto-Installation of LZO Libraries
[
https://issues.apache.org/jira/browse/AMBARI-22383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16244461#comment-16244461
]
Hadoop QA commented on AMBARI-22383:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12896685/AMBARI-22383.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/12633//console
This message is automatically generated.
> Remove Auto-Installation of LZO Libraries
> -
>
> Key: AMBARI-22383
> URL: https://issues.apache.org/jira/browse/AMBARI-22383
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.6.1
>
> Attachments: AMBARI-22383.patch
>
>
> The LZO library licenses are not compatible with Ambari's license and should
> not be assumed to be available in Apache-based repositories.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22382) Integrate Host-component maintenance state and stale configs with websocket events
[
https://issues.apache.org/jira/browse/AMBARI-22382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16243830#comment-16243830
]
Hadoop QA commented on AMBARI-22382:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12896643/AMBARI-22382.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/12632//console
This message is automatically generated.
> Integrate Host-component maintenance state and stale configs with websocket
> events
> --
>
> Key: AMBARI-22382
> URL: https://issues.apache.org/jira/browse/AMBARI-22382
> 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-22382.patch
>
>
> /events/hostcomponents should be extended or add another topic in order to
> provide these fields.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22379) get_phoenix_query_server_hosts is undefined in hbase service_advisor
[
https://issues.apache.org/jira/browse/AMBARI-22379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16243776#comment-16243776
]
Hadoop QA commented on AMBARI-22379:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12896512/AMBARI-22379.v1.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-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12631//console
This message is automatically generated.
> get_phoenix_query_server_hosts is undefined in hbase service_advisor
>
>
> Key: AMBARI-22379
> URL: https://issues.apache.org/jira/browse/AMBARI-22379
> Project: Ambari
> Issue Type: Bug
>Reporter: Ted Yu
> Attachments: AMBARI-22379.v1.patch
>
>
> When deploying HDP 3.0 TP, I got:
> {code}
> Stack Advisor reported an error. Exit Code: 2. Error: AttributeError:
> 'HBASERecommender' object has no attribute 'get_phoenix_query_server_hosts'
> {code}
> Related code seems to have come from AMBARI-20327
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22249) Add service group dependencies
[
https://issues.apache.org/jira/browse/AMBARI-22249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16243747#comment-16243747
]
Hadoop QA commented on AMBARI-22249:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12896540/AMBARI-22249_part2.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/12630//console
This message is automatically generated.
> Add service group dependencies
> --
>
> Key: AMBARI-22249
> URL: https://issues.apache.org/jira/browse/AMBARI-22249
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
> Fix For: 3.0.0
>
> Attachments: AMBARI-22249.patch, AMBARI-22249_part2.patch
>
>
> Add table servicegroupdependencies
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22377) Ambari 3.0: Implement new design for Admin View: Views page
[
https://issues.apache.org/jira/browse/AMBARI-22377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16242454#comment-16242454
]
Hadoop QA commented on AMBARI-22377:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12896454/AMBARI-22377.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-admin.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12629//console
This message is automatically generated.
> Ambari 3.0: Implement new design for Admin View: Views page
> ---
>
> Key: AMBARI-22377
> URL: https://issues.apache.org/jira/browse/AMBARI-22377
> 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-22377.patch
>
>
> Views and View URLs pages will be merged into one.
> Add Create Instance modal.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22378) BI 4.2.5 repoinfo misses the redhat-ppc7 section
[
https://issues.apache.org/jira/browse/AMBARI-22378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16242375#comment-16242375
]
Hadoop QA commented on AMBARI-22378:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12896460/AMBARI-22378.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/12628//console
This message is automatically generated.
> BI 4.2.5 repoinfo misses the redhat-ppc7 section
>
>
> Key: AMBARI-22378
> URL: https://issues.apache.org/jira/browse/AMBARI-22378
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.1
>Reporter: Di Li
>Assignee: Di Li
> Fix For: 2.6.1
>
> Attachments: AMBARI-22378.patch
>
>
> BI 4.2.5 repoinfo misses the redhat-ppc7 section, where it currently only has
> a redhat6 and a redhat7 section.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22377) Ambari 3.0: Implement new design for Admin View: Views page
[
https://issues.apache.org/jira/browse/AMBARI-22377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16242373#comment-16242373
]
Hadoop QA commented on AMBARI-22377:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12896454/AMBARI-22377.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-admin.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12627//console
This message is automatically generated.
> Ambari 3.0: Implement new design for Admin View: Views page
> ---
>
> Key: AMBARI-22377
> URL: https://issues.apache.org/jira/browse/AMBARI-22377
> 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-22377.patch
>
>
> Views and View URLs pages will be merged into one.
> Add Create Instance modal.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22376) Log Search UI: add navigation to first and last page
[
https://issues.apache.org/jira/browse/AMBARI-22376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16242187#comment-16242187
]
Hadoop QA commented on AMBARI-22376:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12896441/AMBARI-22376.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/12625//console
This message is automatically generated.
> Log Search UI: add navigation to first and last page
>
>
> Key: AMBARI-22376
> URL: https://issues.apache.org/jira/browse/AMBARI-22376
> Project: Ambari
> Issue Type: Task
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Istvan Tobias
> Fix For: 3.0.0
>
> Attachments: AMBARI-22376.patch
>
>
> Pagination controls block should contain links to the first and last page.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22375) Multiple issue with handling unexcepted situations
[
https://issues.apache.org/jira/browse/AMBARI-22375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16242045#comment-16242045
]
Hadoop QA commented on AMBARI-22375:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12896429/AMBARI-22375.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/12624//console
This message is automatically generated.
> Multiple issue with handling unexcepted situations
> --
>
> Key: AMBARI-22375
> URL: https://issues.apache.org/jira/browse/AMBARI-22375
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-22375.patch
>
>
> * If on_update_cache fails cache should be discard
> * loggers should log messages during initialization of classes
> * hash of cache should only updated if saving/processing it was sucessful
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22375) Multiple issue with handling unexcepted situations
[
https://issues.apache.org/jira/browse/AMBARI-22375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16242032#comment-16242032
]
Hadoop QA commented on AMBARI-22375:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12896429/AMBARI-22375.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/12623//console
This message is automatically generated.
> Multiple issue with handling unexcepted situations
> --
>
> Key: AMBARI-22375
> URL: https://issues.apache.org/jira/browse/AMBARI-22375
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-22375.patch
>
>
> * If on_update_cache fails cache should be discard
> * loggers should log messages during initialization of classes
> * hash of cache should only updated if saving/processing it was sucessful
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22374) Log Search UI: button with caret doesn't toggle dropdown is some cases
[
https://issues.apache.org/jira/browse/AMBARI-22374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16242028#comment-16242028
]
Hadoop QA commented on AMBARI-22374:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12896426/AMBARI-22374.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/12622//console
This message is automatically generated.
> Log Search UI: button with caret doesn't toggle dropdown is some cases
> --
>
> Key: AMBARI-22374
> URL: https://issues.apache.org/jira/browse/AMBARI-22374
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Istvan Tobias
> Fix For: 3.0.0
>
> Attachments: AMBARI-22374.patch
>
>
> If user clicks in the gap between icon and caret, dropdown isn't toggled.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22369) Remove Auto-Installation of Mysql Connector
[
https://issues.apache.org/jira/browse/AMBARI-22369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241625#comment-16241625
]
Hadoop QA commented on AMBARI-22369:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12896262/AMBARI-22369.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/12621//console
This message is automatically generated.
> Remove Auto-Installation of Mysql Connector
> ---
>
> Key: AMBARI-22369
> URL: https://issues.apache.org/jira/browse/AMBARI-22369
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22369.patch
>
>
> The mysql connector license is not compatible with Ambari's license and it is
> a big assumption that users will be able to create their own repo definition
> that includes it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22370) Remove HADOOP_HOME From Environment For Daemons
[
https://issues.apache.org/jira/browse/AMBARI-22370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241619#comment-16241619
]
Hadoop QA commented on AMBARI-22370:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12896272/AMBARI-22370.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 5 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-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12620//console
This message is automatically generated.
> Remove HADOOP_HOME From Environment For Daemons
> ---
>
> Key: AMBARI-22370
> URL: https://issues.apache.org/jira/browse/AMBARI-22370
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.1
>
> Attachments: AMBARI-22370.patch
>
>
> The wrapper scripts for services should be setting {{HADOOP_HOME}} correctly
> regardless of whether or not an upgrade is taking place. There are many spots
> which we current override this value and pass it in:
> - Either via the Python files and setting the {{environment}}
> - Or by setting it in configuration files
> This should be removed since we must rely on correct {{HADOOP_HOME}} to be
> set by the wrapper scripts.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22371) Bulk host delete to be hidden as experimental property
[
https://issues.apache.org/jira/browse/AMBARI-22371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241593#comment-16241593
]
Hadoop QA commented on AMBARI-22371:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12896309/AMBARI-22371_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/12619//console
This message is automatically generated.
> Bulk host delete to be hidden as experimental property
> --
>
> Key: AMBARI-22371
> URL: https://issues.apache.org/jira/browse/AMBARI-22371
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2, 2.6.0
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
> Fix For: 2.6.1
>
> Attachments: AMBARI-22371_branch-2.6.patch
>
>
> Bulk delete host option is not supported up to 2.6 release and should be an
> experimental property. Also backport fix for AMBARI-18805
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22372) DLM install failed on an unsecure upgraded cluster, due to missing configs
[
https://issues.apache.org/jira/browse/AMBARI-22372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241589#comment-16241589
]
Hadoop QA commented on AMBARI-22372:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12896329/AMBARI-22372.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-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12618//console
This message is automatically generated.
> DLM install failed on an unsecure upgraded cluster, due to missing configs
> --
>
> Key: AMBARI-22372
> URL: https://issues.apache.org/jira/browse/AMBARI-22372
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
> Fix For: trunk, 2.6.1
>
> Attachments: AMBARI-22372.patch, AMBARI-22372_branch-2.6.patch,
> Screen Shot 2017-10-27 at 18.32.05 (1).png, Screen Shot 2017-10-27 at 4.14.39
> PM.png
>
>
> On an upgraded unsecure cluster, dlm install fails , this could be due to
> some of the dependent configs missing:
> Screen Shot 2017-10-27 at 4.14.39 PM.png
> The missing configs can be found in the screenshot below (This cluster is a
> fresh install of hdp2.6.3 where the dlm add service succeeded)
> Screen Shot 2017-10-27 at 18.32.05 (1).png
> Add service of DLM works fine on a secure upgraded cluster as well as fresh
> install (no-upgrade) unsecure cluster
> This is a multi-cluster environment (2 clusters)
> Setup details:
> ambari version before upgrade :2.5.2.0-298
> ambari version after upgrade: 2.6.0.0-264
> hdp version after upgrade :2.6.3.0-232
> DLM mpack version :
> http://s3.amazonaws.com/dev.hortonworks.com/DLM/centos7/1.x/BUILDS/1.0.0.0-155/tars/beacon/beacon-ambari-mpack-1.0.0.0-155.tar.gz
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22368) Log Search UI: move top menu down
[
https://issues.apache.org/jira/browse/AMBARI-22368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16240659#comment-16240659
]
Hadoop QA commented on AMBARI-22368:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12896222/AMBARI-22368.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/12617//console
This message is automatically generated.
> Log Search UI: move top menu down
> -
>
> Key: AMBARI-22368
> URL: https://issues.apache.org/jira/browse/AMBARI-22368
> Project: Ambari
> Issue Type: Task
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Istvan Tobias
> Fix For: 3.0.0
>
> Attachments: AMBARI-22368.patch
>
>
> Top menu (Undo, Redo, Refresh, History) should be located on one line with
> tabs, aligned to right. Logout button should remain on its place.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22368) Log Search UI: move top menu down
[
https://issues.apache.org/jira/browse/AMBARI-22368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16240619#comment-16240619
]
Hadoop QA commented on AMBARI-22368:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12616//console
This message is automatically generated.
> Log Search UI: move top menu down
> -
>
> Key: AMBARI-22368
> URL: https://issues.apache.org/jira/browse/AMBARI-22368
> Project: Ambari
> Issue Type: Task
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Istvan Tobias
> Fix For: 3.0.0
>
> Attachments: AMBARI-22368.patch
>
>
> Top menu (Undo, Redo, Refresh, History) should be located on one line with
> tabs, aligned to right. Logout button should remain on its place.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
