[jira] [Created] (AMBARI-19045) Remove unnecessary Log Feeder Date Mapper tests
Miklos Gergely created AMBARI-19045: --- Summary: Remove unnecessary Log Feeder Date Mapper tests Key: AMBARI-19045 URL: https://issues.apache.org/jira/browse/AMBARI-19045 Project: Ambari Issue Type: Bug Reporter: Miklos Gergely Assignee: Miklos Gergely Some unit tests for Date Mapper in the Log Feeder (testMapperDate_patternWithoutYear_previousYearLog, testMapperDate_patternWithoutYear_currentYearLog) make no sense, but fail in December. Remove these tests. Options -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19046) Ambari ResourceManager alerts not working with ResourceManager HA
Thomas Larsson created AMBARI-19046: --- Summary: Ambari ResourceManager alerts not working with ResourceManager HA Key: AMBARI-19046 URL: https://issues.apache.org/jira/browse/AMBARI-19046 Project: Ambari Issue Type: Bug Components: alerts Affects Versions: 2.2.2 Reporter: Thomas Larsson Priority: Minor When enabling ResourceManager HA, alerts such as "ResourceManager CPU utilisation" become aware that there are two RM's to check. However, when the alert queries the standby RM it will just respond with a http 307 redirect and the alert will end up in an "Unknown" state. This means that after RM HA is enabled, either you live with these alert constantly alerting, or you disable them. Perhaps this is unsolvable without changes to the RM but I'll create the ticket here as the first place. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19034) Upgrade History Displays Wrong Upgrade Type
[ https://issues.apache.org/jira/browse/AMBARI-19034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19034: -- Attachment: AMBARI-19034.patch > Upgrade History Displays Wrong Upgrade Type > --- > > Key: AMBARI-19034 > URL: https://issues.apache.org/jira/browse/AMBARI-19034 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.5.0 > > Attachments: AMBARI-19034.patch, AMBARI-19034_branch-2.5.patch, > Screen Shot 2016-11-10 at 1.24.12 PM.png, Screen Shot 2016-11-10 at 1.27.28 > PM.png > > > Perform a HOST_ORDERED upgrade. After the upgrade has completed, navigate to > the "Upgrade History". The type of upgrade displayed is "Rolling". > Additionally, when clicking on the upgrade, it shows as "HOST_ORDERED" > instead of "Host Ordered" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19034) Upgrade History Displays Wrong Upgrade Type
[ https://issues.apache.org/jira/browse/AMBARI-19034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19034: -- Status: Open (was: Patch Available) > Upgrade History Displays Wrong Upgrade Type > --- > > Key: AMBARI-19034 > URL: https://issues.apache.org/jira/browse/AMBARI-19034 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.5.0 > > Attachments: AMBARI-19034.patch, AMBARI-19034_branch-2.5.patch, > Screen Shot 2016-11-10 at 1.24.12 PM.png, Screen Shot 2016-11-10 at 1.27.28 > PM.png > > > Perform a HOST_ORDERED upgrade. After the upgrade has completed, navigate to > the "Upgrade History". The type of upgrade displayed is "Rolling". > Additionally, when clicking on the upgrade, it shows as "HOST_ORDERED" > instead of "Host Ordered" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19034) Upgrade History Displays Wrong Upgrade Type
[ https://issues.apache.org/jira/browse/AMBARI-19034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19034: -- Attachment: (was: AMBARI-19034.patch) > Upgrade History Displays Wrong Upgrade Type > --- > > Key: AMBARI-19034 > URL: https://issues.apache.org/jira/browse/AMBARI-19034 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.5.0 > > Attachments: AMBARI-19034.patch, AMBARI-19034_branch-2.5.patch, > Screen Shot 2016-11-10 at 1.24.12 PM.png, Screen Shot 2016-11-10 at 1.27.28 > PM.png > > > Perform a HOST_ORDERED upgrade. After the upgrade has completed, navigate to > the "Upgrade History". The type of upgrade displayed is "Rolling". > Additionally, when clicking on the upgrade, it shows as "HOST_ORDERED" > instead of "Host Ordered" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19034) Upgrade History Displays Wrong Upgrade Type
[ https://issues.apache.org/jira/browse/AMBARI-19034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19034: -- Status: Patch Available (was: Open) > Upgrade History Displays Wrong Upgrade Type > --- > > Key: AMBARI-19034 > URL: https://issues.apache.org/jira/browse/AMBARI-19034 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.5.0 > > Attachments: AMBARI-19034.patch, AMBARI-19034_branch-2.5.patch, > Screen Shot 2016-11-10 at 1.24.12 PM.png, Screen Shot 2016-11-10 at 1.27.28 > PM.png > > > Perform a HOST_ORDERED upgrade. After the upgrade has completed, navigate to > the "Upgrade History". The type of upgrade displayed is "Rolling". > Additionally, when clicking on the upgrade, it shows as "HOST_ORDERED" > instead of "Host Ordered" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19045) Remove unnecessary Log Feeder Date Mapper tests
[ https://issues.apache.org/jira/browse/AMBARI-19045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-19045: Attachment: AMBARI-19045.patch > Remove unnecessary Log Feeder Date Mapper tests > --- > > Key: AMBARI-19045 > URL: https://issues.apache.org/jira/browse/AMBARI-19045 > Project: Ambari > Issue Type: Bug >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Attachments: AMBARI-19045.patch > > > Some unit tests for Date Mapper in the Log Feeder > (testMapperDate_patternWithoutYear_previousYearLog, > testMapperDate_patternWithoutYear_currentYearLog) make no sense, but fail in > December. Remove these tests. > Options -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19046) Ambari ResourceManager alerts not working with ResourceManager HA
[ https://issues.apache.org/jira/browse/AMBARI-19046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Larsson updated AMBARI-19046: Description: When enabling ResourceManager HA, alerts such as "ResourceManager CPU utilisation" become aware that there are two RM's to check. However, when the alert queries the standby RM it will just respond with a http 307 redirect and the alert will end up in an "Unknown" state. This means that after RM HA is enabled, either you live with these alert constantly alerting, or you disable them. Perhaps this is unsolvable without changes to the RM but I'll create the ticket here as the first place. The alerts that we had to disable are: * ResourceManager CPU Utilization * ResourceManager RPC Latency * NodeManager Health Summary was: When enabling ResourceManager HA, alerts such as "ResourceManager CPU utilisation" become aware that there are two RM's to check. However, when the alert queries the standby RM it will just respond with a http 307 redirect and the alert will end up in an "Unknown" state. This means that after RM HA is enabled, either you live with these alert constantly alerting, or you disable them. Perhaps this is unsolvable without changes to the RM but I'll create the ticket here as the first place. > Ambari ResourceManager alerts not working with ResourceManager HA > - > > Key: AMBARI-19046 > URL: https://issues.apache.org/jira/browse/AMBARI-19046 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.2.2 >Reporter: Thomas Larsson >Priority: Minor > > When enabling ResourceManager HA, alerts such as "ResourceManager CPU > utilisation" become aware that there are two RM's to check. > However, when the alert queries the standby RM it will just respond with a > http 307 redirect and the alert will end up in an "Unknown" state. > This means that after RM HA is enabled, either you live with these alert > constantly alerting, or you disable them. > Perhaps this is unsolvable without changes to the RM but I'll create the > ticket here as the first place. > The alerts that we had to disable are: > * ResourceManager CPU Utilization > * ResourceManager RPC Latency > * NodeManager Health Summary -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19045) Remove unnecessary Log Feeder Date Mapper tests
[ https://issues.apache.org/jira/browse/AMBARI-19045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-19045: Status: Patch Available (was: In Progress) > Remove unnecessary Log Feeder Date Mapper tests > --- > > Key: AMBARI-19045 > URL: https://issues.apache.org/jira/browse/AMBARI-19045 > Project: Ambari > Issue Type: Bug >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Attachments: AMBARI-19045.patch > > > Some unit tests for Date Mapper in the Log Feeder > (testMapperDate_patternWithoutYear_previousYearLog, > testMapperDate_patternWithoutYear_currentYearLog) make no sense, but fail in > December. Remove these tests. > Options -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18713) use exclude list of mount device types on docker containers
[ https://issues.apache.org/jira/browse/AMBARI-18713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-18713: - Attachment: AMBARI-18713-2.5.patch.1 > use exclude list of mount device types on docker containers > --- > > Key: AMBARI-18713 > URL: https://issues.apache.org/jira/browse/AMBARI-18713 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Dmytro Grinenko >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18713-2.5.patch, AMBARI-18713-2.5.patch.1, > AMBARI-18713.patch, AMBARI-18713.patch.1, AMBARI-18713.patch.2 > > > * Remove logic from UI that picks a single host to represent the entire > cluster > * Have each host report their mount devices and how much space is available > in each one, so Ambari can store this in the DB (this will affect new > installs only or newly registered hosts) > * Move logic to Stack Advisor > * Use exclude list -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18713) use exclude list of mount device types on docker containers
[ https://issues.apache.org/jira/browse/AMBARI-18713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-18713: - Attachment: (was: AMBARI-18713-2.5.patch.1) > use exclude list of mount device types on docker containers > --- > > Key: AMBARI-18713 > URL: https://issues.apache.org/jira/browse/AMBARI-18713 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Dmytro Grinenko >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18713-2.5.patch, AMBARI-18713.patch, > AMBARI-18713.patch.1, AMBARI-18713.patch.2 > > > * Remove logic from UI that picks a single host to represent the entire > cluster > * Have each host report their mount devices and how much space is available > in each one, so Ambari can store this in the DB (this will affect new > installs only or newly registered hosts) > * Move logic to Stack Advisor > * Use exclude list -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19034) Upgrade History Displays Wrong Upgrade Type
[
https://issues.apache.org/jira/browse/AMBARI-19034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15711595#comment-15711595
]
Hadoop QA commented on AMBARI-19034:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841257/AMBARI-19034.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9476//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9476//console
This message is automatically generated.
> Upgrade History Displays Wrong Upgrade Type
> ---
>
> Key: AMBARI-19034
> URL: https://issues.apache.org/jira/browse/AMBARI-19034
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 2.5.0
>
> Attachments: AMBARI-19034.patch, AMBARI-19034_branch-2.5.patch,
> Screen Shot 2016-11-10 at 1.24.12 PM.png, Screen Shot 2016-11-10 at 1.27.28
> PM.png
>
>
> Perform a HOST_ORDERED upgrade. After the upgrade has completed, navigate to
> the "Upgrade History". The type of upgrade displayed is "Rolling".
> Additionally, when clicking on the upgrade, it shows as "HOST_ORDERED"
> instead of "Host Ordered"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18713) use exclude list of mount device types on docker containers
[ https://issues.apache.org/jira/browse/AMBARI-18713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-18713: - Attachment: AMBARI-18713-2.5.patch.1 > use exclude list of mount device types on docker containers > --- > > Key: AMBARI-18713 > URL: https://issues.apache.org/jira/browse/AMBARI-18713 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Dmytro Grinenko >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18713-2.5.patch, AMBARI-18713-2.5.patch.1, > AMBARI-18713.patch, AMBARI-18713.patch.1, AMBARI-18713.patch.2 > > > * Remove logic from UI that picks a single host to represent the entire > cluster > * Have each host report their mount devices and how much space is available > in each one, so Ambari can store this in the DB (this will affect new > installs only or newly registered hosts) > * Move logic to Stack Advisor > * Use exclude list -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18713) use exclude list of mount device types on docker containers
[ https://issues.apache.org/jira/browse/AMBARI-18713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-18713: - Attachment: AMBARI-18713.patch.2 > use exclude list of mount device types on docker containers > --- > > Key: AMBARI-18713 > URL: https://issues.apache.org/jira/browse/AMBARI-18713 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Dmytro Grinenko >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18713-2.5.patch, AMBARI-18713-2.5.patch.1, > AMBARI-18713.patch, AMBARI-18713.patch.1, AMBARI-18713.patch.2 > > > * Remove logic from UI that picks a single host to represent the entire > cluster > * Have each host report their mount devices and how much space is available > in each one, so Ambari can store this in the DB (this will affect new > installs only or newly registered hosts) > * Move logic to Stack Advisor > * Use exclude list -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19033) Log Search: Cannot increase the number of shards per node for solr collections
[ https://issues.apache.org/jira/browse/AMBARI-19033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-19033: -- Attachment: AMBARI-19033.patch > Log Search: Cannot increase the number of shards per node for solr collections > -- > > Key: AMBARI-19033 > URL: https://issues.apache.org/jira/browse/AMBARI-19033 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-19033.patch, AMBARI-19033.patch > > Original Estimate: 24h > Remaining Estimate: 24h > > If the user changes the number of shards for collections, logsearch cannot > create the new shards if there is not enough solr cores for that > (same for hadoop_logs and audit_logs collection) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18713) use exclude list of mount device types on docker containers
[ https://issues.apache.org/jira/browse/AMBARI-18713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-18713: - Attachment: (was: AMBARI-18713.patch.2) > use exclude list of mount device types on docker containers > --- > > Key: AMBARI-18713 > URL: https://issues.apache.org/jira/browse/AMBARI-18713 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Dmytro Grinenko >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18713-2.5.patch, AMBARI-18713-2.5.patch.1, > AMBARI-18713.patch, AMBARI-18713.patch.1, AMBARI-18713.patch.2 > > > * Remove logic from UI that picks a single host to represent the entire > cluster > * Have each host report their mount devices and how much space is available > in each one, so Ambari can store this in the DB (this will affect new > installs only or newly registered hosts) > * Move logic to Stack Advisor > * Use exclude list -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19045) Remove unnecessary Log Feeder Date Mapper tests
[
https://issues.apache.org/jira/browse/AMBARI-19045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15711623#comment-15711623
]
Miklos Gergely commented on AMBARI-19045:
-
committed to trunk:
{code:java}
commit dc5f4e259ce0f83a3a648de54468f6dadacd5291
Author: Miklos Gergely
Date: Thu Dec 1 11:43:28 2016 +0100
AMBARI-19045 Remove unnecessary Log Feeder Date Mapper tests
Change-Id: Ia8d613c0c53bff04c5ccee0579a337b8cbb3a00a
{code}
committed to branch-2.5:
{code:java}
commit 5709f438b5b52aecd1f1fdf93fadbb8630b77e6d
Author: Miklos Gergely
Date: Thu Dec 1 11:41:42 2016 +0100
AMBARI-19045 Remove unnecessary Log Feeder Date Mapper tests
Change-Id: I9f47bfc5a18b63d1a3f4dd208e7186952f804430
{code}
> Remove unnecessary Log Feeder Date Mapper tests
> ---
>
> Key: AMBARI-19045
> URL: https://issues.apache.org/jira/browse/AMBARI-19045
> Project: Ambari
> Issue Type: Bug
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Attachments: AMBARI-19045.patch
>
>
> Some unit tests for Date Mapper in the Log Feeder
> (testMapperDate_patternWithoutYear_previousYearLog,
> testMapperDate_patternWithoutYear_currentYearLog) make no sense, but fail in
> December. Remove these tests.
> Options
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19033) Log Search: Cannot increase the number of shards per node for solr collections
[ https://issues.apache.org/jira/browse/AMBARI-19033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-19033: -- Attachment: (was: AMBARI-19033.patch) > Log Search: Cannot increase the number of shards per node for solr collections > -- > > Key: AMBARI-19033 > URL: https://issues.apache.org/jira/browse/AMBARI-19033 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-19033.patch > > Original Estimate: 24h > Remaining Estimate: 24h > > If the user changes the number of shards for collections, logsearch cannot > create the new shards if there is not enough solr cores for that > (same for hadoop_logs and audit_logs collection) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-19033) Log Search: Cannot increase the number of shards per node for solr collections
[
https://issues.apache.org/jira/browse/AMBARI-19033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó resolved AMBARI-19033.
---
Resolution: Fixed
committed to trunk:
{code:java}
commit 195b7456c0b4dc15833b502463daba7b29a51bee
Author: oleewere
Date: Thu Dec 1 11:34:45 2016 +0100
AMBARI-19033. Log Search: Cannot increase the number of shards per node for
solr collections (oleewere)
Change-Id: I44fa2c96befa2eff3d6f2acfb608eff8ed45f021
{code}
committed to branch-2.5:
{code:java}
commit 80b5348cac1c54942ca33d92dbc392faa74c9662
Author: oleewere
Date: Thu Dec 1 11:34:45 2016 +0100
AMBARI-19033. Log Search: Cannot increase the number of shards per node for
solr collections (oleewere)
Change-Id: I44fa2c96befa2eff3d6f2acfb608eff8ed45f021
{code}
> Log Search: Cannot increase the number of shards per node for solr collections
> --
>
> Key: AMBARI-19033
> URL: https://issues.apache.org/jira/browse/AMBARI-19033
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-19033.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> If the user changes the number of shards for collections, logsearch cannot
> create the new shards if there is not enough solr cores for that
> (same for hadoop_logs and audit_logs collection)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19034) Upgrade History Displays Wrong Upgrade Type
[ https://issues.apache.org/jira/browse/AMBARI-19034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15711621#comment-15711621 ] Andrii Tkach commented on AMBARI-19034: --- 20020 tests complete (26 seconds) 155 tests pending > Upgrade History Displays Wrong Upgrade Type > --- > > Key: AMBARI-19034 > URL: https://issues.apache.org/jira/browse/AMBARI-19034 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.5.0 > > Attachments: AMBARI-19034.patch, AMBARI-19034_branch-2.5.patch, > Screen Shot 2016-11-10 at 1.24.12 PM.png, Screen Shot 2016-11-10 at 1.27.28 > PM.png > > > Perform a HOST_ORDERED upgrade. After the upgrade has completed, navigate to > the "Upgrade History". The type of upgrade displayed is "Rolling". > Additionally, when clicking on the upgrade, it shows as "HOST_ORDERED" > instead of "Host Ordered" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19034) Upgrade History Displays Wrong Upgrade Type
[ https://issues.apache.org/jira/browse/AMBARI-19034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19034: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Upgrade History Displays Wrong Upgrade Type > --- > > Key: AMBARI-19034 > URL: https://issues.apache.org/jira/browse/AMBARI-19034 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.5.0 > > Attachments: AMBARI-19034.patch, AMBARI-19034_branch-2.5.patch, > Screen Shot 2016-11-10 at 1.24.12 PM.png, Screen Shot 2016-11-10 at 1.27.28 > PM.png > > > Perform a HOST_ORDERED upgrade. After the upgrade has completed, navigate to > the "Upgrade History". The type of upgrade displayed is "Rolling". > Additionally, when clicking on the upgrade, it shows as "HOST_ORDERED" > instead of "Host Ordered" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19034) Upgrade History Displays Wrong Upgrade Type
[ https://issues.apache.org/jira/browse/AMBARI-19034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15711634#comment-15711634 ] Andrii Tkach commented on AMBARI-19034: --- committed to trunk and branch-2.5 > Upgrade History Displays Wrong Upgrade Type > --- > > Key: AMBARI-19034 > URL: https://issues.apache.org/jira/browse/AMBARI-19034 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.5.0 > > Attachments: AMBARI-19034.patch, AMBARI-19034_branch-2.5.patch, > Screen Shot 2016-11-10 at 1.24.12 PM.png, Screen Shot 2016-11-10 at 1.27.28 > PM.png > > > Perform a HOST_ORDERED upgrade. After the upgrade has completed, navigate to > the "Upgrade History". The type of upgrade displayed is "Rolling". > Additionally, when clicking on the upgrade, it shows as "HOST_ORDERED" > instead of "Host Ordered" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18975) Remove Zeppelin View from Ambari
[ https://issues.apache.org/jira/browse/AMBARI-18975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Renjith Kamath updated AMBARI-18975: Attachment: AMBARI-18975-branch-2.5-v2.patch > Remove Zeppelin View from Ambari > > > Key: AMBARI-18975 > URL: https://issues.apache.org/jira/browse/AMBARI-18975 > Project: Ambari > Issue Type: Improvement >Reporter: Renjith Kamath >Assignee: Renjith Kamath > Fix For: 2.5.0 > > Attachments: AMBARI-18975-branch-2.5-v1.patch, > AMBARI-18975-branch-2.5-v2.patch > > > Currently Zeppelin view is an iframe loading Zeppelin UI. There are no > advantages of loading the UI of a service in an iframe and also limits the ux > of Zeppelin due to fixed iframe width in Ambari. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18975) Remove Zeppelin View from Ambari
[ https://issues.apache.org/jira/browse/AMBARI-18975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Renjith Kamath updated AMBARI-18975: Attachment: AMBARI-18975-branch-2.5-v3.patch > Remove Zeppelin View from Ambari > > > Key: AMBARI-18975 > URL: https://issues.apache.org/jira/browse/AMBARI-18975 > Project: Ambari > Issue Type: Improvement >Reporter: Renjith Kamath >Assignee: Renjith Kamath > Fix For: 2.5.0 > > Attachments: AMBARI-18975-branch-2.5-v1.patch, > AMBARI-18975-branch-2.5-v2.patch, AMBARI-18975-branch-2.5-v3.patch > > > Currently Zeppelin view is an iframe loading Zeppelin UI. There are no > advantages of loading the UI of a service in an iframe and also limits the ux > of Zeppelin due to fixed iframe width in Ambari. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19045) Remove unnecessary Log Feeder Date Mapper tests
[ https://issues.apache.org/jira/browse/AMBARI-19045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15711691#comment-15711691 ] Hudson commented on AMBARI-19045: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #428 (See [https://builds.apache.org/job/Ambari-branch-2.5/428/]) AMBARI-19045 Remove unnecessary Log Feeder Date Mapper tests (mgergely: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=5709f438b5b52aecd1f1fdf93fadbb8630b77e6d]) * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/test/java/org/apache/ambari/logfeeder/mapper/MapperDateTest.java > Remove unnecessary Log Feeder Date Mapper tests > --- > > Key: AMBARI-19045 > URL: https://issues.apache.org/jira/browse/AMBARI-19045 > Project: Ambari > Issue Type: Bug >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Attachments: AMBARI-19045.patch > > > Some unit tests for Date Mapper in the Log Feeder > (testMapperDate_patternWithoutYear_previousYearLog, > testMapperDate_patternWithoutYear_currentYearLog) make no sense, but fail in > December. Remove these tests. > Options -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19033) Log Search: Cannot increase the number of shards per node for solr collections
[ https://issues.apache.org/jira/browse/AMBARI-19033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15711692#comment-15711692 ] Hudson commented on AMBARI-19033: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #428 (See [https://builds.apache.org/job/Ambari-branch-2.5/428/]) AMBARI-19033. Log Search: Cannot increase the number of shards per node (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=80b5348cac1c54942ca33d92dbc392faa74c9662]) * (edit) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/dao/SolrCollectionDao.java > Log Search: Cannot increase the number of shards per node for solr collections > -- > > Key: AMBARI-19033 > URL: https://issues.apache.org/jira/browse/AMBARI-19033 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-19033.patch > > Original Estimate: 24h > Remaining Estimate: 24h > > If the user changes the number of shards for collections, logsearch cannot > create the new shards if there is not enough solr cores for that > (same for hadoop_logs and audit_logs collection) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19045) Remove unnecessary Log Feeder Date Mapper tests
[ https://issues.apache.org/jira/browse/AMBARI-19045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15711700#comment-15711700 ] Hudson commented on AMBARI-19045: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6125 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6125/]) AMBARI-19045 Remove unnecessary Log Feeder Date Mapper tests (mgergely: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=dc5f4e259ce0f83a3a648de54468f6dadacd5291]) * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/test/java/org/apache/ambari/logfeeder/mapper/MapperDateTest.java > Remove unnecessary Log Feeder Date Mapper tests > --- > > Key: AMBARI-19045 > URL: https://issues.apache.org/jira/browse/AMBARI-19045 > Project: Ambari > Issue Type: Bug >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Attachments: AMBARI-19045.patch > > > Some unit tests for Date Mapper in the Log Feeder > (testMapperDate_patternWithoutYear_previousYearLog, > testMapperDate_patternWithoutYear_currentYearLog) make no sense, but fail in > December. Remove these tests. > Options -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19033) Log Search: Cannot increase the number of shards per node for solr collections
[ https://issues.apache.org/jira/browse/AMBARI-19033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15711701#comment-15711701 ] Hudson commented on AMBARI-19033: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6125 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6125/]) AMBARI-19033. Log Search: Cannot increase the number of shards per node (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=195b7456c0b4dc15833b502463daba7b29a51bee]) * (edit) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/dao/SolrCollectionDao.java > Log Search: Cannot increase the number of shards per node for solr collections > -- > > Key: AMBARI-19033 > URL: https://issues.apache.org/jira/browse/AMBARI-19033 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-19033.patch > > Original Estimate: 24h > Remaining Estimate: 24h > > If the user changes the number of shards for collections, logsearch cannot > create the new shards if there is not enough solr cores for that > (same for hadoop_logs and audit_logs collection) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19034) Upgrade History Displays Wrong Upgrade Type
[ https://issues.apache.org/jira/browse/AMBARI-19034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15711775#comment-15711775 ] Hudson commented on AMBARI-19034: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #429 (See [https://builds.apache.org/job/Ambari-branch-2.5/429/]) AMBARI-19034 Upgrade History Displays Wrong Upgrade Type (atkach) (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8aa88e1675806d6e7a4dc9e801d63c9f1fcdaf65]) * (edit) ambari-web/app/models/stack_version/stack_upgrade_history.js * (edit) ambari-web/app/mappers/stack_upgrade_history_mapper.js * (edit) ambari-web/app/views/main/admin/stack_upgrade/upgrade_history_view.js * (edit) ambari-web/app/messages.js * (edit) ambari-web/app/styles/stack_versions.less * (edit) ambari-web/app/views/main/admin/stack_upgrade/upgrade_history_details_view.js * (edit) ambari-web/app/controllers/main/admin/stack_upgrade_history_controller.js > Upgrade History Displays Wrong Upgrade Type > --- > > Key: AMBARI-19034 > URL: https://issues.apache.org/jira/browse/AMBARI-19034 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.5.0 > > Attachments: AMBARI-19034.patch, AMBARI-19034_branch-2.5.patch, > Screen Shot 2016-11-10 at 1.24.12 PM.png, Screen Shot 2016-11-10 at 1.27.28 > PM.png > > > Perform a HOST_ORDERED upgrade. After the upgrade has completed, navigate to > the "Upgrade History". The type of upgrade displayed is "Rolling". > Additionally, when clicking on the upgrade, it shows as "HOST_ORDERED" > instead of "Host Ordered" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19045) Remove unnecessary Log Feeder Date Mapper tests
[
https://issues.apache.org/jira/browse/AMBARI-19045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15711800#comment-15711800
]
Hadoop QA commented on AMBARI-19045:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841258/AMBARI-19045.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/9477//console
This message is automatically generated.
> Remove unnecessary Log Feeder Date Mapper tests
> ---
>
> Key: AMBARI-19045
> URL: https://issues.apache.org/jira/browse/AMBARI-19045
> Project: Ambari
> Issue Type: Bug
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Attachments: AMBARI-19045.patch
>
>
> Some unit tests for Date Mapper in the Log Feeder
> (testMapperDate_patternWithoutYear_previousYearLog,
> testMapperDate_patternWithoutYear_currentYearLog) make no sense, but fail in
> December. Remove these tests.
> Options
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18975) Remove Zeppelin View from Ambari
[
https://issues.apache.org/jira/browse/AMBARI-18975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15711802#comment-15711802
]
Hadoop QA commented on AMBARI-18975:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841269/AMBARI-18975-branch-2.5-v3.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/9478//console
This message is automatically generated.
> Remove Zeppelin View from Ambari
>
>
> Key: AMBARI-18975
> URL: https://issues.apache.org/jira/browse/AMBARI-18975
> Project: Ambari
> Issue Type: Improvement
>Reporter: Renjith Kamath
>Assignee: Renjith Kamath
> Fix For: 2.5.0
>
> Attachments: AMBARI-18975-branch-2.5-v1.patch,
> AMBARI-18975-branch-2.5-v2.patch, AMBARI-18975-branch-2.5-v3.patch
>
>
> Currently Zeppelin view is an iframe loading Zeppelin UI. There are no
> advantages of loading the UI of a service in an iframe and also limits the ux
> of Zeppelin due to fixed iframe width in Ambari.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19047) Select Versions page: 'Remove' tooltip does not disappear
Oleg Nechiporenko created AMBARI-19047: -- Summary: Select Versions page: 'Remove' tooltip does not disappear Key: AMBARI-19047 URL: https://issues.apache.org/jira/browse/AMBARI-19047 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Oleg Nechiporenko Assignee: Oleg Nechiporenko Fix For: 3.0.0 Attachments: Screen Shot 2016-11-29 at 3.12.07 PM.png -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19047) Select Versions page: 'Remove' tooltip does not disappear
[ https://issues.apache.org/jira/browse/AMBARI-19047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-19047: --- Attachment: Screen Shot 2016-11-29 at 3.12.07 PM.png > Select Versions page: 'Remove' tooltip does not disappear > - > > Key: AMBARI-19047 > URL: https://issues.apache.org/jira/browse/AMBARI-19047 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: Screen Shot 2016-11-29 at 3.12.07 PM.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19047) Select Versions page: 'Remove' tooltip does not disappear
[ https://issues.apache.org/jira/browse/AMBARI-19047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-19047: --- Attachment: AMBARI-19047.patch > Select Versions page: 'Remove' tooltip does not disappear > - > > Key: AMBARI-19047 > URL: https://issues.apache.org/jira/browse/AMBARI-19047 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-19047.patch, Screen Shot 2016-11-29 at 3.12.07 > PM.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19043) CAPACITY-SCHEDULER & PIG View not loading for Ambari-2.5.0
[ https://issues.apache.org/jira/browse/AMBARI-19043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-19043: --- Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk and branch-2.5 > CAPACITY-SCHEDULER & PIG View not loading for Ambari-2.5.0 > -- > > Key: AMBARI-19043 > URL: https://issues.apache.org/jira/browse/AMBARI-19043 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Blocker > Fix For: 2.5.0 > > Attachments: AMBARI-19043.branch-2.5.patch, Capacity Scheduler View > Not Loading.png, Pig View Not Loading.png > > > CAPACITY-SCHEDULER View not loading for Ambari-2.5.0 in the cluster: > http://172.27.29.71:8080/#/main/views/CAPACITY-SCHEDULER/1.0.0/NEW_INSTANCE > Facing error while loading pig view in live cluster: > http://172.27.23.128:8080/views/PIG/1.0.0/PIG/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19047) Select Versions page: 'Remove' tooltip does not disappear
[ https://issues.apache.org/jira/browse/AMBARI-19047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-19047: --- Status: Patch Available (was: Open) > Select Versions page: 'Remove' tooltip does not disappear > - > > Key: AMBARI-19047 > URL: https://issues.apache.org/jira/browse/AMBARI-19047 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-19047.patch, Screen Shot 2016-11-29 at 3.12.07 > PM.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-19047) Select Versions page: 'Remove' tooltip does not disappear
[ https://issues.apache.org/jira/browse/AMBARI-19047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15711840#comment-15711840 ] Oleg Nechiporenko edited comment on AMBARI-19047 at 12/1/16 12:26 PM: -- +1 by [~atkach] on the review board was (Author: onechiporenko): +1 by @atkach on the review board > Select Versions page: 'Remove' tooltip does not disappear > - > > Key: AMBARI-19047 > URL: https://issues.apache.org/jira/browse/AMBARI-19047 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-19047.patch, Screen Shot 2016-11-29 at 3.12.07 > PM.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19047) Select Versions page: 'Remove' tooltip does not disappear
[ https://issues.apache.org/jira/browse/AMBARI-19047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15711840#comment-15711840 ] Oleg Nechiporenko commented on AMBARI-19047: +1 by @atkach on the review board > Select Versions page: 'Remove' tooltip does not disappear > - > > Key: AMBARI-19047 > URL: https://issues.apache.org/jira/browse/AMBARI-19047 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-19047.patch, Screen Shot 2016-11-29 at 3.12.07 > PM.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19031) AMBARI-19031: UI Enhancements, import/export assets and smart version configuration
[
https://issues.apache.org/jira/browse/AMBARI-19031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15711847#comment-15711847
]
Hadoop QA commented on AMBARI-19031:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841240/AMBARI-19031.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 7 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in
contrib/views/wfmanager/src/main/resources/ui contrib/views/wfmanager
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9479//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9479//console
This message is automatically generated.
> AMBARI-19031: UI Enhancements, import/export assets and smart version
> configuration
> ---
>
> Key: AMBARI-19031
> URL: https://issues.apache.org/jira/browse/AMBARI-19031
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Padma Priya Nagaraj
> Attachments: AMBARI-19031.01.patch
>
>
> UX Enhancemenets
> - Dashboard as a tab
> - Coordinator UI changes
> - Bundle smart name autofil
> Features
> - Version setting picked up from Oozie
> - Ability to import/export assets(actions)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19007) Atlas to support configuration of hooks from separate cluster
[
https://issues.apache.org/jira/browse/AMBARI-19007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15711849#comment-15711849
]
Hadoop QA commented on AMBARI-19007:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841239/AMBARI-19007.01.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/9480//console
This message is automatically generated.
> Atlas to support configuration of hooks from separate cluster
> -
>
> Key: AMBARI-19007
> URL: https://issues.apache.org/jira/browse/AMBARI-19007
> Project: Ambari
> Issue Type: New Feature
> Components: ambari-server
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Blocker
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19007-trunk.01.patch, AMBARI-19007-trunk.patch,
> AMBARI-19007.01.patch, AMBARI-19007.patch
>
>
> *Need support in ambari to allow atlas to communicate with hooks installed on
> separate clusters*
> # Ambari Stack definition changes (for all four hooks being installed on
> Separate Cluster) - this information will be stored in blueprints.
> # Need to be able to sync with Atlas to leverage tag based security via
> tagsync service
> # Ambari driven configuration and addition of flags to support the feature.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19047) Select Versions page: 'Remove' tooltip does not disappear
[
https://issues.apache.org/jira/browse/AMBARI-19047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15711885#comment-15711885
]
Hadoop QA commented on AMBARI-19047:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841280/AMBARI-19047.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9481//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9481//console
This message is automatically generated.
> Select Versions page: 'Remove' tooltip does not disappear
> -
>
> Key: AMBARI-19047
> URL: https://issues.apache.org/jira/browse/AMBARI-19047
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-19047.patch, Screen Shot 2016-11-29 at 3.12.07
> PM.png
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19047) Select Versions page: 'Remove' tooltip does not disappear
[ https://issues.apache.org/jira/browse/AMBARI-19047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15711887#comment-15711887 ] Oleg Nechiporenko commented on AMBARI-19047: Committed to trunk > Select Versions page: 'Remove' tooltip does not disappear > - > > Key: AMBARI-19047 > URL: https://issues.apache.org/jira/browse/AMBARI-19047 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-19047.patch, Screen Shot 2016-11-29 at 3.12.07 > PM.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19047) Select Versions page: 'Remove' tooltip does not disappear
[ https://issues.apache.org/jira/browse/AMBARI-19047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15711886#comment-15711886 ] Oleg Nechiporenko commented on AMBARI-19047: Tested manually on the real cluster > Select Versions page: 'Remove' tooltip does not disappear > - > > Key: AMBARI-19047 > URL: https://issues.apache.org/jira/browse/AMBARI-19047 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-19047.patch, Screen Shot 2016-11-29 at 3.12.07 > PM.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19043) CAPACITY-SCHEDULER & PIG View not loading for Ambari-2.5.0
[ https://issues.apache.org/jira/browse/AMBARI-19043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15711913#comment-15711913 ] Hudson commented on AMBARI-19043: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #430 (See [https://builds.apache.org/job/Ambari-branch-2.5/430/]) AMBARI-19043 : CAPACITY-SCHEDULER & PIG View not loading for (nitiraj.rathore: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d036e0e2145a4b5c240803cd6b5c7fc4572ed128]) * (edit) contrib/views/pig/src/main/resources/ui/pig-web/app/app.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/app.js > CAPACITY-SCHEDULER & PIG View not loading for Ambari-2.5.0 > -- > > Key: AMBARI-19043 > URL: https://issues.apache.org/jira/browse/AMBARI-19043 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Blocker > Fix For: 2.5.0 > > Attachments: AMBARI-19043.branch-2.5.patch, Capacity Scheduler View > Not Loading.png, Pig View Not Loading.png > > > CAPACITY-SCHEDULER View not loading for Ambari-2.5.0 in the cluster: > http://172.27.29.71:8080/#/main/views/CAPACITY-SCHEDULER/1.0.0/NEW_INSTANCE > Facing error while loading pig view in live cluster: > http://172.27.23.128:8080/views/PIG/1.0.0/PIG/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19047) Select Versions page: 'Remove' tooltip does not disappear
[
https://issues.apache.org/jira/browse/AMBARI-19047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15711983#comment-15711983
]
Hadoop QA commented on AMBARI-19047:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841280/AMBARI-19047.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/9482//console
This message is automatically generated.
> Select Versions page: 'Remove' tooltip does not disappear
> -
>
> Key: AMBARI-19047
> URL: https://issues.apache.org/jira/browse/AMBARI-19047
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-19047.patch, Screen Shot 2016-11-29 at 3.12.07
> PM.png
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19048) Delete service action should show the config recommendation popup
Andrii Babiichuk created AMBARI-19048: - Summary: Delete service action should show the config recommendation popup Key: AMBARI-19048 URL: https://issues.apache.org/jira/browse/AMBARI-19048 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.5.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Fix For: 2.5.0 When a service is deleted, it's related configuration are changed as per stack advisor recommendation. As scope of this ticket, ambari-web should show all the configuration that will be changed in recommendation popup when a service is deleted. This popup should be same as the one shown while doing service->config change and clicking on save button. Following similar flow as on service->config page, When user confirms recommended changes, ambari-web should male API call for checked config changes. If no config will be changed on any service deletion action then in that case recommendation popup should bot be shown -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18736) Perf: Simulate alerts for multiple Ambari Agents running on single Host
[ https://issues.apache.org/jira/browse/AMBARI-18736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18736: --- Attachment: AMBARI-18736.patch > Perf: Simulate alerts for multiple Ambari Agents running on single Host > --- > > Key: AMBARI-18736 > URL: https://issues.apache.org/jira/browse/AMBARI-18736 > Project: Ambari > Issue Type: Story > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Vitaly Brodetskyi > Fix For: 2.5.0 > > Attachments: AMBARI-18736.patch, AMBARI-18736.patch > > > The PERF stack can actually create Python scripts to run actual alerts whose > behavior is controlled by configs to either always pass, always fail, pass > with some success %, flip/thrash, timeout, etc. > For other types of alerts (web, host:port), we will need to override the > Alert Scheduler on the Ambari Agent to return fake values. > The goal is to stress test Ambari Server when multiple Ambari Agents run on a > single host. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18736) Perf: Simulate alerts for multiple Ambari Agents running on single Host
[ https://issues.apache.org/jira/browse/AMBARI-18736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18736: --- Attachment: (was: AMBARI-18736.patch) > Perf: Simulate alerts for multiple Ambari Agents running on single Host > --- > > Key: AMBARI-18736 > URL: https://issues.apache.org/jira/browse/AMBARI-18736 > Project: Ambari > Issue Type: Story > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Vitaly Brodetskyi > Fix For: 2.5.0 > > Attachments: AMBARI-18736.patch > > > The PERF stack can actually create Python scripts to run actual alerts whose > behavior is controlled by configs to either always pass, always fail, pass > with some success %, flip/thrash, timeout, etc. > For other types of alerts (web, host:port), we will need to override the > Alert Scheduler on the Ambari Agent to return fake values. > The goal is to stress test Ambari Server when multiple Ambari Agents run on a > single host. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19048) Delete service action should show the config recommendation popup
[ https://issues.apache.org/jira/browse/AMBARI-19048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-19048: -- Attachment: AMBARI-19048.patch > Delete service action should show the config recommendation popup > - > > Key: AMBARI-19048 > URL: https://issues.apache.org/jira/browse/AMBARI-19048 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 2.5.0 > > Attachments: AMBARI-19048.patch > > > When a service is deleted, it's related configuration are changed as per > stack advisor recommendation. > As scope of this ticket, ambari-web should show all the configuration that > will be changed in recommendation popup when a service is deleted. This popup > should be same as the one shown while doing service->config change and > clicking on save button. > Following similar flow as on service->config page, When user confirms > recommended changes, ambari-web should male API call for checked config > changes. > If no config will be changed on any service deletion action then in that case > recommendation popup should bot be shown -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19048) Delete service action should show the config recommendation popup
[ https://issues.apache.org/jira/browse/AMBARI-19048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-19048: -- Status: Patch Available (was: Open) > Delete service action should show the config recommendation popup > - > > Key: AMBARI-19048 > URL: https://issues.apache.org/jira/browse/AMBARI-19048 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 2.5.0 > > Attachments: AMBARI-19048.patch > > > When a service is deleted, it's related configuration are changed as per > stack advisor recommendation. > As scope of this ticket, ambari-web should show all the configuration that > will be changed in recommendation popup when a service is deleted. This popup > should be same as the one shown while doing service->config change and > clicking on save button. > Following similar flow as on service->config page, When user confirms > recommended changes, ambari-web should male API call for checked config > changes. > If no config will be changed on any service deletion action then in that case > recommendation popup should bot be shown -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19049) Alerts Popup displays full error stacktrace instead of minimal content
Antonenko Alexander created AMBARI-19049: Summary: Alerts Popup displays full error stacktrace instead of minimal content Key: AMBARI-19049 URL: https://issues.apache.org/jira/browse/AMBARI-19049 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Antonenko Alexander Assignee: Antonenko Alexander Fix For: 2.5.0 Alerts Popup displays full error stacktrace instead of minimal content STR: Navigate to any service page Click on Alerts button from top right corner of summary panel The complete error message should be displayed as a tooltip text or minimal text should be displayed. But the complete stacktrace is displayed in the popup window which makes the list of alerts look unorganized. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18736) Perf: Simulate alerts for multiple Ambari Agents running on single Host
[ https://issues.apache.org/jira/browse/AMBARI-18736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18736: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.5 > Perf: Simulate alerts for multiple Ambari Agents running on single Host > --- > > Key: AMBARI-18736 > URL: https://issues.apache.org/jira/browse/AMBARI-18736 > Project: Ambari > Issue Type: Story > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Vitaly Brodetskyi > Fix For: 2.5.0 > > Attachments: AMBARI-18736.patch > > > The PERF stack can actually create Python scripts to run actual alerts whose > behavior is controlled by configs to either always pass, always fail, pass > with some success %, flip/thrash, timeout, etc. > For other types of alerts (web, host:port), we will need to override the > Alert Scheduler on the Ambari Agent to return fake values. > The goal is to stress test Ambari Server when multiple Ambari Agents run on a > single host. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19048) Delete service action should show the config recommendation popup
[
https://issues.apache.org/jira/browse/AMBARI-19048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15712185#comment-15712185
]
Hadoop QA commented on AMBARI-19048:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841285/AMBARI-19048.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9483//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9483//console
This message is automatically generated.
> Delete service action should show the config recommendation popup
> -
>
> Key: AMBARI-19048
> URL: https://issues.apache.org/jira/browse/AMBARI-19048
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19048.patch
>
>
> When a service is deleted, it's related configuration are changed as per
> stack advisor recommendation.
> As scope of this ticket, ambari-web should show all the configuration that
> will be changed in recommendation popup when a service is deleted. This popup
> should be same as the one shown while doing service->config change and
> clicking on save button.
> Following similar flow as on service->config page, When user confirms
> recommended changes, ambari-web should male API call for checked config
> changes.
> If no config will be changed on any service deletion action then in that case
> recommendation popup should bot be shown
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19048) Delete service action should show the config recommendation popup
[ https://issues.apache.org/jira/browse/AMBARI-19048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15712198#comment-15712198 ] Andrii Babiichuk commented on AMBARI-19048: --- Committed to trunk > Delete service action should show the config recommendation popup > - > > Key: AMBARI-19048 > URL: https://issues.apache.org/jira/browse/AMBARI-19048 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 2.5.0 > > Attachments: AMBARI-19048.patch > > > When a service is deleted, it's related configuration are changed as per > stack advisor recommendation. > As scope of this ticket, ambari-web should show all the configuration that > will be changed in recommendation popup when a service is deleted. This popup > should be same as the one shown while doing service->config change and > clicking on save button. > Following similar flow as on service->config page, When user confirms > recommended changes, ambari-web should male API call for checked config > changes. > If no config will be changed on any service deletion action then in that case > recommendation popup should bot be shown -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19034) Upgrade History Displays Wrong Upgrade Type
[ https://issues.apache.org/jira/browse/AMBARI-19034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15712234#comment-15712234 ] Hudson commented on AMBARI-19034: - ABORTED: Integrated in Jenkins build Ambari-trunk-Commit #6126 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6126/]) AMBARI-19034 Upgrade History Displays Wrong Upgrade Type (atkach) (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4b387915117412b7153a7c36b3f26412538b756d]) * (edit) ambari-web/app/mappers/stack_upgrade_history_mapper.js * (edit) ambari-web/app/views/main/admin/stack_upgrade/upgrade_history_details_view.js * (edit) ambari-web/app/messages.js * (edit) ambari-web/app/styles/stack_versions.less * (edit) ambari-web/app/controllers/main/admin/stack_upgrade_history_controller.js * (edit) ambari-web/app/models/stack_version/stack_upgrade_history.js * (edit) ambari-web/app/views/main/admin/stack_upgrade/upgrade_history_view.js > Upgrade History Displays Wrong Upgrade Type > --- > > Key: AMBARI-19034 > URL: https://issues.apache.org/jira/browse/AMBARI-19034 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.5.0 > > Attachments: AMBARI-19034.patch, AMBARI-19034_branch-2.5.patch, > Screen Shot 2016-11-10 at 1.24.12 PM.png, Screen Shot 2016-11-10 at 1.27.28 > PM.png > > > Perform a HOST_ORDERED upgrade. After the upgrade has completed, navigate to > the "Upgrade History". The type of upgrade displayed is "Rolling". > Additionally, when clicking on the upgrade, it shows as "HOST_ORDERED" > instead of "Host Ordered" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19050) In sys-prepped environments, oozie share lib should be created and populated using the sharelib create facility exposed by Oozie.
Andrew Onischuk created AMBARI-19050:
Summary: In sys-prepped environments, oozie share lib should be
created and populated using the sharelib create facility exposed by Oozie.
Key: AMBARI-19050
URL: https://issues.apache.org/jira/browse/AMBARI-19050
Project: Ambari
Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
Fix For: 2.5.0
This jira can be used to track the cleanup effort to make these changes
identical to the way it is done in non sys prepped environments.
put_shared_lib_to_hdfs_cmd = format("{oozie_setup_sh} sharelib create -fs
{fs_root} -locallib {oozie_shared_lib}")
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18736) Perf: Simulate alerts for multiple Ambari Agents running on single Host
[ https://issues.apache.org/jira/browse/AMBARI-18736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15712253#comment-15712253 ] Hudson commented on AMBARI-18736: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #431 (See [https://builds.apache.org/job/Ambari-branch-2.5/431/]) AMBARI-18736. Perf: Simulate alerts for multiple Ambari Agents running (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=3a342138832357f38a2114fa520f5bb217a654bb]) * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HDFS/package/alerts/alert_checkpoint_time.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/YARN/configuration/yarn-alert-config.xml * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HBASE/alerts.json * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/HDFS/package/alerts/alert_nfs_gateway_process.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/HBASE/configuration/hbase-alert-config.xml * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/HBASE/package/alerts/hbase_master_process.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HDFS/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HDFS/package/alerts/alert_upgrade_finalized.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HDFS/package/alerts/alert_datanode_unmounted_data_dir.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/SNOW/package/alerts/alert_snow_process.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/SLEEPY/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HAPPY/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HDFS/alerts.json * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/HDFS/package/alerts/alert_snamenode_process.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/ZOOKEEPER/alerts.json * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/SLEEPY/configuration/sleepy-alert-config.xml * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/YARN/alerts.json * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/HDFS/configuration/hdfs-alert-config.xml * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/SLEEPY/package/alerts/alert_sleepy_process.py * (delete) ambari-server/src/main/resources/stacks/PERF/1.0/services/HDFS/package/alerts/alert_metrics_deviation.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/YARN/package/alerts/alert_resourcemanager_process.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/SLEEPY/alerts.json * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/YARN/package/alerts/alert_history_process.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/HAPPY/package/alerts/alert_happy_process.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/YARN/package/alerts/alert_timeline_process.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/YARN/package/alerts/alert_nodemanager_health.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/SNOW/configuration/snow-alert-config.xml * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/YARN/metainfo.xml * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/HAPPY/configuration/happy-alert-config.xml * (add) ambari-common/src/main/python/resource_management/libraries/functions/simulate_perf_cluster_alert_behaviour.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/HBASE/package/alerts/hbase_regionserver_process.py * (delete) ambari-server/src/main/resources/stacks/PERF/1.0/services/YARN/package/alerts/alert_nodemanagers_summary.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/SNOW/alerts.json * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HBASE/metainfo.xml * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/ZOOKEEPER/package/alerts/alert_zk_server_process.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/SNOW/metainfo.xml * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/ZOOKEEPER/configuration/zk-alert-config.xml * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/HAPPY/alerts.json * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/ZOOKEEPER/metainfo.xml * (delete) ambari-server/src/main/resources/stacks/PERF/1.0/services/HDFS/package/alerts/alert_ha_namenode_health.py > Perf: Simulate alerts for multiple Ambari Agents running on single Host > --- > > Key: AMBARI-18736 > URL: https://issues.apache.org/jira/browse/AMBARI-18
[jira] [Updated] (AMBARI-18978) Create Quick link profile data model and json parser
[ https://issues.apache.org/jira/browse/AMBARI-18978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-18978: --- Status: Patch Available (was: Open) > Create Quick link profile data model and json parser > > > Key: AMBARI-18978 > URL: https://issues.apache.org/jira/browse/AMBARI-18978 > Project: Ambari > Issue Type: Task >Affects Versions: 2.5.0 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári > Fix For: 2.5.0 > > Attachments: AMBARI-18978-quick-link-profile-data-model_trunk_v2.patch > > > Create the data model and JSON parser for quick link profiles. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18978) Create Quick link profile data model and json parser
[ https://issues.apache.org/jira/browse/AMBARI-18978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-18978: --- Attachment: AMBARI-18978-quick-link-profile-data-model_trunk_v2.patch Patch with the fix. > Create Quick link profile data model and json parser > > > Key: AMBARI-18978 > URL: https://issues.apache.org/jira/browse/AMBARI-18978 > Project: Ambari > Issue Type: Task >Affects Versions: 2.5.0 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári > Fix For: 2.5.0 > > Attachments: AMBARI-18978-quick-link-profile-data-model_trunk_v2.patch > > > Create the data model and JSON parser for quick link profiles. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18978) Create Quick link profile data model and json parser
[ https://issues.apache.org/jira/browse/AMBARI-18978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-18978: --- Fix Version/s: trunk > Create Quick link profile data model and json parser > > > Key: AMBARI-18978 > URL: https://issues.apache.org/jira/browse/AMBARI-18978 > Project: Ambari > Issue Type: Task >Affects Versions: 2.5.0 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-18978-quick-link-profile-data-model_trunk_v2.patch > > > Create the data model and JSON parser for quick link profiles. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-18713) use exclude list of mount device types on docker containers
[ https://issues.apache.org/jira/browse/AMBARI-18713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko resolved AMBARI-18713. - Resolution: Fixed Committed 3a34213..ab6d552 branch-2.5 -> branch-2.5 9b21f30..bb8be5b trunk -> trunk > use exclude list of mount device types on docker containers > --- > > Key: AMBARI-18713 > URL: https://issues.apache.org/jira/browse/AMBARI-18713 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Dmytro Grinenko >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18713-2.5.patch, AMBARI-18713-2.5.patch.1, > AMBARI-18713.patch, AMBARI-18713.patch.1, AMBARI-18713.patch.2 > > > * Remove logic from UI that picks a single host to represent the entire > cluster > * Have each host report their mount devices and how much space is available > in each one, so Ambari can store this in the DB (this will affect new > installs only or newly registered hosts) > * Move logic to Stack Advisor > * Use exclude list -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18780) Fix livy configuration upgrade from HDP 2.5 to HDP 2.6
[ https://issues.apache.org/jira/browse/AMBARI-18780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-18780: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.5 > Fix livy configuration upgrade from HDP 2.5 to HDP 2.6 > -- > > Key: AMBARI-18780 > URL: https://issues.apache.org/jira/browse/AMBARI-18780 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Jeff Zhang >Assignee: Jeff Zhang > Fix For: 2.5.0 > > Attachments: AMBARI-18780-1.patch > > > Follow up work for upgrade fix of AMBARI-18758 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18736) Perf: Simulate alerts for multiple Ambari Agents running on single Host
[ https://issues.apache.org/jira/browse/AMBARI-18736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15712317#comment-15712317 ] Hudson commented on AMBARI-18736: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6127 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6127/]) AMBARI-18736. Perf: Simulate alerts for multiple Ambari Agents running (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ef63373ef2fa886d819589b8500e4c1c81390a87]) * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/SNOW/metainfo.xml * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/HDFS/configuration/hdfs-alert-config.xml * (add) ambari-common/src/main/python/resource_management/libraries/functions/simulate_perf_cluster_alert_behaviour.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HBASE/alerts.json * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/HBASE/package/alerts/hbase_regionserver_process.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/SNOW/package/alerts/alert_snow_process.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/HAPPY/package/alerts/alert_happy_process.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/HAPPY/configuration/happy-alert-config.xml * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HDFS/package/alerts/alert_upgrade_finalized.py * (delete) ambari-server/src/main/resources/stacks/PERF/1.0/services/YARN/package/alerts/alert_nodemanagers_summary.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/SNOW/configuration/snow-alert-config.xml * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/YARN/package/alerts/alert_resourcemanager_process.py * (delete) ambari-server/src/main/resources/stacks/PERF/1.0/services/HDFS/package/alerts/alert_metrics_deviation.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/YARN/package/alerts/alert_history_process.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HDFS/package/alerts/alert_checkpoint_time.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HDFS/package/alerts/alert_datanode_unmounted_data_dir.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/SLEEPY/alerts.json * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/HDFS/package/alerts/alert_snamenode_process.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/ZOOKEEPER/package/alerts/alert_zk_server_process.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HAPPY/metainfo.xml * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/YARN/package/alerts/alert_timeline_process.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/SLEEPY/metainfo.xml * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/ZOOKEEPER/configuration/zk-alert-config.xml * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/HBASE/configuration/hbase-alert-config.xml * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/HDFS/package/alerts/alert_nfs_gateway_process.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/SLEEPY/configuration/sleepy-alert-config.xml * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HDFS/alerts.json * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/ZOOKEEPER/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/YARN/metainfo.xml * (delete) ambari-server/src/main/resources/stacks/PERF/1.0/services/HDFS/package/alerts/alert_ha_namenode_health.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/ZOOKEEPER/alerts.json * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/YARN/configuration/yarn-alert-config.xml * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/YARN/alerts.json * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/YARN/package/alerts/alert_nodemanager_health.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/HAPPY/alerts.json * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HBASE/metainfo.xml * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/HBASE/package/alerts/hbase_master_process.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HDFS/metainfo.xml * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/SLEEPY/package/alerts/alert_sleepy_process.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/SNOW/alerts.json > Perf: Simulate alerts for multiple Ambari Agents running on single Host > --- > > Key: AMBARI-18736 > URL: https://issues.apache.org/jira/browse/AMB
[jira] [Commented] (AMBARI-19047) Select Versions page: 'Remove' tooltip does not disappear
[ https://issues.apache.org/jira/browse/AMBARI-19047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15712315#comment-15712315 ] Hudson commented on AMBARI-19047: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6127 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6127/]) AMBARI-19047. Select Versions page: 'Remove' tooltip does not disappear (onechiporenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9a72a6009c922f26ee47f2841a5ce89089a24883]) * (edit) ambari-web/app/views/wizard/step1_view.js * (edit) ambari-web/app/templates/wizard/step1.hbs > Select Versions page: 'Remove' tooltip does not disappear > - > > Key: AMBARI-19047 > URL: https://issues.apache.org/jira/browse/AMBARI-19047 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-19047.patch, Screen Shot 2016-11-29 at 3.12.07 > PM.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19048) Delete service action should show the config recommendation popup
[ https://issues.apache.org/jira/browse/AMBARI-19048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15712316#comment-15712316 ] Hudson commented on AMBARI-19048: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6127 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6127/]) AMBARI-19048 Delete service action should show the config recommendation (ababiichuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9b21f30b5f081d7b313f9070ae125afc84db7647]) * (add) ambari-web/app/templates/main/service/info/delete_service_warning_popup.hbs * (edit) ambari-web/app/controllers/main/service/info/configs.js * (edit) ambari-web/app/controllers/main/service/item.js * (edit) ambari-web/app/mixins/main/service/groups_mapping.js * (edit) ambari-web/app/controllers/wizard/step7_controller.js * (edit) ambari-web/test/controllers/main/service/item_test.js > Delete service action should show the config recommendation popup > - > > Key: AMBARI-19048 > URL: https://issues.apache.org/jira/browse/AMBARI-19048 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 2.5.0 > > Attachments: AMBARI-19048.patch > > > When a service is deleted, it's related configuration are changed as per > stack advisor recommendation. > As scope of this ticket, ambari-web should show all the configuration that > will be changed in recommendation popup when a service is deleted. This popup > should be same as the one shown while doing service->config change and > clicking on save button. > Following similar flow as on service->config page, When user confirms > recommended changes, ambari-web should male API call for checked config > changes. > If no config will be changed on any service deletion action then in that case > recommendation popup should bot be shown -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19043) CAPACITY-SCHEDULER & PIG View not loading for Ambari-2.5.0
[ https://issues.apache.org/jira/browse/AMBARI-19043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15712319#comment-15712319 ] Hudson commented on AMBARI-19043: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6127 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6127/]) AMBARI-19043 : CAPACITY-SCHEDULER & PIG View not loading for (nitiraj.rathore: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7c07dd3595068b4e9a58db0fd2d6a8415898261c]) * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/app.js * (edit) contrib/views/pig/src/main/resources/ui/pig-web/app/app.js > CAPACITY-SCHEDULER & PIG View not loading for Ambari-2.5.0 > -- > > Key: AMBARI-19043 > URL: https://issues.apache.org/jira/browse/AMBARI-19043 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Blocker > Fix For: 2.5.0 > > Attachments: AMBARI-19043.branch-2.5.patch, Capacity Scheduler View > Not Loading.png, Pig View Not Loading.png > > > CAPACITY-SCHEDULER View not loading for Ambari-2.5.0 in the cluster: > http://172.27.29.71:8080/#/main/views/CAPACITY-SCHEDULER/1.0.0/NEW_INSTANCE > Facing error while loading pig view in live cluster: > http://172.27.23.128:8080/views/PIG/1.0.0/PIG/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19048) Delete service action should show the config recommendation popup
[
https://issues.apache.org/jira/browse/AMBARI-19048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15712268#comment-15712268
]
Hadoop QA commented on AMBARI-19048:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841285/AMBARI-19048.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/9484//console
This message is automatically generated.
> Delete service action should show the config recommendation popup
> -
>
> Key: AMBARI-19048
> URL: https://issues.apache.org/jira/browse/AMBARI-19048
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19048.patch
>
>
> When a service is deleted, it's related configuration are changed as per
> stack advisor recommendation.
> As scope of this ticket, ambari-web should show all the configuration that
> will be changed in recommendation popup when a service is deleted. This popup
> should be same as the one shown while doing service->config change and
> clicking on save button.
> Following similar flow as on service->config page, When user confirms
> recommended changes, ambari-web should male API call for checked config
> changes.
> If no config will be changed on any service deletion action then in that case
> recommendation popup should bot be shown
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18780) Fix livy configuration upgrade from HDP 2.5 to HDP 2.6
[ https://issues.apache.org/jira/browse/AMBARI-18780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15712412#comment-15712412 ] Hudson commented on AMBARI-18780: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6128 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6128/]) AMBARI-18780. Fix livy configuration upgrade from HDP 2.5 to HDP 2.6 (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6100be63867209de5dd5eaae6087aad850e25466]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml > Fix livy configuration upgrade from HDP 2.5 to HDP 2.6 > -- > > Key: AMBARI-18780 > URL: https://issues.apache.org/jira/browse/AMBARI-18780 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Jeff Zhang >Assignee: Jeff Zhang > Fix For: 2.5.0 > > Attachments: AMBARI-18780-1.patch > > > Follow up work for upgrade fix of AMBARI-18758 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18713) use exclude list of mount device types on docker containers
[ https://issues.apache.org/jira/browse/AMBARI-18713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15712411#comment-15712411 ] Hudson commented on AMBARI-18713: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6128 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6128/]) AMBARI-18713. use exclude list of mount device types on docker (dlysnichenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=bb8be5ba6a950b64382fb1a44f04c1dbf24db382]) * (edit) ambari-server/src/main/resources/stacks/stack_advisor.py * (edit) ambari-web/test/utils/configs/config_initializer_test.js * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py * (edit) ambari-web/app/utils/configs/config_initializer.js * (add) ambari-server/src/test/python/stacks/test_stack_adviser.py * (edit) ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py * (edit) ambari-server/src/test/python/stacks/2.1/common/test_stack_advisor.py * (edit) ambari-web/test/utils/ajax/ajax_test.js * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.1/services/stack_advisor.py * (delete) ambari-web/app/utils/configs/mount_points_based_initializer_mixin.js * (edit) ambari-server/src/main/resources/scripts/stack_advisor.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/configuration/cluster-env.xml * (edit) ambari-server/src/test/python/stacks/2.0.6/common/test_stack_advisor.py * (edit) ambari-web/app/mixins.js > use exclude list of mount device types on docker containers > --- > > Key: AMBARI-18713 > URL: https://issues.apache.org/jira/browse/AMBARI-18713 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Dmytro Grinenko >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18713-2.5.patch, AMBARI-18713-2.5.patch.1, > AMBARI-18713.patch, AMBARI-18713.patch.1, AMBARI-18713.patch.2 > > > * Remove logic from UI that picks a single host to represent the entire > cluster > * Have each host report their mount devices and how much space is available > in each one, so Ambari can store this in the DB (this will affect new > installs only or newly registered hosts) > * Move logic to Stack Advisor > * Use exclude list -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19051) Stage is dometimes marked as failed on command reschedule.
Myroslav Papirkovskyi created AMBARI-19051: -- Summary: Stage is dometimes marked as failed on command reschedule. Key: AMBARI-19051 URL: https://issues.apache.org/jira/browse/AMBARI-19051 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0 Reporter: Myroslav Papirkovskyi Assignee: Myroslav Papirkovskyi Priority: Critical Fix For: 2.5.0 Sometimes when server processes command timeout and reschedules task for agent execution, fail report is received from agent (after cancel command processing) and whole stage/request gets marked as failed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19051) Stage is sometimes marked as failed on command reschedule.
[ https://issues.apache.org/jira/browse/AMBARI-19051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myroslav Papirkovskyi updated AMBARI-19051: --- Summary: Stage is sometimes marked as failed on command reschedule. (was: Stage is dometimes marked as failed on command reschedule.) > Stage is sometimes marked as failed on command reschedule. > -- > > Key: AMBARI-19051 > URL: https://issues.apache.org/jira/browse/AMBARI-19051 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi >Priority: Critical > Fix For: 2.5.0 > > > Sometimes when server processes command timeout and reschedules task for > agent execution, fail report is received from agent (after cancel command > processing) and whole stage/request gets marked as failed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19051) Stage is sometimes marked as failed on command reschedule.
[ https://issues.apache.org/jira/browse/AMBARI-19051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myroslav Papirkovskyi updated AMBARI-19051: --- Attachment: AMBARI-19051.patch > Stage is sometimes marked as failed on command reschedule. > -- > > Key: AMBARI-19051 > URL: https://issues.apache.org/jira/browse/AMBARI-19051 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19051.patch > > > Sometimes when server processes command timeout and reschedules task for > agent execution, fail report is received from agent (after cancel command > processing) and whole stage/request gets marked as failed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18978) Create Quick link profile data model and json parser
[
https://issues.apache.org/jira/browse/AMBARI-18978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15712492#comment-15712492
]
Hadoop QA commented on AMBARI-18978:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841297/AMBARI-18978-quick-link-profile-data-model_trunk_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 4 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.state.ServicePropertiesTest
org.apache.ambari.server.controller.metrics.JMXPropertyProviderTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9485//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9485//console
This message is automatically generated.
> Create Quick link profile data model and json parser
>
>
> Key: AMBARI-18978
> URL: https://issues.apache.org/jira/browse/AMBARI-18978
> Project: Ambari
> Issue Type: Task
>Affects Versions: 2.5.0
>Reporter: Balázs Bence Sári
>Assignee: Balázs Bence Sári
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-18978-quick-link-profile-data-model_trunk_v2.patch
>
>
> Create the data model and JSON parser for quick link profiles.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19052) Re-arrange "Role Based Access Control" info table
Aleksandr Kovalenko created AMBARI-19052: Summary: Re-arrange "Role Based Access Control" info table Key: AMBARI-19052 URL: https://issues.apache.org/jira/browse/AMBARI-19052 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.5.0 The RBAC info table should be organized so that the permissions flow down like below: ||Permissions||Role 1||Role 2||Role 3|| |Perm 1|(/)|(/)|(/)| |Perm 2| |(/)|(/)| |Perm 3| | |(/)| We have areas in the table where it doesn't look like that, for example "View service operational logs" should be right after "Manage configuration groups". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19052) Re-arrange "Role Based Access Control" info table
[ https://issues.apache.org/jira/browse/AMBARI-19052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-19052: - Attachment: AMBARI-19052.patch > Re-arrange "Role Based Access Control" info table > - > > Key: AMBARI-19052 > URL: https://issues.apache.org/jira/browse/AMBARI-19052 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.5.0 > > Attachments: AMBARI-19052.patch > > > The RBAC info table should be organized so that the permissions flow down > like below: > ||Permissions||Role 1||Role 2||Role 3|| > |Perm 1|(/)|(/)|(/)| > |Perm 2| |(/)|(/)| > |Perm 3| | |(/)| > We have areas in the table where it doesn't look like that, for example "View > service operational logs" should be right after "Manage configuration groups". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19052) Re-arrange "Role Based Access Control" info table
[ https://issues.apache.org/jira/browse/AMBARI-19052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-19052: - Status: Patch Available (was: Open) > Re-arrange "Role Based Access Control" info table > - > > Key: AMBARI-19052 > URL: https://issues.apache.org/jira/browse/AMBARI-19052 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.5.0 > > Attachments: AMBARI-19052.patch > > > The RBAC info table should be organized so that the permissions flow down > like below: > ||Permissions||Role 1||Role 2||Role 3|| > |Perm 1|(/)|(/)|(/)| > |Perm 2| |(/)|(/)| > |Perm 3| | |(/)| > We have areas in the table where it doesn't look like that, for example "View > service operational logs" should be right after "Manage configuration groups". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18929) Yarn service check fails when either resource manager is down in HA enabled cluster
[ https://issues.apache.org/jira/browse/AMBARI-18929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18929: - Fix Version/s: 2.5.0 > Yarn service check fails when either resource manager is down in HA enabled > cluster > --- > > Key: AMBARI-18929 > URL: https://issues.apache.org/jira/browse/AMBARI-18929 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Weiwei Yang >Assignee: Weiwei Yang > Fix For: 2.5.0 > > Attachments: AMBARI-18929_trunk.02.patch, AMBARI-18929_trunk.patch > > > When HA is enabled, yarn service_check.py fails if one of RM is down, even > the other one is active. This gives user the wrong impression the yarn > cluster is not healthy. Instead, service check should pass, or at least pass > with warning that lets user know there is one RM down. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19052) Re-arrange "Role Based Access Control" info table
[
https://issues.apache.org/jira/browse/AMBARI-19052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15712577#comment-15712577
]
Hadoop QA commented on AMBARI-19052:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841318/AMBARI-19052.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-admin.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9486//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9486//console
This message is automatically generated.
> Re-arrange "Role Based Access Control" info table
> -
>
> Key: AMBARI-19052
> URL: https://issues.apache.org/jira/browse/AMBARI-19052
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.5.0
>
> Attachments: AMBARI-19052.patch
>
>
> The RBAC info table should be organized so that the permissions flow down
> like below:
> ||Permissions||Role 1||Role 2||Role 3||
> |Perm 1|(/)|(/)|(/)|
> |Perm 2| |(/)|(/)|
> |Perm 3| | |(/)|
> We have areas in the table where it doesn't look like that, for example "View
> service operational logs" should be right after "Manage configuration groups".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18929) Yarn service check fails when either resource manager is down in HA enabled cluster
[ https://issues.apache.org/jira/browse/AMBARI-18929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18929: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to trunk, commit 88e0c29e0617f05c0ecb72a75e74b2bb3def6bac branch-2.5, commit d6877d721b83220f4b43736d9a80e2f3be67ff7f > Yarn service check fails when either resource manager is down in HA enabled > cluster > --- > > Key: AMBARI-18929 > URL: https://issues.apache.org/jira/browse/AMBARI-18929 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Weiwei Yang >Assignee: Weiwei Yang > Fix For: 2.5.0 > > Attachments: AMBARI-18929_trunk.02.patch, AMBARI-18929_trunk.patch > > > When HA is enabled, yarn service_check.py fails if one of RM is down, even > the other one is active. This gives user the wrong impression the yarn > cluster is not healthy. Instead, service check should pass, or at least pass > with warning that lets user know there is one RM down. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19006) EU to message users to start YARN queues if work preserving recovery is disabled
[
https://issues.apache.org/jira/browse/AMBARI-19006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-19006:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to trunk, commit 63938e09ca9e79ee541dd51104964322192e293f
branch-2.5, commit 9976fb741273cbeb05b4d4d81f0d1120870ed6dd
> EU to message users to start YARN queues if work preserving recovery is
> disabled
>
>
> Key: AMBARI-19006
> URL: https://issues.apache.org/jira/browse/AMBARI-19006
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
> Attachments: AMBARI-19006.patch
>
>
> Today, the Express Upgrade packs message users to stop YARN queues if they do
> not have work preserving recovery enabled.
> However, there's no message reminding users to enable it again.
> E.g.,
> {code}
>
> false
> true
>
>
> property="yarn.resourcemanager.work-preserving-recovery.enabled" value="true"
> comparison="not-equal"/>
>
> Before continuing, please start all YARN queues if you
> stopped them in a previous step.
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19045) Remove unnecessary Log Feeder Date Mapper tests
[ https://issues.apache.org/jira/browse/AMBARI-19045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15712638#comment-15712638 ] Miklos Gergely commented on AMBARI-19045: - [~smohanty] Should I add this patch to branch-2.4 too? Without this patch the test that I've removed would fail in December (the test uses the current date, and fails in December) on this branch too. > Remove unnecessary Log Feeder Date Mapper tests > --- > > Key: AMBARI-19045 > URL: https://issues.apache.org/jira/browse/AMBARI-19045 > Project: Ambari > Issue Type: Bug >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Attachments: AMBARI-19045.patch > > > Some unit tests for Date Mapper in the Log Feeder > (testMapperDate_patternWithoutYear_previousYearLog, > testMapperDate_patternWithoutYear_currentYearLog) make no sense, but fail in > December. Remove these tests. > Options -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18929) Yarn service check fails when either resource manager is down in HA enabled cluster
[ https://issues.apache.org/jira/browse/AMBARI-18929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15712654#comment-15712654 ] Hudson commented on AMBARI-18929: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6129 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6129/]) AMBARI-18929. Yarn service check fails when either resource manager is (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=88e0c29e0617f05c0ecb72a75e74b2bb3def6bac]) * (edit) ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py * (edit) ambari-server/src/test/python/stacks/2.0.6/YARN/test_yarn_service_check.py > Yarn service check fails when either resource manager is down in HA enabled > cluster > --- > > Key: AMBARI-18929 > URL: https://issues.apache.org/jira/browse/AMBARI-18929 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Weiwei Yang >Assignee: Weiwei Yang > Fix For: 2.5.0 > > Attachments: AMBARI-18929_trunk.02.patch, AMBARI-18929_trunk.patch > > > When HA is enabled, yarn service_check.py fails if one of RM is down, even > the other one is active. This gives user the wrong impression the yarn > cluster is not healthy. Instead, service check should pass, or at least pass > with warning that lets user know there is one RM down. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19052) Re-arrange "Role Based Access Control" info table
[ https://issues.apache.org/jira/browse/AMBARI-19052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15712673#comment-15712673 ] Aleksandr Kovalenko commented on AMBARI-19052: -- committed to trunk and branch-2.5 > Re-arrange "Role Based Access Control" info table > - > > Key: AMBARI-19052 > URL: https://issues.apache.org/jira/browse/AMBARI-19052 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.5.0 > > Attachments: AMBARI-19052.patch > > > The RBAC info table should be organized so that the permissions flow down > like below: > ||Permissions||Role 1||Role 2||Role 3|| > |Perm 1|(/)|(/)|(/)| > |Perm 2| |(/)|(/)| > |Perm 3| | |(/)| > We have areas in the table where it doesn't look like that, for example "View > service operational logs" should be right after "Manage configuration groups". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19052) Re-arrange "Role Based Access Control" info table
[ https://issues.apache.org/jira/browse/AMBARI-19052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15712672#comment-15712672 ] Aleksandr Kovalenko commented on AMBARI-19052: -- Patch consist of changes for ambari-admin, checking these unit tests are not included to Hadoop QA job. > Re-arrange "Role Based Access Control" info table > - > > Key: AMBARI-19052 > URL: https://issues.apache.org/jira/browse/AMBARI-19052 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.5.0 > > Attachments: AMBARI-19052.patch > > > The RBAC info table should be organized so that the permissions flow down > like below: > ||Permissions||Role 1||Role 2||Role 3|| > |Perm 1|(/)|(/)|(/)| > |Perm 2| |(/)|(/)| > |Perm 3| | |(/)| > We have areas in the table where it doesn't look like that, for example "View > service operational logs" should be right after "Manage configuration groups". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19052) Re-arrange "Role Based Access Control" info table
[
https://issues.apache.org/jira/browse/AMBARI-19052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15712689#comment-15712689
]
Hadoop QA commented on AMBARI-19052:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841318/AMBARI-19052.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/9487//console
This message is automatically generated.
> Re-arrange "Role Based Access Control" info table
> -
>
> Key: AMBARI-19052
> URL: https://issues.apache.org/jira/browse/AMBARI-19052
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.5.0
>
> Attachments: AMBARI-19052.patch
>
>
> The RBAC info table should be organized so that the permissions flow down
> like below:
> ||Permissions||Role 1||Role 2||Role 3||
> |Perm 1|(/)|(/)|(/)|
> |Perm 2| |(/)|(/)|
> |Perm 3| | |(/)|
> We have areas in the table where it doesn't look like that, for example "View
> service operational logs" should be right after "Manage configuration groups".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19053) RU: wrong version exposed when Downgrade is going
Nate Cole created AMBARI-19053:
--
Summary: RU: wrong version exposed when Downgrade is going
Key: AMBARI-19053
URL: https://issues.apache.org/jira/browse/AMBARI-19053
Project: Ambari
Issue Type: Bug
Components: ambari-server
Reporter: Nate Cole
Assignee: Nate Cole
Priority: Critical
Fix For: 3.0.0
Currently on downgrade server returns from and to version same:
{code:java}
{
"href" :
"http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/upgrades/7?fields=Upgrade/*&_=1479742056069";,
"Upgrade" : {
"cluster_name" : "c1",
"create_time" : 1479741414972,
"direction" : "DOWNGRADE",
"downgrade_allowed" : true,
"end_time" : -1,
"exclusive" : false,
"from_version" : "2.3.6.0-3796",
"pack" : "nonrolling-upgrade-2.4",
"progress_percent" : 56.664,
"request_context" : "Downgrading to 2.3.6.0-3796",
"request_id" : 7,
"request_status" : "HOLDING_TIMEDOUT",
"skip_failures" : false,
"skip_service_check_failures" : false,
"start_time" : 1479741415378,
"suspended" : false,
"to_version" : "2.3.6.0-3796",
"type" : "INTERNAL_REQUEST",
"upgrade_type" : "NON_ROLLING"
}
}
{code}
However they should be:
||Direction||from_version||to_version||
|UPGRADE|2.5.0.0|2.5.1.0|
|DOWNGRADE|2.5.1.0|2.5.0.0|
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18780) Fix livy configuration upgrade from HDP 2.5 to HDP 2.6
[ https://issues.apache.org/jira/browse/AMBARI-18780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15712890#comment-15712890 ] Hudson commented on AMBARI-18780: - ABORTED: Integrated in Jenkins build Ambari-branch-2.5 #432 (See [https://builds.apache.org/job/Ambari-branch-2.5/432/]) AMBARI-18780. Fix livy configuration upgrade from HDP 2.5 to HDP 2.6 (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=00c832c472f745c6ed75e82d69dff6b119aef7b5]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml > Fix livy configuration upgrade from HDP 2.5 to HDP 2.6 > -- > > Key: AMBARI-18780 > URL: https://issues.apache.org/jira/browse/AMBARI-18780 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Jeff Zhang >Assignee: Jeff Zhang > Fix For: 2.5.0 > > Attachments: AMBARI-18780-1.patch > > > Follow up work for upgrade fix of AMBARI-18758 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18713) use exclude list of mount device types on docker containers
[ https://issues.apache.org/jira/browse/AMBARI-18713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15712889#comment-15712889 ] Hudson commented on AMBARI-18713: - ABORTED: Integrated in Jenkins build Ambari-branch-2.5 #432 (See [https://builds.apache.org/job/Ambari-branch-2.5/432/]) AMBARI-18713. use exclude list of mount device types on docker (dlysnichenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ab6d552340bbe601209509556c5dead8ba7d14ae]) * (add) ambari-server/src/test/python/stacks/test_stack_adviser.py * (edit) ambari-web/test/utils/configs/config_initializer_test.js * (edit) ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py * (edit) ambari-web/app/utils/configs/config_initializer.js * (edit) ambari-server/src/main/resources/stacks/HDP/2.1/services/stack_advisor.py * (edit) ambari-web/test/utils/ajax/ajax_test.js * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py * (delete) ambari-web/app/utils/configs/mount_points_based_initializer_mixin.js * (edit) ambari-server/src/main/resources/stacks/stack_advisor.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py * (edit) ambari-server/src/test/python/stacks/2.0.6/common/test_stack_advisor.py * (edit) ambari-web/app/mixins.js * (edit) ambari-server/src/main/resources/scripts/stack_advisor.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/configuration/cluster-env.xml * (edit) ambari-server/src/test/python/stacks/2.1/common/test_stack_advisor.py > use exclude list of mount device types on docker containers > --- > > Key: AMBARI-18713 > URL: https://issues.apache.org/jira/browse/AMBARI-18713 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Dmytro Grinenko >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18713-2.5.patch, AMBARI-18713-2.5.patch.1, > AMBARI-18713.patch, AMBARI-18713.patch.1, AMBARI-18713.patch.2 > > > * Remove logic from UI that picks a single host to represent the entire > cluster > * Have each host report their mount devices and how much space is available > in each one, so Ambari can store this in the DB (this will affect new > installs only or newly registered hosts) > * Move logic to Stack Advisor > * Use exclude list -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19041) Choose services page select/deselect all services not working while adding smartsense to the cluster
[ https://issues.apache.org/jira/browse/AMBARI-19041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Rathod updated AMBARI-19041: -- Summary: Choose services page select/deselect all services not working while adding smartsense to the cluster (was: User should not be able to delete Smartsense(from UI or API) as it is mandatory) > Choose services page select/deselect all services not working while adding > smartsense to the cluster > > > Key: AMBARI-19041 > URL: https://issues.apache.org/jira/browse/AMBARI-19041 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Rathod > Fix For: 2.5.0 > > > User should not be able to delete Smartsense from UI or API because it is > mandatory in ambari 250. > Also, after deleting Smartsense, Choose services page on add service wizard > is broken(Select/Deselect All button does not work as designed). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19041) Choose services page select/deselect all services not working while adding smartsense to the cluster
[ https://issues.apache.org/jira/browse/AMBARI-19041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Rathod updated AMBARI-19041: -- Description: Smartsense is mandatory install. But UI and API allows user to delete it. After deleting smartsense, on adding smartsense, on choose services page, select/deselect all button does not work as expected. was: User should not be able to delete Smartsense from UI or API because it is mandatory in ambari 250. Also, after deleting Smartsense, Choose services page on add service wizard is broken(Select/Deselect All button does not work as designed). > Choose services page select/deselect all services not working while adding > smartsense to the cluster > > > Key: AMBARI-19041 > URL: https://issues.apache.org/jira/browse/AMBARI-19041 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Rathod > Fix For: 2.5.0 > > > Smartsense is mandatory install. But UI and API allows user to delete it. > After deleting smartsense, on adding smartsense, on choose services page, > select/deselect all button does not work as expected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18929) Yarn service check fails when either resource manager is down in HA enabled cluster
[ https://issues.apache.org/jira/browse/AMBARI-18929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15712973#comment-15712973 ] Hudson commented on AMBARI-18929: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #433 (See [https://builds.apache.org/job/Ambari-branch-2.5/433/]) AMBARI-18929. Yarn service check fails when either resource manager is (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d6877d721b83220f4b43736d9a80e2f3be67ff7f]) * (edit) ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py * (edit) ambari-server/src/test/python/stacks/2.0.6/YARN/test_yarn_service_check.py > Yarn service check fails when either resource manager is down in HA enabled > cluster > --- > > Key: AMBARI-18929 > URL: https://issues.apache.org/jira/browse/AMBARI-18929 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Weiwei Yang >Assignee: Weiwei Yang > Fix For: 2.5.0 > > Attachments: AMBARI-18929_trunk.02.patch, AMBARI-18929_trunk.patch > > > When HA is enabled, yarn service_check.py fails if one of RM is down, even > the other one is active. This gives user the wrong impression the yarn > cluster is not healthy. Instead, service check should pass, or at least pass > with warning that lets user know there is one RM down. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19006) EU to message users to start YARN queues if work preserving recovery is disabled
[
https://issues.apache.org/jira/browse/AMBARI-19006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15712971#comment-15712971
]
Hudson commented on AMBARI-19006:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #433 (See
[https://builds.apache.org/job/Ambari-branch-2.5/433/])
AMBARI-19006. EU to message users to start YARN queues if work (afernandez:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9976fb741273cbeb05b4d4d81f0d1120870ed6dd])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.3.xml
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ConfigurationCondition.java
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.4.xml
* (edit) ambari-server/src/main/resources/upgrade-pack.xsd
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.5.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.5.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.6.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.5.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/nonrolling-upgrade-2.6.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.4.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.6.xml
> EU to message users to start YARN queues if work preserving recovery is
> disabled
>
>
> Key: AMBARI-19006
> URL: https://issues.apache.org/jira/browse/AMBARI-19006
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
> Attachments: AMBARI-19006.patch
>
>
> Today, the Express Upgrade packs message users to stop YARN queues if they do
> not have work preserving recovery enabled.
> However, there's no message reminding users to enable it again.
> E.g.,
> {code}
>
> false
> true
>
>
> property="yarn.resourcemanager.work-preserving-recovery.enabled" value="true"
> comparison="not-equal"/>
>
> Before continuing, please start all YARN queues if you
> stopped them in a previous step.
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19052) Re-arrange "Role Based Access Control" info table
[ https://issues.apache.org/jira/browse/AMBARI-19052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15712972#comment-15712972 ] Hudson commented on AMBARI-19052: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #433 (See [https://builds.apache.org/job/Ambari-branch-2.5/433/]) AMBARI-19052. Re-arrange "Role Based Access Control" info table (akovalenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ab3d72914254b9ee13708cb8a5987d0a2c4459a9]) * (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/modals/RoleDetailsModal.html * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/RoleDetailsModal.js * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/Cluster.js > Re-arrange "Role Based Access Control" info table > - > > Key: AMBARI-19052 > URL: https://issues.apache.org/jira/browse/AMBARI-19052 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.5.0 > > Attachments: AMBARI-19052.patch > > > The RBAC info table should be organized so that the permissions flow down > like below: > ||Permissions||Role 1||Role 2||Role 3|| > |Perm 1|(/)|(/)|(/)| > |Perm 2| |(/)|(/)| > |Perm 3| | |(/)| > We have areas in the table where it doesn't look like that, for example "View > service operational logs" should be right after "Manage configuration groups". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19032) HDFS Metric alerts turns to UNKNOWN state with error "'NoneType' object has no attribute 'split'"
[ https://issues.apache.org/jira/browse/AMBARI-19032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-19032: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.5 > HDFS Metric alerts turns to UNKNOWN state with error "'NoneType' object has > no attribute 'split'" > - > > Key: AMBARI-19032 > URL: https://issues.apache.org/jira/browse/AMBARI-19032 > Project: Ambari > Issue Type: Bug > Components: alerts, ambari-metrics >Affects Versions: 2.5.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: 2.5.0 > > Attachments: AMBARI-19032_1.patch, AMBARI-19032_2.patch > > > HDFS Metric alerts turns to UNKNOWN state with error "'NoneType' object has > no attribute 'split'". > STR: > Update the alert definition interval to 1 min, and thresholds to have minimum > values to trigger the Alert. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19054) Grafana failed to start at deployment
Aravindan Vijayan created AMBARI-19054:
--
Summary: Grafana failed to start at deployment
Key: AMBARI-19054
URL: https://issues.apache.org/jira/browse/AMBARI-19054
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Affects Versions: 2.5.0
Reporter: Aravindan Vijayan
Assignee: Aravindan Vijayan
Priority: Blocker
Fix For: 2.5.0
Grafana failed to start at deployment. No retries were given, but the live
cluster shows it is up
{noformat}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
line 77, in
AmsGrafana().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 282, in execute
method(env)
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
line 49, in start
not_if = params.grafana_process_exists_cmd,
File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
line 155, 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
'/usr/sbin/ambari-metrics-grafana start' returned 1. Hortonworks
#
This is MOTD message, added for testing in qe infra
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19054) Grafana failed to start at deployment
[
https://issues.apache.org/jira/browse/AMBARI-19054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-19054:
---
Attachment: AMBARI-19054.patch
> Grafana failed to start at deployment
> -
>
> Key: AMBARI-19054
> URL: https://issues.apache.org/jira/browse/AMBARI-19054
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19054.patch
>
>
> Grafana failed to start at deployment. No retries were given, but the live
> cluster shows it is up
> {noformat}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 77, in
> AmsGrafana().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 282, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 49, in start
> not_if = params.grafana_process_exists_cmd,
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, 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
> '/usr/sbin/ambari-metrics-grafana start' returned 1. Hortonworks
> #
> This is MOTD message, added for testing in qe infra
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19054) Grafana failed to start at deployment
[
https://issues.apache.org/jira/browse/AMBARI-19054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-19054:
---
Status: Patch Available (was: Open)
> Grafana failed to start at deployment
> -
>
> Key: AMBARI-19054
> URL: https://issues.apache.org/jira/browse/AMBARI-19054
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19054.patch
>
>
> Grafana failed to start at deployment. No retries were given, but the live
> cluster shows it is up
> {noformat}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 77, in
> AmsGrafana().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 282, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 49, in start
> not_if = params.grafana_process_exists_cmd,
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, 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
> '/usr/sbin/ambari-metrics-grafana start' returned 1. Hortonworks
> #
> This is MOTD message, added for testing in qe infra
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19055) Removing Tasks From host_role_command Causes Upgrades To Show As PENDING
Jonathan Hurley created AMBARI-19055:
Summary: Removing Tasks From host_role_command Causes Upgrades To
Show As PENDING
Key: AMBARI-19055
URL: https://issues.apache.org/jira/browse/AMBARI-19055
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.2.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Priority: Critical
Fix For: 2.5.0
It may be necessary to remove entries from the {{host_role_command}} table if
the size of the table has grown excessively large in order to reduce the query
times for "IN_PROGRESS" requests.
However, if you remove all tasks for an upgrade, but you leave the stages,
request, and upgrade items, the upgrade will appear as though it is now
{{PENDING}}.
{noformat:title=Before Removal}
{
"href": "http://localhost:8080/api/v1/clusters/c1/upgrades/12";,
"Upgrade": {
"cluster_name": "c1",
"create_time": 1480517560897,
"direction": "UPGRADE",
"downgrade_allowed": true,
"end_time": 1480517643350,
"exclusive": false,
"from_version": "2.5.0.0-1237",
"pack": "nonrolling-upgrade-2.5",
"progress_percent": 0,
"request_context": "Upgrading to 2.5.2.0-67",
"request_id": 12,
"request_status": "COMPLETED",
"skip_failures": false,
"skip_service_check_failures": false,
"start_time": 1480517560950,
"suspended": false,
"to_version": "2.5.2.0-67",
"type": "INTERNAL_REQUEST",
"upgrade_type": "NON_ROLLING"
},
"upgrade_groups": [
...
{noformat}
{noformat:title=After Removal}
{
"href": "http://localhost:8080/api/v1/clusters/c1/upgrades/12";,
"Upgrade": {
"cluster_name": "c1",
"create_time": 1480517560897,
"direction": "UPGRADE",
"downgrade_allowed": true,
"end_time": 1480517643350,
"exclusive": false,
"from_version": "2.5.0.0-1237",
"pack": "nonrolling-upgrade-2.5",
"progress_percent": 0,
"request_context": "Upgrading to 2.5.2.0-67",
"request_id": 12,
"request_status": "PENDING",
"skip_failures": false,
"skip_service_check_failures": false,
"start_time": 1480517560950,
"suspended": false,
"to_version": "2.5.2.0-67",
"type": "INTERNAL_REQUEST",
"upgrade_type": "NON_ROLLING"
},
"upgrade_groups": [
...
{noformat}
The actual request is showing as {{COMPLETED}} correctly:
{noformat}
{
"href": "http://localhost:8080/api/v1/clusters/c1/requests/12";,
"Requests": {
"aborted_task_count": 0,
"cluster_name": "c1",
"completed_task_count": 0,
"create_time": 1480517560897,
"end_time": 1480517643350,
"exclusive": false,
"failed_task_count": 0,
"id": 12,
"inputs": null,
"operation_level": null,
"progress_percent": 100,
"queued_task_count": 0,
"request_context": "Upgrading to 2.5.2.0-67",
"request_schedule": null,
"request_status": "COMPLETED",
"resource_filters": [],
"start_time": 1480517560950,
"task_count": 0,
"timed_out_task_count": 0,
"type": "INTERNAL_REQUEST"
},
"tasks": [],
...
{noformat}
STR:
- Perform a simple upgrade of a ZK-only cluster
- Find out the ID of the upgrade request (say its 12)
- Remove tasks
{code}
DELETE FROM execution_command WHERE task_id IN (SELECT task_id FROM
host_role_command WHERE request_id = 12)
DELETE FROM host_role_command WHERE request_id = 12
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19055) Removing Tasks From host_role_command Causes Upgrades To Show As PENDING
[
https://issues.apache.org/jira/browse/AMBARI-19055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-19055:
-
Attachment: AMBARI-19055.patch
AMBARI-19055.patch
> Removing Tasks From host_role_command Causes Upgrades To Show As PENDING
>
>
> Key: AMBARI-19055
> URL: https://issues.apache.org/jira/browse/AMBARI-19055
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19055.patch
>
>
> It may be necessary to remove entries from the {{host_role_command}} table if
> the size of the table has grown excessively large in order to reduce the
> query times for "IN_PROGRESS" requests.
> However, if you remove all tasks for an upgrade, but you leave the stages,
> request, and upgrade items, the upgrade will appear as though it is now
> {{PENDING}}.
> {noformat:title=Before Removal}
> {
> "href": "http://localhost:8080/api/v1/clusters/c1/upgrades/12";,
> "Upgrade": {
> "cluster_name": "c1",
> "create_time": 1480517560897,
> "direction": "UPGRADE",
> "downgrade_allowed": true,
> "end_time": 1480517643350,
> "exclusive": false,
> "from_version": "2.5.0.0-1237",
> "pack": "nonrolling-upgrade-2.5",
> "progress_percent": 0,
> "request_context": "Upgrading to 2.5.2.0-67",
> "request_id": 12,
> "request_status": "COMPLETED",
> "skip_failures": false,
> "skip_service_check_failures": false,
> "start_time": 1480517560950,
> "suspended": false,
> "to_version": "2.5.2.0-67",
> "type": "INTERNAL_REQUEST",
> "upgrade_type": "NON_ROLLING"
> },
> "upgrade_groups": [
> ...
> {noformat}
> {noformat:title=After Removal}
> {
> "href": "http://localhost:8080/api/v1/clusters/c1/upgrades/12";,
> "Upgrade": {
> "cluster_name": "c1",
> "create_time": 1480517560897,
> "direction": "UPGRADE",
> "downgrade_allowed": true,
> "end_time": 1480517643350,
> "exclusive": false,
> "from_version": "2.5.0.0-1237",
> "pack": "nonrolling-upgrade-2.5",
> "progress_percent": 0,
> "request_context": "Upgrading to 2.5.2.0-67",
> "request_id": 12,
> "request_status": "PENDING",
> "skip_failures": false,
> "skip_service_check_failures": false,
> "start_time": 1480517560950,
> "suspended": false,
> "to_version": "2.5.2.0-67",
> "type": "INTERNAL_REQUEST",
> "upgrade_type": "NON_ROLLING"
> },
> "upgrade_groups": [
> ...
> {noformat}
> The actual request is showing as {{COMPLETED}} correctly:
> {noformat}
> {
> "href": "http://localhost:8080/api/v1/clusters/c1/requests/12";,
> "Requests": {
> "aborted_task_count": 0,
> "cluster_name": "c1",
> "completed_task_count": 0,
> "create_time": 1480517560897,
> "end_time": 1480517643350,
> "exclusive": false,
> "failed_task_count": 0,
> "id": 12,
> "inputs": null,
> "operation_level": null,
> "progress_percent": 100,
> "queued_task_count": 0,
> "request_context": "Upgrading to 2.5.2.0-67",
> "request_schedule": null,
> "request_status": "COMPLETED",
> "resource_filters": [],
> "start_time": 1480517560950,
> "task_count": 0,
> "timed_out_task_count": 0,
> "type": "INTERNAL_REQUEST"
> },
> "tasks": [],
> ...
> {noformat}
> STR:
> - Perform a simple upgrade of a ZK-only cluster
> - Find out the ID of the upgrade request (say its 12)
> - Remove tasks
> {code}
> DELETE FROM execution_command WHERE task_id IN (SELECT task_id FROM
> host_role_command WHERE request_id = 12)
> DELETE FROM host_role_command WHERE request_id = 12
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19055) Removing Tasks From host_role_command Causes Upgrades To Show As PENDING
[
https://issues.apache.org/jira/browse/AMBARI-19055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-19055:
-
Status: Patch Available (was: Open)
> Removing Tasks From host_role_command Causes Upgrades To Show As PENDING
>
>
> Key: AMBARI-19055
> URL: https://issues.apache.org/jira/browse/AMBARI-19055
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19055.patch
>
>
> It may be necessary to remove entries from the {{host_role_command}} table if
> the size of the table has grown excessively large in order to reduce the
> query times for "IN_PROGRESS" requests.
> However, if you remove all tasks for an upgrade, but you leave the stages,
> request, and upgrade items, the upgrade will appear as though it is now
> {{PENDING}}.
> {noformat:title=Before Removal}
> {
> "href": "http://localhost:8080/api/v1/clusters/c1/upgrades/12";,
> "Upgrade": {
> "cluster_name": "c1",
> "create_time": 1480517560897,
> "direction": "UPGRADE",
> "downgrade_allowed": true,
> "end_time": 1480517643350,
> "exclusive": false,
> "from_version": "2.5.0.0-1237",
> "pack": "nonrolling-upgrade-2.5",
> "progress_percent": 0,
> "request_context": "Upgrading to 2.5.2.0-67",
> "request_id": 12,
> "request_status": "COMPLETED",
> "skip_failures": false,
> "skip_service_check_failures": false,
> "start_time": 1480517560950,
> "suspended": false,
> "to_version": "2.5.2.0-67",
> "type": "INTERNAL_REQUEST",
> "upgrade_type": "NON_ROLLING"
> },
> "upgrade_groups": [
> ...
> {noformat}
> {noformat:title=After Removal}
> {
> "href": "http://localhost:8080/api/v1/clusters/c1/upgrades/12";,
> "Upgrade": {
> "cluster_name": "c1",
> "create_time": 1480517560897,
> "direction": "UPGRADE",
> "downgrade_allowed": true,
> "end_time": 1480517643350,
> "exclusive": false,
> "from_version": "2.5.0.0-1237",
> "pack": "nonrolling-upgrade-2.5",
> "progress_percent": 0,
> "request_context": "Upgrading to 2.5.2.0-67",
> "request_id": 12,
> "request_status": "PENDING",
> "skip_failures": false,
> "skip_service_check_failures": false,
> "start_time": 1480517560950,
> "suspended": false,
> "to_version": "2.5.2.0-67",
> "type": "INTERNAL_REQUEST",
> "upgrade_type": "NON_ROLLING"
> },
> "upgrade_groups": [
> ...
> {noformat}
> The actual request is showing as {{COMPLETED}} correctly:
> {noformat}
> {
> "href": "http://localhost:8080/api/v1/clusters/c1/requests/12";,
> "Requests": {
> "aborted_task_count": 0,
> "cluster_name": "c1",
> "completed_task_count": 0,
> "create_time": 1480517560897,
> "end_time": 1480517643350,
> "exclusive": false,
> "failed_task_count": 0,
> "id": 12,
> "inputs": null,
> "operation_level": null,
> "progress_percent": 100,
> "queued_task_count": 0,
> "request_context": "Upgrading to 2.5.2.0-67",
> "request_schedule": null,
> "request_status": "COMPLETED",
> "resource_filters": [],
> "start_time": 1480517560950,
> "task_count": 0,
> "timed_out_task_count": 0,
> "type": "INTERNAL_REQUEST"
> },
> "tasks": [],
> ...
> {noformat}
> STR:
> - Perform a simple upgrade of a ZK-only cluster
> - Find out the ID of the upgrade request (say its 12)
> - Remove tasks
> {code}
> DELETE FROM execution_command WHERE task_id IN (SELECT task_id FROM
> host_role_command WHERE request_id = 12)
> DELETE FROM host_role_command WHERE request_id = 12
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
