[jira] [Commented] (AMBARI-22260) Update Spark2 log4j default settings to latest
[ https://issues.apache.org/jira/browse/AMBARI-22260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16254573#comment-16254573 ] Hudson commented on AMBARI-22260: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8400 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8400/]) AMBARI-22260. Update Spark2 log4j default settings to latest. (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4042f9fde14548be77a5ed5daf45364df307c08a]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml * (add) ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK2/configuration/spark2-log4j-properties.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml > Update Spark2 log4j default settings to latest > -- > > Key: AMBARI-22260 > URL: https://issues.apache.org/jira/browse/AMBARI-22260 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Saisai Shao >Assignee: Saisai Shao > Fix For: 2.6.1 > > > Apache Spark log4j definition has changed in some places, we should update > this default setting in Ambari Spark2 stack definition to reflect such > changes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22260) Update Spark2 log4j default settings to latest
[ https://issues.apache.org/jira/browse/AMBARI-22260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16254566#comment-16254566 ] Hudson commented on AMBARI-22260: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #460 (See [https://builds.apache.org/job/Ambari-branch-2.6/460/]) AMBARI-22260. Update Spark2 log4j default settings to latest. (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=26cf2cf21174d15c5267c18c1e8d10da7a915957]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml * (add) ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK2/configuration/spark2-log4j-properties.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml > Update Spark2 log4j default settings to latest > -- > > Key: AMBARI-22260 > URL: https://issues.apache.org/jira/browse/AMBARI-22260 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Saisai Shao >Assignee: Saisai Shao > Fix For: 2.6.1 > > > Apache Spark log4j definition has changed in some places, we should update > this default setting in Ambari Spark2 stack definition to reflect such > changes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-22260) Update Spark2 log4j default settings to latest
[ https://issues.apache.org/jira/browse/AMBARI-22260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar resolved AMBARI-22260. -- Resolution: Fixed > Update Spark2 log4j default settings to latest > -- > > Key: AMBARI-22260 > URL: https://issues.apache.org/jira/browse/AMBARI-22260 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Saisai Shao >Assignee: Saisai Shao > Fix For: 2.6.1 > > > Apache Spark log4j definition has changed in some places, we should update > this default setting in Ambari Spark2 stack definition to reflect such > changes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22260) Update Spark2 log4j default settings to latest
[
https://issues.apache.org/jira/browse/AMBARI-22260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16254525#comment-16254525
]
Swapan Shridhar commented on AMBARI-22260:
--
commits
trunk:
{code}
commit 4042f9fde14548be77a5ed5daf45364df307c08a
Author: Swapan Shridhar
Date: Wed Nov 15 16:21:31 2017 -0800
AMBARI-22260. Update Spark2 log4j default settings to latest. (sai.sai.shao
via sshridhar).
{code}
2.6.1:
{code}
commit 26cf2cf21174d15c5267c18c1e8d10da7a915957
Author: Swapan Shridhar
Date: Wed Nov 15 16:25:23 2017 -0800
AMBARI-22260. Update Spark2 log4j default settings to latest. (sai.sai.shao
via sshridhar).
{code}
> Update Spark2 log4j default settings to latest
> --
>
> Key: AMBARI-22260
> URL: https://issues.apache.org/jira/browse/AMBARI-22260
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Saisai Shao
>Assignee: Saisai Shao
> Fix For: 2.6.1
>
>
> Apache Spark log4j definition has changed in some places, we should update
> this default setting in Ambari Spark2 stack definition to reflect such
> changes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22260) Update Spark2 log4j default settings to latest
[ https://issues.apache.org/jira/browse/AMBARI-22260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-22260: - Component/s: (was: stacks) ambari-server > Update Spark2 log4j default settings to latest > -- > > Key: AMBARI-22260 > URL: https://issues.apache.org/jira/browse/AMBARI-22260 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Saisai Shao >Assignee: Saisai Shao > Fix For: 2.6.1 > > > Apache Spark log4j definition has changed in some places, we should update > this default setting in Ambari Spark2 stack definition to reflect such > changes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22260) Update Spark2 log4j default settings to latest
[ https://issues.apache.org/jira/browse/AMBARI-22260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-22260: - Fix Version/s: 2.6.1 > Update Spark2 log4j default settings to latest > -- > > Key: AMBARI-22260 > URL: https://issues.apache.org/jira/browse/AMBARI-22260 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.6.0 >Reporter: Saisai Shao >Assignee: Saisai Shao > Fix For: 2.6.1 > > > Apache Spark log4j definition has changed in some places, we should update > this default setting in Ambari Spark2 stack definition to reflect such > changes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22444) Add Native Libraries To Tez Tarball
[
https://issues.apache.org/jira/browse/AMBARI-22444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16254475#comment-16254475
]
Hudson commented on AMBARI-22444:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8399 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8399/])
AMBARI-22444 - Add Native Libraries To Tez Tarball (part2) (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0936f463042cf5ba195b0461479d8c29c88330dd])
* (edit)
ambari-common/src/main/python/resource_management/libraries/functions/copy_tarball.py
> Add Native Libraries To Tez Tarball
> ---
>
> Key: AMBARI-22444
> URL: https://issues.apache.org/jira/browse/AMBARI-22444
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22444.patch
>
>
> As part of the investigation for getting patch upgrades working in Ambari
> 2.6.1, it was determined that the Tez tarball will need to have the hadoop
> native libraries added to it so that they can be detected from the tarball.
> STR:
> - Install ZK, MapR, Tez, Yarn, Hive
> - Enable a non-LZO codec, like Snappy
> - Patch Hive to a new version
> - Change the following properties in {{tez-site}}:
> -- tez.am.launch.env = LD_LIBRARY=./tezlib/lib/native
> -- tez.task.launch.env = LD_LIBRARY=./tezlib/lib/native
> When Hive commands run, they will attempt to load the native snappy libraries
> from the Tez tarball and will fail with:
> {code}
> Caused by: java.io.IOException: Unable to get CompressorType for codec
> (org.apache.hadoop.io.compress.SnappyCodec). This is most likely due to
> missing native libraries for the codec.
> at
> org.apache.tez.runtime.library.common.sort.impl.ExternalSorter.(ExternalSorter.java:217)
> {code}
> In order to fix this, the Tez tarball should include the native hadoop
> libraries as well:
> {code}
> ├── tez
> │ ├── lib
> │ │ ├── native
> │ │ │ ├── libhadoop.a
> │ │ │ ├── libhadoop.so -> libhadoop.so.1.0.0
> │ │ │ ├── libhadoop.so.1.0.0
> │ │ │ ├── libhadooppipes.a
> │ │ │ ├── libhadooputils.a
> │ │ │ ├── libhdfs.a
> │ │ │ ├── libhdfs.so -> libhdfs.so.0.0.0
> │ │ │ ├── libhdfs.so.0.0.0
> │ │ │ ├── libsnappy.so -> libsnappy.so.1.1.4
> │ │ │ ├── libsnappy.so.1 -> libsnappy.so.1.1.4
> │ │ │ └── libsnappy.so.1.1.4
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22444) Add Native Libraries To Tez Tarball
[
https://issues.apache.org/jira/browse/AMBARI-22444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16254441#comment-16254441
]
Hudson commented on AMBARI-22444:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.6 #459 (See
[https://builds.apache.org/job/Ambari-branch-2.6/459/])
AMBARI-22444 - Add Native Libraries To Tez Tarball (part2) (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a8496eedbf55310bc37e44d0012520ed0e014737])
* (edit)
ambari-common/src/main/python/resource_management/libraries/functions/copy_tarball.py
> Add Native Libraries To Tez Tarball
> ---
>
> Key: AMBARI-22444
> URL: https://issues.apache.org/jira/browse/AMBARI-22444
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22444.patch
>
>
> As part of the investigation for getting patch upgrades working in Ambari
> 2.6.1, it was determined that the Tez tarball will need to have the hadoop
> native libraries added to it so that they can be detected from the tarball.
> STR:
> - Install ZK, MapR, Tez, Yarn, Hive
> - Enable a non-LZO codec, like Snappy
> - Patch Hive to a new version
> - Change the following properties in {{tez-site}}:
> -- tez.am.launch.env = LD_LIBRARY=./tezlib/lib/native
> -- tez.task.launch.env = LD_LIBRARY=./tezlib/lib/native
> When Hive commands run, they will attempt to load the native snappy libraries
> from the Tez tarball and will fail with:
> {code}
> Caused by: java.io.IOException: Unable to get CompressorType for codec
> (org.apache.hadoop.io.compress.SnappyCodec). This is most likely due to
> missing native libraries for the codec.
> at
> org.apache.tez.runtime.library.common.sort.impl.ExternalSorter.(ExternalSorter.java:217)
> {code}
> In order to fix this, the Tez tarball should include the native hadoop
> libraries as well:
> {code}
> ├── tez
> │ ├── lib
> │ │ ├── native
> │ │ │ ├── libhadoop.a
> │ │ │ ├── libhadoop.so -> libhadoop.so.1.0.0
> │ │ │ ├── libhadoop.so.1.0.0
> │ │ │ ├── libhadooppipes.a
> │ │ │ ├── libhadooputils.a
> │ │ │ ├── libhdfs.a
> │ │ │ ├── libhdfs.so -> libhdfs.so.0.0.0
> │ │ │ ├── libhdfs.so.0.0.0
> │ │ │ ├── libsnappy.so -> libsnappy.so.1.1.4
> │ │ │ ├── libsnappy.so.1 -> libsnappy.so.1.1.4
> │ │ │ └── libsnappy.so.1.1.4
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22445) Warn the user appropriately for default MySQL server install for Hive
[ https://issues.apache.org/jira/browse/AMBARI-22445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16254415#comment-16254415 ] Hudson commented on AMBARI-22445: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8398 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8398/]) AMBARI-22445. Warn the user appropriately for default MySQL server (vivekratnavel90: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8fe6ac4bd03739202a35f8862270be7dcec95421]) * (edit) ambari-web/app/views/common/controls_view.js * (edit) ambari-web/test/views/common/controls_view_test.js > Warn the user appropriately for default MySQL server install for Hive > - > > Key: AMBARI-22445 > URL: https://issues.apache.org/jira/browse/AMBARI-22445 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Blocker > Fix For: 2.6.1 > > Attachments: AMBARI-22445.v0.branch-2.6.patch > > > The mysql connector license is not compatible with Ambari's license and > Ambari no longer auto installs mysql-connector after AMBARI-22369. Warn the > user appropriately to install and setup mysql-connector to be used by Hive. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22445) Warn the user appropriately for default MySQL server install for Hive
[ https://issues.apache.org/jira/browse/AMBARI-22445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16254373#comment-16254373 ] Hudson commented on AMBARI-22445: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #458 (See [https://builds.apache.org/job/Ambari-branch-2.6/458/]) AMBARI-22445. Warn the user appropriately for default MySQL server (vivekratnavel90: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=822fe2d5aa02c6d7f1fafdf74b5c0e23cf657bbc]) * (edit) ambari-web/app/views/common/controls_view.js * (edit) ambari-web/test/views/common/controls_view_test.js > Warn the user appropriately for default MySQL server install for Hive > - > > Key: AMBARI-22445 > URL: https://issues.apache.org/jira/browse/AMBARI-22445 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Blocker > Fix For: 2.6.1 > > Attachments: AMBARI-22445.v0.branch-2.6.patch > > > The mysql connector license is not compatible with Ambari's license and > Ambari no longer auto installs mysql-connector after AMBARI-22369. Warn the > user appropriately to install and setup mysql-connector to be used by Hive. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22445) Warn the user appropriately for default MySQL server install for Hive
[ https://issues.apache.org/jira/browse/AMBARI-22445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-22445: Resolution: Fixed Status: Resolved (was: Patch Available) > Warn the user appropriately for default MySQL server install for Hive > - > > Key: AMBARI-22445 > URL: https://issues.apache.org/jira/browse/AMBARI-22445 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Blocker > Fix For: 2.6.1 > > Attachments: AMBARI-22445.v0.branch-2.6.patch > > > The mysql connector license is not compatible with Ambari's license and > Ambari no longer auto installs mysql-connector after AMBARI-22369. Warn the > user appropriately to install and setup mysql-connector to be used by Hive. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22445) Warn the user appropriately for default MySQL server install for Hive
[ https://issues.apache.org/jira/browse/AMBARI-22445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16254344#comment-16254344 ] Vivek Ratnavel Subramanian commented on AMBARI-22445: - Patch committed to: branch-2.6 - 822fe2d5aa02c6d7f1fafdf74b5c0e23cf657bbc trunk - 8fe6ac4bd03739202a35f8862270be7dcec95421 > Warn the user appropriately for default MySQL server install for Hive > - > > Key: AMBARI-22445 > URL: https://issues.apache.org/jira/browse/AMBARI-22445 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Blocker > Fix For: 2.6.1 > > Attachments: AMBARI-22445.v0.branch-2.6.patch > > > The mysql connector license is not compatible with Ambari's license and > Ambari no longer auto installs mysql-connector after AMBARI-22369. Warn the > user appropriately to install and setup mysql-connector to be used by Hive. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22459) IOP/HDP migration NN HA restart post Ambari upgrade fails
[
https://issues.apache.org/jira/browse/AMBARI-22459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16254348#comment-16254348
]
Hadoop QA commented on AMBARI-22459:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897851/AMBARI-22459.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12678//console
This message is automatically generated.
> IOP/HDP migration NN HA restart post Ambari upgrade fails
> -
>
> Key: AMBARI-22459
> URL: https://issues.apache.org/jira/browse/AMBARI-22459
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Di Li
>Assignee: Di Li
> Fix For: 2.6.1
>
> Attachments: AMBARI-22459.patch
>
>
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_select.py",
> line 109, in get_package_name
> package = get_packages(PACKAGE_SCOPE_STACK_SELECT, service_name,
> component_name)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_select.py",
> line 234, in get_packages
> raise Fail("The package {0} is not supported by this version of the
> stack-select tool.".format(package))
> resource_management.core.exceptions.Fail: The package hadoop-hdfs-zkfc is not
> supported by this version of the stack-select tool.
> Need your help in understanding expected behavior.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22459) IOP/HDP migration NN HA restart post Ambari upgrade fails
[
https://issues.apache.org/jira/browse/AMBARI-22459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Di Li updated AMBARI-22459:
---
Status: Patch Available (was: Open)
> IOP/HDP migration NN HA restart post Ambari upgrade fails
> -
>
> Key: AMBARI-22459
> URL: https://issues.apache.org/jira/browse/AMBARI-22459
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Di Li
>Assignee: Di Li
> Fix For: 2.6.1
>
> Attachments: AMBARI-22459.patch
>
>
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_select.py",
> line 109, in get_package_name
> package = get_packages(PACKAGE_SCOPE_STACK_SELECT, service_name,
> component_name)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_select.py",
> line 234, in get_packages
> raise Fail("The package {0} is not supported by this version of the
> stack-select tool.".format(package))
> resource_management.core.exceptions.Fail: The package hadoop-hdfs-zkfc is not
> supported by this version of the stack-select tool.
> Need your help in understanding expected behavior.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22459) IOP/HDP migration NN HA restart post Ambari upgrade fails
[
https://issues.apache.org/jira/browse/AMBARI-22459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Di Li updated AMBARI-22459:
---
Attachment: AMBARI-22459.patch
> IOP/HDP migration NN HA restart post Ambari upgrade fails
> -
>
> Key: AMBARI-22459
> URL: https://issues.apache.org/jira/browse/AMBARI-22459
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Di Li
>Assignee: Di Li
> Fix For: 2.6.1
>
> Attachments: AMBARI-22459.patch
>
>
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_select.py",
> line 109, in get_package_name
> package = get_packages(PACKAGE_SCOPE_STACK_SELECT, service_name,
> component_name)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_select.py",
> line 234, in get_packages
> raise Fail("The package {0} is not supported by this version of the
> stack-select tool.".format(package))
> resource_management.core.exceptions.Fail: The package hadoop-hdfs-zkfc is not
> supported by this version of the stack-select tool.
> Need your help in understanding expected behavior.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-22459) IOP/HDP migration NN HA restart post Ambari upgrade fails
[
https://issues.apache.org/jira/browse/AMBARI-22459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Di Li reassigned AMBARI-22459:
--
Assignee: Di Li
> IOP/HDP migration NN HA restart post Ambari upgrade fails
> -
>
> Key: AMBARI-22459
> URL: https://issues.apache.org/jira/browse/AMBARI-22459
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Di Li
>Assignee: Di Li
> Fix For: 2.6.1
>
>
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_select.py",
> line 109, in get_package_name
> package = get_packages(PACKAGE_SCOPE_STACK_SELECT, service_name,
> component_name)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_select.py",
> line 234, in get_packages
> raise Fail("The package {0} is not supported by this version of the
> stack-select tool.".format(package))
> resource_management.core.exceptions.Fail: The package hadoop-hdfs-zkfc is not
> supported by this version of the stack-select tool.
> Need your help in understanding expected behavior.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22459) IOP/HDP migration NN HA restart post Ambari upgrade fails
Di Li created AMBARI-22459:
--
Summary: IOP/HDP migration NN HA restart post Ambari upgrade fails
Key: AMBARI-22459
URL: https://issues.apache.org/jira/browse/AMBARI-22459
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.6.0
Reporter: Di Li
Fix For: 2.6.1
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_select.py",
line 109, in get_package_name
package = get_packages(PACKAGE_SCOPE_STACK_SELECT, service_name,
component_name)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_select.py",
line 234, in get_packages
raise Fail("The package {0} is not supported by this version of the
stack-select tool.".format(package))
resource_management.core.exceptions.Fail: The package hadoop-hdfs-zkfc is not
supported by this version of the stack-select tool.
Need your help in understanding expected behavior.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22444) Add Native Libraries To Tez Tarball
[
https://issues.apache.org/jira/browse/AMBARI-22444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16254238#comment-16254238
]
Hudson commented on AMBARI-22444:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8397 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8397/])
AMBARI-22444 - Add Native Libraries To Tez Tarball (jonathanhurley) (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c67a3246e2121c6977094e10cdb1414f45cf1482])
* (edit)
ambari-common/src/main/python/resource_management/libraries/functions/copy_tarball.py
* (edit)
ambari-common/src/main/python/resource_management/libraries/functions/tar_archive.py
* (edit) ambari-server/src/test/python/stacks/2.1/FALCON/test_falcon_server.py
> Add Native Libraries To Tez Tarball
> ---
>
> Key: AMBARI-22444
> URL: https://issues.apache.org/jira/browse/AMBARI-22444
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22444.patch
>
>
> As part of the investigation for getting patch upgrades working in Ambari
> 2.6.1, it was determined that the Tez tarball will need to have the hadoop
> native libraries added to it so that they can be detected from the tarball.
> STR:
> - Install ZK, MapR, Tez, Yarn, Hive
> - Enable a non-LZO codec, like Snappy
> - Patch Hive to a new version
> - Change the following properties in {{tez-site}}:
> -- tez.am.launch.env = LD_LIBRARY=./tezlib/lib/native
> -- tez.task.launch.env = LD_LIBRARY=./tezlib/lib/native
> When Hive commands run, they will attempt to load the native snappy libraries
> from the Tez tarball and will fail with:
> {code}
> Caused by: java.io.IOException: Unable to get CompressorType for codec
> (org.apache.hadoop.io.compress.SnappyCodec). This is most likely due to
> missing native libraries for the codec.
> at
> org.apache.tez.runtime.library.common.sort.impl.ExternalSorter.(ExternalSorter.java:217)
> {code}
> In order to fix this, the Tez tarball should include the native hadoop
> libraries as well:
> {code}
> ├── tez
> │ ├── lib
> │ │ ├── native
> │ │ │ ├── libhadoop.a
> │ │ │ ├── libhadoop.so -> libhadoop.so.1.0.0
> │ │ │ ├── libhadoop.so.1.0.0
> │ │ │ ├── libhadooppipes.a
> │ │ │ ├── libhadooputils.a
> │ │ │ ├── libhdfs.a
> │ │ │ ├── libhdfs.so -> libhdfs.so.0.0.0
> │ │ │ ├── libhdfs.so.0.0.0
> │ │ │ ├── libsnappy.so -> libsnappy.so.1.1.4
> │ │ │ ├── libsnappy.so.1 -> libsnappy.so.1.1.4
> │ │ │ └── libsnappy.so.1.1.4
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22458) NMP Trap should have sysuptime field filled
amarnath reddy pappu created AMBARI-22458: - Summary: NMP Trap should have sysuptime field filled Key: AMBARI-22458 URL: https://issues.apache.org/jira/browse/AMBARI-22458 Project: Ambari Issue Type: Improvement Components: ambari-server Affects Versions: 2.6.0 Reporter: amarnath reddy pappu Currently Ambari SNMP traps does not have sysuptime field - some of the SNMP processing tool/application drops (considers invalid)the traps if it does not find sysuptime field. RFC https://tools.ietf.org/search/rfc3416 does not say whether it is required/option field - but customers expecting that Ambari should fill this. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22444) Add Native Libraries To Tez Tarball
[
https://issues.apache.org/jira/browse/AMBARI-22444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16254084#comment-16254084
]
Hudson commented on AMBARI-22444:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #457 (See
[https://builds.apache.org/job/Ambari-branch-2.6/457/])
AMBARI-22444 - Add Native Libraries To Tez Tarball (jonathanhurley) (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6e247b3f5c06bb108687e8278f474ed3d6330ade])
* (edit) ambari-server/src/test/python/stacks/2.1/FALCON/test_falcon_server.py
* (edit)
ambari-common/src/main/python/resource_management/libraries/functions/copy_tarball.py
* (edit)
ambari-common/src/main/python/resource_management/libraries/functions/tar_archive.py
> Add Native Libraries To Tez Tarball
> ---
>
> Key: AMBARI-22444
> URL: https://issues.apache.org/jira/browse/AMBARI-22444
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22444.patch
>
>
> As part of the investigation for getting patch upgrades working in Ambari
> 2.6.1, it was determined that the Tez tarball will need to have the hadoop
> native libraries added to it so that they can be detected from the tarball.
> STR:
> - Install ZK, MapR, Tez, Yarn, Hive
> - Enable a non-LZO codec, like Snappy
> - Patch Hive to a new version
> - Change the following properties in {{tez-site}}:
> -- tez.am.launch.env = LD_LIBRARY=./tezlib/lib/native
> -- tez.task.launch.env = LD_LIBRARY=./tezlib/lib/native
> When Hive commands run, they will attempt to load the native snappy libraries
> from the Tez tarball and will fail with:
> {code}
> Caused by: java.io.IOException: Unable to get CompressorType for codec
> (org.apache.hadoop.io.compress.SnappyCodec). This is most likely due to
> missing native libraries for the codec.
> at
> org.apache.tez.runtime.library.common.sort.impl.ExternalSorter.(ExternalSorter.java:217)
> {code}
> In order to fix this, the Tez tarball should include the native hadoop
> libraries as well:
> {code}
> ├── tez
> │ ├── lib
> │ │ ├── native
> │ │ │ ├── libhadoop.a
> │ │ │ ├── libhadoop.so -> libhadoop.so.1.0.0
> │ │ │ ├── libhadoop.so.1.0.0
> │ │ │ ├── libhadooppipes.a
> │ │ │ ├── libhadooputils.a
> │ │ │ ├── libhdfs.a
> │ │ │ ├── libhdfs.so -> libhdfs.so.0.0.0
> │ │ │ ├── libhdfs.so.0.0.0
> │ │ │ ├── libsnappy.so -> libsnappy.so.1.1.4
> │ │ │ ├── libsnappy.so.1 -> libsnappy.so.1.1.4
> │ │ │ └── libsnappy.so.1.1.4
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22444) Add Native Libraries To Tez Tarball
[
https://issues.apache.org/jira/browse/AMBARI-22444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-22444:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Add Native Libraries To Tez Tarball
> ---
>
> Key: AMBARI-22444
> URL: https://issues.apache.org/jira/browse/AMBARI-22444
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22444.patch
>
>
> As part of the investigation for getting patch upgrades working in Ambari
> 2.6.1, it was determined that the Tez tarball will need to have the hadoop
> native libraries added to it so that they can be detected from the tarball.
> STR:
> - Install ZK, MapR, Tez, Yarn, Hive
> - Enable a non-LZO codec, like Snappy
> - Patch Hive to a new version
> - Change the following properties in {{tez-site}}:
> -- tez.am.launch.env = LD_LIBRARY=./tezlib/lib/native
> -- tez.task.launch.env = LD_LIBRARY=./tezlib/lib/native
> When Hive commands run, they will attempt to load the native snappy libraries
> from the Tez tarball and will fail with:
> {code}
> Caused by: java.io.IOException: Unable to get CompressorType for codec
> (org.apache.hadoop.io.compress.SnappyCodec). This is most likely due to
> missing native libraries for the codec.
> at
> org.apache.tez.runtime.library.common.sort.impl.ExternalSorter.(ExternalSorter.java:217)
> {code}
> In order to fix this, the Tez tarball should include the native hadoop
> libraries as well:
> {code}
> ├── tez
> │ ├── lib
> │ │ ├── native
> │ │ │ ├── libhadoop.a
> │ │ │ ├── libhadoop.so -> libhadoop.so.1.0.0
> │ │ │ ├── libhadoop.so.1.0.0
> │ │ │ ├── libhadooppipes.a
> │ │ │ ├── libhadooputils.a
> │ │ │ ├── libhdfs.a
> │ │ │ ├── libhdfs.so -> libhdfs.so.0.0.0
> │ │ │ ├── libhdfs.so.0.0.0
> │ │ │ ├── libsnappy.so -> libsnappy.so.1.1.4
> │ │ │ ├── libsnappy.so.1 -> libsnappy.so.1.1.4
> │ │ │ └── libsnappy.so.1.1.4
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22455) Ambari Logsearch Web unit tests are sometimes failing
[
https://issues.apache.org/jira/browse/AMBARI-22455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16254008#comment-16254008
]
Hudson commented on AMBARI-22455:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8396 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8396/])
AMBARI-22455 Ambari Logsearch Web unit tests are sometimes failing.
(ababiichuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2d81d49fb3cc5fefbed079e7994cea7b41c5a125])
* (edit)
ambari-logsearch/ambari-logsearch-web/src/app/services/auth.service.spec.ts
> Ambari Logsearch Web unit tests are sometimes failing
> -
>
> Key: AMBARI-22455
> URL: https://issues.apache.org/jira/browse/AMBARI-22455
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-22455.patch
>
>
> Ambari Logsearch Web unit tests fail on CI builds:
> {code}
> [INFO] PhantomJS 2.1.1 (Linux 0.0.0) UtilsService #isEqual() undefined values
> equality FAILED
> [INFO]Expected false to be true.
> [INFO]http://localhost:9876/_karma_webpack_/main.bundle.js:9369:31
> [INFO]
> __tryOrUnsub@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55648:20
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55595:34
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55535:30
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57133:34
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57437:30
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55243:29
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:54628:35
> [INFO]http://localhost:9876/_karma_webpack_/vendor.bundle.js:415:62
> [INFO]
> __tryOrUnsub@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55648:20
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55595:34
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55535:30
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> _tryNext@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58081:30
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58068:33
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58466:38
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> observe@http://localhost:9876/_karma_webpack_/vendor.bundle.js:54715:54
> [INFO]
> dispatch@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57869:29
> [INFO]
> _execute@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58652:22
> [INFO]
> execute@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58781:26
> [INFO]
> flush@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58726:39
> [INFO]
> schedule@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58775:29
> [INFO]
> schedule@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55175:61
> [INFO]
> scheduleMessage@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57873:41
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57876:29
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55243:29
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:54628:35
> [INFO]
> dispatch@http://localhost:9876/_karma_webpack_/vendor.bundle.js:464:30
> [INFO]
> setParameters@http://localhost:9876/_karma_webpack_/main.bundle.js:737:28
> [INFO]
> setParameter@http://localhost:9876/_karma_webpack_/main.bundle.js:734:27
> [INFO]
> setLoginInProgressAppState@http://localhost:9876/_karma_webpack_/main.bundle.js:9452:35
> [INFO]
> onLoginResponse@http://localhost:9876/_karma_webpack_/main.bundle.js:9468:44
> [INFO]http://localhost:9876/_karma_webpack_/main.bundle.js:9433:69
> [INFO]
> __tryOrUnsub@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55648:20
> [INFO]
>
[jira] [Commented] (AMBARI-22448) Oozie Jobs on Hive Fail With Missing Tarball
[
https://issues.apache.org/jira/browse/AMBARI-22448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16254010#comment-16254010
]
Hudson commented on AMBARI-22448:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8396 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8396/])
AMBARI-22448. Oozie Jobs on Hive Fail With Missing Tarball (ncole) (ncole:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=99152d3257a0eb4180283fa882f8283a3eaba196])
* (edit)
ambari-server/src/main/resources/stacks/HDP/3.0/properties/stack_packages.json
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.0.6/properties/stack_packages.json
> Oozie Jobs on Hive Fail With Missing Tarball
>
>
> Key: AMBARI-22448
> URL: https://issues.apache.org/jira/browse/AMBARI-22448
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.6 1
>
> Attachments: AMBARI-22448.patch
>
>
> STR:
> - Install an HDP 2.6.3.0 cluster with Oozie, HIve, MapR, Yarn, ZK, HDFS
> - Patch only Oozie to a new version, such as 2.6.3.1-1
> - Attempt to run an Oozie job on Hive
> The workflow job will fail with:
> {code}
> org.apache.oozie.action.ActionExecutorException: JA008: File does not exist:
> hdfs://jhurley-pu-1.openstacklocal:8020/hdp/apps/2.6.3.1-1/mapreduce/mapreduce.tar.gz
> at
> org.apache.oozie.action.ActionExecutor.convertExceptionHelper(ActionExecutor.java:457)
> at
> org.apache.oozie.action.ActionExecutor.convertException(ActionExecutor.java:441)
> at
> org.apache.oozie.action.hadoop.JavaActionExecutor.submitLauncher(JavaActionExecutor.java:1211)
> at
> org.apache.oozie.action.hadoop.JavaActionExecutor.start(JavaActionExecutor.java:1382)
> at
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:234)
> at
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:65)
> at org.apache.oozie.command.XCommand.call(XCommand.java:287)
> at
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:331)
> at
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:260)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:178)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> This is because Oozie appears to be trying to use a version of the MapReduce
> tarball which matches its version. However, since it does not ship its
> version, it cannot find it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22418) Make Ambari configuration API consistent with existing API.
[ https://issues.apache.org/jira/browse/AMBARI-22418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16254009#comment-16254009 ] Hudson commented on AMBARI-22418: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8396 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8396/]) AMBARI-22418. Make Ambari configuration API consistent with existing (rlevas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3f2743b58ba65c4bdc7d37df5348d17124bf305a]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/events/listeners/alerts/AlertStateChangedListener.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/ldap/LdapModuleFunctionalTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/ldap/LdapConfigurationRequest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/ldap/service/ads/DefaultLdapConfigurationServiceTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/MaintenanceStateHelper.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/ldap/domain/AmbariLdapConfiguration.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/ResourceProviderFactory.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/ldap/domain/AmbariLdapConfigurationFactory.java * (delete) ambari-server/src/main/java/org/apache/ambari/server/api/services/AmbariConfigurationResponseSwagger.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/metadata/AmbariServiceAlertDefinitions.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/services/AmbariServerAlertService.java * (add) ambari-server/src/main/java/org/apache/ambari/server/controller/RootComponent.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RootServiceComponentResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RootServiceComponentPropertyProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/dao/AlertDefinitionDAO.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java * (add) ambari-server/src/main/java/org/apache/ambari/server/controller/RootService.java * (delete) ambari-server/src/main/java/org/apache/ambari/server/api/services/AmbariConfigurationService.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/alerts/AlertReceivedListenerTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/events/listeners/alerts/AlertReceivedListener.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/metadata/AgentAlertDefinitionsTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/RootServiceResponseFactoryTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/AmbariMetaInfo.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/RootServiceService.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/ldap/LdapConfigurationService.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RootServiceComponentResourceProviderTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/ldap/service/ads/DefaultLdapAttributeDetectionServiceTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AbstractControllerResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/stackadvisor/commands/StackAdvisorCommand.java * (delete) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AmbariConfigurationResourceProviderTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RootServiceComponentPropertyProviderTest.java * (add) ambari-server/src/main/java/org/apache/ambari/server/api/services/RootServiceComponentConfigurationRequestSwagger.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/dao/AlertDispatchDAO.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/orm/dao/AlertDefinitionDAOTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/spi/Resource.java * (delete) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AmbariConfigurationResourceProvider.java * (add) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RootServiceComponentConfigurationResourceProviderTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/ldap/domain/TestAmbariLdapConfigurationFactory.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariManagementControllerTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/resources/ResourceInstanceFactoryImpl.java * (add)
[jira] [Updated] (AMBARI-22445) Warn the user appropriately for default MySQL server install for Hive
[ https://issues.apache.org/jira/browse/AMBARI-22445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-22445: Attachment: AMBARI-22445.v0.branch-2.6.patch > Warn the user appropriately for default MySQL server install for Hive > - > > Key: AMBARI-22445 > URL: https://issues.apache.org/jira/browse/AMBARI-22445 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Blocker > Fix For: 2.6.1 > > Attachments: AMBARI-22445.v0.branch-2.6.patch > > > The mysql connector license is not compatible with Ambari's license and > Ambari no longer auto installs mysql-connector after AMBARI-22369. Warn the > user appropriately to install and setup mysql-connector to be used by Hive. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22445) Warn the user appropriately for default MySQL server install for Hive
[ https://issues.apache.org/jira/browse/AMBARI-22445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-22445: Status: Patch Available (was: In Progress) > Warn the user appropriately for default MySQL server install for Hive > - > > Key: AMBARI-22445 > URL: https://issues.apache.org/jira/browse/AMBARI-22445 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Blocker > Fix For: 2.6.1 > > Attachments: AMBARI-22445.v0.branch-2.6.patch > > > The mysql connector license is not compatible with Ambari's license and > Ambari no longer auto installs mysql-connector after AMBARI-22369. Warn the > user appropriately to install and setup mysql-connector to be used by Hive. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22448) Oozie Jobs on Hive Fail With Missing Tarball
[
https://issues.apache.org/jira/browse/AMBARI-22448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253992#comment-16253992
]
Hudson commented on AMBARI-22448:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #456 (See
[https://builds.apache.org/job/Ambari-branch-2.6/456/])
AMBARI-22448. Oozie Jobs on Hive Fail With Missing Tarball (ncole) (ncole:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=56079f2979bc4e9794ea1f52cbfa50faf11c0510])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.0.6/properties/stack_packages.json
> Oozie Jobs on Hive Fail With Missing Tarball
>
>
> Key: AMBARI-22448
> URL: https://issues.apache.org/jira/browse/AMBARI-22448
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.6 1
>
> Attachments: AMBARI-22448.patch
>
>
> STR:
> - Install an HDP 2.6.3.0 cluster with Oozie, HIve, MapR, Yarn, ZK, HDFS
> - Patch only Oozie to a new version, such as 2.6.3.1-1
> - Attempt to run an Oozie job on Hive
> The workflow job will fail with:
> {code}
> org.apache.oozie.action.ActionExecutorException: JA008: File does not exist:
> hdfs://jhurley-pu-1.openstacklocal:8020/hdp/apps/2.6.3.1-1/mapreduce/mapreduce.tar.gz
> at
> org.apache.oozie.action.ActionExecutor.convertExceptionHelper(ActionExecutor.java:457)
> at
> org.apache.oozie.action.ActionExecutor.convertException(ActionExecutor.java:441)
> at
> org.apache.oozie.action.hadoop.JavaActionExecutor.submitLauncher(JavaActionExecutor.java:1211)
> at
> org.apache.oozie.action.hadoop.JavaActionExecutor.start(JavaActionExecutor.java:1382)
> at
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:234)
> at
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:65)
> at org.apache.oozie.command.XCommand.call(XCommand.java:287)
> at
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:331)
> at
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:260)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:178)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> This is because Oozie appears to be trying to use a version of the MapReduce
> tarball which matches its version. However, since it does not ship its
> version, it cannot find it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22454) ambari-server upgrade to 2.6.1 should surface the GPL agreement
[ https://issues.apache.org/jira/browse/AMBARI-22454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253972#comment-16253972 ] Siddharth Wagle commented on AMBARI-22454: -- Few more points: - The users who do not use lzo should not be prompted - Thereby the flow of control should check whether user has lzo enabled and only then surface the agreement - If the user chooses no, we need to fail the upgrade and ask user to disable lzo > ambari-server upgrade to 2.6.1 should surface the GPL agreement > --- > > Key: AMBARI-22454 > URL: https://issues.apache.org/jira/browse/AMBARI-22454 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.6.1 > > Attachments: AMBARI-22454.patch > > > . -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22424) Quicklinks for OneFS
[
https://issues.apache.org/jira/browse/AMBARI-22424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253949#comment-16253949
]
Hadoop QA commented on AMBARI-22424:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897789/AMBARI-22424.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12676//console
This message is automatically generated.
> Quicklinks for OneFS
>
>
> Key: AMBARI-22424
> URL: https://issues.apache.org/jira/browse/AMBARI-22424
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Attila Magyar
>Assignee: Attila Magyar
> Fix For: 3.0.0
>
> Attachments: AMBARI-22424.patch
>
>
> The OneFS mpack should hava a quicklink.json. A quicklink should point to the
> OneFS web admin UI.
> Currently only master components can have quicklinks. The OneFS is a client
> only service.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22452) Ambari install wizard throws HTTP 400 on the assign master page due to err in he ambari service advisor class
[ https://issues.apache.org/jira/browse/AMBARI-22452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-22452: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari install wizard throws HTTP 400 on the assign master page due to err in > he ambari service advisor class > - > > Key: AMBARI-22452 > URL: https://issues.apache.org/jira/browse/AMBARI-22452 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-22452.patch > > > Ambari install wizard throws HTTP 400 on the assign master page due to err in > he ambari service advisor class -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22448) Oozie Jobs on Hive Fail With Missing Tarball
[
https://issues.apache.org/jira/browse/AMBARI-22448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole updated AMBARI-22448:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Oozie Jobs on Hive Fail With Missing Tarball
>
>
> Key: AMBARI-22448
> URL: https://issues.apache.org/jira/browse/AMBARI-22448
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.6 1
>
> Attachments: AMBARI-22448.patch
>
>
> STR:
> - Install an HDP 2.6.3.0 cluster with Oozie, HIve, MapR, Yarn, ZK, HDFS
> - Patch only Oozie to a new version, such as 2.6.3.1-1
> - Attempt to run an Oozie job on Hive
> The workflow job will fail with:
> {code}
> org.apache.oozie.action.ActionExecutorException: JA008: File does not exist:
> hdfs://jhurley-pu-1.openstacklocal:8020/hdp/apps/2.6.3.1-1/mapreduce/mapreduce.tar.gz
> at
> org.apache.oozie.action.ActionExecutor.convertExceptionHelper(ActionExecutor.java:457)
> at
> org.apache.oozie.action.ActionExecutor.convertException(ActionExecutor.java:441)
> at
> org.apache.oozie.action.hadoop.JavaActionExecutor.submitLauncher(JavaActionExecutor.java:1211)
> at
> org.apache.oozie.action.hadoop.JavaActionExecutor.start(JavaActionExecutor.java:1382)
> at
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:234)
> at
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:65)
> at org.apache.oozie.command.XCommand.call(XCommand.java:287)
> at
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:331)
> at
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:260)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:178)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> This is because Oozie appears to be trying to use a version of the MapReduce
> tarball which matches its version. However, since it does not ship its
> version, it cannot find it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22457) Conditionally Install LZO packages through Ambari
[ https://issues.apache.org/jira/browse/AMBARI-22457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-22457: - Attachment: GPL Use Cases.jpg > Conditionally Install LZO packages through Ambari > - > > Key: AMBARI-22457 > URL: https://issues.apache.org/jira/browse/AMBARI-22457 > Project: Ambari > Issue Type: Epic > Components: ambari-agent, ambari-server >Affects Versions: 2.6.1 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Fix For: 2.6.1 > > Attachments: GPL Use Cases.jpg > > > LZO should only be installed if the user has met the requirements to allow > Ambari to download and install them. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22457) Conditionally Install LZO packages through Ambari
Siddharth Wagle created AMBARI-22457: Summary: Conditionally Install LZO packages through Ambari Key: AMBARI-22457 URL: https://issues.apache.org/jira/browse/AMBARI-22457 Project: Ambari Issue Type: Epic Components: ambari-agent, ambari-server Affects Versions: 2.6.1 Reporter: Siddharth Wagle Assignee: Siddharth Wagle Priority: Critical Fix For: 2.6.1 LZO should only be installed if the user has met the requirements to allow Ambari to download and install them. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (AMBARI-22454) ambari-server upgrade to 2.6.1 should surface the GPL agreement
[ https://issues.apache.org/jira/browse/AMBARI-22454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253861#comment-16253861 ] Siddharth Wagle edited comment on AMBARI-22454 at 11/15/17 5:49 PM: [~aonishuk] Ther are a bunch of LOG statements that seem to be debugging purpose only, can you please remove them? Minor nit: Typo in var -> compressioonCodecs and "Cannot proceed upgrade please accept GPL license or disable lzo from your clusters." Should be "Cannot proceed with upgrade..." was (Author: swagle): [~aonishuk] Ther are a bunch of LOG statements that seem to be debugging purpose only, can you please remove them? Minor nit: Typo in var -> compressioonCodecs > ambari-server upgrade to 2.6.1 should surface the GPL agreement > --- > > Key: AMBARI-22454 > URL: https://issues.apache.org/jira/browse/AMBARI-22454 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.6.1 > > Attachments: AMBARI-22454.patch > > > . -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (AMBARI-22454) ambari-server upgrade to 2.6.1 should surface the GPL agreement
[ https://issues.apache.org/jira/browse/AMBARI-22454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253861#comment-16253861 ] Siddharth Wagle edited comment on AMBARI-22454 at 11/15/17 5:48 PM: [~aonishuk] Ther are a bunch of LOG statements that seem to be debugging purpose only, can you please remove them? Minor nit: Typo in var -> compressioonCodecs was (Author: swagle): [~aonishuk] Ther are a bunch of LOG statements that seem to be debugging purpose only, can you please remove them? > ambari-server upgrade to 2.6.1 should surface the GPL agreement > --- > > Key: AMBARI-22454 > URL: https://issues.apache.org/jira/browse/AMBARI-22454 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.6.1 > > Attachments: AMBARI-22454.patch > > > . -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22454) ambari-server upgrade to 2.6.1 should surface the GPL agreement
[ https://issues.apache.org/jira/browse/AMBARI-22454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253861#comment-16253861 ] Siddharth Wagle commented on AMBARI-22454: -- [~aonishuk] Ther are a bunch of LOG statements that seem to be debugging purpose only, can you please remove them? > ambari-server upgrade to 2.6.1 should surface the GPL agreement > --- > > Key: AMBARI-22454 > URL: https://issues.apache.org/jira/browse/AMBARI-22454 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.6.1 > > Attachments: AMBARI-22454.patch > > > . -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22418) Make Ambari configuration API consistent with existing API.
[
https://issues.apache.org/jira/browse/AMBARI-22418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-22418:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
{noformat}
commit 3f2743b58ba65c4bdc7d37df5348d17124bf305a
Author: Robert Levas
Date: Wed Nov 15 12:11:34 2017 -0500
{noformat}
> Make Ambari configuration API consistent with existing API.
> ---
>
> Key: AMBARI-22418
> URL: https://issues.apache.org/jira/browse/AMBARI-22418
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Fix For: 3.0.0
>
> Attachments: AMBARI-22418_trunk_01.patch
>
>
> Make Ambari configuration API consistent with existing API.
> The current API entry point (as of AMBARI-21307) is
> {{/api/v1/ambariconfigs}}. This should be more inline with the existing entry
> point for Ambari server related data...
> {{/api/v1/services/AMBARI/components/AMBARI_SERVER}}.
> The new API entry point for Ambari server related configuration data should
> be {{/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations}}.
> Example Rest API calls:
> *Create/Set configuration*
> Used to create a new or explicitly set properties an existing Ambari Server
> configuration
> {noformat:title=URL}
> POST /api/v1/services/AMBARI/components/AMBARI_SERVER/configurations
> {noformat}
> {code:title=Payload}
> {
> "Configuration": {
> "category" : "ldap-configuration",
> "properties": {
> "ambari.ldap.bindanonymously": "true",
> "ambari.ldap.server.port": "389",
> "ambari.ldap.base.dn": "dc=example,dc=com",
> "ambari.ldap.user.object.class":"person",
> "ambari.ldap.user.name.attribute":"uid",
> "ambari.ldap.user.search.base": "dc=example,dc=com",
> "ambari.ldap.group.object.class":"groupOfUniqueNames",
> "ambari.ldap.group.name.attribute":"cn",
> "ambari.ldap.group.member.attribute":"uniqueMember",
> "ambari.ldap.group.search.base": "dc=example,dc=com"
> }
> }
> }
> {code}
> *Update configuration*
> Used to update existing properties or add new properties to an existing
> Ambari Server configuration
> {noformat:title=URL}
> PUT
> /api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/ldap-configuration
> {noformat}
> {code:title=Payload}
> {
> "Configuration": {
> "properties": {
> "ambari.ldap.bindanonymously": "true",
> "ambari.ldap.server.port": "389",
> "ambari.ldap.base.dn": "dc=example,dc=com",
> "ambari.ldap.user.object.class":"person",
> "ambari.ldap.user.name.attribute":"uid",
> "ambari.ldap.user.search.base": "dc=example,dc=com",
> "ambari.ldap.group.object.class":"groupOfUniqueNames",
> "ambari.ldap.group.name.attribute":"cn",
> "ambari.ldap.group.member.attribute":"uniqueMember",
> "ambari.ldap.group.search.base": "dc=example,dc=com"
> }
> }
> }
> {code}
> *Delete configuration*
> Deletes an existing Ambari Server configuration
> {noformat:title=URL}
> DELETE
> /api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/ldap-configuration
> {noformat}
> *Get configurations*
> Used to retrieve a list of the existing Ambari Server configurations
> {noformat:title=URL}
> GET /api/v1/services/AMBARI/components/AMBARI_SERVER/configurations
> {noformat}
> {code:title=Response}
> {
> "href" :
> "http://c6401.ambari.apache.org:8080/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations;,
> "items" : [
> {
> "href" :
> "http://c6401.ambari.apache.org:8080/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/ldap-configuration;,
> "Configuration" : {
> "category" : "ldap-configuration",
> "component_name" : "AMBARI_SERVER",
> "service_name" : "AMBARI"
> }
> }
> ]
> }
> {code}
> *Get configuration*
> Used to retrieve a the details about an existing Ambari Server configuration
> {noformat:title=URL}
> GET
> /api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/ldap-configuration
> {noformat}
> {code:title=Response}
> {
> "href" :
> "http://c6401.ambari.apache.org:8080/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/ldap-configuration;,
> "Configuration" : {
> "category" : "ldap-configuration",
> "component_name" : "AMBARI_SERVER",
> "service_name" : "AMBARI",
> "properties" : {
> "ambari.ldap.base.dn" : "dc=example,dc=com",
> "ambari.ldap.bindanonymously" : "true",
> "ambari.ldap.group.member.attribute" : "uniqueMember",
> "ambari.ldap.group.name.attribute" : "cn",
>
[jira] [Resolved] (AMBARI-22450) Log Search: reference Log Feeder IDE/maven dev setup in README.md
[ https://issues.apache.org/jira/browse/AMBARI-22450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-22450. --- Resolution: Fixed > Log Search: reference Log Feeder IDE/maven dev setup in README.md > - > > Key: AMBARI-22450 > URL: https://issues.apache.org/jira/browse/AMBARI-22450 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 3.0.0 > > > simple README.md update -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22456) Installing custom service hangs at install step for 15-20 mins when having to install dependencies.
Christopher Jackson created AMBARI-22456: Summary: Installing custom service hangs at install step for 15-20 mins when having to install dependencies. Key: AMBARI-22456 URL: https://issues.apache.org/jira/browse/AMBARI-22456 Project: Ambari Issue Type: Bug Affects Versions: 2.5.0, 2.6.0 Environment: CENTOS7, RHEL7 Reporter: Christopher Jackson When installing a custom service that has a client component that has several dependencies on clients of other services, for example: ``` HDFS/HDFS_CLIENT host true ``` the installation step in the install service wizard hangs for several minutes (10-20mins) while it installs all those clients on the various nodes in the cluster. The UI reports `Preparing to install ` and sits at 0% until all the dependency clients are installed. Once the dependencies are installed progress begins on installing the components of the custom service and the UI shows progress correctly. I would not expect this behavior. I would expect the UI to report that it is making progress installing the clients that are dependencies so that it does not appear that the installation has hung. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22424) Quicklinks for OneFS
[ https://issues.apache.org/jira/browse/AMBARI-22424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar updated AMBARI-22424: --- Attachment: AMBARI-22424.patch > Quicklinks for OneFS > > > Key: AMBARI-22424 > URL: https://issues.apache.org/jira/browse/AMBARI-22424 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Attila Magyar >Assignee: Attila Magyar > Fix For: 3.0.0 > > Attachments: AMBARI-22424.patch > > > The OneFS mpack should hava a quicklink.json. A quicklink should point to the > OneFS web admin UI. > Currently only master components can have quicklinks. The OneFS is a client > only service. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22424) Quicklinks for OneFS
[ https://issues.apache.org/jira/browse/AMBARI-22424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar updated AMBARI-22424: --- Status: Patch Available (was: Open) > Quicklinks for OneFS > > > Key: AMBARI-22424 > URL: https://issues.apache.org/jira/browse/AMBARI-22424 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Attila Magyar >Assignee: Attila Magyar > Fix For: 3.0.0 > > Attachments: AMBARI-22424.patch > > > The OneFS mpack should hava a quicklink.json. A quicklink should point to the > OneFS web admin UI. > Currently only master components can have quicklinks. The OneFS is a client > only service. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22455) Ambari Logsearch Web unit tests are sometimes failing
[
https://issues.apache.org/jira/browse/AMBARI-22455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Babiichuk updated AMBARI-22455:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
> Ambari Logsearch Web unit tests are sometimes failing
> -
>
> Key: AMBARI-22455
> URL: https://issues.apache.org/jira/browse/AMBARI-22455
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-22455.patch
>
>
> Ambari Logsearch Web unit tests fail on CI builds:
> {code}
> [INFO] PhantomJS 2.1.1 (Linux 0.0.0) UtilsService #isEqual() undefined values
> equality FAILED
> [INFO]Expected false to be true.
> [INFO]http://localhost:9876/_karma_webpack_/main.bundle.js:9369:31
> [INFO]
> __tryOrUnsub@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55648:20
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55595:34
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55535:30
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57133:34
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57437:30
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55243:29
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:54628:35
> [INFO]http://localhost:9876/_karma_webpack_/vendor.bundle.js:415:62
> [INFO]
> __tryOrUnsub@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55648:20
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55595:34
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55535:30
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> _tryNext@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58081:30
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58068:33
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58466:38
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> observe@http://localhost:9876/_karma_webpack_/vendor.bundle.js:54715:54
> [INFO]
> dispatch@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57869:29
> [INFO]
> _execute@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58652:22
> [INFO]
> execute@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58781:26
> [INFO]
> flush@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58726:39
> [INFO]
> schedule@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58775:29
> [INFO]
> schedule@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55175:61
> [INFO]
> scheduleMessage@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57873:41
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57876:29
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55243:29
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:54628:35
> [INFO]
> dispatch@http://localhost:9876/_karma_webpack_/vendor.bundle.js:464:30
> [INFO]
> setParameters@http://localhost:9876/_karma_webpack_/main.bundle.js:737:28
> [INFO]
> setParameter@http://localhost:9876/_karma_webpack_/main.bundle.js:734:27
> [INFO]
> setLoginInProgressAppState@http://localhost:9876/_karma_webpack_/main.bundle.js:9452:35
> [INFO]
> onLoginResponse@http://localhost:9876/_karma_webpack_/main.bundle.js:9468:44
> [INFO]http://localhost:9876/_karma_webpack_/main.bundle.js:9433:69
> [INFO]
> __tryOrUnsub@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55648:20
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55595:34
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55535:30
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> observe@http://localhost:9876/_karma_webpack_/vendor.bundle.js:54715:54
>
[jira] [Commented] (AMBARI-22450) Log Search: reference Log Feeder IDE/maven dev setup in README.md
[ https://issues.apache.org/jira/browse/AMBARI-22450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253725#comment-16253725 ] Hudson commented on AMBARI-22450: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8395 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8395/]) AMBARI-22450. Log Search: reference Log Feeder IDE/maven dev setup in (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1a99da4470d3ce1d928ab56f1a4c2845f940ef53]) * (edit) ambari-logsearch/README.md > Log Search: reference Log Feeder IDE/maven dev setup in README.md > - > > Key: AMBARI-22450 > URL: https://issues.apache.org/jira/browse/AMBARI-22450 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 3.0.0 > > > simple README.md update -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22455) Ambari Logsearch Web unit tests are sometimes failing
[
https://issues.apache.org/jira/browse/AMBARI-22455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253714#comment-16253714
]
Hadoop QA commented on AMBARI-22455:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897770/AMBARI-22455.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-logsearch/ambari-logsearch-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12675//console
This message is automatically generated.
> Ambari Logsearch Web unit tests are sometimes failing
> -
>
> Key: AMBARI-22455
> URL: https://issues.apache.org/jira/browse/AMBARI-22455
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-22455.patch
>
>
> Ambari Logsearch Web unit tests fail on CI builds:
> {code}
> [INFO] PhantomJS 2.1.1 (Linux 0.0.0) UtilsService #isEqual() undefined values
> equality FAILED
> [INFO]Expected false to be true.
> [INFO]http://localhost:9876/_karma_webpack_/main.bundle.js:9369:31
> [INFO]
> __tryOrUnsub@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55648:20
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55595:34
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55535:30
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57133:34
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57437:30
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55243:29
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:54628:35
> [INFO]http://localhost:9876/_karma_webpack_/vendor.bundle.js:415:62
> [INFO]
> __tryOrUnsub@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55648:20
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55595:34
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55535:30
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> _tryNext@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58081:30
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58068:33
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58466:38
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> observe@http://localhost:9876/_karma_webpack_/vendor.bundle.js:54715:54
> [INFO]
> dispatch@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57869:29
> [INFO]
> _execute@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58652:22
> [INFO]
> execute@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58781:26
> [INFO]
> flush@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58726:39
> [INFO]
> schedule@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58775:29
> [INFO]
> schedule@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55175:61
> [INFO]
> scheduleMessage@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57873:41
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57876:29
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55243:29
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:54628:35
> [INFO]
>
[jira] [Commented] (AMBARI-22444) Add Native Libraries To Tez Tarball
[
https://issues.apache.org/jira/browse/AMBARI-22444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253653#comment-16253653
]
Hadoop QA commented on AMBARI-22444:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897772/AMBARI-22444.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12674//console
This message is automatically generated.
> Add Native Libraries To Tez Tarball
> ---
>
> Key: AMBARI-22444
> URL: https://issues.apache.org/jira/browse/AMBARI-22444
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22444.patch
>
>
> As part of the investigation for getting patch upgrades working in Ambari
> 2.6.1, it was determined that the Tez tarball will need to have the hadoop
> native libraries added to it so that they can be detected from the tarball.
> STR:
> - Install ZK, MapR, Tez, Yarn, Hive
> - Enable a non-LZO codec, like Snappy
> - Patch Hive to a new version
> - Change the following properties in {{tez-site}}:
> -- tez.am.launch.env = LD_LIBRARY=./tezlib/lib/native
> -- tez.task.launch.env = LD_LIBRARY=./tezlib/lib/native
> When Hive commands run, they will attempt to load the native snappy libraries
> from the Tez tarball and will fail with:
> {code}
> Caused by: java.io.IOException: Unable to get CompressorType for codec
> (org.apache.hadoop.io.compress.SnappyCodec). This is most likely due to
> missing native libraries for the codec.
> at
> org.apache.tez.runtime.library.common.sort.impl.ExternalSorter.(ExternalSorter.java:217)
> {code}
> In order to fix this, the Tez tarball should include the native hadoop
> libraries as well:
> {code}
> ├── tez
> │ ├── lib
> │ │ ├── native
> │ │ │ ├── libhadoop.a
> │ │ │ ├── libhadoop.so -> libhadoop.so.1.0.0
> │ │ │ ├── libhadoop.so.1.0.0
> │ │ │ ├── libhadooppipes.a
> │ │ │ ├── libhadooputils.a
> │ │ │ ├── libhdfs.a
> │ │ │ ├── libhdfs.so -> libhdfs.so.0.0.0
> │ │ │ ├── libhdfs.so.0.0.0
> │ │ │ ├── libsnappy.so -> libsnappy.so.1.1.4
> │ │ │ ├── libsnappy.so.1 -> libsnappy.so.1.1.4
> │ │ │ └── libsnappy.so.1.1.4
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22444) Add Native Libraries To Tez Tarball
[
https://issues.apache.org/jira/browse/AMBARI-22444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-22444:
-
Attachment: AMBARI-22444.patch
> Add Native Libraries To Tez Tarball
> ---
>
> Key: AMBARI-22444
> URL: https://issues.apache.org/jira/browse/AMBARI-22444
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22444.patch
>
>
> As part of the investigation for getting patch upgrades working in Ambari
> 2.6.1, it was determined that the Tez tarball will need to have the hadoop
> native libraries added to it so that they can be detected from the tarball.
> STR:
> - Install ZK, MapR, Tez, Yarn, Hive
> - Enable a non-LZO codec, like Snappy
> - Patch Hive to a new version
> - Change the following properties in {{tez-site}}:
> -- tez.am.launch.env = LD_LIBRARY=./tezlib/lib/native
> -- tez.task.launch.env = LD_LIBRARY=./tezlib/lib/native
> When Hive commands run, they will attempt to load the native snappy libraries
> from the Tez tarball and will fail with:
> {code}
> Caused by: java.io.IOException: Unable to get CompressorType for codec
> (org.apache.hadoop.io.compress.SnappyCodec). This is most likely due to
> missing native libraries for the codec.
> at
> org.apache.tez.runtime.library.common.sort.impl.ExternalSorter.(ExternalSorter.java:217)
> {code}
> In order to fix this, the Tez tarball should include the native hadoop
> libraries as well:
> {code}
> ├── tez
> │ ├── lib
> │ │ ├── native
> │ │ │ ├── libhadoop.a
> │ │ │ ├── libhadoop.so -> libhadoop.so.1.0.0
> │ │ │ ├── libhadoop.so.1.0.0
> │ │ │ ├── libhadooppipes.a
> │ │ │ ├── libhadooputils.a
> │ │ │ ├── libhdfs.a
> │ │ │ ├── libhdfs.so -> libhdfs.so.0.0.0
> │ │ │ ├── libhdfs.so.0.0.0
> │ │ │ ├── libsnappy.so -> libsnappy.so.1.1.4
> │ │ │ ├── libsnappy.so.1 -> libsnappy.so.1.1.4
> │ │ │ └── libsnappy.so.1.1.4
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22451) Components with stale_configs should be updated via websockets
[ https://issues.apache.org/jira/browse/AMBARI-22451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253646#comment-16253646 ] Andrii Tkach commented on AMBARI-22451: --- committed to branch-3.0-perf > Components with stale_configs should be updated via websockets > -- > > Key: AMBARI-22451 > URL: https://issues.apache.org/jira/browse/AMBARI-22451 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22451.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22444) Add Native Libraries To Tez Tarball
[
https://issues.apache.org/jira/browse/AMBARI-22444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-22444:
-
Status: Patch Available (was: Open)
> Add Native Libraries To Tez Tarball
> ---
>
> Key: AMBARI-22444
> URL: https://issues.apache.org/jira/browse/AMBARI-22444
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.1
>
>
> As part of the investigation for getting patch upgrades working in Ambari
> 2.6.1, it was determined that the Tez tarball will need to have the hadoop
> native libraries added to it so that they can be detected from the tarball.
> STR:
> - Install ZK, MapR, Tez, Yarn, Hive
> - Enable a non-LZO codec, like Snappy
> - Patch Hive to a new version
> - Change the following properties in {{tez-site}}:
> -- tez.am.launch.env = LD_LIBRARY=./tezlib/lib/native
> -- tez.task.launch.env = LD_LIBRARY=./tezlib/lib/native
> When Hive commands run, they will attempt to load the native snappy libraries
> from the Tez tarball and will fail with:
> {code}
> Caused by: java.io.IOException: Unable to get CompressorType for codec
> (org.apache.hadoop.io.compress.SnappyCodec). This is most likely due to
> missing native libraries for the codec.
> at
> org.apache.tez.runtime.library.common.sort.impl.ExternalSorter.(ExternalSorter.java:217)
> {code}
> In order to fix this, the Tez tarball should include the native hadoop
> libraries as well:
> {code}
> ├── tez
> │ ├── lib
> │ │ ├── native
> │ │ │ ├── libhadoop.a
> │ │ │ ├── libhadoop.so -> libhadoop.so.1.0.0
> │ │ │ ├── libhadoop.so.1.0.0
> │ │ │ ├── libhadooppipes.a
> │ │ │ ├── libhadooputils.a
> │ │ │ ├── libhdfs.a
> │ │ │ ├── libhdfs.so -> libhdfs.so.0.0.0
> │ │ │ ├── libhdfs.so.0.0.0
> │ │ │ ├── libsnappy.so -> libsnappy.so.1.1.4
> │ │ │ ├── libsnappy.so.1 -> libsnappy.so.1.1.4
> │ │ │ └── libsnappy.so.1.1.4
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22451) Components with stale_configs should be updated via websockets
[ https://issues.apache.org/jira/browse/AMBARI-22451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22451: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Components with stale_configs should be updated via websockets > -- > > Key: AMBARI-22451 > URL: https://issues.apache.org/jira/browse/AMBARI-22451 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22451.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22455) Ambari Logsearch Web unit tests are sometimes failing
[
https://issues.apache.org/jira/browse/AMBARI-22455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Babiichuk updated AMBARI-22455:
--
Status: Patch Available (was: Open)
> Ambari Logsearch Web unit tests are sometimes failing
> -
>
> Key: AMBARI-22455
> URL: https://issues.apache.org/jira/browse/AMBARI-22455
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-22455.patch
>
>
> Ambari Logsearch Web unit tests fail on CI builds:
> {code}
> [INFO] PhantomJS 2.1.1 (Linux 0.0.0) UtilsService #isEqual() undefined values
> equality FAILED
> [INFO]Expected false to be true.
> [INFO]http://localhost:9876/_karma_webpack_/main.bundle.js:9369:31
> [INFO]
> __tryOrUnsub@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55648:20
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55595:34
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55535:30
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57133:34
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57437:30
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55243:29
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:54628:35
> [INFO]http://localhost:9876/_karma_webpack_/vendor.bundle.js:415:62
> [INFO]
> __tryOrUnsub@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55648:20
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55595:34
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55535:30
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> _tryNext@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58081:30
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58068:33
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58466:38
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> observe@http://localhost:9876/_karma_webpack_/vendor.bundle.js:54715:54
> [INFO]
> dispatch@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57869:29
> [INFO]
> _execute@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58652:22
> [INFO]
> execute@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58781:26
> [INFO]
> flush@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58726:39
> [INFO]
> schedule@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58775:29
> [INFO]
> schedule@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55175:61
> [INFO]
> scheduleMessage@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57873:41
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57876:29
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55243:29
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:54628:35
> [INFO]
> dispatch@http://localhost:9876/_karma_webpack_/vendor.bundle.js:464:30
> [INFO]
> setParameters@http://localhost:9876/_karma_webpack_/main.bundle.js:737:28
> [INFO]
> setParameter@http://localhost:9876/_karma_webpack_/main.bundle.js:734:27
> [INFO]
> setLoginInProgressAppState@http://localhost:9876/_karma_webpack_/main.bundle.js:9452:35
> [INFO]
> onLoginResponse@http://localhost:9876/_karma_webpack_/main.bundle.js:9468:44
> [INFO]http://localhost:9876/_karma_webpack_/main.bundle.js:9433:69
> [INFO]
> __tryOrUnsub@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55648:20
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55595:34
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55535:30
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> observe@http://localhost:9876/_karma_webpack_/vendor.bundle.js:54715:54
> [INFO]
>
[jira] [Updated] (AMBARI-22455) Ambari Logsearch Web unit tests are sometimes failing
[
https://issues.apache.org/jira/browse/AMBARI-22455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Babiichuk updated AMBARI-22455:
--
Attachment: AMBARI-22455.patch
> Ambari Logsearch Web unit tests are sometimes failing
> -
>
> Key: AMBARI-22455
> URL: https://issues.apache.org/jira/browse/AMBARI-22455
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-22455.patch
>
>
> Ambari Logsearch Web unit tests fail on CI builds:
> {code}
> [INFO] PhantomJS 2.1.1 (Linux 0.0.0) UtilsService #isEqual() undefined values
> equality FAILED
> [INFO]Expected false to be true.
> [INFO]http://localhost:9876/_karma_webpack_/main.bundle.js:9369:31
> [INFO]
> __tryOrUnsub@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55648:20
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55595:34
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55535:30
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57133:34
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57437:30
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55243:29
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:54628:35
> [INFO]http://localhost:9876/_karma_webpack_/vendor.bundle.js:415:62
> [INFO]
> __tryOrUnsub@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55648:20
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55595:34
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55535:30
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> _tryNext@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58081:30
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58068:33
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58466:38
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> observe@http://localhost:9876/_karma_webpack_/vendor.bundle.js:54715:54
> [INFO]
> dispatch@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57869:29
> [INFO]
> _execute@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58652:22
> [INFO]
> execute@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58781:26
> [INFO]
> flush@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58726:39
> [INFO]
> schedule@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58775:29
> [INFO]
> schedule@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55175:61
> [INFO]
> scheduleMessage@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57873:41
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57876:29
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55243:29
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:54628:35
> [INFO]
> dispatch@http://localhost:9876/_karma_webpack_/vendor.bundle.js:464:30
> [INFO]
> setParameters@http://localhost:9876/_karma_webpack_/main.bundle.js:737:28
> [INFO]
> setParameter@http://localhost:9876/_karma_webpack_/main.bundle.js:734:27
> [INFO]
> setLoginInProgressAppState@http://localhost:9876/_karma_webpack_/main.bundle.js:9452:35
> [INFO]
> onLoginResponse@http://localhost:9876/_karma_webpack_/main.bundle.js:9468:44
> [INFO]http://localhost:9876/_karma_webpack_/main.bundle.js:9433:69
> [INFO]
> __tryOrUnsub@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55648:20
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55595:34
> [INFO]
> _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55535:30
> [INFO]
> next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
> [INFO]
> observe@http://localhost:9876/_karma_webpack_/vendor.bundle.js:54715:54
> [INFO]
>
[jira] [Commented] (AMBARI-22451) Components with stale_configs should be updated via websockets
[ https://issues.apache.org/jira/browse/AMBARI-22451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253639#comment-16253639 ] Aleksandr Kovalenko commented on AMBARI-22451: -- +1 for the patch > Components with stale_configs should be updated via websockets > -- > > Key: AMBARI-22451 > URL: https://issues.apache.org/jira/browse/AMBARI-22451 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22451.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22455) Ambari Logsearch Web unit tests are sometimes failing
Andrii Babiichuk created AMBARI-22455:
-
Summary: Ambari Logsearch Web unit tests are sometimes failing
Key: AMBARI-22455
URL: https://issues.apache.org/jira/browse/AMBARI-22455
Project: Ambari
Issue Type: Bug
Components: ambari-logsearch
Affects Versions: 3.0.0
Reporter: Andrii Babiichuk
Assignee: Andrii Babiichuk
Priority: Critical
Fix For: 3.0.0
Ambari Logsearch Web unit tests fail on CI builds:
{code}
[INFO] PhantomJS 2.1.1 (Linux 0.0.0) UtilsService #isEqual() undefined values
equality FAILED
[INFO] Expected false to be true.
[INFO] http://localhost:9876/_karma_webpack_/main.bundle.js:9369:31
[INFO]
__tryOrUnsub@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55648:20
[INFO] next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55595:34
[INFO] _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55535:30
[INFO] next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
[INFO] _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57133:34
[INFO] next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
[INFO] _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57437:30
[INFO] next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
[INFO] next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55243:29
[INFO] next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:54628:35
[INFO] http://localhost:9876/_karma_webpack_/vendor.bundle.js:415:62
[INFO]
__tryOrUnsub@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55648:20
[INFO] next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55595:34
[INFO] _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55535:30
[INFO] next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
[INFO] _tryNext@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58081:30
[INFO] _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58068:33
[INFO] next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
[INFO] _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58466:38
[INFO] next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
[INFO] observe@http://localhost:9876/_karma_webpack_/vendor.bundle.js:54715:54
[INFO] dispatch@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57869:29
[INFO] _execute@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58652:22
[INFO] execute@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58781:26
[INFO] flush@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58726:39
[INFO] schedule@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58775:29
[INFO] schedule@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55175:61
[INFO]
scheduleMessage@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57873:41
[INFO] _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:57876:29
[INFO] next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
[INFO] next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55243:29
[INFO] next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:54628:35
[INFO] dispatch@http://localhost:9876/_karma_webpack_/vendor.bundle.js:464:30
[INFO]
setParameters@http://localhost:9876/_karma_webpack_/main.bundle.js:737:28
[INFO] setParameter@http://localhost:9876/_karma_webpack_/main.bundle.js:734:27
[INFO]
setLoginInProgressAppState@http://localhost:9876/_karma_webpack_/main.bundle.js:9452:35
[INFO]
onLoginResponse@http://localhost:9876/_karma_webpack_/main.bundle.js:9468:44
[INFO] http://localhost:9876/_karma_webpack_/main.bundle.js:9433:69
[INFO]
__tryOrUnsub@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55648:20
[INFO] next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55595:34
[INFO] _next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55535:30
[INFO] next@http://localhost:9876/_karma_webpack_/vendor.bundle.js:55499:23
[INFO] observe@http://localhost:9876/_karma_webpack_/vendor.bundle.js:54715:54
[INFO] dispatch@http://localhost:9876/_karma_webpack_/vendor.bundle.js:56976:47
[INFO] _execute@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58652:22
[INFO] execute@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58627:34
[INFO] flush@http://localhost:9876/_karma_webpack_/vendor.bundle.js:58726:39
[INFO] [native code]
[INFO]
invokeTask@http://localhost:9876/_karma_webpack_/polyfills.bundle.js:5364:36
[INFO]
onInvokeTask@http://localhost:9876/_karma_webpack_/vendor.bundle.js:60542:49
[INFO]
invokeTask@http://localhost:9876/_karma_webpack_/polyfills.bundle.js:5363:48
[INFO]
runTask@http://localhost:9876/_karma_webpack_/polyfills.bundle.js:5131:57
[INFO]
invokeTask@http://localhost:9876/_karma_webpack_/polyfills.bundle.js:5438:41
[INFO]
[jira] [Commented] (AMBARI-22451) Components with stale_configs should be updated via websockets
[ https://issues.apache.org/jira/browse/AMBARI-22451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253628#comment-16253628 ] Andrii Tkach commented on AMBARI-22451: --- 21424 passing (28s) 128 pending > Components with stale_configs should be updated via websockets > -- > > Key: AMBARI-22451 > URL: https://issues.apache.org/jira/browse/AMBARI-22451 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22451.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22451) Components with stale_configs should be updated via websockets
[ https://issues.apache.org/jira/browse/AMBARI-22451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22451: -- Attachment: AMBARI-22451.patch > Components with stale_configs should be updated via websockets > -- > > Key: AMBARI-22451 > URL: https://issues.apache.org/jira/browse/AMBARI-22451 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22451.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22451) Components with stale_configs should be updated via websockets
[ https://issues.apache.org/jira/browse/AMBARI-22451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22451: -- Status: Patch Available (was: Open) > Components with stale_configs should be updated via websockets > -- > > Key: AMBARI-22451 > URL: https://issues.apache.org/jira/browse/AMBARI-22451 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22451.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22450) Log Search: reference Log Feeder IDE/maven dev setup in README.md
[
https://issues.apache.org/jira/browse/AMBARI-22450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253596#comment-16253596
]
Olivér Szabó commented on AMBARI-22450:
---
committed to trunk:
{code:java}
commit 1a99da4470d3ce1d928ab56f1a4c2845f940ef53
Author: Oliver Szabo
Date: Wed Nov 15 12:54:25 2017 +0100
AMBARI-22450. Log Search: reference Log Feeder IDE/maven dev setup in
README.md (oleewere)
{code}
> Log Search: reference Log Feeder IDE/maven dev setup in README.md
> -
>
> Key: AMBARI-22450
> URL: https://issues.apache.org/jira/browse/AMBARI-22450
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 3.0.0
>
>
> simple README.md update
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22450) Log Search: reference Log Feeder IDE/maven dev setup in README.md
[ https://issues.apache.org/jira/browse/AMBARI-22450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-22450: -- Description: simple README.md update > Log Search: reference Log Feeder IDE/maven dev setup in README.md > - > > Key: AMBARI-22450 > URL: https://issues.apache.org/jira/browse/AMBARI-22450 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 3.0.0 > > > simple README.md update -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22454) ambari-server upgrade to 2.6.1 should surface the GPL agreement
[ https://issues.apache.org/jira/browse/AMBARI-22454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253543#comment-16253543 ] Andrew Onischuk commented on AMBARI-22454: -- Unit tests are pending. For now attached for a review. [~swagle] can you please review the patch here as it won't upload it to review board because it's dependent on the previous patch. > ambari-server upgrade to 2.6.1 should surface the GPL agreement > --- > > Key: AMBARI-22454 > URL: https://issues.apache.org/jira/browse/AMBARI-22454 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.6.1 > > Attachments: AMBARI-22454.patch > > > . -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22454) ambari-server upgrade to 2.6.1 should surface the GPL agreement
[ https://issues.apache.org/jira/browse/AMBARI-22454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-22454: - Attachment: (was: AMBARI-22454.patch) > ambari-server upgrade to 2.6.1 should surface the GPL agreement > --- > > Key: AMBARI-22454 > URL: https://issues.apache.org/jira/browse/AMBARI-22454 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.6.1 > > Attachments: AMBARI-22454.patch > > > . -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22454) ambari-server upgrade to 2.6.1 should surface the GPL agreement
[ https://issues.apache.org/jira/browse/AMBARI-22454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-22454: - Attachment: AMBARI-22454.patch > ambari-server upgrade to 2.6.1 should surface the GPL agreement > --- > > Key: AMBARI-22454 > URL: https://issues.apache.org/jira/browse/AMBARI-22454 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.6.1 > > Attachments: AMBARI-22454.patch, AMBARI-22454.patch > > > . -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22454) ambari-server upgrade to 2.6.1 should surface the GPL agreement
[ https://issues.apache.org/jira/browse/AMBARI-22454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-22454: - Status: Patch Available (was: Open) > ambari-server upgrade to 2.6.1 should surface the GPL agreement > --- > > Key: AMBARI-22454 > URL: https://issues.apache.org/jira/browse/AMBARI-22454 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.6.1 > > Attachments: AMBARI-22454.patch > > > . -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22454) ambari-server upgrade to 2.6.1 should surface the GPL agreement
[ https://issues.apache.org/jira/browse/AMBARI-22454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-22454: - Attachment: AMBARI-22454.patch > ambari-server upgrade to 2.6.1 should surface the GPL agreement > --- > > Key: AMBARI-22454 > URL: https://issues.apache.org/jira/browse/AMBARI-22454 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.6.1 > > Attachments: AMBARI-22454.patch > > > . -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22454) ambari-server upgrade to 2.6.1 should surface the GPL agreement
Andrew Onischuk created AMBARI-22454: Summary: ambari-server upgrade to 2.6.1 should surface the GPL agreement Key: AMBARI-22454 URL: https://issues.apache.org/jira/browse/AMBARI-22454 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.6.1 . -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22453) ambari-server setup should surface GPL software agreement
Andrew Onischuk created AMBARI-22453: Summary: ambari-server setup should surface GPL software agreement Key: AMBARI-22453 URL: https://issues.apache.org/jira/browse/AMBARI-22453 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.6.1 * Ask the user if they are okay with installing GPL license software * Surface the license agreement subtext, for now use placeholder * Save the result in ambari.properties * The user selection should be available through API for the client and also stack scripts -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22453) ambari-server setup should surface GPL software agreement
[ https://issues.apache.org/jira/browse/AMBARI-22453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-22453: - Attachment: AMBARI-22453.patch > ambari-server setup should surface GPL software agreement > - > > Key: AMBARI-22453 > URL: https://issues.apache.org/jira/browse/AMBARI-22453 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.6.1 > > Attachments: AMBARI-22453.patch > > > * Ask the user if they are okay with installing GPL license software > * Surface the license agreement subtext, for now use placeholder > * Save the result in ambari.properties > * The user selection should be available through API for the client and > also stack scripts -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22453) ambari-server setup should surface GPL software agreement
[ https://issues.apache.org/jira/browse/AMBARI-22453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-22453: - Status: Patch Available (was: Open) > ambari-server setup should surface GPL software agreement > - > > Key: AMBARI-22453 > URL: https://issues.apache.org/jira/browse/AMBARI-22453 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.6.1 > > Attachments: AMBARI-22453.patch > > > * Ask the user if they are okay with installing GPL license software > * Surface the license agreement subtext, for now use placeholder > * Save the result in ambari.properties > * The user selection should be available through API for the client and > also stack scripts -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22452) Ambari install wizard throws HTTP 400 on the assign master page due to err in he ambari service advisor class
[ https://issues.apache.org/jira/browse/AMBARI-22452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-22452: --- Status: Patch Available (was: Open) > Ambari install wizard throws HTTP 400 on the assign master page due to err in > he ambari service advisor class > - > > Key: AMBARI-22452 > URL: https://issues.apache.org/jira/browse/AMBARI-22452 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-22452.patch > > > Ambari install wizard throws HTTP 400 on the assign master page due to err in > he ambari service advisor class -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22452) Ambari install wizard throws HTTP 400 on the assign master page due to err in he ambari service advisor class
[ https://issues.apache.org/jira/browse/AMBARI-22452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-22452: --- Description: Ambari install wizard throws HTTP 400 on the assign master page due to err in he ambari service advisor class > Ambari install wizard throws HTTP 400 on the assign master page due to err in > he ambari service advisor class > - > > Key: AMBARI-22452 > URL: https://issues.apache.org/jira/browse/AMBARI-22452 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-22452.patch > > > Ambari install wizard throws HTTP 400 on the assign master page due to err in > he ambari service advisor class -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22452) Ambari install wizard throws HTTP 400 on the assign master page due to err in he ambari service advisor class
[ https://issues.apache.org/jira/browse/AMBARI-22452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-22452: --- Attachment: AMBARI-22452.patch > Ambari install wizard throws HTTP 400 on the assign master page due to err in > he ambari service advisor class > - > > Key: AMBARI-22452 > URL: https://issues.apache.org/jira/browse/AMBARI-22452 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-22452.patch > > > Ambari install wizard throws HTTP 400 on the assign master page due to err in > he ambari service advisor class -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22452) Ambari install wizard throws HTTP 400 on the assign master page due to err in he ambari service advisor class
Di Li created AMBARI-22452: -- Summary: Ambari install wizard throws HTTP 400 on the assign master page due to err in he ambari service advisor class Key: AMBARI-22452 URL: https://issues.apache.org/jira/browse/AMBARI-22452 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: trunk Reporter: Di Li Assignee: Di Li Fix For: trunk -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22398) Upstart is not able to stop the ambari-agent
[
https://issues.apache.org/jira/browse/AMBARI-22398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253482#comment-16253482
]
Doroszlai, Attila commented on AMBARI-22398:
{noformat:title=https://builds.apache.org/job/Ambari-trunk-Commit/8394/console}
[INFO] Ambari Agent ... SUCCESS [01:23 min]
{noformat}
> Upstart is not able to stop the ambari-agent
>
>
> Key: AMBARI-22398
> URL: https://issues.apache.org/jira/browse/AMBARI-22398
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 3.0.0, 2.6.1
>
> Attachments: AMBARI-22398.patch, AMBARI-22398_unit_test.patch
>
>
> While starting ambari-agent using "service ambari-agent start" it works fine
> but when we used try to check status using "start ambari-agent" (upstart
> command) facing issue. But when we start ambari agent using "start ambari-
> agent" it's works but at this time when we checked status using service
> command facing issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22448) Oozie Jobs on Hive Fail With Missing Tarball
[
https://issues.apache.org/jira/browse/AMBARI-22448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253468#comment-16253468
]
Nate Cole commented on AMBARI-22448:
There are no tests required as this is a simple json change - no logic changes.
> Oozie Jobs on Hive Fail With Missing Tarball
>
>
> Key: AMBARI-22448
> URL: https://issues.apache.org/jira/browse/AMBARI-22448
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.6 1
>
> Attachments: AMBARI-22448.patch
>
>
> STR:
> - Install an HDP 2.6.3.0 cluster with Oozie, HIve, MapR, Yarn, ZK, HDFS
> - Patch only Oozie to a new version, such as 2.6.3.1-1
> - Attempt to run an Oozie job on Hive
> The workflow job will fail with:
> {code}
> org.apache.oozie.action.ActionExecutorException: JA008: File does not exist:
> hdfs://jhurley-pu-1.openstacklocal:8020/hdp/apps/2.6.3.1-1/mapreduce/mapreduce.tar.gz
> at
> org.apache.oozie.action.ActionExecutor.convertExceptionHelper(ActionExecutor.java:457)
> at
> org.apache.oozie.action.ActionExecutor.convertException(ActionExecutor.java:441)
> at
> org.apache.oozie.action.hadoop.JavaActionExecutor.submitLauncher(JavaActionExecutor.java:1211)
> at
> org.apache.oozie.action.hadoop.JavaActionExecutor.start(JavaActionExecutor.java:1382)
> at
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:234)
> at
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:65)
> at org.apache.oozie.command.XCommand.call(XCommand.java:287)
> at
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:331)
> at
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:260)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:178)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> This is because Oozie appears to be trying to use a version of the MapReduce
> tarball which matches its version. However, since it does not ship its
> version, it cannot find it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22451) Components with stale_configs should be updated via websockets
Andrii Tkach created AMBARI-22451: - Summary: Components with stale_configs should be updated via websockets Key: AMBARI-22451 URL: https://issues.apache.org/jira/browse/AMBARI-22451 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 3.0.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22398) Upstart is not able to stop the ambari-agent
[ https://issues.apache.org/jira/browse/AMBARI-22398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253392#comment-16253392 ] Hudson commented on AMBARI-22398: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8394 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8394/]) AMBARI-22398. Upstart is not able to stop the ambari-agent - fix unit (adoroszlai: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a4e7bf379dc2392253bd9bad3ab42ab9c2d9552e]) * (edit) ambari-agent/src/test/python/ambari_agent/TestAmbariAgent.py > Upstart is not able to stop the ambari-agent > > > Key: AMBARI-22398 > URL: https://issues.apache.org/jira/browse/AMBARI-22398 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0, 2.6.1 > > Attachments: AMBARI-22398.patch, AMBARI-22398_unit_test.patch > > > While starting ambari-agent using "service ambari-agent start" it works fine > but when we used try to check status using "start ambari-agent" (upstart > command) facing issue. But when we start ambari agent using "start ambari- > agent" it's works but at this time when we checked status using service > command facing issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22398) Upstart is not able to stop the ambari-agent
[ https://issues.apache.org/jira/browse/AMBARI-22398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253384#comment-16253384 ] Hudson commented on AMBARI-22398: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #455 (See [https://builds.apache.org/job/Ambari-branch-2.6/455/]) AMBARI-22398. Upstart is not able to stop the ambari-agent - fix unit (adoroszlai: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e91bee14de888d183c51e2ba7356dbbf608cb32f]) * (edit) ambari-agent/src/test/python/ambari_agent/TestAmbariAgent.py > Upstart is not able to stop the ambari-agent > > > Key: AMBARI-22398 > URL: https://issues.apache.org/jira/browse/AMBARI-22398 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0, 2.6.1 > > Attachments: AMBARI-22398.patch, AMBARI-22398_unit_test.patch > > > While starting ambari-agent using "service ambari-agent start" it works fine > but when we used try to check status using "start ambari-agent" (upstart > command) facing issue. But when we start ambari agent using "start ambari- > agent" it's works but at this time when we checked status using service > command facing issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22398) Upstart is not able to stop the ambari-agent
[ https://issues.apache.org/jira/browse/AMBARI-22398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-22398: --- Attachment: AMBARI-22398_unit_test.patch > Upstart is not able to stop the ambari-agent > > > Key: AMBARI-22398 > URL: https://issues.apache.org/jira/browse/AMBARI-22398 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0, 2.6.1 > > Attachments: AMBARI-22398.patch, AMBARI-22398_unit_test.patch > > > While starting ambari-agent using "service ambari-agent start" it works fine > but when we used try to check status using "start ambari-agent" (upstart > command) facing issue. But when we start ambari agent using "start ambari- > agent" it's works but at this time when we checked status using service > command facing issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22398) Upstart is not able to stop the ambari-agent
[ https://issues.apache.org/jira/browse/AMBARI-22398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-22398: --- Component/s: ambari-agent > Upstart is not able to stop the ambari-agent > > > Key: AMBARI-22398 > URL: https://issues.apache.org/jira/browse/AMBARI-22398 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0, 2.6.1 > > Attachments: AMBARI-22398.patch, AMBARI-22398_unit_test.patch > > > While starting ambari-agent using "service ambari-agent start" it works fine > but when we used try to check status using "start ambari-agent" (upstart > command) facing issue. But when we start ambari agent using "start ambari- > agent" it's works but at this time when we checked status using service > command facing issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-22398) Upstart is not able to stop the ambari-agent
[ https://issues.apache.org/jira/browse/AMBARI-22398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila resolved AMBARI-22398. Resolution: Fixed Fix Version/s: (was: 2.5.0) 2.6.1 3.0.0 Fix for unit test committed to [branch-2.6|http://git-wip-us.apache.org/repos/asf/ambari/commit/e91bee14de] and [trunk|http://git-wip-us.apache.org/repos/asf/ambari/commit/a4e7bf379d]. > Upstart is not able to stop the ambari-agent > > > Key: AMBARI-22398 > URL: https://issues.apache.org/jira/browse/AMBARI-22398 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0, 2.6.1 > > Attachments: AMBARI-22398.patch > > > While starting ambari-agent using "service ambari-agent start" it works fine > but when we used try to check status using "start ambari-agent" (upstart > command) facing issue. But when we start ambari agent using "start ambari- > agent" it's works but at this time when we checked status using service > command facing issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22441) Integrate Alert Groups on Alert page with websocket events
[ https://issues.apache.org/jira/browse/AMBARI-22441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22441: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Integrate Alert Groups on Alert page with websocket events > -- > > Key: AMBARI-22441 > URL: https://issues.apache.org/jira/browse/AMBARI-22441 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22441.patch > > > Subscribe to /events/alert_groups topic, which will update/add/delete groups > of alerts. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22441) Integrate Alert Groups on Alert page with websocket events
[ https://issues.apache.org/jira/browse/AMBARI-22441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253322#comment-16253322 ] Andrii Tkach commented on AMBARI-22441: --- committed to trunk > Integrate Alert Groups on Alert page with websocket events > -- > > Key: AMBARI-22441 > URL: https://issues.apache.org/jira/browse/AMBARI-22441 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22441.patch > > > Subscribe to /events/alert_groups topic, which will update/add/delete groups > of alerts. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (AMBARI-22441) Integrate Alert Groups on Alert page with websocket events
[ https://issues.apache.org/jira/browse/AMBARI-22441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253322#comment-16253322 ] Andrii Tkach edited comment on AMBARI-22441 at 11/15/17 11:32 AM: -- committed to branch-3.0-perf was (Author: atkach): committed to trunk > Integrate Alert Groups on Alert page with websocket events > -- > > Key: AMBARI-22441 > URL: https://issues.apache.org/jira/browse/AMBARI-22441 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22441.patch > > > Subscribe to /events/alert_groups topic, which will update/add/delete groups > of alerts. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22450) Log Search: reference Log Feeder IDE/maven dev setup in README.md
Olivér Szabó created AMBARI-22450: - Summary: Log Search: reference Log Feeder IDE/maven dev setup in README.md Key: AMBARI-22450 URL: https://issues.apache.org/jira/browse/AMBARI-22450 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 3.0.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22448) Oozie Jobs on Hive Fail With Missing Tarball
[
https://issues.apache.org/jira/browse/AMBARI-22448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253313#comment-16253313
]
Hadoop QA commented on AMBARI-22448:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897655/AMBARI-22448.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12673//console
This message is automatically generated.
> Oozie Jobs on Hive Fail With Missing Tarball
>
>
> Key: AMBARI-22448
> URL: https://issues.apache.org/jira/browse/AMBARI-22448
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.6 1
>
> Attachments: AMBARI-22448.patch
>
>
> STR:
> - Install an HDP 2.6.3.0 cluster with Oozie, HIve, MapR, Yarn, ZK, HDFS
> - Patch only Oozie to a new version, such as 2.6.3.1-1
> - Attempt to run an Oozie job on Hive
> The workflow job will fail with:
> {code}
> org.apache.oozie.action.ActionExecutorException: JA008: File does not exist:
> hdfs://jhurley-pu-1.openstacklocal:8020/hdp/apps/2.6.3.1-1/mapreduce/mapreduce.tar.gz
> at
> org.apache.oozie.action.ActionExecutor.convertExceptionHelper(ActionExecutor.java:457)
> at
> org.apache.oozie.action.ActionExecutor.convertException(ActionExecutor.java:441)
> at
> org.apache.oozie.action.hadoop.JavaActionExecutor.submitLauncher(JavaActionExecutor.java:1211)
> at
> org.apache.oozie.action.hadoop.JavaActionExecutor.start(JavaActionExecutor.java:1382)
> at
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:234)
> at
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:65)
> at org.apache.oozie.command.XCommand.call(XCommand.java:287)
> at
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:331)
> at
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:260)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:178)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> This is because Oozie appears to be trying to use a version of the MapReduce
> tarball which matches its version. However, since it does not ship its
> version, it cannot find it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22443) Log Feeder: do not try to connect AMS, when it is disabled
[ https://issues.apache.org/jira/browse/AMBARI-22443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253308#comment-16253308 ] Hudson commented on AMBARI-22443: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8393 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8393/]) AMBARI-22443. Log Feeder: do not try to connect AMS, when it is disabled (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2b917f491f5577a85ec88380d7f3f93397cececf]) * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/test/java/org/apache/ambari/logfeeder/metrics/MetricsManagerTest.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/metrics/LogFeederAMSClient.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/metrics/MetricsManager.java > Log Feeder: do not try to connect AMS, when it is disabled > -- > > Key: AMBARI-22443 > URL: https://issues.apache.org/jira/browse/AMBARI-22443 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22441) Integrate Alert Groups on Alert page with websocket events
[ https://issues.apache.org/jira/browse/AMBARI-22441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253303#comment-16253303 ] Andrii Babiichuk commented on AMBARI-22441: --- +1 for the patch > Integrate Alert Groups on Alert page with websocket events > -- > > Key: AMBARI-22441 > URL: https://issues.apache.org/jira/browse/AMBARI-22441 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22441.patch > > > Subscribe to /events/alert_groups topic, which will update/add/delete groups > of alerts. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-22443) Log Feeder: do not try to connect AMS, when it is disabled
[
https://issues.apache.org/jira/browse/AMBARI-22443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó resolved AMBARI-22443.
---
Resolution: Fixed
committed to trunk:
{code:java}
commit 2b917f491f5577a85ec88380d7f3f93397cececf
Author: Oliver Szabo
Date: Tue Nov 14 19:15:57 2017 +0100
AMBARI-22443. Log Feeder: do not try to connect AMS, when it is disabled
(oleewere)
{code}
> Log Feeder: do not try to connect AMS, when it is disabled
> --
>
> Key: AMBARI-22443
> URL: https://issues.apache.org/jira/browse/AMBARI-22443
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 3.0.0
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22441) Integrate Alert Groups on Alert page with websocket events
[
https://issues.apache.org/jira/browse/AMBARI-22441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253269#comment-16253269
]
Hadoop QA commented on AMBARI-22441:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897709/AMBARI-22441.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12672//console
This message is automatically generated.
> Integrate Alert Groups on Alert page with websocket events
> --
>
> Key: AMBARI-22441
> URL: https://issues.apache.org/jira/browse/AMBARI-22441
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-22441.patch
>
>
> Subscribe to /events/alert_groups topic, which will update/add/delete groups
> of alerts.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22449) Improved service/component dependency support
Attila Magyar created AMBARI-22449: -- Summary: Improved service/component dependency support Key: AMBARI-22449 URL: https://issues.apache.org/jira/browse/AMBARI-22449 Project: Ambari Issue Type: Task Components: ambari-server, ambari-web Affects Versions: 3.0.0 Reporter: Attila Magyar Assignee: Attila Magyar Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22441) Integrate Alert Groups on Alert page with websocket events
[
https://issues.apache.org/jira/browse/AMBARI-22441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253197#comment-16253197
]
Hadoop QA commented on AMBARI-22441:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897709/AMBARI-22441.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12671//console
This message is automatically generated.
> Integrate Alert Groups on Alert page with websocket events
> --
>
> Key: AMBARI-22441
> URL: https://issues.apache.org/jira/browse/AMBARI-22441
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-22441.patch
>
>
> Subscribe to /events/alert_groups topic, which will update/add/delete groups
> of alerts.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22441) Integrate Alert Groups on Alert page with websocket events
[ https://issues.apache.org/jira/browse/AMBARI-22441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253189#comment-16253189 ] Andrii Tkach commented on AMBARI-22441: --- 21420 passing (27s) 128 pending > Integrate Alert Groups on Alert page with websocket events > -- > > Key: AMBARI-22441 > URL: https://issues.apache.org/jira/browse/AMBARI-22441 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22441.patch > > > Subscribe to /events/alert_groups topic, which will update/add/delete groups > of alerts. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22441) Integrate Alert Groups on Alert page with websocket events
[ https://issues.apache.org/jira/browse/AMBARI-22441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22441: -- Status: Patch Available (was: Open) > Integrate Alert Groups on Alert page with websocket events > -- > > Key: AMBARI-22441 > URL: https://issues.apache.org/jira/browse/AMBARI-22441 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22441.patch > > > Subscribe to /events/alert_groups topic, which will update/add/delete groups > of alerts. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22441) Integrate Alert Groups on Alert page with websocket events
[ https://issues.apache.org/jira/browse/AMBARI-22441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22441: -- Attachment: AMBARI-22441.patch > Integrate Alert Groups on Alert page with websocket events > -- > > Key: AMBARI-22441 > URL: https://issues.apache.org/jira/browse/AMBARI-22441 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22441.patch > > > Subscribe to /events/alert_groups topic, which will update/add/delete groups > of alerts. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
