[jira] [Created] (AMBARI-22746) Ambari Metrics not starting in Debian.
Aravindan Vijayan created AMBARI-22746: -- Summary: Ambari Metrics not starting in Debian. Key: AMBARI-22746 URL: https://issues.apache.org/jira/browse/AMBARI-22746 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.6.1 Reporter: Aravindan Vijayan Priority: Critical ambari-metrics-assembly is installed, but it does not create /usr/lib/ambari-metrics-collector. If the folder is manually created, and then reinstall works (apt-get install --reinstall ambari-metrics-assembly). It seems there's something wrong with the deb package that causes it to silently fail to create the folder before trying to place the jars. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-22746) Ambari Metrics not starting in Debian.
[ https://issues.apache.org/jira/browse/AMBARI-22746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan reassigned AMBARI-22746: -- Assignee: Aravindan Vijayan > Ambari Metrics not starting in Debian. > -- > > Key: AMBARI-22746 > URL: https://issues.apache.org/jira/browse/AMBARI-22746 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.6.1 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > > ambari-metrics-assembly is installed, but it does not create > /usr/lib/ambari-metrics-collector. > If the folder is manually created, and then reinstall works (apt-get install > --reinstall ambari-metrics-assembly). It seems there's something wrong with > the deb package that causes it to silently fail to create the folder before > trying to place the jars. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22740) Fix integration test for HBase in branch-3.0-ams due to UUID changes
[
https://issues.apache.org/jira/browse/AMBARI-22740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16314180#comment-16314180
]
Hadoop QA commented on AMBARI-22740:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904853/AMBARI-22740.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/12937//console
This message is automatically generated.
> Fix integration test for HBase in branch-3.0-ams due to UUID changes
>
>
> Key: AMBARI-22740
> URL: https://issues.apache.org/jira/browse/AMBARI-22740
> Project: Ambari
> Issue Type: Task
> Components: ambari-metrics
>Affects Versions: 3.0.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-22740.patch
>
>
> Fixing all integration tests in AMS timeline-service module.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22741) Log Search UI: implement graph for access logs
[ https://issues.apache.org/jira/browse/AMBARI-22741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16314178#comment-16314178 ] Hudson commented on AMBARI-22741: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8579 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8579/]) AMBARI-22741 Log Search UI: implement graph for access logs. (ababiichuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=011e448e22acf6b5f677aaab0c41d064e4d66577]) * (add) ambari-logsearch/ambari-logsearch-web/src/app/components/time-line-graph/time-line-graph.component.less * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/logs-container/logs-container.component.html * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/time-histogram/time-histogram.component.html * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/menu-button/menu-button.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/time-range-picker/time-range-picker.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/top-menu/top-menu.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/horizontal-histogram/horizontal-histogram.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/component-actions.service.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/time-histogram/time-histogram.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/classes/models/store.ts * (add) ambari-logsearch/ambari-logsearch-web/src/app/components/time-line-graph/time-line-graph.component.spec.ts * (add) ambari-logsearch/ambari-logsearch-web/src/app/components/time-line-graph/time-line-graph.component.html * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/component-generator.service.spec.ts * (add) ambari-logsearch/ambari-logsearch-web/src/app/services/storage/audit-logs-graph-data.service.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/audit-logs-table/audit-logs-table.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/logs-container/logs-container.component.ts * (add) ambari-logsearch/ambari-logsearch-web/src/app/classes/components/graph/time-graph.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/app.module.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/mock-data.ts * (add) ambari-logsearch/ambari-logsearch-web/src/app/components/time-line-graph/time-line-graph.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/audit-logs-entries/audit-logs-entries.component.html * (add) ambari-logsearch/ambari-logsearch-web/src/app/classes/components/graph/time-graph.component.less * (edit) ambari-logsearch/ambari-logsearch-web/src/app/classes/queries/service-logs-histogram-query-params.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/collapsible-panel/collapsible-panel.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/filters-panel/filters-panel.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/filter-dropdown/filter-dropdown.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/time-histogram/time-histogram.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/classes/graph.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/logs-container.service.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/http-client.service.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/logs-container/logs-container.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/filter-button/filter-button.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/collapsible-panel/collapsible-panel.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/classes/components/graph/graph.component.less * (edit) ambari-logsearch/ambari-logsearch-web/src/assets/i18n/en.json * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/dropdown-list/dropdown-list.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/collapsible-panel/collapsible-panel.component.html * (delete) ambari-logsearch/ambari-logsearch-web/src/app/classes/queries/service-logs-histogram-query-params.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/log-context/log-context.component.spec.ts * (add) ambari-logsearch/ambari-logsearch-web/src/app/classes/queries/audit-logs-graph-query-params.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/logs-container.service.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/service-logs-table/service-logs-table.component.spe
[jira] [Updated] (AMBARI-22741) Log Search UI: implement graph for access logs
[ https://issues.apache.org/jira/browse/AMBARI-22741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-22741: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > Log Search UI: implement graph for access logs > -- > > Key: AMBARI-22741 > URL: https://issues.apache.org/jira/browse/AMBARI-22741 > 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-22741.patch > > > Line chart with time-dependent counts of access events from different sources > should be implemented. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22741) Log Search UI: implement graph for access logs
[
https://issues.apache.org/jira/browse/AMBARI-22741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16314114#comment-16314114
]
Hadoop QA commented on AMBARI-22741:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904845/AMBARI-22741.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/12936//console
This message is automatically generated.
> Log Search UI: implement graph for access logs
> --
>
> Key: AMBARI-22741
> URL: https://issues.apache.org/jira/browse/AMBARI-22741
> 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-22741.patch
>
>
> Line chart with time-dependent counts of access events from different sources
> should be implemented.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22744) Fix issues with webapp deployment with new Hadoop common changes
[ https://issues.apache.org/jira/browse/AMBARI-22744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-22744: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to branch-3.0-ams > Fix issues with webapp deployment with new Hadoop common changes > > > Key: AMBARI-22744 > URL: https://issues.apache.org/jira/browse/AMBARI-22744 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-22744.patch > > > - Fix deploy time issues after migration. > - Fix imports. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22740) Fix integration test for HBase in branch-3.0-ams due to UUID changes
[ https://issues.apache.org/jira/browse/AMBARI-22740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-22740: --- Issue Type: Task (was: Bug) > Fix integration test for HBase in branch-3.0-ams due to UUID changes > > > Key: AMBARI-22740 > URL: https://issues.apache.org/jira/browse/AMBARI-22740 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-22740.patch > > > Fixing all integration tests in AMS timeline-service module. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22740) Fix integration test for HBase in branch-3.0-ams due to UUID changes
[ https://issues.apache.org/jira/browse/AMBARI-22740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-22740: --- Status: Patch Available (was: Open) > Fix integration test for HBase in branch-3.0-ams due to UUID changes > > > Key: AMBARI-22740 > URL: https://issues.apache.org/jira/browse/AMBARI-22740 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-22740.patch > > > Fixing all integration tests in AMS timeline-service module. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-22737) /events/hostcomponents topic should react on maintenance and stale configs events
[ https://issues.apache.org/jira/browse/AMBARI-22737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myroslav Papirkovskyi resolved AMBARI-22737. Resolution: Fixed Committed to branch-3.0-perf > /events/hostcomponents topic should react on maintenance and stale configs > events > - > > Key: AMBARI-22737 > URL: https://issues.apache.org/jira/browse/AMBARI-22737 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi > Fix For: 3.0.0 > > > */events/hostcomponents* topic should react on maintenance state on/off and > stale configs events. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22740) Fix integration test for HBase in branch-3.0-ams due to UUID changes
[ https://issues.apache.org/jira/browse/AMBARI-22740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-22740: --- Attachment: AMBARI-22740.patch > Fix integration test for HBase in branch-3.0-ams due to UUID changes > > > Key: AMBARI-22740 > URL: https://issues.apache.org/jira/browse/AMBARI-22740 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-22740.patch > > > Fixing all integration tests in AMS timeline-service module. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22744) Fix issues with webapp deployment with new Hadoop common changes
[ https://issues.apache.org/jira/browse/AMBARI-22744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-22744: - Attachment: AMBARI-22744.patch > Fix issues with webapp deployment with new Hadoop common changes > > > Key: AMBARI-22744 > URL: https://issues.apache.org/jira/browse/AMBARI-22744 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-22744.patch > > > - Fix deploy time issues after migration. > - Fix imports. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22744) Fix issues with webapp deployment with new Hadoop common changes
[ https://issues.apache.org/jira/browse/AMBARI-22744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-22744: - Status: Patch Available (was: Open) > Fix issues with webapp deployment with new Hadoop common changes > > > Key: AMBARI-22744 > URL: https://issues.apache.org/jira/browse/AMBARI-22744 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-22744.patch > > > - Fix deploy time issues after migration. > - Fix imports. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22745) Migrate AMS from HBase 1.1.2 to HBase 2.0
Siddharth Wagle created AMBARI-22745: Summary: Migrate AMS from HBase 1.1.2 to HBase 2.0 Key: AMBARI-22745 URL: https://issues.apache.org/jira/browse/AMBARI-22745 Project: Ambari Issue Type: Epic Components: ambari-metrics Affects Versions: 3.0.0 Reporter: Siddharth Wagle Assignee: Siddharth Wagle Priority: Critical Fix For: 3.0.0 As part of the move towards HDP 3, we'll be upgrading HBase from 1.1.2 to HBase 2.0. This task is used to track the work necessary to make Ambari metric services compile and run against HBase 2.0. All underlying system integration tests and unit tests should also be running against HBase 2.0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22743) Refactor heartbeat processing classes
Myroslav Papirkovskyi created AMBARI-22743: -- Summary: Refactor heartbeat processing classes Key: AMBARI-22743 URL: https://issues.apache.org/jira/browse/AMBARI-22743 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 3.0.0 Reporter: Myroslav Papirkovskyi Assignee: Myroslav Papirkovskyi Fix For: 3.0.0 Move reports processing out of HeartbeatProcessor, since they technically don't belong to heartbeats anymore. Consider removing unused stuff related to heartbeats. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22744) Fix issues with webapp deployment with new Hadoop common changes
Siddharth Wagle created AMBARI-22744: Summary: Fix issues with webapp deployment with new Hadoop common changes Key: AMBARI-22744 URL: https://issues.apache.org/jira/browse/AMBARI-22744 Project: Ambari Issue Type: Task Components: ambari-metrics Affects Versions: 3.0.0 Reporter: Siddharth Wagle Assignee: Siddharth Wagle Priority: Critical Fix For: 3.0.0 - Fix deploy time issues after migration. - Fix imports. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22742) Add event for changes in upgrade.
Myroslav Papirkovskyi created AMBARI-22742: -- Summary: Add event for changes in upgrade. Key: AMBARI-22742 URL: https://issues.apache.org/jira/browse/AMBARI-22742 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 3.0.0 Reporter: Myroslav Papirkovskyi Assignee: Myroslav Papirkovskyi Fix For: 3.0.0 Server should raise events to publish created/updated upgrades to STOMP topic. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22741) Log Search UI: implement graph for access logs
[
https://issues.apache.org/jira/browse/AMBARI-22741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16313749#comment-16313749
]
Hadoop QA commented on AMBARI-22741:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904845/AMBARI-22741.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/12935//artifact/patch-work/patchJavacWarnings.txt].
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12935//console
This message is automatically generated.
> Log Search UI: implement graph for access logs
> --
>
> Key: AMBARI-22741
> URL: https://issues.apache.org/jira/browse/AMBARI-22741
> 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-22741.patch
>
>
> Line chart with time-dependent counts of access events from different sources
> should be implemented.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22741) Log Search UI: implement graph for access logs
[ https://issues.apache.org/jira/browse/AMBARI-22741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-22741: -- Attachment: AMBARI-22741.patch > Log Search UI: implement graph for access logs > -- > > Key: AMBARI-22741 > URL: https://issues.apache.org/jira/browse/AMBARI-22741 > 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-22741.patch > > > Line chart with time-dependent counts of access events from different sources > should be implemented. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22741) Log Search UI: implement graph for access logs
[ https://issues.apache.org/jira/browse/AMBARI-22741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-22741: -- Status: Patch Available (was: Open) > Log Search UI: implement graph for access logs > -- > > Key: AMBARI-22741 > URL: https://issues.apache.org/jira/browse/AMBARI-22741 > 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-22741.patch > > > Line chart with time-dependent counts of access events from different sources > should be implemented. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22741) Log Search UI: implement graph for access logs
Andrii Babiichuk created AMBARI-22741: - Summary: Log Search UI: implement graph for access logs Key: AMBARI-22741 URL: https://issues.apache.org/jira/browse/AMBARI-22741 Project: Ambari Issue Type: Task Components: ambari-logsearch Affects Versions: 3.0.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Fix For: 3.0.0 Line chart with time-dependent counts of access events from different sources should be implemented. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-22740) Fix integration test for HBase in branch-3.0-ams due to UUID changes
[ https://issues.apache.org/jira/browse/AMBARI-22740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan reassigned AMBARI-22740: -- Assignee: Aravindan Vijayan > Fix integration test for HBase in branch-3.0-ams due to UUID changes > > > Key: AMBARI-22740 > URL: https://issues.apache.org/jira/browse/AMBARI-22740 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 3.0.0 > > > Fixing all integration tests in AMS timeline-service module. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22740) Fix integration test for HBase in branch-3.0-ams due to UUID changes
Aravindan Vijayan created AMBARI-22740: -- Summary: Fix integration test for HBase in branch-3.0-ams due to UUID changes Key: AMBARI-22740 URL: https://issues.apache.org/jira/browse/AMBARI-22740 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 3.0.0 Reporter: Aravindan Vijayan Priority: Critical Fixing all integration tests in AMS timeline-service module. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22740) Fix integration test for HBase in branch-3.0-ams due to UUID changes
[ https://issues.apache.org/jira/browse/AMBARI-22740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-22740: --- Fix Version/s: 3.0.0 > Fix integration test for HBase in branch-3.0-ams due to UUID changes > > > Key: AMBARI-22740 > URL: https://issues.apache.org/jira/browse/AMBARI-22740 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 3.0.0 > > > Fixing all integration tests in AMS timeline-service module. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22739) Add event for changes in alert groups
Myroslav Papirkovskyi created AMBARI-22739: -- Summary: Add event for changes in alert groups Key: AMBARI-22739 URL: https://issues.apache.org/jira/browse/AMBARI-22739 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 3.0.0 Reporter: Myroslav Papirkovskyi Assignee: Myroslav Papirkovskyi Fix For: 3.0.0 Server should raise events to publish created/removed/updated alert groups to STOMP topic. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22736) Filter of Config Versions should be case insensitive
[ https://issues.apache.org/jira/browse/AMBARI-22736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16313616#comment-16313616 ] Hudson commented on AMBARI-22736: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8578 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8578/]) AMBARI-22736 Filter of Config Versions should be case insensitive. (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2b9a34b0fae681ed3d20459538f2c7711a314b51]) * (edit) ambari-web/app/assets/test/tests.js * (add) ambari-web/test/views/common/configs/config_versions_dropdown_view_test.js * (edit) ambari-web/app/views/common/configs/config_versions_dropdown_view.js > Filter of Config Versions should be case insensitive > > > Key: AMBARI-22736 > URL: https://issues.apache.org/jira/browse/AMBARI-22736 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Minor > Fix For: 3.0.0 > > Attachments: AMBARI-22736.patch, cv-filter.png > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22121) Create mpack for Isilon OneFS
[
https://issues.apache.org/jira/browse/AMBARI-22121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16313589#comment-16313589
]
Hadoop QA commented on AMBARI-22121:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904815/AMBARI-22121.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/12934//console
This message is automatically generated.
> Create mpack for Isilon OneFS
> -
>
> Key: AMBARI-22121
> URL: https://issues.apache.org/jira/browse/AMBARI-22121
> Project: Ambari
> Issue Type: Task
> Components: contrib
>Affects Versions: 3.0.0
>Reporter: Attila Magyar
>Assignee: Attila Magyar
> Fix For: 3.0.0
>
> Attachments: AMBARI-22121.patch, AMBARI-22121_2.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-22738) Setup heartbeat for api endpoint.
[ https://issues.apache.org/jira/browse/AMBARI-22738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myroslav Papirkovskyi resolved AMBARI-22738. Resolution: Fixed Pushed to branch-3.0-perf > Setup heartbeat for api endpoint. > - > > Key: AMBARI-22738 > URL: https://issues.apache.org/jira/browse/AMBARI-22738 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi > Fix For: 3.0.0 > > > API endpoint uses sockJS fallback options. The SockJS protocol requires > server to set proper heartbeat configuration. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22736) Filter of Config Versions should be case insensitive
[ https://issues.apache.org/jira/browse/AMBARI-22736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22736: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Filter of Config Versions should be case insensitive > > > Key: AMBARI-22736 > URL: https://issues.apache.org/jira/browse/AMBARI-22736 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Minor > Fix For: 3.0.0 > > Attachments: AMBARI-22736.patch, cv-filter.png > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22736) Filter of Config Versions should be case insensitive
[ https://issues.apache.org/jira/browse/AMBARI-22736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16313550#comment-16313550 ] Andrii Tkach commented on AMBARI-22736: --- committed to trunk > Filter of Config Versions should be case insensitive > > > Key: AMBARI-22736 > URL: https://issues.apache.org/jira/browse/AMBARI-22736 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Minor > Fix For: 3.0.0 > > Attachments: AMBARI-22736.patch, cv-filter.png > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22738) Setup heartbeat for api endpoint.
Myroslav Papirkovskyi created AMBARI-22738: -- Summary: Setup heartbeat for api endpoint. Key: AMBARI-22738 URL: https://issues.apache.org/jira/browse/AMBARI-22738 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 3.0.0 Reporter: Myroslav Papirkovskyi Assignee: Myroslav Papirkovskyi Fix For: 3.0.0 API endpoint uses sockJS fallback options. The SockJS protocol requires server to set proper heartbeat configuration. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22736) Filter of Config Versions should be case insensitive
[ https://issues.apache.org/jira/browse/AMBARI-22736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16313489#comment-16313489 ] Andrii Babiichuk commented on AMBARI-22736: --- +1 for the patch > Filter of Config Versions should be case insensitive > > > Key: AMBARI-22736 > URL: https://issues.apache.org/jira/browse/AMBARI-22736 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Minor > Fix For: 3.0.0 > > Attachments: AMBARI-22736.patch, cv-filter.png > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22736) Filter of Config Versions should be case insensitive
[ https://issues.apache.org/jira/browse/AMBARI-22736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22736: -- Attachment: cv-filter.png > Filter of Config Versions should be case insensitive > > > Key: AMBARI-22736 > URL: https://issues.apache.org/jira/browse/AMBARI-22736 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Minor > Fix For: 3.0.0 > > Attachments: AMBARI-22736.patch, cv-filter.png > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-22735) Delete host event doesn't have hostName property
[
https://issues.apache.org/jira/browse/AMBARI-22735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myroslav Papirkovskyi resolved AMBARI-22735.
Resolution: Fixed
Pushed to branch-3.0-perf
> Delete host event doesn't have hostName property
>
>
> Key: AMBARI-22735
> URL: https://issues.apache.org/jira/browse/AMBARI-22735
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
> Fix For: 3.0.0
>
>
> When deleting a host, you get an event from /events/ui_topologies, but it
> doesn't contain hostName property:
> {noformat}
> {"hash":"922d90764f61dcb2687a33e1e4bfc55b5eb755492b14f48044c940d19324b5e72e669b5af42321383026d46df0775730dd8a0f55a28c625b14f6295bfed02917","eventType":"DELETE","clusters":{"2":{"hosts":[{"hostId":51}]}}}
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-22733) UI receives a topology event when turning on/off maintenance mode for the host
[ https://issues.apache.org/jira/browse/AMBARI-22733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myroslav Papirkovskyi resolved AMBARI-22733. Resolution: Fixed Pushed to branch-3.0-perf > UI receives a topology event when turning on/off maintenance mode for the host > -- > > Key: AMBARI-22733 > URL: https://issues.apache.org/jira/browse/AMBARI-22733 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi > Fix For: 3.0.0 > > > UI receives a topology event(/events/ui_topologies) when turning on/off > maintenance mode for the host. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-22734) alert_definitions topic doesn't emit any events to client
[ https://issues.apache.org/jira/browse/AMBARI-22734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myroslav Papirkovskyi resolved AMBARI-22734. Resolution: Fixed Pushed to branch-3.0-perf > alert_definitions topic doesn't emit any events to client > - > > Key: AMBARI-22734 > URL: https://issues.apache.org/jira/browse/AMBARI-22734 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi > Fix For: 3.0.0 > > > /alert_definitions topic doesn't emit any events to the client when > definition properties are modified. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22736) Filter of Config Versions should be case insensitive
[
https://issues.apache.org/jira/browse/AMBARI-22736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16313450#comment-16313450
]
Hadoop QA commented on AMBARI-22736:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904817/AMBARI-22736.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-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12932//console
This message is automatically generated.
> Filter of Config Versions should be case insensitive
>
>
> Key: AMBARI-22736
> URL: https://issues.apache.org/jira/browse/AMBARI-22736
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: AMBARI-22736.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22733) UI receives a topology event when turning on/off maintenance mode for the host
[ https://issues.apache.org/jira/browse/AMBARI-22733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myroslav Papirkovskyi updated AMBARI-22733: --- Description: UI receives a topology event(/events/ui_topologies) when turning on/off maintenance mode for the host. (was: */events/hostcomponents* topic should react on maintenance state on/off and stale configs events.) > UI receives a topology event when turning on/off maintenance mode for the host > -- > > Key: AMBARI-22733 > URL: https://issues.apache.org/jira/browse/AMBARI-22733 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi > Fix For: 3.0.0 > > > UI receives a topology event(/events/ui_topologies) when turning on/off > maintenance mode for the host. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22733) UI receives a topology event when turning on/off maintenance mode for the host
[ https://issues.apache.org/jira/browse/AMBARI-22733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myroslav Papirkovskyi updated AMBARI-22733: --- Summary: UI receives a topology event when turning on/off maintenance mode for the host (was: /events/hostcomponents topic should react on maintenance and stale configs events) > UI receives a topology event when turning on/off maintenance mode for the host > -- > > Key: AMBARI-22733 > URL: https://issues.apache.org/jira/browse/AMBARI-22733 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi > Fix For: 3.0.0 > > > */events/hostcomponents* topic should react on maintenance state on/off and > stale configs events. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22736) Filter of Config Versions should be case insensitive
[ https://issues.apache.org/jira/browse/AMBARI-22736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22736: -- Attachment: AMBARI-22736.patch > Filter of Config Versions should be case insensitive > > > Key: AMBARI-22736 > URL: https://issues.apache.org/jira/browse/AMBARI-22736 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Minor > Fix For: 3.0.0 > > Attachments: AMBARI-22736.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22736) Filter of Config Versions should be case insensitive
[ https://issues.apache.org/jira/browse/AMBARI-22736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22736: -- Status: Patch Available (was: Open) > Filter of Config Versions should be case insensitive > > > Key: AMBARI-22736 > URL: https://issues.apache.org/jira/browse/AMBARI-22736 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Minor > Fix For: 3.0.0 > > Attachments: AMBARI-22736.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22724) Idempotent issue on Ambari Upgrade, renameServiceDeletedColumn failed with column already exists exception
[
https://issues.apache.org/jira/browse/AMBARI-22724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16313363#comment-16313363
]
Hudson commented on AMBARI-22724:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8577 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8577/])
AMBARI-22724. Idempotent issue on Ambari Upgrade, (vbrodetskyi:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=cd5c1cad8f62c45de62094de2b5e442d161c9b34])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog252.java
> Idempotent issue on Ambari Upgrade, renameServiceDeletedColumn failed with
> column already exists exception
> --
>
> Key: AMBARI-22724
> URL: https://issues.apache.org/jira/browse/AMBARI-22724
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.2
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.6.2
>
> Attachments: AMBARI-22724.patch
>
>
> Issue discovered alongside with another bugs which leads upgrade to fail in
> the middle with partially applying changes to DB. It leads to exception in
> code:
> {code}
> private void renameServiceDeletedColumn() throws AmbariException,
> SQLException {
> if (dbAccessor.tableHasColumn(CLUSTER_CONFIG_TABLE,
> SERVICE_DELETED_COLUMN)) {
> dbAccessor.renameColumn(CLUSTER_CONFIG_TABLE, SERVICE_DELETED_COLUMN,
> new DBAccessor.DBColumnInfo(UNMAPPED_COLUMN, Short.class, null, 0, false));
> }
> }
> {code}
> Exception: ERROR: column "unmapped" of relation "clusterconfig" already
> exists (err.png)
> Table generated DDL from current state:
> {code}
> -- auto-generated definition
> CREATE TABLE clusterconfig
> (
> config_id INT8(19) NOT NULL
> CONSTRAINT pk_clusterconfig
> PRIMARY KEY,
> version_tagVARCHAR(255) NOT NULL,
> versionINT8(19) NOT NULL,
> type_name VARCHAR(255) NOT NULL,
> cluster_id INT8(19) NOT NULL
> CONSTRAINT fk_clusterconfig_cluster_id
> REFERENCES clusters,
> stack_id INT8(19) NOT NULL
> CONSTRAINT fk_clusterconfig_stack_id
> REFERENCES stack,
> config_dataTEXT(max) NOT NULL,
> config_attributes TEXT(max),
> create_timestamp INT8(19) NOT NULL,
> unmapped INT2(5) DEFAULT 0 NOT NULL,
> selected INT2(5) DEFAULT 0 NOT NULL,
> selected_timestamp INT8(19) DEFAULT 0 NOT NULL,
> service_deletedINT2(5) DEFAULT 0 NOT NULL
> );
> CREATE UNIQUE INDEX uq_config_type_tag
> ON clusterconfig (cluster_id, type_name, version_tag);
> CREATE UNIQUE INDEX uq_config_type_version
> ON clusterconfig (cluster_id, type_name, version);
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22737) /events/hostcomponents topic should react on maintenance and stale configs events
Myroslav Papirkovskyi created AMBARI-22737: -- Summary: /events/hostcomponents topic should react on maintenance and stale configs events Key: AMBARI-22737 URL: https://issues.apache.org/jira/browse/AMBARI-22737 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 3.0.0 Reporter: Myroslav Papirkovskyi Assignee: Myroslav Papirkovskyi Fix For: 3.0.0 */events/hostcomponents* topic should react on maintenance state on/off and stale configs events. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22121) Create mpack for Isilon OneFS
[ https://issues.apache.org/jira/browse/AMBARI-22121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar updated AMBARI-22121: --- Attachment: AMBARI-22121.patch AMBARI-22121_2.patch > Create mpack for Isilon OneFS > - > > Key: AMBARI-22121 > URL: https://issues.apache.org/jira/browse/AMBARI-22121 > Project: Ambari > Issue Type: Task > Components: contrib >Affects Versions: 3.0.0 >Reporter: Attila Magyar >Assignee: Attila Magyar > Fix For: 3.0.0 > > Attachments: AMBARI-22121.patch, AMBARI-22121_2.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22736) Filter of Config Versions should be case insensitive
Andrii Tkach created AMBARI-22736: - Summary: Filter of Config Versions should be case insensitive Key: AMBARI-22736 URL: https://issues.apache.org/jira/browse/AMBARI-22736 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Priority: Minor Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22735) Delete host event doesn't have hostName property
Myroslav Papirkovskyi created AMBARI-22735:
--
Summary: Delete host event doesn't have hostName property
Key: AMBARI-22735
URL: https://issues.apache.org/jira/browse/AMBARI-22735
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 3.0.0
Reporter: Myroslav Papirkovskyi
Assignee: Myroslav Papirkovskyi
Fix For: 3.0.0
When deleting a host, you get an event from /events/ui_topologies, but it
doesn't contain hostName property:
{noformat}
{"hash":"922d90764f61dcb2687a33e1e4bfc55b5eb755492b14f48044c940d19324b5e72e669b5af42321383026d46df0775730dd8a0f55a28c625b14f6295bfed02917","eventType":"DELETE","clusters":{"2":{"hosts":[{"hostId":51}]}}}
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22656) Add slot info for Hosts page
[
https://issues.apache.org/jira/browse/AMBARI-22656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16313296#comment-16313296
]
Hadoop QA commented on AMBARI-22656:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904719/AMBARI-22656.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/12931//console
This message is automatically generated.
> Add slot info for Hosts page
>
>
> Key: AMBARI-22656
> URL: https://issues.apache.org/jira/browse/AMBARI-22656
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-agent, ambari-server, ambari-web
>Affects Versions: 2.5.2
>Reporter: mathildaMa09
> Fix For: 2.5.2
>
> Attachments: AMBARI-22656.patch
>
>
> In Hosts Page lists info about hosts like Rack、IP、Cores、DiskUsage .etc, but I
> need more details about my hosts’ physical position, like slot for instance,
> to know exactly where my machine locates. So, in hosts page, we can add slot
> info to describe their location.
--
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&focusedCommentId=16313294#comment-16313294
]
Hadoop QA commented on AMBARI-22449:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904774/AMBARI-22449_2.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 ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12930//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, AMBARI-22449_2.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22732) Make Select Metric dropdown in Create Widget wizard wider
[ https://issues.apache.org/jira/browse/AMBARI-22732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16313273#comment-16313273 ] Hudson commented on AMBARI-22732: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8576 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8576/]) AMBARI-22732 Make Select Metric dropdown in Create Widget wizard wider. (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e13bfb95ce15cfe38e9d9d5409cbe44de59d44b8]) * (edit) ambari-web/app/styles/enhanced_service_dashboard.less > Make Select Metric dropdown in Create Widget wizard wider > - > > Key: AMBARI-22732 > URL: https://issues.apache.org/jira/browse/AMBARI-22732 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Minor > Fix For: 3.0.0 > > Attachments: AMBARI-22732.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22734) alert_definitions topic doesn't emit any events to client
Myroslav Papirkovskyi created AMBARI-22734: -- Summary: alert_definitions topic doesn't emit any events to client Key: AMBARI-22734 URL: https://issues.apache.org/jira/browse/AMBARI-22734 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0 Reporter: Myroslav Papirkovskyi Assignee: Myroslav Papirkovskyi Fix For: 3.0.0 /alert_definitions topic doesn't emit any events to the client when definition properties are modified. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22733) /events/hostcomponents topic should react on maintenance and stale configs events
Myroslav Papirkovskyi created AMBARI-22733: -- Summary: /events/hostcomponents topic should react on maintenance and stale configs events Key: AMBARI-22733 URL: https://issues.apache.org/jira/browse/AMBARI-22733 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0 Reporter: Myroslav Papirkovskyi Assignee: Myroslav Papirkovskyi Fix For: 3.0.0 */events/hostcomponents* topic should react on maintenance state on/off and stale configs events. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22724) Idempotent issue on Ambari Upgrade, renameServiceDeletedColumn failed with column already exists exception
[
https://issues.apache.org/jira/browse/AMBARI-22724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16313223#comment-16313223
]
Hudson commented on AMBARI-22724:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #566 (See
[https://builds.apache.org/job/Ambari-branch-2.6/566/])
AMBARI-22724. Idempotent issue on Ambari Upgrade, (vbrodetskyi:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=680f737c944bf4e10c282266c0bb39e43074cec2])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog252.java
> Idempotent issue on Ambari Upgrade, renameServiceDeletedColumn failed with
> column already exists exception
> --
>
> Key: AMBARI-22724
> URL: https://issues.apache.org/jira/browse/AMBARI-22724
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.2
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.6.2
>
> Attachments: AMBARI-22724.patch
>
>
> Issue discovered alongside with another bugs which leads upgrade to fail in
> the middle with partially applying changes to DB. It leads to exception in
> code:
> {code}
> private void renameServiceDeletedColumn() throws AmbariException,
> SQLException {
> if (dbAccessor.tableHasColumn(CLUSTER_CONFIG_TABLE,
> SERVICE_DELETED_COLUMN)) {
> dbAccessor.renameColumn(CLUSTER_CONFIG_TABLE, SERVICE_DELETED_COLUMN,
> new DBAccessor.DBColumnInfo(UNMAPPED_COLUMN, Short.class, null, 0, false));
> }
> }
> {code}
> Exception: ERROR: column "unmapped" of relation "clusterconfig" already
> exists (err.png)
> Table generated DDL from current state:
> {code}
> -- auto-generated definition
> CREATE TABLE clusterconfig
> (
> config_id INT8(19) NOT NULL
> CONSTRAINT pk_clusterconfig
> PRIMARY KEY,
> version_tagVARCHAR(255) NOT NULL,
> versionINT8(19) NOT NULL,
> type_name VARCHAR(255) NOT NULL,
> cluster_id INT8(19) NOT NULL
> CONSTRAINT fk_clusterconfig_cluster_id
> REFERENCES clusters,
> stack_id INT8(19) NOT NULL
> CONSTRAINT fk_clusterconfig_stack_id
> REFERENCES stack,
> config_dataTEXT(max) NOT NULL,
> config_attributes TEXT(max),
> create_timestamp INT8(19) NOT NULL,
> unmapped INT2(5) DEFAULT 0 NOT NULL,
> selected INT2(5) DEFAULT 0 NOT NULL,
> selected_timestamp INT8(19) DEFAULT 0 NOT NULL,
> service_deletedINT2(5) DEFAULT 0 NOT NULL
> );
> CREATE UNIQUE INDEX uq_config_type_tag
> ON clusterconfig (cluster_id, type_name, version_tag);
> CREATE UNIQUE INDEX uq_config_type_version
> ON clusterconfig (cluster_id, type_name, version);
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-22724) Idempotent issue on Ambari Upgrade, renameServiceDeletedColumn failed with column already exists exception
[
https://issues.apache.org/jira/browse/AMBARI-22724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi resolved AMBARI-22724.
Resolution: Fixed
Committed to trunk and branch-2.6
> Idempotent issue on Ambari Upgrade, renameServiceDeletedColumn failed with
> column already exists exception
> --
>
> Key: AMBARI-22724
> URL: https://issues.apache.org/jira/browse/AMBARI-22724
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.2
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.6.2
>
> Attachments: AMBARI-22724.patch
>
>
> Issue discovered alongside with another bugs which leads upgrade to fail in
> the middle with partially applying changes to DB. It leads to exception in
> code:
> {code}
> private void renameServiceDeletedColumn() throws AmbariException,
> SQLException {
> if (dbAccessor.tableHasColumn(CLUSTER_CONFIG_TABLE,
> SERVICE_DELETED_COLUMN)) {
> dbAccessor.renameColumn(CLUSTER_CONFIG_TABLE, SERVICE_DELETED_COLUMN,
> new DBAccessor.DBColumnInfo(UNMAPPED_COLUMN, Short.class, null, 0, false));
> }
> }
> {code}
> Exception: ERROR: column "unmapped" of relation "clusterconfig" already
> exists (err.png)
> Table generated DDL from current state:
> {code}
> -- auto-generated definition
> CREATE TABLE clusterconfig
> (
> config_id INT8(19) NOT NULL
> CONSTRAINT pk_clusterconfig
> PRIMARY KEY,
> version_tagVARCHAR(255) NOT NULL,
> versionINT8(19) NOT NULL,
> type_name VARCHAR(255) NOT NULL,
> cluster_id INT8(19) NOT NULL
> CONSTRAINT fk_clusterconfig_cluster_id
> REFERENCES clusters,
> stack_id INT8(19) NOT NULL
> CONSTRAINT fk_clusterconfig_stack_id
> REFERENCES stack,
> config_dataTEXT(max) NOT NULL,
> config_attributes TEXT(max),
> create_timestamp INT8(19) NOT NULL,
> unmapped INT2(5) DEFAULT 0 NOT NULL,
> selected INT2(5) DEFAULT 0 NOT NULL,
> selected_timestamp INT8(19) DEFAULT 0 NOT NULL,
> service_deletedINT2(5) DEFAULT 0 NOT NULL
> );
> CREATE UNIQUE INDEX uq_config_type_tag
> ON clusterconfig (cluster_id, type_name, version_tag);
> CREATE UNIQUE INDEX uq_config_type_version
> ON clusterconfig (cluster_id, type_name, version);
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22732) Make Select Metric dropdown in Create Widget wizard wider
[ https://issues.apache.org/jira/browse/AMBARI-22732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22732: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Make Select Metric dropdown in Create Widget wizard wider > - > > Key: AMBARI-22732 > URL: https://issues.apache.org/jira/browse/AMBARI-22732 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Minor > Fix For: 3.0.0 > > Attachments: AMBARI-22732.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22732) Make Select Metric dropdown in Create Widget wizard wider
[ https://issues.apache.org/jira/browse/AMBARI-22732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16313196#comment-16313196 ] Andrii Tkach commented on AMBARI-22732: --- committed to trunk > Make Select Metric dropdown in Create Widget wizard wider > - > > Key: AMBARI-22732 > URL: https://issues.apache.org/jira/browse/AMBARI-22732 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Minor > Fix For: 3.0.0 > > Attachments: AMBARI-22732.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22732) Make Select Metric dropdown in Create Widget wizard wider
[ https://issues.apache.org/jira/browse/AMBARI-22732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16313189#comment-16313189 ] Andrii Babiichuk commented on AMBARI-22732: --- +1 for the patch > Make Select Metric dropdown in Create Widget wizard wider > - > > Key: AMBARI-22732 > URL: https://issues.apache.org/jira/browse/AMBARI-22732 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Minor > Fix For: 3.0.0 > > Attachments: AMBARI-22732.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22732) Make Select Metric dropdown in Create Widget wizard wider
[
https://issues.apache.org/jira/browse/AMBARI-22732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16313179#comment-16313179
]
Hadoop QA commented on AMBARI-22732:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904799/AMBARI-22732.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/12928//console
This message is automatically generated.
> Make Select Metric dropdown in Create Widget wizard wider
> -
>
> Key: AMBARI-22732
> URL: https://issues.apache.org/jira/browse/AMBARI-22732
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: AMBARI-22732.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22732) Make Select Metric dropdown in Create Widget wizard wider
[ https://issues.apache.org/jira/browse/AMBARI-22732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22732: -- Attachment: AMBARI-22732.patch > Make Select Metric dropdown in Create Widget wizard wider > - > > Key: AMBARI-22732 > URL: https://issues.apache.org/jira/browse/AMBARI-22732 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Minor > Fix For: 3.0.0 > > Attachments: AMBARI-22732.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22732) Make Select Metric dropdown in Create Widget wizard wider
[ https://issues.apache.org/jira/browse/AMBARI-22732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22732: -- Status: Patch Available (was: Open) > Make Select Metric dropdown in Create Widget wizard wider > - > > Key: AMBARI-22732 > URL: https://issues.apache.org/jira/browse/AMBARI-22732 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Minor > Fix For: 3.0.0 > > Attachments: AMBARI-22732.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22732) Make Select Metric dropdown in Create Widget wizard wider
Andrii Tkach created AMBARI-22732: - Summary: Make Select Metric dropdown in Create Widget wizard wider Key: AMBARI-22732 URL: https://issues.apache.org/jira/browse/AMBARI-22732 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 3.0.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Priority: Minor Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22731) Infra Manager: hdfs upload support for archiving Infra Solr
Krisztian Kasa created AMBARI-22731: --- Summary: Infra Manager: hdfs upload support for archiving Infra Solr Key: AMBARI-22731 URL: https://issues.apache.org/jira/browse/AMBARI-22731 Project: Ambari Issue Type: Improvement Components: ambari-infra Affects Versions: 3.0.0 Reporter: Krisztian Kasa Assignee: Krisztian Kasa Fix For: 3.0.0 Upload exported document from infa solr to a specified hdfs server. hdfs configuration should be defined in the ambari-infra-manager.properties file for each jobs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22449) Improved service/component dependency support
[ https://issues.apache.org/jira/browse/AMBARI-22449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar updated AMBARI-22449: --- Attachment: AMBARI-22449_2.patch > 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, AMBARI-22449_2.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22656) Add slot info for Hosts page
[ https://issues.apache.org/jira/browse/AMBARI-22656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mathildaMa09 updated AMBARI-22656: -- Attachment: (was: AMBARI-22656_branch-2.5.patch) > Add slot info for Hosts page > > > Key: AMBARI-22656 > URL: https://issues.apache.org/jira/browse/AMBARI-22656 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent, ambari-server, ambari-web >Affects Versions: 2.5.2 >Reporter: mathildaMa09 > Fix For: 2.5.2 > > Attachments: AMBARI-22656.patch > > > In Hosts Page lists info about hosts like Rack、IP、Cores、DiskUsage .etc, but I > need more details about my hosts’ physical position, like slot for instance, > to know exactly where my machine locates. So, in hosts page, we can add slot > info to describe their location. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22725) Update Hadoop RPC Encryption Properties During Kerberization and Upgrade
[
https://issues.apache.org/jira/browse/AMBARI-22725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16312724#comment-16312724
]
Hadoop QA commented on AMBARI-22725:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904672/AMBARI-22725.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 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/12927//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12927//console
This message is automatically generated.
> Update Hadoop RPC Encryption Properties During Kerberization and Upgrade
>
>
> Key: AMBARI-22725
> URL: https://issues.apache.org/jira/browse/AMBARI-22725
> Project: Ambari
> Issue Type: Task
>Affects Versions: 2.6.2
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.2
>
> Attachments: AMBARI-22725.patch
>
>
> Clients should have the ability to choose encrypted communication over RPC
> when talking to core hadoop components. Today, the properties that control
> this are:
> - {{core-site.xml : hadoop.rpc.protection = authentication}}
> - {{hdfs-site.xml : dfs.data.transfer.protection = authentication}}
> The new value of {{privacy}} enables clients to choose an encrypted means of
> communication. By keeping {{authentication}} first, it will be taken as the
> default mechanism so that wire encryption is not automatically enabled by
> accident.
> The following properties should be changed to add {{privacy}}:
> - {{core-site.xml : hadoop.rpc.protection = authentication,privacy}}
> - {{hdfs-site.xml : dfs.data.transfer.protection = authentication,privacy}}
> The following are cases when this needs to be performed:
> - During Kerberization, the above two properties should be automatically
> reconfigured.
> - During a stack upgrade to any version of HDP 2.6, they should be
> automatically merged
> Blueprint deployment is not a scenario being covered here.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22419) Ambari upgrade failed
[
https://issues.apache.org/jira/browse/AMBARI-22419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16312717#comment-16312717
]
Hudson commented on AMBARI-22419:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8575 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8575/])
AMBARI-22419 Ambari upgrade failed (dgrinenko) (hapylestat:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d6f26fb1c7d79fa6ba9a289daf51f6151c6bb3de])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/api/services/AmbariMetaInfoTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/api/services/AmbariMetaInfo.java
> Ambari upgrade failed
> -
>
> Key: AMBARI-22419
> URL: https://issues.apache.org/jira/browse/AMBARI-22419
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: 2.6.0
>Reporter: amarnath reddy pappu
>Assignee: Dmytro Grinenko
> Fix For: 2.6.2
>
> Attachments: AMBARI-22419.branch-2.6.patch, AMBARI-22419.trunk.patch
>
>
> Ambari upgrade would fail during the DMLStatements execution if there is no
> service definition in the stacks.
> For example: Customer database has entry for GANGLIA in alert_definition
> table but there is no stack definition - hence its getting failed with below
> exception.
> {noformat}
> org.apache.ambari.server.AmbariException: Service not found,
> clusterName=comcastdrcluster, serviceName=GANGLIA
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:234)
>
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:424)
>
> Caused by: org.apache.ambari.server.ServiceNotFoundException: Service not
> found, clusterName=comcastdrcluster, serviceName=GANGLIA
> at
> org.apache.ambari.server.state.cluster.ClusterImpl.getService(ClusterImpl.java:864)
>
> at
> org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1240)
>
> at
> org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46)
>
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:938)
>
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:231)
>
> ... 1 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22419) Ambari upgrade failed
[
https://issues.apache.org/jira/browse/AMBARI-22419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16312709#comment-16312709
]
Hudson commented on AMBARI-22419:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #565 (See
[https://builds.apache.org/job/Ambari-branch-2.6/565/])
AMBARI-22419 Ambari upgrade failed (dgrinenko) (hapylestat:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=868949acdb60c739914da8bccc6bffe09f067b8a])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/api/services/AmbariMetaInfo.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/api/services/AmbariMetaInfoTest.java
> Ambari upgrade failed
> -
>
> Key: AMBARI-22419
> URL: https://issues.apache.org/jira/browse/AMBARI-22419
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: 2.6.0
>Reporter: amarnath reddy pappu
>Assignee: Dmytro Grinenko
> Fix For: 2.6.2
>
> Attachments: AMBARI-22419.branch-2.6.patch, AMBARI-22419.trunk.patch
>
>
> Ambari upgrade would fail during the DMLStatements execution if there is no
> service definition in the stacks.
> For example: Customer database has entry for GANGLIA in alert_definition
> table but there is no stack definition - hence its getting failed with below
> exception.
> {noformat}
> org.apache.ambari.server.AmbariException: Service not found,
> clusterName=comcastdrcluster, serviceName=GANGLIA
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:234)
>
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:424)
>
> Caused by: org.apache.ambari.server.ServiceNotFoundException: Service not
> found, clusterName=comcastdrcluster, serviceName=GANGLIA
> at
> org.apache.ambari.server.state.cluster.ClusterImpl.getService(ClusterImpl.java:864)
>
> at
> org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1240)
>
> at
> org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46)
>
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:938)
>
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:231)
>
> ... 1 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22419) Ambari upgrade failed
[
https://issues.apache.org/jira/browse/AMBARI-22419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-22419:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed:
a020986728..868949acdb branch-2.6 -> branch-2.6
72812bd2bd..d6f26fb1c7 trunk -> trunk
> Ambari upgrade failed
> -
>
> Key: AMBARI-22419
> URL: https://issues.apache.org/jira/browse/AMBARI-22419
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: 2.6.0
>Reporter: amarnath reddy pappu
>Assignee: Dmytro Grinenko
> Fix For: 2.6.2
>
> Attachments: AMBARI-22419.branch-2.6.patch, AMBARI-22419.trunk.patch
>
>
> Ambari upgrade would fail during the DMLStatements execution if there is no
> service definition in the stacks.
> For example: Customer database has entry for GANGLIA in alert_definition
> table but there is no stack definition - hence its getting failed with below
> exception.
> {noformat}
> org.apache.ambari.server.AmbariException: Service not found,
> clusterName=comcastdrcluster, serviceName=GANGLIA
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:234)
>
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:424)
>
> Caused by: org.apache.ambari.server.ServiceNotFoundException: Service not
> found, clusterName=comcastdrcluster, serviceName=GANGLIA
> at
> org.apache.ambari.server.state.cluster.ClusterImpl.getService(ClusterImpl.java:864)
>
> at
> org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1240)
>
> at
> org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46)
>
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:938)
>
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:231)
>
> ... 1 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22419) Ambari upgrade failed
[
https://issues.apache.org/jira/browse/AMBARI-22419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16312660#comment-16312660
]
Hadoop QA commented on AMBARI-22419:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904731/AMBARI-22419.trunk.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/12925//console
This message is automatically generated.
> Ambari upgrade failed
> -
>
> Key: AMBARI-22419
> URL: https://issues.apache.org/jira/browse/AMBARI-22419
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: 2.6.0
>Reporter: amarnath reddy pappu
>Assignee: Dmytro Grinenko
> Fix For: 2.6.2
>
> Attachments: AMBARI-22419.branch-2.6.patch, AMBARI-22419.trunk.patch
>
>
> Ambari upgrade would fail during the DMLStatements execution if there is no
> service definition in the stacks.
> For example: Customer database has entry for GANGLIA in alert_definition
> table but there is no stack definition - hence its getting failed with below
> exception.
> {noformat}
> org.apache.ambari.server.AmbariException: Service not found,
> clusterName=comcastdrcluster, serviceName=GANGLIA
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:234)
>
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:424)
>
> Caused by: org.apache.ambari.server.ServiceNotFoundException: Service not
> found, clusterName=comcastdrcluster, serviceName=GANGLIA
> at
> org.apache.ambari.server.state.cluster.ClusterImpl.getService(ClusterImpl.java:864)
>
> at
> org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1240)
>
> at
> org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46)
>
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:938)
>
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:231)
>
> ... 1 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22656) Add slot info for Hosts page
[
https://issues.apache.org/jira/browse/AMBARI-22656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16312664#comment-16312664
]
Hadoop QA commented on AMBARI-22656:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904738/AMBARI-22656_branch-2.5.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12926//console
This message is automatically generated.
> Add slot info for Hosts page
>
>
> Key: AMBARI-22656
> URL: https://issues.apache.org/jira/browse/AMBARI-22656
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-agent, ambari-server, ambari-web
>Affects Versions: 2.5.2
>Reporter: mathildaMa09
> Fix For: 2.5.2
>
> Attachments: AMBARI-22656.patch, AMBARI-22656_branch-2.5.patch
>
>
> In Hosts Page lists info about hosts like Rack、IP、Cores、DiskUsage .etc, but I
> need more details about my hosts’ physical position, like slot for instance,
> to know exactly where my machine locates. So, in hosts page, we can add slot
> info to describe their location.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
