[jira] [Updated] (AMBARI-19872) HiveView2.0 : Upload CSV,JSON, XML to create table feature is missing in the new view
[ https://issues.apache.org/jira/browse/AMBARI-19872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-19872: --- Resolution: Fixed Status: Resolved (was: Patch Available) committed to branch-2.5 and trunk > HiveView2.0 : Upload CSV,JSON, XML to create table feature is missing in the > new view > - > > Key: AMBARI-19872 > URL: https://issues.apache.org/jira/browse/AMBARI-19872 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.0 > > Attachments: AMBARI-19872_branch-2.5.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19883) Hive2 view UDF tab is blank always
[ https://issues.apache.org/jira/browse/AMBARI-19883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-19883: - Attachment: (was: AMBARI-19883_trunk.patch) > Hive2 view UDF tab is blank always > -- > > Key: AMBARI-19883 > URL: https://issues.apache.org/jira/browse/AMBARI-19883 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19883_trunk-v3.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19883) Hive2 view UDF tab is blank always
[ https://issues.apache.org/jira/browse/AMBARI-19883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-19883: - Attachment: AMBARI-19883_trunk-v3.patch > Hive2 view UDF tab is blank always > -- > > Key: AMBARI-19883 > URL: https://issues.apache.org/jira/browse/AMBARI-19883 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19883_trunk-v3.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-19528) Ambari views : Adding new FileSystem support to views should work without code changes
[ https://issues.apache.org/jira/browse/AMBARI-19528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore resolved AMBARI-19528. Resolution: Fixed resolving as the related blocker bug was resolved. > Ambari views : Adding new FileSystem support to views should work without > code changes > -- > > Key: AMBARI-19528 > URL: https://issues.apache.org/jira/browse/AMBARI-19528 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.0 > > Attachments: AMBARI-19528_branch-2.5.patch > > > Right now when new file-system support has to be added to views, we need to > add code to include several more key value pairs into the conf to make it > work. > Usually these key value pairs are file-system class names, secret key and > access key. > following 2 changes are proposed. > 1. load the complete core-site and hdfs-site into the conf for creating > filesystem. This will load any secret key, access key configured. It will > also load any other necessary parameters. > 2. Create a new view setting's parameter per view which will have semi colon > separated key=value pairs that needs to be loaded into conf for connecting to > the filesystem. This will cover any extra parameters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-16650) Add Unit Tests for Ranger Kerberos support
[ https://issues.apache.org/jira/browse/AMBARI-16650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gautam Borad resolved AMBARI-16650. --- Resolution: Fixed Done as part of AMBARI-16756 > Add Unit Tests for Ranger Kerberos support > -- > > Key: AMBARI-16650 > URL: https://issues.apache.org/jira/browse/AMBARI-16650 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Gautam Borad >Assignee: Gautam Borad > Fix For: 2.5.0 > > > Need a comprehensive test coverage for the Kerberos support that was added > recently for Ranger component. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-16650) Add Unit Tests for Ranger Kerberos support
[ https://issues.apache.org/jira/browse/AMBARI-16650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15855418#comment-15855418 ] Gautam Borad commented on AMBARI-16650: --- [~u39kun] This is already handled as part of test changes done in AMBARI-16756. Will close this one. > Add Unit Tests for Ranger Kerberos support > -- > > Key: AMBARI-16650 > URL: https://issues.apache.org/jira/browse/AMBARI-16650 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Gautam Borad >Assignee: Gautam Borad > Fix For: 2.5.0 > > > Need a comprehensive test coverage for the Kerberos support that was added > recently for Ranger component. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19823) If by any case Migration Is hampered Then No message is shown in UI Hue-Ambari Migration view
[
https://issues.apache.org/jira/browse/AMBARI-19823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15855366#comment-15855366
]
Hadoop QA commented on AMBARI-19823:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12851195/AMBARI-19823.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
contrib/views/hueambarimigration.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10428//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10428//console
This message is automatically generated.
> If by any case Migration Is hampered Then No message is shown in UI
> Hue-Ambari Migration view
> -
>
> Key: AMBARI-19823
> URL: https://issues.apache.org/jira/browse/AMBARI-19823
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
> Fix For: trunk
>
> Attachments: AMBARI-19823.patch
>
>
> Steps to reproduce.
> 1. Create a successful Hue To Ambari migration view by giving all the
> parameters in view creation page.
> 2. Run The initial check
> 3. After reaching the home-screen of the view. Stop The Database Service(hue
> db/ambari db).
> 4. After clicking on the Submit Button. The progress freezes.
> 5. In the Logs message is displayed "Database connection refused"
> Hence the desired behavior should be, if by any reason migration is hampered
> the appropriate message should be displayed in UI.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19880) WFM: "Workflow Designer" title should be changed to "Workflow Manager" and Minor UI fixes
[
https://issues.apache.org/jira/browse/AMBARI-19880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15855230#comment-15855230
]
Hadoop QA commented on AMBARI-19880:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12851202/AMBARI-19880_branch-2.5.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in
contrib/views/wfmanager/src/main/resources/ui
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10427//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10427//console
This message is automatically generated.
> WFM: "Workflow Designer" title should be changed to "Workflow Manager" and
> Minor UI fixes
> -
>
> Key: AMBARI-19880
> URL: https://issues.apache.org/jira/browse/AMBARI-19880
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: venkat
>Assignee: venkat
> Fix For: 2.5.0
>
> Attachments: AMBARI-19880_branch-2.5.patch
>
>
> "Workflow Designer" title should be changed to "Workflow Manager"
> Width and height of modal popups need to be responsive according to
> resolution.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19886) Update ambari managed llap queue to set preemption policy
[
https://issues.apache.org/jira/browse/AMBARI-19886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15855152#comment-15855152
]
Sumit Mohanty commented on AMBARI-19886:
Should this be reverted when "llap" is disabled?
{{putCapSchedProperty("yarn.scheduler.capacity.root.ordering-policy",
"priority-utilization"}}
> Update ambari managed llap queue to set preemption policy
> -
>
> Key: AMBARI-19886
> URL: https://issues.apache.org/jira/browse/AMBARI-19886
> Project: Ambari
> Issue Type: Task
> Components: stacks
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Fix For: 2.5.0
>
> Attachments: AMBARI-19886.01.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19452) Metrics of flume shows same values for all channels,sinks or sources in host
[
https://issues.apache.org/jira/browse/AMBARI-19452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15855106#comment-15855106
]
wangjianfei commented on AMBARI-19452:
--
[~avijayan] Yes,i tested it in my local environment,the widgets of flume metric
did not show the same graph for both ch1 and ch2,and the api
'/api/v1/clusters/bch/hosts/{hostName}/host_components/FLUME_HANDLER?fields=metrics/flume/flume/CHANNEL/{channel-name}/EventTakeSuccessCount'
returned the right rather than the same values for both ch1 and ch2.
> Metrics of flume shows same values for all channels,sinks or sources in host
>
>
> Key: AMBARI-19452
> URL: https://issues.apache.org/jira/browse/AMBARI-19452
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: wangjianfei
> Fix For: 2.5.0
>
> Attachments: AMBARI-19452.patch, Error.png
>
>
> When configuring multiply Channels-Sinks-Sources in flume,the flume
> metric of hosts always shows the same metric for all the Channels.
> Take Channel for example,actually,if configure Channel.ch1 and
> Channel.ch2,when retrive metrics of both ch1 and ch2 of the host,it returns
> the same metric values(values of last metric) for both ch1 and ch2。
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19887) Add AMS and Grafana to PERF cluster
[ https://issues.apache.org/jira/browse/AMBARI-19887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-19887: --- Status: Patch Available (was: Open) > Add AMS and Grafana to PERF cluster > --- > > Key: AMBARI-19887 > URL: https://issues.apache.org/jira/browse/AMBARI-19887 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-19887.patch > > > The PERF cluster needs AMS + Grafana so we can triage ambari server > performance issues by analyzing the metrics. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19887) Add AMS and Grafana to PERF cluster
[ https://issues.apache.org/jira/browse/AMBARI-19887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-19887: --- Attachment: (was: AMBARI-19887.patch) > Add AMS and Grafana to PERF cluster > --- > > Key: AMBARI-19887 > URL: https://issues.apache.org/jira/browse/AMBARI-19887 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-19887.patch > > > The PERF cluster needs AMS + Grafana so we can triage ambari server > performance issues by analyzing the metrics. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19887) Add AMS and Grafana to PERF cluster
[ https://issues.apache.org/jira/browse/AMBARI-19887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-19887: --- Attachment: AMBARI-19887.patch > Add AMS and Grafana to PERF cluster > --- > > Key: AMBARI-19887 > URL: https://issues.apache.org/jira/browse/AMBARI-19887 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-19887.patch > > > The PERF cluster needs AMS + Grafana so we can triage ambari server > performance issues by analyzing the metrics. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-14512) Add service check script for spark
[ https://issues.apache.org/jira/browse/AMBARI-14512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15855064#comment-15855064 ] Yusaku Sako commented on AMBARI-14512: -- I'm not sure. [~sumitmohanty]? > Add service check script for spark > -- > > Key: AMBARI-14512 > URL: https://issues.apache.org/jira/browse/AMBARI-14512 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.2.0 >Reporter: Jeff Zhang >Assignee: Jeff Zhang > Fix For: 3.0.0 > > Attachments: Ambari-14512-1.patch > > > There's no service check script for spark. It would be better to add that > just like other components in stack. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19452) Metrics of flume shows same values for all channels,sinks or sources in host
[ https://issues.apache.org/jira/browse/AMBARI-19452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15855061#comment-15855061 ] Aravindan Vijayan commented on AMBARI-19452: [~wangjianfei] Sure. Can you confirm if this patch was manually tested? > Metrics of flume shows same values for all channels,sinks or sources in host > > > Key: AMBARI-19452 > URL: https://issues.apache.org/jira/browse/AMBARI-19452 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: wangjianfei > Fix For: 2.5.0 > > Attachments: AMBARI-19452.patch, Error.png > > > When configuring multiply Channels-Sinks-Sources in flume,the flume > metric of hosts always shows the same metric for all the Channels. > Take Channel for example,actually,if configure Channel.ch1 and > Channel.ch2,when retrive metrics of both ch1 and ch2 of the host,it returns > the same metric values(values of last metric) for both ch1 and ch2。 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19887) Add AMS and Grafana to PERF cluster
[ https://issues.apache.org/jira/browse/AMBARI-19887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-19887: --- Attachment: AMBARI-19887.patch > Add AMS and Grafana to PERF cluster > --- > > Key: AMBARI-19887 > URL: https://issues.apache.org/jira/browse/AMBARI-19887 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-19887.patch > > > The PERF cluster needs AMS + Grafana so we can triage ambari server > performance issues by analyzing the metrics. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-14512) Add service check script for spark
[ https://issues.apache.org/jira/browse/AMBARI-14512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15855050#comment-15855050 ] Jeff Zhang commented on AMBARI-14512: - [~u39kun] Why is it reverted ? > Add service check script for spark > -- > > Key: AMBARI-14512 > URL: https://issues.apache.org/jira/browse/AMBARI-14512 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.2.0 >Reporter: Jeff Zhang >Assignee: Jeff Zhang > Fix For: 3.0.0 > > Attachments: Ambari-14512-1.patch > > > There's no service check script for spark. It would be better to add that > just like other components in stack. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19887) Add AMS and Grafana to PERF cluster
Aravindan Vijayan created AMBARI-19887: -- Summary: Add AMS and Grafana to PERF cluster Key: AMBARI-19887 URL: https://issues.apache.org/jira/browse/AMBARI-19887 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.5.0 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 2.5.0 The PERF cluster needs AMS + Grafana so we can triage ambari server performance issues by analyzing the metrics. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19886) Update ambari managed llap queue to set preemption policy
[ https://issues.apache.org/jira/browse/AMBARI-19886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated AMBARI-19886: Attachment: AMBARI-19886.01.patch Simple patch to set a few extra cs parameters. cc [~sumitmohanty], [~swapanshridhar], [~leftnoteasy] for review. > Update ambari managed llap queue to set preemption policy > - > > Key: AMBARI-19886 > URL: https://issues.apache.org/jira/browse/AMBARI-19886 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.0 > > Attachments: AMBARI-19886.01.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19886) Update ambari managed llap queue to set preemption policy
[ https://issues.apache.org/jira/browse/AMBARI-19886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated AMBARI-19886: Component/s: stacks > Update ambari managed llap queue to set preemption policy > - > > Key: AMBARI-19886 > URL: https://issues.apache.org/jira/browse/AMBARI-19886 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.0 > > Attachments: AMBARI-19886.01.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19886) Update ambari managed llap queue to set preemption policy
[ https://issues.apache.org/jira/browse/AMBARI-19886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated AMBARI-19886: Status: Patch Available (was: Open) > Update ambari managed llap queue to set preemption policy > - > > Key: AMBARI-19886 > URL: https://issues.apache.org/jira/browse/AMBARI-19886 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.0 > > Attachments: AMBARI-19886.01.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19886) Update ambari managed llap queue to set preemption policy
Siddharth Seth created AMBARI-19886: --- Summary: Update ambari managed llap queue to set preemption policy Key: AMBARI-19886 URL: https://issues.apache.org/jira/browse/AMBARI-19886 Project: Ambari Issue Type: Task Reporter: Siddharth Seth Assignee: Siddharth Seth -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19883) Hive2 view UDF tab is blank always
[
https://issues.apache.org/jira/browse/AMBARI-19883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15855029#comment-15855029
]
Hadoop QA commented on AMBARI-19883:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12851243/AMBARI-19883_trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 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/hive20
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10425//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10425//console
This message is automatically generated.
> Hive2 view UDF tab is blank always
> --
>
> Key: AMBARI-19883
> URL: https://issues.apache.org/jira/browse/AMBARI-19883
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Pallav Kulshreshtha
>Assignee: Pallav Kulshreshtha
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19883_trunk.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19886) Update ambari managed llap queue to set preemption policy
[ https://issues.apache.org/jira/browse/AMBARI-19886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated AMBARI-19886: Fix Version/s: 2.5.0 > Update ambari managed llap queue to set preemption policy > - > > Key: AMBARI-19886 > URL: https://issues.apache.org/jira/browse/AMBARI-19886 > Project: Ambari > Issue Type: Task >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19884) Set a higher value of num aggregated files per container - HDP stack, YARN
[ https://issues.apache.org/jira/browse/AMBARI-19884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated AMBARI-19884: Attachment: AMBARI-19884.01.patch cc [~sumitmohanty], [~swapanshridhar] - please review. > Set a higher value of num aggregated files per container - HDP stack, YARN > -- > > Key: AMBARI-19884 > URL: https://issues.apache.org/jira/browse/AMBARI-19884 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.0 > > Attachments: AMBARI-19884.01.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19881) Ambari Web UI is unusably irresponsive on a 1000-node perf cluster after adding AMS (restart indicator loading is too heavy)
[ https://issues.apache.org/jira/browse/AMBARI-19881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854926#comment-15854926 ] Yusaku Sako commented on AMBARI-19881: -- The UT failure on branch-2.5 is not related to the patch. > Ambari Web UI is unusably irresponsive on a 1000-node perf cluster after > adding AMS (restart indicator loading is too heavy) > > > Key: AMBARI-19881 > URL: https://issues.apache.org/jira/browse/AMBARI-19881 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19881_branch-2.5.patch, AMBARI-19881.patch > > > After adding AMS, the cluster became unusably irresponsive. The browser is > hanging for the most part. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-16229) Generalize the backend code for supporting cluster inherited permission for view instances
[ https://issues.apache.org/jira/browse/AMBARI-16229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854855#comment-15854855 ] Yusaku Sako commented on AMBARI-16229: -- [~dbhowmick] can you resolve this JIRA? > Generalize the backend code for supporting cluster inherited permission for > view instances > -- > > Key: AMBARI-16229 > URL: https://issues.apache.org/jira/browse/AMBARI-16229 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: DIPAYAN BHOWMICK >Assignee: DIPAYAN BHOWMICK > Fix For: 2.5.0 > > > Initial code will be merged with AMBARI-16177 > Implement the changes discussed in https://reviews.apache.org/r/46819/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-16764) When "Use Local Repository" option is selected, the stack cannot be changed
[ https://issues.apache.org/jira/browse/AMBARI-16764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-16764: - Fix Version/s: (was: 2.5.0) 2.4.0 > When "Use Local Repository" option is selected, the stack cannot be changed > --- > > Key: AMBARI-16764 > URL: https://issues.apache.org/jira/browse/AMBARI-16764 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko >Priority: Critical > Fix For: 2.4.0 > > > Clicking on the stack version tab in "Select Stack" page does nothing when > "Use Local Repository" option is selected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19885) Druid broker component need to be downscalable.
slim bouguerra created AMBARI-19885: --- Summary: Druid broker component need to be downscalable. Key: AMBARI-19885 URL: https://issues.apache.org/jira/browse/AMBARI-19885 Project: Ambari Issue Type: Bug Affects Versions: 2.5.0 Reporter: slim bouguerra Priority: Minor Fix For: 2.5.0 Currently druid broker component is declared as MASTER. This makes down scaling nodes containing Broker impossible via API calls. The only way to do it is to move the broker somewhere else first then kill the actual target. To avoid this will declare broker as slave (like druid historical). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-16218) Identify Starts (e.g. NN/Oozie) that are the longest and optimize work done during start
[ https://issues.apache.org/jira/browse/AMBARI-16218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako resolved AMBARI-16218. -- Resolution: Done > Identify Starts (e.g. NN/Oozie) that are the longest and optimize work done > during start > > > Key: AMBARI-16218 > URL: https://issues.apache.org/jira/browse/AMBARI-16218 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Sebastian Toader > Fix For: 2.5.0 > > > There are some components that take longer to start than the other. Identify > the long-poles and optimize the start. Candidates are NameNode and Oozie. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-16774) Install Wizard: Uploading an invalid VDF results in UI being stuck
[ https://issues.apache.org/jira/browse/AMBARI-16774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-16774: - Fix Version/s: (was: 2.5.0) 2.4.0 > Install Wizard: Uploading an invalid VDF results in UI being stuck > -- > > Key: AMBARI-16774 > URL: https://issues.apache.org/jira/browse/AMBARI-16774 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko >Priority: Critical > Fix For: 2.4.0 > > > STR: > 1. Launch Install Wizard > 2. Set cluster name > 3. In "Select Stack" page, upload an invalid VDF (e.g., a PNG file). > 4. You get an error popup. At this point, hit page refresh. You get an error > again with a blank page. > 5. Go back to "Get Started". The Next button is not clickable. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19881) Ambari Web UI is unusably irresponsive on a 1000-node perf cluster after adding AMS (restart indicator loading is too heavy)
[ https://issues.apache.org/jira/browse/AMBARI-19881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854861#comment-15854861 ] Hudson commented on AMBARI-19881: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #913 (See [https://builds.apache.org/job/Ambari-branch-2.5/913/]) AMBARI-19881. Ambari Web UI is unusably irresponsive on a 1000-node perf (yusaku: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c066fa889d76c2240d2ba9b86b35ea48021e266c]) * (edit) ambari-web/app/mappers/server_data_mapper.js * (edit) ambari-web/app/mappers/components_state_mapper.js * (edit) ambari-web/app/views/main/service/menu.js * (edit) ambari-web/app/controllers/main/service.js * (edit) ambari-web/app/models/service.js * (edit) ambari-web/app/models/client_component.js * (edit) ambari-web/app/mappers/component_config_mapper.js * (edit) ambari-web/app/models/host_component.js * (edit) ambari-web/test/controllers/main/service_test.js * (edit) ambari-web/test/models/service_test.js > Ambari Web UI is unusably irresponsive on a 1000-node perf cluster after > adding AMS (restart indicator loading is too heavy) > > > Key: AMBARI-19881 > URL: https://issues.apache.org/jira/browse/AMBARI-19881 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19881_branch-2.5.patch, AMBARI-19881.patch > > > After adding AMS, the cluster became unusably irresponsive. The browser is > hanging for the most part. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19881) Ambari Web UI is unusably irresponsive on a 1000-node perf cluster after adding AMS (restart indicator loading is too heavy)
[ https://issues.apache.org/jira/browse/AMBARI-19881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854885#comment-15854885 ] Hudson commented on AMBARI-19881: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6657 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6657/]) AMBARI-19881. Ambari Web UI is unusably irresponsive on a 1000-node perf (yusaku: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=239d9c1ae8a1bec103c1b3590bf52011cb579a38]) * (edit) ambari-web/app/views/main/service/menu.js * (edit) ambari-web/app/models/service.js * (edit) ambari-web/app/controllers/main/service.js * (edit) ambari-web/test/models/service_test.js * (edit) ambari-web/app/models/client_component.js * (edit) ambari-web/app/mappers/components_state_mapper.js * (edit) ambari-web/test/controllers/main/service_test.js * (edit) ambari-web/app/mappers/server_data_mapper.js * (edit) ambari-web/app/mappers/component_config_mapper.js * (edit) ambari-web/app/models/host_component.js > Ambari Web UI is unusably irresponsive on a 1000-node perf cluster after > adding AMS (restart indicator loading is too heavy) > > > Key: AMBARI-19881 > URL: https://issues.apache.org/jira/browse/AMBARI-19881 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19881_branch-2.5.patch, AMBARI-19881.patch > > > After adding AMS, the cluster became unusably irresponsive. The browser is > hanging for the most part. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-15834) Add better error handling to LogSearch Integration code in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-15834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Nettleton resolved AMBARI-15834. --- Resolution: Fixed This issue has been resolved by other patches in the LogSearch integration code that have removed the associated TODOs. > Add better error handling to LogSearch Integration code in Ambari > - > > Key: AMBARI-15834 > URL: https://issues.apache.org/jira/browse/AMBARI-15834 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Robert Nettleton >Assignee: Robert Nettleton >Priority: Critical > Fix For: 2.5.0 > > > This issue tracks the work involved in improving the error-handling code for > the LogSearch integration in Ambari. > Once the following patch has been approved and committed: > https://reviews.apache.org/r/45979/ > additional error-handling and logging should be added/improved to the > integration layer. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-16764) When "Use Local Repository" option is selected, the stack cannot be changed
[ https://issues.apache.org/jira/browse/AMBARI-16764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako resolved AMBARI-16764. -- Resolution: Fixed > When "Use Local Repository" option is selected, the stack cannot be changed > --- > > Key: AMBARI-16764 > URL: https://issues.apache.org/jira/browse/AMBARI-16764 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko >Priority: Critical > Fix For: 2.4.0 > > > Clicking on the stack version tab in "Select Stack" page does nothing when > "Use Local Repository" option is selected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-16774) Install Wizard: Uploading an invalid VDF results in UI being stuck
[ https://issues.apache.org/jira/browse/AMBARI-16774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako resolved AMBARI-16774. -- Resolution: Fixed > Install Wizard: Uploading an invalid VDF results in UI being stuck > -- > > Key: AMBARI-16774 > URL: https://issues.apache.org/jira/browse/AMBARI-16774 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko >Priority: Critical > Fix For: 2.4.0 > > > STR: > 1. Launch Install Wizard > 2. Set cluster name > 3. In "Select Stack" page, upload an invalid VDF (e.g., a PNG file). > 4. You get an error popup. At this point, hit page refresh. You get an error > again with a blank page. > 5. Go back to "Get Started". The Next button is not clickable. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19884) Set a higher value of num aggregated files per container - HDP stack, YARN
[ https://issues.apache.org/jira/browse/AMBARI-19884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated AMBARI-19884: Status: Patch Available (was: Open) > Set a higher value of num aggregated files per container - HDP stack, YARN > -- > > Key: AMBARI-19884 > URL: https://issues.apache.org/jira/browse/AMBARI-19884 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.0 > > Attachments: AMBARI-19884.01.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-15834) Add better error handling to LogSearch Integration code in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-15834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854860#comment-15854860 ] Robert Nettleton commented on AMBARI-15834: --- Hi [~jluniya], I don't believe this JIRA is still required. I looked at the review mentioned above, and the TODOs in this area of the code, in the LoggingService, have been removed by subsequent patches, so this tracking JIRA no longer appears to be needed. I'll close this out. Thanks. CC [~mahadev], [~u39kun], [~jluniya] > Add better error handling to LogSearch Integration code in Ambari > - > > Key: AMBARI-15834 > URL: https://issues.apache.org/jira/browse/AMBARI-15834 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Robert Nettleton >Assignee: Robert Nettleton >Priority: Critical > Fix For: 2.5.0 > > > This issue tracks the work involved in improving the error-handling code for > the LogSearch integration in Ambari. > Once the following patch has been approved and committed: > https://reviews.apache.org/r/45979/ > additional error-handling and logging should be added/improved to the > integration layer. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-16650) Add Unit Tests for Ranger Kerberos support
[ https://issues.apache.org/jira/browse/AMBARI-16650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854854#comment-15854854 ] Yusaku Sako commented on AMBARI-16650: -- Hi [~gautamborad], is there any action item on this? > Add Unit Tests for Ranger Kerberos support > -- > > Key: AMBARI-16650 > URL: https://issues.apache.org/jira/browse/AMBARI-16650 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Gautam Borad >Assignee: Gautam Borad > Fix For: 2.5.0 > > > Need a comprehensive test coverage for the Kerberos support that was added > recently for Ranger component. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19884) Set a higher value of num aggregated files per container - HDP stack, YARN
Siddharth Seth created AMBARI-19884: --- Summary: Set a higher value of num aggregated files per container - HDP stack, YARN Key: AMBARI-19884 URL: https://issues.apache.org/jira/browse/AMBARI-19884 Project: Ambari Issue Type: Task Components: stacks Reporter: Siddharth Seth Assignee: Siddharth Seth Fix For: 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-15368) there are some mistake in vendor.js when insatll hbase
[ https://issues.apache.org/jira/browse/AMBARI-15368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-15368: - Fix Version/s: 2.1.1 > there are some mistake in vendor.js when insatll hbase > -- > > Key: AMBARI-15368 > URL: https://issues.apache.org/jira/browse/AMBARI-15368 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.1.1 >Reporter: wuhui > Fix For: 2.1.1 > > Attachments: hbase_error.png > > > if you install hbase there will be a error at the step7 in vendor.js which > showed uncaught Error: could not respond to event > didChangeData in state rootState -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-15297) In the step 2 of install resourcemanager ha ,the hosts showd in mistake
[ https://issues.apache.org/jira/browse/AMBARI-15297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako resolved AMBARI-15297. -- Resolution: Won't Fix > In the step 2 of install resourcemanager ha ,the hosts showd in mistake > --- > > Key: AMBARI-15297 > URL: https://issues.apache.org/jira/browse/AMBARI-15297 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.1.1 >Reporter: wuhui > Fix For: 2.1.1 > > Attachments: rm_error.jpg > > > In the step 2 of install RM HA,if you select the extra host for the HA > host,it will show a error host which not match with the selected host. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-15368) there are some mistake in vendor.js when insatll hbase
[ https://issues.apache.org/jira/browse/AMBARI-15368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako resolved AMBARI-15368. -- Resolution: Won't Fix > there are some mistake in vendor.js when insatll hbase > -- > > Key: AMBARI-15368 > URL: https://issues.apache.org/jira/browse/AMBARI-15368 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.1.1 >Reporter: wuhui > Fix For: 2.1.1 > > Attachments: hbase_error.png > > > if you install hbase there will be a error at the step7 in vendor.js which > showed uncaught Error: could not respond to event > didChangeData in state rootState -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-15297) In the step 2 of install resourcemanager ha ,the hosts showd in mistake
[ https://issues.apache.org/jira/browse/AMBARI-15297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-15297: - Fix Version/s: (was: 2.5.0) 2.1.1 > In the step 2 of install resourcemanager ha ,the hosts showd in mistake > --- > > Key: AMBARI-15297 > URL: https://issues.apache.org/jira/browse/AMBARI-15297 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.1.1 >Reporter: wuhui > Fix For: 2.1.1 > > Attachments: rm_error.jpg > > > In the step 2 of install RM HA,if you select the extra host for the HA > host,it will show a error host which not match with the selected host. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-16107) Refactor technical debt to cleanup usage of params.version and other variables during RU/EU
[ https://issues.apache.org/jira/browse/AMBARI-16107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-16107: - Fix Version/s: (was: 2.5.0) 3.0.0 > Refactor technical debt to cleanup usage of params.version and other > variables during RU/EU > --- > > Key: AMBARI-16107 > URL: https://issues.apache.org/jira/browse/AMBARI-16107 > Project: Ambari > Issue Type: Story > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 3.0.0 > > > The service scripts each use their own method of how to get the version that > the stack is on and in many cases the confusion leads to bugs and regressions. > This is because we use > * /hostLevelParams/stack_version to represent the version that is "desired", > such as 2.2 or 2.3 > * /commandParams/request_version (not sure what this is) > * /commandParams/version for the version upgrading or downgrading to, which > includes the build number > * /commandParams/downgrade_from_version when in RU/DU and doing a downgrade, > this includes the build number as well > And the methods in hdp_select.py and conf_select.py tend to do hacky things. > We need a consistent way of getting the different types of version (e.g., > only the major and minor, full with build number, the version during an > RU/EU), and perhaps even put it in Script.py so that there's less confusion > between scripts. > Further, params.version was needed only during RU/EU restart commands, but > now scripts are using it for checks even on fresh install and need to make > comparisons like >= 2.3.4.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-15966) ambari-web 2.2.1 build error
[ https://issues.apache.org/jira/browse/AMBARI-15966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako resolved AMBARI-15966. -- Resolution: Won't Fix Later versions of Ambari Web has been modified to work with NodeJS v4. > ambari-web 2.2.1 build error > > > Key: AMBARI-15966 > URL: https://issues.apache.org/jira/browse/AMBARI-15966 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.1 >Reporter: skrho >Assignee: Jaimin Jetly > Fix For: 2.2.1 > > > Hi Everyone~~ > Now I am building the ambari-web 2.2.1 version > My Environment is > npm : 3.8.7 > node : 4.4.3 > brunch : 2.5.3 > I have a problem when building .. > I just command > # $apache-ambari-2.2.1-src/ambari-web]#brunch build -d > There is error message > brunch:config Trying to load brunch-config +0ms > brunch:config Trying to load config +5ms > 19 Apr 08:26:28 - warn: config.files.stylesheets.defaultPaths was removed > 19 Apr 08:26:28 - warn: config.files.templates.defaultPaths was removed > 19 Apr 08:26:28 - error: Initialization error - You probably need to execute > `npm install` to install brunch plugins. SyntaxError: Setter must have > exactly one formal parameter. > at /usr/lib/node_modules/brunch/lib/plugins.js:101:17 > at Array.map (native) > at deps.filter.dependency.map > (/usr/lib/node_modules/brunch/lib/plugins.js:88:8) > at packages.filter.plugins.map.plugin.filter.deps.filter.allPlugins.filter > (/usr/lib/node_modules/brunch/lib/plugins.js:108:19) > at > Object.packages.filter.plugins.map.plugin.filter.deps.filter.exports.init.plugins.filter.map.preCompilers.push.teardownBrunch > [as init] (/usr/lib/node_modules/brunch/lib/plugins.js:131:20) > at /usr/lib/node_modules/brunch/lib/watch.js:101:19 > Please Help me~ > What can I do that? > In advanced Thank you everyone -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-15078) Command "ambari-server backup" fails as /var/run/ambari-server/bootstrap/ does not exist.
[
https://issues.apache.org/jira/browse/AMBARI-15078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako updated AMBARI-15078:
-
Fix Version/s: (was: 2.5.0)
3.0.0
> Command "ambari-server backup" fails as /var/run/ambari-server/bootstrap/
> does not exist.
> -
>
> Key: AMBARI-15078
> URL: https://issues.apache.org/jira/browse/AMBARI-15078
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.1.2
> Environment: CentOS Linux release 7.2.1511 (Core)
> ambari-agent-2.1.2-377.x86_64
> ambari-server-2.1.2-377.x86_64
> ambari-metrics-hadoop-sink-2.1.2-377.x86_64
> ambari-metrics-monitor-2.1.2-377.x86_64
> ambari-metrics-collector-2.1.2-377.x86_64
>Reporter: Mark S
> Fix For: 3.0.0
>
>
> I am looking to backup my Ambari 2.1.2 instance and I am trying to follow the
> instructions outlined here:
> http://docs.hortonworks.com/HDPDocuments/Ambari-2.1.2.0/bk_ambari_reference_guide/content/_back_up_current_data.html
> However, the final step throws an error:
> {code}
> ambari-server backup
> Using python /usr/bin/python2.7
> Backing up Ambari File System state... *this will not backup the server
> database*
> Backup requested.
> No path specified. Will use /var/lib/ambari-server/Ambari_State_Backup.zip
> Backup process initiated.
> Error while validating folders. Folder /var/run/ambari-server/bootstrap/ does
> not exist.
> {code}
> There seems to be missing folders:
> {code}
> ls -al /var/run/ambari-server/
> total 0
> drwxr-xr-x. 2 root root 40 Feb 17 15:10 .
> drwxr-xr-x. 38 root root 1000 Feb 11 17:38 ..
> {code}
> {panel}
> Note**: It is worth mentioning that this issue does not occur on my Ambari
> 2.2.0 instance.
> {panel}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-15966) ambari-web 2.2.1 build error
[ https://issues.apache.org/jira/browse/AMBARI-15966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-15966: - Fix Version/s: (was: 2.5.0) 2.2.1 > ambari-web 2.2.1 build error > > > Key: AMBARI-15966 > URL: https://issues.apache.org/jira/browse/AMBARI-15966 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.1 >Reporter: skrho >Assignee: Jaimin Jetly > Fix For: 2.2.1 > > > Hi Everyone~~ > Now I am building the ambari-web 2.2.1 version > My Environment is > npm : 3.8.7 > node : 4.4.3 > brunch : 2.5.3 > I have a problem when building .. > I just command > # $apache-ambari-2.2.1-src/ambari-web]#brunch build -d > There is error message > brunch:config Trying to load brunch-config +0ms > brunch:config Trying to load config +5ms > 19 Apr 08:26:28 - warn: config.files.stylesheets.defaultPaths was removed > 19 Apr 08:26:28 - warn: config.files.templates.defaultPaths was removed > 19 Apr 08:26:28 - error: Initialization error - You probably need to execute > `npm install` to install brunch plugins. SyntaxError: Setter must have > exactly one formal parameter. > at /usr/lib/node_modules/brunch/lib/plugins.js:101:17 > at Array.map (native) > at deps.filter.dependency.map > (/usr/lib/node_modules/brunch/lib/plugins.js:88:8) > at packages.filter.plugins.map.plugin.filter.deps.filter.allPlugins.filter > (/usr/lib/node_modules/brunch/lib/plugins.js:108:19) > at > Object.packages.filter.plugins.map.plugin.filter.deps.filter.exports.init.plugins.filter.map.preCompilers.push.teardownBrunch > [as init] (/usr/lib/node_modules/brunch/lib/plugins.js:131:20) > at /usr/lib/node_modules/brunch/lib/watch.js:101:19 > Please Help me~ > What can I do that? > In advanced Thank you everyone -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-14512) Add service check script for spark
[ https://issues.apache.org/jira/browse/AMBARI-14512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854845#comment-15854845 ] Yusaku Sako commented on AMBARI-14512: -- This was committed and then reverted. > Add service check script for spark > -- > > Key: AMBARI-14512 > URL: https://issues.apache.org/jira/browse/AMBARI-14512 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.2.0 >Reporter: Jeff Zhang >Assignee: Jeff Zhang > Fix For: 3.0.0 > > Attachments: Ambari-14512-1.patch > > > There's no service check script for spark. It would be better to add that > just like other components in stack. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-14512) Add service check script for spark
[ https://issues.apache.org/jira/browse/AMBARI-14512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-14512: - Fix Version/s: (was: 2.5.0) 3.0.0 > Add service check script for spark > -- > > Key: AMBARI-14512 > URL: https://issues.apache.org/jira/browse/AMBARI-14512 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.2.0 >Reporter: Jeff Zhang >Assignee: Jeff Zhang > Fix For: 3.0.0 > > Attachments: Ambari-14512-1.patch > > > There's no service check script for spark. It would be better to add that > just like other components in stack. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-14423) Ambari Web Unit Test failures in trunk
[ https://issues.apache.org/jira/browse/AMBARI-14423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako resolved AMBARI-14423. -- Resolution: Cannot Reproduce > Ambari Web Unit Test failures in trunk > -- > > Key: AMBARI-14423 > URL: https://issues.apache.org/jira/browse/AMBARI-14423 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jayush Luniya >Assignee: Richard Zang >Priority: Blocker > Fix For: 2.5.0 > > > https://builds.apache.org/job/Ambari-trunk-Commit/4059/consoleFull > Missing translation: admin.highAvailability.wizard.step2.header.title > Missing translation: admin.highAvailability.wizard.step2.notice.inProgress > [91m â[0m[31m 1 of 11625 tests failed[0m[90m:[0m > [0m 1) Ambari Web Unit tests > test/models/configs/service_config_version_test App.ServiceConfigVersion > #createdDate should return created date: > > [41mactual[0m [42mexpected[0m > > "Wed, Dec 16, 2015 [42m14[0m[41m12[0m:06" > [0m[90m > at > file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/node_modules/chai/chai.js:925 > at assertEqual > (file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/node_modules/chai/chai.js:1402) > at > file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/node_modules/chai/chai.js:3638 > at > file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/public/test/javascripts/test.js:52112 > at > file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/node_modules/mocha/mocha.js:4039 > at > file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/node_modules/mocha/mocha.js:4404 > at > file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/node_modules/mocha/mocha.js:4463 > at next > (file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/node_modules/mocha/mocha.js:4330) > at > file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/node_modules/mocha/mocha.js:4339 > at next > (file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/node_modules/mocha/mocha.js:4287) > at > file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/node_modules/mocha/mocha.js:4307 > at timeslice > (file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/node_modules/mocha/mocha.js:5279) > [0m > npm ERR! Test failed. See above for more details. > npm ERR! not ok code 0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-14480) Ambari Admin: string constants used in controllers, directives and services should be defined once
[ https://issues.apache.org/jira/browse/AMBARI-14480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-14480: - Fix Version/s: (was: 2.5.0) 3.0.0 > Ambari Admin: string constants used in controllers, directives and services > should be defined once > -- > > Key: AMBARI-14480 > URL: https://issues.apache.org/jira/browse/AMBARI-14480 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 3.0.0 > > > Move string constants from controller, directives and services files to > common config file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-14023) Phoenix command line tool support
[
https://issues.apache.org/jira/browse/AMBARI-14023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako updated AMBARI-14023:
-
Fix Version/s: (was: 2.5.0)
3.0.0
> Phoenix command line tool support
> -
>
> Key: AMBARI-14023
> URL: https://issues.apache.org/jira/browse/AMBARI-14023
> Project: Ambari
> Issue Type: Improvement
> Components: stacks
>Affects Versions: 2.2.0
>Reporter: Nick Dimiduk
> Fix For: 3.0.0
>
>
> Phoenix client scripts appear to be installed where ever HBase client is
> installed. However, those scripts are not available in the path, a la
> {{/usr/bin/hbase}} is available in the path. The user must manually:
> - specify JAVA_HOME
> - place java in the path
> - invoke sqlline.py via pull path specification
> - explicitly provide hbase connection details
> A script in {{/usr/bin}} should:
> - consume in ambari provided JAVA_HOME and java
> - provide sqlline.py in the path
> - use cluster connection details as default when no connection information
> is provided on the command line
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-14375) Modify users API endpoint to use user id as PK instead of user name
[
https://issues.apache.org/jira/browse/AMBARI-14375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako updated AMBARI-14375:
-
Fix Version/s: (was: 2.5.0)
> Modify users API endpoint to use user id as PK instead of user name
> ---
>
> Key: AMBARI-14375
> URL: https://issues.apache.org/jira/browse/AMBARI-14375
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
>
> Currently user is accessed via API endpoint using its name.
> {{/users/admin}}
> which is not unique actually, we can have few users with same name if they
> are of different type (local, ldap, jwt).
> Such situation causes hard fail right now, conflicting users are unable to
> login.
> This also restricts us from using case-insensitive login when preserving
> original case.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-14023) Phoenix command line tool support
[
https://issues.apache.org/jira/browse/AMBARI-14023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854835#comment-15854835
]
Yusaku Sako commented on AMBARI-14023:
--
Yep, seems like the commit log had a reference to this JIRA incorrectly.
> Phoenix command line tool support
> -
>
> Key: AMBARI-14023
> URL: https://issues.apache.org/jira/browse/AMBARI-14023
> Project: Ambari
> Issue Type: Improvement
> Components: stacks
>Affects Versions: 2.2.0
>Reporter: Nick Dimiduk
> Fix For: 2.5.0
>
>
> Phoenix client scripts appear to be installed where ever HBase client is
> installed. However, those scripts are not available in the path, a la
> {{/usr/bin/hbase}} is available in the path. The user must manually:
> - specify JAVA_HOME
> - place java in the path
> - invoke sqlline.py via pull path specification
> - explicitly provide hbase connection details
> A script in {{/usr/bin}} should:
> - consume in ambari provided JAVA_HOME and java
> - provide sqlline.py in the path
> - use cluster connection details as default when no connection information
> is provided on the command line
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (AMBARI-2330) Ambari should support "auto start" and "desired state" of service components
[ https://issues.apache.org/jira/browse/AMBARI-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako resolved AMBARI-2330. - Resolution: Fixed > Ambari should support "auto start" and "desired state" of service components > > > Key: AMBARI-2330 > URL: https://issues.apache.org/jira/browse/AMBARI-2330 > Project: Ambari > Issue Type: Improvement >Affects Versions: 1.2.4 >Reporter: Jeff Sposetti >Assignee: Antonenko Alexander > Fix For: 2.5.0 > > > Ambari Server and Agents can be setup to auto-start on system reboot (using > the init.d scripts) > In the case of hadoop Components (like NN, JT, DN, etc), the user has to go > into Ambari and click "start", which can be cumbersome. And if > missed/forgotten, can cause unintended outages. > Ambari should impose "desired" service state, with the ability to designate > "auto start". -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19881) Ambari Web UI is unusably irresponsive on a 1000-node perf cluster after adding AMS (restart indicator loading is too heavy)
[ https://issues.apache.org/jira/browse/AMBARI-19881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854799#comment-15854799 ] Yusaku Sako commented on AMBARI-19881: -- +1'd on ReviewBoard. Committed to trunk and branch-2.5. > Ambari Web UI is unusably irresponsive on a 1000-node perf cluster after > adding AMS (restart indicator loading is too heavy) > > > Key: AMBARI-19881 > URL: https://issues.apache.org/jira/browse/AMBARI-19881 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19881_branch-2.5.patch, AMBARI-19881.patch > > > After adding AMS, the cluster became unusably irresponsive. The browser is > hanging for the most part. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19883) Hive2 view UDF tab is blank always
[ https://issues.apache.org/jira/browse/AMBARI-19883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-19883: - Attachment: AMBARI-19883_trunk.patch > Hive2 view UDF tab is blank always > -- > > Key: AMBARI-19883 > URL: https://issues.apache.org/jira/browse/AMBARI-19883 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19883_trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19883) Hive2 view UDF tab is blank always
[ https://issues.apache.org/jira/browse/AMBARI-19883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-19883: - Status: Patch Available (was: Open) > Hive2 view UDF tab is blank always > -- > > Key: AMBARI-19883 > URL: https://issues.apache.org/jira/browse/AMBARI-19883 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19883_trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19882) Search in recent projects should also search in path and search should be case insensitive
[ https://issues.apache.org/jira/browse/AMBARI-19882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-19882: Status: Patch Available (was: Open) > Search in recent projects should also search in path and search should be > case insensitive > -- > > Key: AMBARI-19882 > URL: https://issues.apache.org/jira/browse/AMBARI-19882 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-19882_branch-2.5.patch > > > Search in recent projects should be case insensitive and should search in > path also. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19882) Search in recent projects should also search in path and search should be case insensitive
[ https://issues.apache.org/jira/browse/AMBARI-19882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-19882: Attachment: AMBARI-19882_branch-2.5.patch > Search in recent projects should also search in path and search should be > case insensitive > -- > > Key: AMBARI-19882 > URL: https://issues.apache.org/jira/browse/AMBARI-19882 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-19882_branch-2.5.patch > > > Search in recent projects should be case insensitive and should search in > path also. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-19882) Search in recent projects should also search in path and search should be case insensitive
[ https://issues.apache.org/jira/browse/AMBARI-19882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat reassigned AMBARI-19882: --- Assignee: venkat > Search in recent projects should also search in path and search should be > case insensitive > -- > > Key: AMBARI-19882 > URL: https://issues.apache.org/jira/browse/AMBARI-19882 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > > Search in recent projects should be case insensitive and should search in > path also. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19871) Config version switch/compare/revert doesn't work
[ https://issues.apache.org/jira/browse/AMBARI-19871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854675#comment-15854675 ] Hudson commented on AMBARI-19871: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6656 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6656/]) AMBARI-19871 - Config version switch/compare/revert doesn't work (rzang) (rzang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e35bfd32b90282eae83fd14bbfaaf50e1bf47c87]) * (edit) ambari-web/app/views/common/configs/config_history_flow.js > Config version switch/compare/revert doesn't work > - > > Key: AMBARI-19871 > URL: https://issues.apache.org/jira/browse/AMBARI-19871 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19871.patch > > > *Steps to reproduce:* > 1. Go to any service with multiple config versions. > 2. On the bottom left of the config history bar(the cross button), select an > older version and click View. > *Actual result:* > Now direct clicking on other config version block will not be able to switch > version. Only through the cross button can you switch to other version. > Compare configs also does not work, it always compare to the current version > and end up with empty diff. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19871) Config version switch/compare/revert doesn't work
[ https://issues.apache.org/jira/browse/AMBARI-19871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854674#comment-15854674 ] Hudson commented on AMBARI-19871: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #912 (See [https://builds.apache.org/job/Ambari-branch-2.5/912/]) AMBARI-19871 - Config version switch/compare/revert doesn't work (rzang) (rzang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=bcf76586b6da2a704a5b986958050a28fd0c6d26]) * (edit) ambari-web/app/views/common/configs/config_history_flow.js > Config version switch/compare/revert doesn't work > - > > Key: AMBARI-19871 > URL: https://issues.apache.org/jira/browse/AMBARI-19871 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19871.patch > > > *Steps to reproduce:* > 1. Go to any service with multiple config versions. > 2. On the bottom left of the config history bar(the cross button), select an > older version and click View. > *Actual result:* > Now direct clicking on other config version block will not be able to switch > version. Only through the cross button can you switch to other version. > Compare configs also does not work, it always compare to the current version > and end up with empty diff. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19881) Ambari Web UI is unusably irresponsive on a 1000-node perf cluster after adding AMS (restart indicator loading is too heavy)
[
https://issues.apache.org/jira/browse/AMBARI-19881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854626#comment-15854626
]
Hadoop QA commented on AMBARI-19881:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12851226/AMBARI-19881.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10423//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10423//console
This message is automatically generated.
> Ambari Web UI is unusably irresponsive on a 1000-node perf cluster after
> adding AMS (restart indicator loading is too heavy)
>
>
> Key: AMBARI-19881
> URL: https://issues.apache.org/jira/browse/AMBARI-19881
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19881_branch-2.5.patch, AMBARI-19881.patch
>
>
> After adding AMS, the cluster became unusably irresponsive. The browser is
> hanging for the most part.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19871) Config version switch/compare/revert doesn't work
[ https://issues.apache.org/jira/browse/AMBARI-19871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-19871: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and 2.5 e35bfd32b90282eae83fd14bbfaaf50e1bf47c87 > Config version switch/compare/revert doesn't work > - > > Key: AMBARI-19871 > URL: https://issues.apache.org/jira/browse/AMBARI-19871 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19871.patch > > > *Steps to reproduce:* > 1. Go to any service with multiple config versions. > 2. On the bottom left of the config history bar(the cross button), select an > older version and click View. > *Actual result:* > Now direct clicking on other config version block will not be able to switch > version. Only through the cross button can you switch to other version. > Compare configs also does not work, it always compare to the current version > and end up with empty diff. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19881) Ambari Web UI is unusably irresponsive on a 1000-node perf cluster after adding AMS (restart indicator loading is too heavy)
[ https://issues.apache.org/jira/browse/AMBARI-19881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854580#comment-15854580 ] Andrii Tkach commented on AMBARI-19881: --- 20326 passing (36s) 153 pending > Ambari Web UI is unusably irresponsive on a 1000-node perf cluster after > adding AMS (restart indicator loading is too heavy) > > > Key: AMBARI-19881 > URL: https://issues.apache.org/jira/browse/AMBARI-19881 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19881_branch-2.5.patch, AMBARI-19881.patch > > > After adding AMS, the cluster became unusably irresponsive. The browser is > hanging for the most part. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19881) Ambari Web UI is unusably irresponsive on a 1000-node perf cluster after adding AMS (restart indicator loading is too heavy)
[ https://issues.apache.org/jira/browse/AMBARI-19881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19881: -- Attachment: AMBARI-19881.patch > Ambari Web UI is unusably irresponsive on a 1000-node perf cluster after > adding AMS (restart indicator loading is too heavy) > > > Key: AMBARI-19881 > URL: https://issues.apache.org/jira/browse/AMBARI-19881 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19881_branch-2.5.patch, AMBARI-19881.patch > > > After adding AMS, the cluster became unusably irresponsive. The browser is > hanging for the most part. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19881) Ambari Web UI is unusably irresponsive on a 1000-node perf cluster after adding AMS (restart indicator loading is too heavy)
[ https://issues.apache.org/jira/browse/AMBARI-19881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19881: -- Status: Patch Available (was: Open) > Ambari Web UI is unusably irresponsive on a 1000-node perf cluster after > adding AMS (restart indicator loading is too heavy) > > > Key: AMBARI-19881 > URL: https://issues.apache.org/jira/browse/AMBARI-19881 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19881_branch-2.5.patch, AMBARI-19881.patch > > > After adding AMS, the cluster became unusably irresponsive. The browser is > hanging for the most part. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19881) Ambari Web UI is unusably irresponsive on a 1000-node perf cluster after adding AMS (restart indicator loading is too heavy)
[ https://issues.apache.org/jira/browse/AMBARI-19881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19881: -- Attachment: AMBARI-19881_branch-2.5.patch > Ambari Web UI is unusably irresponsive on a 1000-node perf cluster after > adding AMS (restart indicator loading is too heavy) > > > Key: AMBARI-19881 > URL: https://issues.apache.org/jira/browse/AMBARI-19881 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19881_branch-2.5.patch > > > After adding AMS, the cluster became unusably irresponsive. The browser is > hanging for the most part. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19881) Ambari Web UI is unusably irresponsive on a 1000-node perf cluster after adding AMS (restart indicator loading is too heavy)
Andrii Tkach created AMBARI-19881: - Summary: Ambari Web UI is unusably irresponsive on a 1000-node perf cluster after adding AMS (restart indicator loading is too heavy) Key: AMBARI-19881 URL: https://issues.apache.org/jira/browse/AMBARI-19881 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Priority: Critical Fix For: 2.5.0 After adding AMS, the cluster became unusably irresponsive. The browser is hanging for the most part. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19857) Side Nav: create clickable breadcrumbs on top showing current path
[ https://issues.apache.org/jira/browse/AMBARI-19857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-19857: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to side-navigation-feature-branch > Side Nav: create clickable breadcrumbs on top showing current path > -- > > Key: AMBARI-19857 > URL: https://issues.apache.org/jira/browse/AMBARI-19857 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-19857.patch > > > Should show breadcrumbs on the top bar showing current path. > User can navigate to any parent page by clicking on the breadcrumbs > Eg. Ambari / Services-HDFS > Ambari / Hosts / hostname -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-19826) Side Nav: menu should be collapsed(expanded) on clicking
[ https://issues.apache.org/jira/browse/AMBARI-19826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang resolved AMBARI-19826. -- Resolution: Fixed Committed to side-navigation-feature-branch > Side Nav: menu should be collapsed(expanded) on clicking > > > Key: AMBARI-19826 > URL: https://issues.apache.org/jira/browse/AMBARI-19826 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-19826.patch, AMBARI-19826.patch > > > Expected: On the Side Navigation, each menu item has a sub-menu should be > collapsed/expanded on clicking. > Current: will be collapsed on clicking the chevron icon. > (Menus with sub-menu: Services/Admin/Ambari) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-19803) Side Nav: Long menu should be visible if longer than window height
[ https://issues.apache.org/jira/browse/AMBARI-19803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang resolved AMBARI-19803. -- Resolution: Fixed Committed to side-navigation-feature-branch > Side Nav: Long menu should be visible if longer than window height > -- > > Key: AMBARI-19803 > URL: https://issues.apache.org/jira/browse/AMBARI-19803 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-19803.patch > > > If the Services menu is long (or the browser window is short) , should be > able to see all menu items. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19880) WFM: "Workflow Designer" title should be changed to "Workflow Manager" and Minor UI fixes
[ https://issues.apache.org/jira/browse/AMBARI-19880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-19880: Attachment: AMBARI-19880_branch-2.5.patch > WFM: "Workflow Designer" title should be changed to "Workflow Manager" and > Minor UI fixes > - > > Key: AMBARI-19880 > URL: https://issues.apache.org/jira/browse/AMBARI-19880 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-19880_branch-2.5.patch > > > "Workflow Designer" title should be changed to "Workflow Manager" > Width and height of modal popups need to be responsive according to > resolution. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19880) WFM: "Workflow Designer" title should be changed to "Workflow Manager" and Minor UI fixes
[ https://issues.apache.org/jira/browse/AMBARI-19880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-19880: Status: Patch Available (was: Open) > WFM: "Workflow Designer" title should be changed to "Workflow Manager" and > Minor UI fixes > - > > Key: AMBARI-19880 > URL: https://issues.apache.org/jira/browse/AMBARI-19880 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > > "Workflow Designer" title should be changed to "Workflow Manager" > Width and height of modal popups need to be responsive according to > resolution. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19880) WFM: "Workflow Designer" title should be changed to "Workflow Manager" and Minor UI fixes
[ https://issues.apache.org/jira/browse/AMBARI-19880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-19880: Description: "Workflow Designer" title should be changed to "Workflow Manager" Width and height of modal popups need to be responsive according to resolution. > WFM: "Workflow Designer" title should be changed to "Workflow Manager" and > Minor UI fixes > - > > Key: AMBARI-19880 > URL: https://issues.apache.org/jira/browse/AMBARI-19880 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > > "Workflow Designer" title should be changed to "Workflow Manager" > Width and height of modal popups need to be responsive according to > resolution. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19880) WFM: "Workflow Designer" title should be changed to "Workflow Manager" and Minor UI fixes
venkat created AMBARI-19880: --- Summary: WFM: "Workflow Designer" title should be changed to "Workflow Manager" and Minor UI fixes Key: AMBARI-19880 URL: https://issues.apache.org/jira/browse/AMBARI-19880 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: venkat Assignee: venkat Fix For: 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19768) Package Installation fails due to error in Berkeley DB library
[
https://issues.apache.org/jira/browse/AMBARI-19768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854420#comment-15854420
]
Hadoop QA commented on AMBARI-19768:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12851160/AMBARI-19768.2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 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-agent.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10422//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10422//console
This message is automatically generated.
> Package Installation fails due to error in Berkeley DB library
> --
>
> Key: AMBARI-19768
> URL: https://issues.apache.org/jira/browse/AMBARI-19768
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19768.1.patch, AMBARI-19768.2.patch,
> AMBARI-19768.patch
>
>
> *Steps*
> # Deploy HDP-2.5.0.0 with Ambari 2.4.1.0
> # Upgrade ambari to 2.5.0.0-481 (I did not register Falcon library, as the
> jar was already present in /var/lib/ambari-server/resources/je-5.0.73.jar on
> Ambari server node)
> # Register HDP-2.6.0.0-216
> # Start package installation
> *Result:*
> Got below errors:
> {code}
> 2016-12-16 13:47:10,419|INFO|MainThread|machine.py:145 -
> run()|CRITICAL:yum.main:
> 2016-12-16 13:47:10,419|INFO|MainThread|machine.py:145 - run()|
> 2016-12-16 13:47:10,419|INFO|MainThread|machine.py:145 - run()|Error: rpmdb
> open failed
> 2016-12-16 13:47:10,420|INFO|MainThread|machine.py:145 - run()|Traceback
> (most recent call last):
> 2016-12-16 13:47:10,420|INFO|MainThread|machine.py:145 - run()|File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 166, in actionexecute
> 2016-12-16 13:47:10,420|INFO|MainThread|machine.py:145 - run()|ret_code =
> self.install_packages(package_list)
> 2016-12-16 13:47:10,420|INFO|MainThread|machine.py:145 - run()|File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 400, in install_packages
> 2016-12-16 13:47:10,420|INFO|MainThread|machine.py:145 - run()|if not
> verifyDependencies():
> 2016-12-16 13:47:10,421|INFO|MainThread|machine.py:145 - run()|File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/packages_analyzer.py",
> line 311, in verifyDependencies
> 2016-12-16 13:47:10,421|INFO|MainThread|machine.py:145 - run()|code, out =
> rmf_shell.checked_call(cmd, sudo=True)
> 2016-12-16 13:47:10,421|INFO|MainThread|machine.py:145 - run()|File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 72, in inner
> 2016-12-16 13:47:10,421|INFO|MainThread|machine.py:145 - run()|result =
> function(command, **kwargs)
> 2016-12-16 13:47:10,421|INFO|MainThread|machine.py:145 - run()|File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 102, in checked_call
> 2016-12-16 13:47:10,422|INFO|MainThread|machine.py:145 - run()|tries=tries,
> try_sleep=try_sleep, timeout_kill_strategy=timeout_kill_strategy)
> 2016-12-16 13:47:10,422|INFO|MainThread|machine.py:145 - run()|File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 150, in _call_wrapper
> 2016-12-16 13:47:10,422|INFO|MainThread|machine.py:145 - run()|result =
> _call(command, **kwargs_copy)
> 2016-12-16 13:47:10,422|INFO|MainThread|machine.py:145 - run()|File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 303, in _call
> 2016-12-16 13:47:10,423|INFO|MainThread|machine.py:145 - run()|raise
> ExecutionFailed(err_msg, code, out, err)
> 2016-12-16 13:47:10,423|INFO|MainThread|machine.py:145 -
> run()|ExecutionFailed: Execution of '/usr/bin/yum -d 0 -e 0 check
> dependencies' returned 1. error: rpmdb: BDB0113 Thread/process
> 16016/139791567193920 failed: BDB1507 Thread died in Berkeley DB library
> 2016-12-16 13:47:10,424|INFO|MainThread|machine.py:145 - run()|error: db5
> error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run
> database recovery
> 2016-12-16
[jira] [Updated] (AMBARI-19823) If by any case Migration Is hampered Then No message is shown in UI Hue-Ambari Migration view
[ https://issues.apache.org/jira/browse/AMBARI-19823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-19823: - Status: Patch Available (was: Open) > If by any case Migration Is hampered Then No message is shown in UI > Hue-Ambari Migration view > - > > Key: AMBARI-19823 > URL: https://issues.apache.org/jira/browse/AMBARI-19823 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk > > Attachments: AMBARI-19823.patch > > > Steps to reproduce. > 1. Create a successful Hue To Ambari migration view by giving all the > parameters in view creation page. > 2. Run The initial check > 3. After reaching the home-screen of the view. Stop The Database Service(hue > db/ambari db). > 4. After clicking on the Submit Button. The progress freezes. > 5. In the Logs message is displayed "Database connection refused" > Hence the desired behavior should be, if by any reason migration is hampered > the appropriate message should be displayed in UI. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19823) If by any case Migration Is hampered Then No message is shown in UI Hue-Ambari Migration view
[ https://issues.apache.org/jira/browse/AMBARI-19823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-19823: - Attachment: (was: AMBARI-19823.patch) > If by any case Migration Is hampered Then No message is shown in UI > Hue-Ambari Migration view > - > > Key: AMBARI-19823 > URL: https://issues.apache.org/jira/browse/AMBARI-19823 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk > > Attachments: AMBARI-19823.patch > > > Steps to reproduce. > 1. Create a successful Hue To Ambari migration view by giving all the > parameters in view creation page. > 2. Run The initial check > 3. After reaching the home-screen of the view. Stop The Database Service(hue > db/ambari db). > 4. After clicking on the Submit Button. The progress freezes. > 5. In the Logs message is displayed "Database connection refused" > Hence the desired behavior should be, if by any reason migration is hampered > the appropriate message should be displayed in UI. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19823) If by any case Migration Is hampered Then No message is shown in UI Hue-Ambari Migration view
[ https://issues.apache.org/jira/browse/AMBARI-19823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-19823: - Attachment: AMBARI-19823.patch > If by any case Migration Is hampered Then No message is shown in UI > Hue-Ambari Migration view > - > > Key: AMBARI-19823 > URL: https://issues.apache.org/jira/browse/AMBARI-19823 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk > > Attachments: AMBARI-19823.patch > > > Steps to reproduce. > 1. Create a successful Hue To Ambari migration view by giving all the > parameters in view creation page. > 2. Run The initial check > 3. After reaching the home-screen of the view. Stop The Database Service(hue > db/ambari db). > 4. After clicking on the Submit Button. The progress freezes. > 5. In the Logs message is displayed "Database connection refused" > Hence the desired behavior should be, if by any reason migration is hampered > the appropriate message should be displayed in UI. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19823) If by any case Migration Is hampered Then No message is shown in UI Hue-Ambari Migration view
[ https://issues.apache.org/jira/browse/AMBARI-19823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-19823: - Attachment: AMBARI-19823.patch > If by any case Migration Is hampered Then No message is shown in UI > Hue-Ambari Migration view > - > > Key: AMBARI-19823 > URL: https://issues.apache.org/jira/browse/AMBARI-19823 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk > > Attachments: AMBARI-19823.patch > > > Steps to reproduce. > 1. Create a successful Hue To Ambari migration view by giving all the > parameters in view creation page. > 2. Run The initial check > 3. After reaching the home-screen of the view. Stop The Database Service(hue > db/ambari db). > 4. After clicking on the Submit Button. The progress freezes. > 5. In the Logs message is displayed "Database connection refused" > Hence the desired behavior should be, if by any reason migration is hampered > the appropriate message should be displayed in UI. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19823) If by any case Migration Is hampered Then No message is shown in UI Hue-Ambari Migration view
[ https://issues.apache.org/jira/browse/AMBARI-19823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-19823: - Attachment: (was: AMBARI-19823.patch) > If by any case Migration Is hampered Then No message is shown in UI > Hue-Ambari Migration view > - > > Key: AMBARI-19823 > URL: https://issues.apache.org/jira/browse/AMBARI-19823 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk > > Attachments: AMBARI-19823.patch > > > Steps to reproduce. > 1. Create a successful Hue To Ambari migration view by giving all the > parameters in view creation page. > 2. Run The initial check > 3. After reaching the home-screen of the view. Stop The Database Service(hue > db/ambari db). > 4. After clicking on the Submit Button. The progress freezes. > 5. In the Logs message is displayed "Database connection refused" > Hence the desired behavior should be, if by any reason migration is hampered > the appropriate message should be displayed in UI. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19877) Confirmation for deleting services show serviceName and not displayName
[
https://issues.apache.org/jira/browse/AMBARI-19877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854373#comment-15854373
]
Hadoop QA commented on AMBARI-19877:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12851158/AMBARI-19877.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/10421//console
This message is automatically generated.
> Confirmation for deleting services show serviceName and not displayName
> ---
>
> Key: AMBARI-19877
> URL: https://issues.apache.org/jira/browse/AMBARI-19877
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-19877.patch
>
>
> Example:
> Shown: "Service LOGSEARCH was successfully deleted"
> Should be: "Service Log Search was successfully deleted"
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19878) Log Search Portal time zone selection bug
[
https://issues.apache.org/jira/browse/AMBARI-19878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854367#comment-15854367
]
Hadoop QA commented on AMBARI-19878:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12851180/AMBARI-19878.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-logsearch/ambari-logsearch-portal.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10420//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10420//console
This message is automatically generated.
> Log Search Portal time zone selection bug
> -
>
> Key: AMBARI-19878
> URL: https://issues.apache.org/jira/browse/AMBARI-19878
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.5.0
>
> Attachments: AMBARI-19878.patch
>
>
> In the time zone selection box the two CST time zones collide: "Central
> Standard Time" and "China Standard Time" are both abbreviated as CST, and due
> to this if the user clicks on the CST button, or moves the mouse over any of
> these regions, then both of them are highlighted.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19846) ambari-agent.out getting filled with "dummy" traceback
[
https://issues.apache.org/jira/browse/AMBARI-19846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854354#comment-15854354
]
Hudson commented on AMBARI-19846:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6655 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6655/])
AMBARI-19846. ambari-agent.out getting filled with dummy traceback. (stoader:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=df8c06ca7cae9fe3af75e49d7a31e197d250ba9b])
* (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py
* (edit)
ambari-agent/src/test/python/ambari_agent/TestCustomServiceOrchestrator.py
> ambari-agent.out getting filled with "dummy" traceback
> --
>
> Key: AMBARI-19846
> URL: https://issues.apache.org/jira/browse/AMBARI-19846
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 3.0.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: AMBARI-19846.patch
>
>
> {noformat:title=ambari-agent.out}
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/ambari_agent/CustomServiceOrchestrator.py",
> line 312, in runCommand
> task_id = command['taskId']
> KeyError: 'taskId'
> The above exception was the cause of the following exception:
> {noformat}
> Note:
> * the "following exception" has no stack trace (it's a
> {{ClientComponentHasNoStatus}}, but could be a few other subtypes of
> {{Fail}}, too)
> * the {{KeyError}} is expected and caught by {{CustomServiceOrchestrator}},
> has no relation to the {{ClientComponentHasNoStatus}} exception
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19879) Updating yarn-env and hadoop-env templates with ZK secure options on stack upgrade
[ https://issues.apache.org/jira/browse/AMBARI-19879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar updated AMBARI-19879: --- Summary: Updating yarn-env and hadoop-env templates with ZK secure options on stack upgrade (was: ZK ACL changes during stack upgrades) > Updating yarn-env and hadoop-env templates with ZK secure options on stack > upgrade > -- > > Key: AMBARI-19879 > URL: https://issues.apache.org/jira/browse/AMBARI-19879 > Project: Ambari > Issue Type: Bug >Reporter: Attila Magyar >Assignee: Attila Magyar > Fix For: 2.5.0 > > > Enabling ZK ACL security fails when upgrading HDP 2.x -> HDP 2.6. The upgrade > scripts should be modified to add the missing zookeeper specific options. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-16658) DevDeploy: Cannot connect to the server using SSLv3
[
https://issues.apache.org/jira/browse/AMBARI-16658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854237#comment-15854237
]
Gonzalo Herreros commented on AMBARI-16658:
---
Hi Andrew,
I think your fix has a side-effect: it forces the server to run on TLS1 (which
is now obsolete) and prevents using 1.1, 1.2 and future versions
In Java 7 they disabled SSLv2Hello by default but by enabling it this way, the
choice of protocol is limited to just TLSv1:
factory.setIncludeProtocols(new String[] { "SSLv2Hello","TLSv1"});
I see 3 ways of solving this side effect:
- extend the list to include 1.1 and 1.2 (maybe make it configurable so 1.3 can
be used when it comes out)
- append the list of JVM available protocols to that array
- remove the line and enable SSLv2Hello by using JVM flags, so the list can be
easily updated
> DevDeploy: Cannot connect to the server using SSLv3
> ---
>
> Key: AMBARI-16658
> URL: https://issues.apache.org/jira/browse/AMBARI-16658
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-16658.patch
>
>
> os-s11-3-irzlbs-devdeployerie-5:~ # curl --sslv3 --insecure -u
> admin:admin https://172.22.106.251:8443/api/v1/clusters/cl1/hosts
> curl: (35) Unknown SSL protocol error in connection to
> 172.22.106.251:8443
>
> os-s11-3-irzlbs-devdeployerie-5:~ # curl --tlsv1 --insecure -u
> admin:admin https://172.22.106.251:8443/api/v1/clusters/cl1/hosts
> {
> "href" : "http://172.22.106.251:8443/api/v1/clusters/cl1/hosts;,
> ...
>
> There are no security.server.disabled.protocols or
> security.server.disabled.ciphers in ambari.properties.
> An error from QE scripts (it's caused because "requests" lib is using sslv3 by
> default):
>
>
> 2016-05-12 08:50:55,683 INFO requests.packages.urllib3.connectionpool :
> Starting new HTTPS connection (1):
> os-s11-3-aijuzs-devdeployerie-5.openstacklocal
> Traceback (most recent call last):
> File "WireEncryption.py", line 205, in
> main()
> File "WireEncryption.py", line 201, in main
> we.TestWireEncryption()
> File "WireEncryption.py", line 36, in TestWireEncryption
> hosts = self.weu.apicl.get_all_hosts()
> File "/ambari_deploy/wireencryption/APICoreLib.py", line 89, in
> get_all_hosts
> result = self.http_get_request(uri)
> File "/ambari_deploy/wireencryption/APICoreLib.py", line 51, in
> http_get_request
> response = requests.get(url=url, auth=basic_auth, verify=False)
> File "/usr/lib64/python2.6/site-packages/requests/api.py", line 68, in
> get
> return request('get', url, **kwargs)
> File "/usr/lib64/python2.6/site-packages/requests/api.py", line 50, in
> request
> response = session.request(method=method, url=url, **kwargs)
> File "/usr/lib64/python2.6/site-packages/requests/sessions.py", line
> 464, in request
> resp = self.send(prep, **send_kwargs)
> File "/usr/lib64/python2.6/site-packages/requests/sessions.py", line
> 576, in send
> r = adapter.send(request, **kwargs)
> File "/usr/lib64/python2.6/site-packages/requests/adapters.py", line
> 428, in send
> raise SSLError(e, request=request)
> requests.exceptions.SSLError: [Errno 8] _ssl.c:491: EOF occurred in
> violation of protocol
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-19879) ZK ACL changes during stack upgrades
Attila Magyar created AMBARI-19879: -- Summary: ZK ACL changes during stack upgrades Key: AMBARI-19879 URL: https://issues.apache.org/jira/browse/AMBARI-19879 Project: Ambari Issue Type: Bug Reporter: Attila Magyar Assignee: Attila Magyar Fix For: 2.5.0 Enabling ZK ACL security fails when upgrading HDP 2.x -> HDP 2.6. The upgrade scripts should be modified to add the missing zookeeper specific options. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19867) Grafana install fails if custom directory's parent does not exist
[
https://issues.apache.org/jira/browse/AMBARI-19867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854205#comment-15854205
]
Hudson commented on AMBARI-19867:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6654 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6654/])
AMBARI-19867. Grafana install fails if custom directory's parent does (stoader:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e05e5296c580b3b714f784f54754318bc09f67de])
* (edit)
ambari-server/src/test/python/stacks/2.0.6/AMBARI_METRICS/test_metrics_grafana.py
* (edit)
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py
> Grafana install fails if custom directory's parent does not exist
> -
>
> Key: AMBARI-19867
> URL: https://issues.apache.org/jira/browse/AMBARI-19867
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Minor
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19867.patch
>
>
> Creating cluster via blueprint with custom {{metrics_grafana_log_dir}} and/or
> {{metrics_grafana_data_dir}} whose parent directory does not exist fails.
> {noformat:title=sample config}
> "ams-grafana-env": {
> "properties": {
> "metrics_grafana_log_dir": "/var/log/ambari/metrics/grafana",
> "metrics_grafana_data_dir": "/var/lib/ambari/metrics/grafana"
> }
> }
> {noformat}
> {noformat:title=error}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 81, in
> AmsGrafana().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 314, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 34, in install
> self.configure(env) # for security
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 117, in locking_configure
> original_configure(obj, *args, **kw)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 39, in configure
> ams(name='grafana', action=action)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py",
> line 426, in ams
> recursive_ownership = True
> 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 189, in action_create
> raise Fail("Applying %s failed, parent directory %s doesn't exist" %
> (self.resource, dirname))
> resource_management.core.exceptions.Fail: Applying
> Directory['/var/log/ambari/metrics/grafana'] failed, parent directory
> /var/log/ambari/metrics doesn't exist
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19867) Grafana install fails if custom directory's parent does not exist
[
https://issues.apache.org/jira/browse/AMBARI-19867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854192#comment-15854192
]
Hudson commented on AMBARI-19867:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #911 (See
[https://builds.apache.org/job/Ambari-branch-2.5/911/])
AMBARI-19867. Grafana install fails if custom directory's parent does (stoader:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=db40937430b442613cf91d96e36fd12c131f5d0d])
* (edit)
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py
* (edit)
ambari-server/src/test/python/stacks/2.0.6/AMBARI_METRICS/test_metrics_grafana.py
> Grafana install fails if custom directory's parent does not exist
> -
>
> Key: AMBARI-19867
> URL: https://issues.apache.org/jira/browse/AMBARI-19867
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Minor
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19867.patch
>
>
> Creating cluster via blueprint with custom {{metrics_grafana_log_dir}} and/or
> {{metrics_grafana_data_dir}} whose parent directory does not exist fails.
> {noformat:title=sample config}
> "ams-grafana-env": {
> "properties": {
> "metrics_grafana_log_dir": "/var/log/ambari/metrics/grafana",
> "metrics_grafana_data_dir": "/var/lib/ambari/metrics/grafana"
> }
> }
> {noformat}
> {noformat:title=error}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 81, in
> AmsGrafana().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 314, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 34, in install
> self.configure(env) # for security
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 117, in locking_configure
> original_configure(obj, *args, **kw)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 39, in configure
> ams(name='grafana', action=action)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py",
> line 426, in ams
> recursive_ownership = True
> 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 189, in action_create
> raise Fail("Applying %s failed, parent directory %s doesn't exist" %
> (self.resource, dirname))
> resource_management.core.exceptions.Fail: Applying
> Directory['/var/log/ambari/metrics/grafana'] failed, parent directory
> /var/log/ambari/metrics doesn't exist
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19846) ambari-agent.out getting filled with "dummy" traceback
[
https://issues.apache.org/jira/browse/AMBARI-19846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-19846:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to
[trunk|http://git-wip-us.apache.org/repos/asf/ambari/commit/df8c06ca].
> ambari-agent.out getting filled with "dummy" traceback
> --
>
> Key: AMBARI-19846
> URL: https://issues.apache.org/jira/browse/AMBARI-19846
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 3.0.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: AMBARI-19846.patch
>
>
> {noformat:title=ambari-agent.out}
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/ambari_agent/CustomServiceOrchestrator.py",
> line 312, in runCommand
> task_id = command['taskId']
> KeyError: 'taskId'
> The above exception was the cause of the following exception:
> {noformat}
> Note:
> * the "following exception" has no stack trace (it's a
> {{ClientComponentHasNoStatus}}, but could be a few other subtypes of
> {{Fail}}, too)
> * the {{KeyError}} is expected and caught by {{CustomServiceOrchestrator}},
> has no relation to the {{ClientComponentHasNoStatus}} exception
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19867) Grafana install fails if custom directory's parent does not exist
[
https://issues.apache.org/jira/browse/AMBARI-19867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-19867:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to
[trunk|http://git-wip-us.apache.org/repos/asf/ambari/commit/e05e5296] and
[branch-2.5|http://git-wip-us.apache.org/repos/asf/ambari/commit/db409374].
> Grafana install fails if custom directory's parent does not exist
> -
>
> Key: AMBARI-19867
> URL: https://issues.apache.org/jira/browse/AMBARI-19867
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Minor
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19867.patch
>
>
> Creating cluster via blueprint with custom {{metrics_grafana_log_dir}} and/or
> {{metrics_grafana_data_dir}} whose parent directory does not exist fails.
> {noformat:title=sample config}
> "ams-grafana-env": {
> "properties": {
> "metrics_grafana_log_dir": "/var/log/ambari/metrics/grafana",
> "metrics_grafana_data_dir": "/var/lib/ambari/metrics/grafana"
> }
> }
> {noformat}
> {noformat:title=error}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 81, in
> AmsGrafana().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 314, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 34, in install
> self.configure(env) # for security
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 117, in locking_configure
> original_configure(obj, *args, **kw)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 39, in configure
> ams(name='grafana', action=action)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py",
> line 426, in ams
> recursive_ownership = True
> 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 189, in action_create
> raise Fail("Applying %s failed, parent directory %s doesn't exist" %
> (self.resource, dirname))
> resource_management.core.exceptions.Fail: Applying
> Directory['/var/log/ambari/metrics/grafana'] failed, parent directory
> /var/log/ambari/metrics doesn't exist
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19878) Log Search Portal time zone selection bug
[ https://issues.apache.org/jira/browse/AMBARI-19878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-19878: Attachment: AMBARI-19878.patch > Log Search Portal time zone selection bug > - > > Key: AMBARI-19878 > URL: https://issues.apache.org/jira/browse/AMBARI-19878 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > Attachments: AMBARI-19878.patch > > > In the time zone selection box the two CST time zones collide: "Central > Standard Time" and "China Standard Time" are both abbreviated as CST, and due > to this if the user clicks on the CST button, or moves the mouse over any of > these regions, then both of them are highlighted. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19878) Log Search Portal time zone selection bug
[ https://issues.apache.org/jira/browse/AMBARI-19878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-19878: Status: Patch Available (was: Open) > Log Search Portal time zone selection bug > - > > Key: AMBARI-19878 > URL: https://issues.apache.org/jira/browse/AMBARI-19878 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > Attachments: AMBARI-19878.patch > > > In the time zone selection box the two CST time zones collide: "Central > Standard Time" and "China Standard Time" are both abbreviated as CST, and due > to this if the user clicks on the CST button, or moves the mouse over any of > these regions, then both of them are highlighted. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19878) Log Search Portal time zone selection bug
Miklos Gergely created AMBARI-19878: --- Summary: Log Search Portal time zone selection bug Key: AMBARI-19878 URL: https://issues.apache.org/jira/browse/AMBARI-19878 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.4.0 Reporter: Miklos Gergely Assignee: Miklos Gergely Fix For: 2.5.0 In the time zone selection box the two CST time zones collide: "Central Standard Time" and "China Standard Time" are both abbreviated as CST, and due to this if the user clicks on the CST button, or moves the mouse over any of these regions, then both of them are highlighted. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19877) Confirmation for deleting services show serviceName and not displayName
[ https://issues.apache.org/jira/browse/AMBARI-19877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854067#comment-15854067 ] Hudson commented on AMBARI-19877: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6653 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6653/]) AMBARI-19877. Confirmation for deleting services show serviceName and (onechiporenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9f2d1d9b6ef7019919e4a6fd1bd80569eaf4e97b]) * (edit) ambari-web/app/controllers/main/service/item.js * (edit) ambari-web/test/controllers/main/service/item_test.js > Confirmation for deleting services show serviceName and not displayName > --- > > Key: AMBARI-19877 > URL: https://issues.apache.org/jira/browse/AMBARI-19877 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-19877.patch > > > Example: > Shown: "Service LOGSEARCH was successfully deleted" > Should be: "Service Log Search was successfully deleted" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19745) Hive History Queries not working for Hive 2.0 in Hue-Migration View
[ https://issues.apache.org/jira/browse/AMBARI-19745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854036#comment-15854036 ] Hudson commented on AMBARI-19745: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #910 (See [https://builds.apache.org/job/Ambari-branch-2.5/910/]) AMBARI-19745. Hive History Queries not working for Hive 2.0 in (grvngr: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e81361bc42e9da94e700306acd54fb542a100567]) * (edit) contrib/views/hueambarimigration/src/main/java/org/apache/ambari/view/huetoambarimigration/migration/hive/historyquery/HiveHistoryQueryMigrationImplementation.java > Hive History Queries not working for Hive 2.0 in Hue-Migration View > --- > > Key: AMBARI-19745 > URL: https://issues.apache.org/jira/browse/AMBARI-19745 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk > > Attachments: AMBARI-19745.patch > > > Hue-Migration View does not support migration history queries to hive-2.0.0's > instances. > Saved queries is working fine. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19745) Hive History Queries not working for Hive 2.0 in Hue-Migration View
[ https://issues.apache.org/jira/browse/AMBARI-19745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854013#comment-15854013 ] Hudson commented on AMBARI-19745: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6652 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6652/]) AMBARI-19745. Hive History Queries not working for Hive 2.0 in (grvngr: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=13f8f96b3e5fedf14fc1a2089abae33a0ee0e204]) * (edit) contrib/views/hueambarimigration/src/main/java/org/apache/ambari/view/huetoambarimigration/migration/hive/historyquery/HiveHistoryQueryMigrationImplementation.java > Hive History Queries not working for Hive 2.0 in Hue-Migration View > --- > > Key: AMBARI-19745 > URL: https://issues.apache.org/jira/browse/AMBARI-19745 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk > > Attachments: AMBARI-19745.patch > > > Hue-Migration View does not support migration history queries to hive-2.0.0's > instances. > Saved queries is working fine. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
