[jira] [Assigned] (AMBARI-21867) Rename hive.custom-extensions.root
[ https://issues.apache.org/jira/browse/AMBARI-21867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader reassigned AMBARI-21867: - Assignee: Vitaly Brodetskyi > Rename hive.custom-extensions.root > -- > > Key: AMBARI-21867 > URL: https://issues.apache.org/jira/browse/AMBARI-21867 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Dharmesh Kakadia >Assignee: Vitaly Brodetskyi > > [https://issues.apache.org/jira/browse/AMBARI-21570] introduced a > configuration hive.custom-extensions.root. > All hive.* variables are treated as hive configuration variables and thus > hive is complaining the following: > "WARN [main] conf.HiveConf (HiveConf.java:initialize(3081)) - HiveConf of > name hive.custom-extensions.root does not exist" > If this is not a hive related configuration, we should not use hive.* > namespace for it. Or > If it is hive related configuration we should add corresponding patch in hive > to add this variable to HiveConf.java > This has broken all our automated tests. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21894) PATCH and MAINT Repositories Should Indicate that they can be Reverted
[
https://issues.apache.org/jira/browse/AMBARI-21894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156456#comment-16156456
]
Hudson commented on AMBARI-21894:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8011 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8011/])
AMBARI-21894 - PATCH and MAINT Repositories Should Indicate that they (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8b5d697c0adb5ae92b16f1df2e2d6d75b066fce5])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/UpgradeContext.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/UpgradeEntity.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/UpgradeDAO.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UpgradeResourceProviderTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProvider.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/RepositoryType.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/UpgradeContextTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog260Test.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/UpgradeDAOTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog260.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/AbstractUpgradeServerAction.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/FinalizeUpgradeAction.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql
> PATCH and MAINT Repositories Should Indicate that they can be Reverted
> --
>
> Key: AMBARI-21894
> URL: https://issues.apache.org/jira/browse/AMBARI-21894
> Project: Ambari
> Issue Type: Task
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-21894.patch
>
>
> In the current PU UI, the revert button is shown for any PATCH type
> repository. The backend should compute whether a version can be reverted.
> The backed should return a value, such as
> {{ClusterStackVersions/supports_revert}} which clients, such as the web
> client, can use.
> {code:title=Example REST Changes}
> {
> "ClusterStackVersions": {
> "cluster_name": "c1",
> "id": 51,
> "repository_version": 51,
> "revert_upgrade_id": 1,
> "stack": "HDP",
> "supports_revert": true,
> "version": "2.6"
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21894) PATCH and MAINT Repositories Should Indicate that they can be Reverted
[
https://issues.apache.org/jira/browse/AMBARI-21894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156443#comment-16156443
]
Hudson commented on AMBARI-21894:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #165 (See
[https://builds.apache.org/job/Ambari-branch-2.6/165/])
AMBARI-21894 - PATCH and MAINT Repositories Should Indicate that they (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=313e3bf0f812a285506ff5e58cf1ef23544764d1])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProvider.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/UpgradeDAOTest.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog260Test.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/RepositoryType.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UpgradeResourceProviderTest.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/FinalizeUpgradeAction.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/UpgradeContextTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/AbstractUpgradeServerAction.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/UpgradeContext.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/UpgradeEntity.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/UpgradeDAO.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog260.java
> PATCH and MAINT Repositories Should Indicate that they can be Reverted
> --
>
> Key: AMBARI-21894
> URL: https://issues.apache.org/jira/browse/AMBARI-21894
> Project: Ambari
> Issue Type: Task
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-21894.patch
>
>
> In the current PU UI, the revert button is shown for any PATCH type
> repository. The backend should compute whether a version can be reverted.
> The backed should return a value, such as
> {{ClusterStackVersions/supports_revert}} which clients, such as the web
> client, can use.
> {code:title=Example REST Changes}
> {
> "ClusterStackVersions": {
> "cluster_name": "c1",
> "id": 51,
> "repository_version": 51,
> "revert_upgrade_id": 1,
> "stack": "HDP",
> "supports_revert": true,
> "version": "2.6"
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-21880) Spark-LLAP Ambari integration
[ https://issues.apache.org/jira/browse/AMBARI-21880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingjie Tang resolved AMBARI-21880. --- Resolution: Won't Fix > Spark-LLAP Ambari integration > - > > Key: AMBARI-21880 > URL: https://issues.apache.org/jira/browse/AMBARI-21880 > Project: Ambari > Issue Type: Bug >Reporter: Mingjie Tang >Assignee: Mingjie Tang > > Add spark-llap configuration via ambari. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21898) Property provider in-memory maps are refreshed too slowly after config updates
[ https://issues.apache.org/jira/browse/AMBARI-21898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156355#comment-16156355 ] Hudson commented on AMBARI-21898: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #164 (See [https://builds.apache.org/job/Ambari-branch-2.6/164/]) AMBARI-21898. Property provider in-memory maps are refreshed too slowly (swagle: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=854d7000f3bfd2c1e237ee29e46c0bdd95356bee]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/Cluster.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AbstractProviderModule.java > Property provider in-memory maps are refreshed too slowly after config updates > -- > > Key: AMBARI-21898 > URL: https://issues.apache.org/jira/browse/AMBARI-21898 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.0.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21898.patch > > > Building the hostComponentMap map for ProviderModule seems does unnecessary > computation going through the ResourceProvider layer. On every configuration > update, we call the reset on these maps which takes a long time to refresh. > Instead, relying on > org.apache.ambari.server.state.cluster.ClusterImpl#serviceComponentHosts will > lead to faster computation without overhead like stale config calculations > for every SCH. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21898) Property provider in-memory maps are refreshed too slowly after config updates
[ https://issues.apache.org/jira/browse/AMBARI-21898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156348#comment-16156348 ] Hudson commented on AMBARI-21898: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8010 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8010/]) AMBARI-21898. Property provider in-memory maps are refreshed too slowly (swagle: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8cb942393ce15efb5f6fbc9f594287c30971c296]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/Cluster.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AbstractProviderModule.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java > Property provider in-memory maps are refreshed too slowly after config updates > -- > > Key: AMBARI-21898 > URL: https://issues.apache.org/jira/browse/AMBARI-21898 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.0.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21898.patch > > > Building the hostComponentMap map for ProviderModule seems does unnecessary > computation going through the ResourceProvider layer. On every configuration > update, we call the reset on these maps which takes a long time to refresh. > Instead, relying on > org.apache.ambari.server.state.cluster.ClusterImpl#serviceComponentHosts will > lead to faster computation without overhead like stale config calculations > for every SCH. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21898) Property provider in-memory maps are refreshed too slowly after config updates
[ https://issues.apache.org/jira/browse/AMBARI-21898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-21898: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to 2.6 and trunk. > Property provider in-memory maps are refreshed too slowly after config updates > -- > > Key: AMBARI-21898 > URL: https://issues.apache.org/jira/browse/AMBARI-21898 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.0.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21898.patch > > > Building the hostComponentMap map for ProviderModule seems does unnecessary > computation going through the ResourceProvider layer. On every configuration > update, we call the reset on these maps which takes a long time to refresh. > Instead, relying on > org.apache.ambari.server.state.cluster.ClusterImpl#serviceComponentHosts will > lead to faster computation without overhead like stale config calculations > for every SCH. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21897) Fix NPE in InstallHostTask
[
https://issues.apache.org/jira/browse/AMBARI-21897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156223#comment-16156223
]
Hudson commented on AMBARI-21897:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #159 (See
[https://builds.apache.org/job/Ambari-branch-2.6/159/])
AMBARI-21897: Fix NPE in InstallHostTask (jluniya) (jluniya:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=34dce14fdf2c946d4740d3237696a4f2021ef27a])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/topology/tasks/RegisterWithConfigGroupTask.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/topology/tasks/InstallHostTask.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/topology/tasks/PersistHostResourcesTask.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/topology/tasks/StartHostTask.java
> Fix NPE in InstallHostTask
> --
>
> Key: AMBARI-21897
> URL: https://issues.apache.org/jira/browse/AMBARI-21897
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-21897.patch
>
>
> {code}
> Exception in thread "pool-4-thread-1" java.lang.NullPointerException
> at
> org.apache.ambari.server.topology.tasks.InstallHostTask.runTask(InstallHostTask.java:54)
> at
> org.apache.ambari.server.topology.tasks.TopologyHostTask.run(TopologyHostTask.java:51)
> at
> org.apache.ambari.server.topology.HostOfferResponse$1.run(HostOfferResponse.java:83)
> 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 seems to be because response can be null if stages is null and we don't
> have a check for it.
> {code}
> RequestStatusResponse response =
> clusterTopology.installHost(hostRequest.getHostName(), skipInstallTaskCreate,
> skipFailure);
> List underlyingTasks = response.getTasks();
> {code}
> {code}
> /**
> * Build a request status response.
> *
> * @return a {@link
> org.apache.ambari.server.controller.RequestStatusResponse} for the request
> */
> public RequestStatusResponse getRequestStatusResponse() {
> RequestStatusResponse response = null;
> if (! stages.isEmpty()) {
> response = new RequestStatusResponse(id);
> List hostRoleCommands =
> actionManager.getRequestTasks(id);
> response.setRequestContext(actionManager.getRequestContext(id));
> List tasks = new ArrayList<>();
> for (HostRoleCommand hostRoleCommand : hostRoleCommands) {
> tasks.add(new ShortTaskStatus(hostRoleCommand));
> }
> response.setTasks(tasks);
> }
> return response;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21897) Fix NPE in InstallHostTask
[
https://issues.apache.org/jira/browse/AMBARI-21897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156125#comment-16156125
]
Hudson commented on AMBARI-21897:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8009 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8009/])
AMBARI-21897: Fix NPE in InstallHostTask (jluniya) (jluniya:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=98b00094c458c904b500919d4ab08190ff4c5155])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/topology/tasks/PersistHostResourcesTask.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/topology/tasks/StartHostTask.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/topology/tasks/InstallHostTask.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/topology/tasks/RegisterWithConfigGroupTask.java
> Fix NPE in InstallHostTask
> --
>
> Key: AMBARI-21897
> URL: https://issues.apache.org/jira/browse/AMBARI-21897
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-21897.patch
>
>
> {code}
> Exception in thread "pool-4-thread-1" java.lang.NullPointerException
> at
> org.apache.ambari.server.topology.tasks.InstallHostTask.runTask(InstallHostTask.java:54)
> at
> org.apache.ambari.server.topology.tasks.TopologyHostTask.run(TopologyHostTask.java:51)
> at
> org.apache.ambari.server.topology.HostOfferResponse$1.run(HostOfferResponse.java:83)
> 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 seems to be because response can be null if stages is null and we don't
> have a check for it.
> {code}
> RequestStatusResponse response =
> clusterTopology.installHost(hostRequest.getHostName(), skipInstallTaskCreate,
> skipFailure);
> List underlyingTasks = response.getTasks();
> {code}
> {code}
> /**
> * Build a request status response.
> *
> * @return a {@link
> org.apache.ambari.server.controller.RequestStatusResponse} for the request
> */
> public RequestStatusResponse getRequestStatusResponse() {
> RequestStatusResponse response = null;
> if (! stages.isEmpty()) {
> response = new RequestStatusResponse(id);
> List hostRoleCommands =
> actionManager.getRequestTasks(id);
> response.setRequestContext(actionManager.getRequestContext(id));
> List tasks = new ArrayList<>();
> for (HostRoleCommand hostRoleCommand : hostRoleCommands) {
> tasks.add(new ShortTaskStatus(hostRoleCommand));
> }
> response.setTasks(tasks);
> }
> return response;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21897) Fix NPE in InstallHostTask
[
https://issues.apache.org/jira/browse/AMBARI-21897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156086#comment-16156086
]
Jayush Luniya commented on AMBARI-21897:
Trunk
commit 98b00094c458c904b500919d4ab08190ff4c5155
Author: Jayush Luniya
Date: Wed Sep 6 14:48:02 2017 -0700
AMBARI-21897: Fix NPE in InstallHostTask (jluniya)
> Fix NPE in InstallHostTask
> --
>
> Key: AMBARI-21897
> URL: https://issues.apache.org/jira/browse/AMBARI-21897
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-21897.patch
>
>
> {code}
> Exception in thread "pool-4-thread-1" java.lang.NullPointerException
> at
> org.apache.ambari.server.topology.tasks.InstallHostTask.runTask(InstallHostTask.java:54)
> at
> org.apache.ambari.server.topology.tasks.TopologyHostTask.run(TopologyHostTask.java:51)
> at
> org.apache.ambari.server.topology.HostOfferResponse$1.run(HostOfferResponse.java:83)
> 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 seems to be because response can be null if stages is null and we don't
> have a check for it.
> {code}
> RequestStatusResponse response =
> clusterTopology.installHost(hostRequest.getHostName(), skipInstallTaskCreate,
> skipFailure);
> List underlyingTasks = response.getTasks();
> {code}
> {code}
> /**
> * Build a request status response.
> *
> * @return a {@link
> org.apache.ambari.server.controller.RequestStatusResponse} for the request
> */
> public RequestStatusResponse getRequestStatusResponse() {
> RequestStatusResponse response = null;
> if (! stages.isEmpty()) {
> response = new RequestStatusResponse(id);
> List hostRoleCommands =
> actionManager.getRequestTasks(id);
> response.setRequestContext(actionManager.getRequestContext(id));
> List tasks = new ArrayList<>();
> for (HostRoleCommand hostRoleCommand : hostRoleCommands) {
> tasks.add(new ShortTaskStatus(hostRoleCommand));
> }
> response.setTasks(tasks);
> }
> return response;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21897) Fix NPE in InstallHostTask
[
https://issues.apache.org/jira/browse/AMBARI-21897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156081#comment-16156081
]
Jayush Luniya commented on AMBARI-21897:
This can also occur in 2.6 if there are no client components on a host.
> Fix NPE in InstallHostTask
> --
>
> Key: AMBARI-21897
> URL: https://issues.apache.org/jira/browse/AMBARI-21897
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-21897.patch
>
>
> {code}
> Exception in thread "pool-4-thread-1" java.lang.NullPointerException
> at
> org.apache.ambari.server.topology.tasks.InstallHostTask.runTask(InstallHostTask.java:54)
> at
> org.apache.ambari.server.topology.tasks.TopologyHostTask.run(TopologyHostTask.java:51)
> at
> org.apache.ambari.server.topology.HostOfferResponse$1.run(HostOfferResponse.java:83)
> 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 seems to be because response can be null if stages is null and we don't
> have a check for it.
> {code}
> RequestStatusResponse response =
> clusterTopology.installHost(hostRequest.getHostName(), skipInstallTaskCreate,
> skipFailure);
> List underlyingTasks = response.getTasks();
> {code}
> {code}
> /**
> * Build a request status response.
> *
> * @return a {@link
> org.apache.ambari.server.controller.RequestStatusResponse} for the request
> */
> public RequestStatusResponse getRequestStatusResponse() {
> RequestStatusResponse response = null;
> if (! stages.isEmpty()) {
> response = new RequestStatusResponse(id);
> List hostRoleCommands =
> actionManager.getRequestTasks(id);
> response.setRequestContext(actionManager.getRequestContext(id));
> List tasks = new ArrayList<>();
> for (HostRoleCommand hostRoleCommand : hostRoleCommands) {
> tasks.add(new ShortTaskStatus(hostRoleCommand));
> }
> response.setTasks(tasks);
> }
> return response;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21897) Fix NPE in InstallHostTask
[
https://issues.apache.org/jira/browse/AMBARI-21897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-21897:
---
Affects Version/s: (was: 3.0.0)
2.6.0
> Fix NPE in InstallHostTask
> --
>
> Key: AMBARI-21897
> URL: https://issues.apache.org/jira/browse/AMBARI-21897
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-21897.patch
>
>
> {code}
> Exception in thread "pool-4-thread-1" java.lang.NullPointerException
> at
> org.apache.ambari.server.topology.tasks.InstallHostTask.runTask(InstallHostTask.java:54)
> at
> org.apache.ambari.server.topology.tasks.TopologyHostTask.run(TopologyHostTask.java:51)
> at
> org.apache.ambari.server.topology.HostOfferResponse$1.run(HostOfferResponse.java:83)
> 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 seems to be because response can be null if stages is null and we don't
> have a check for it.
> {code}
> RequestStatusResponse response =
> clusterTopology.installHost(hostRequest.getHostName(), skipInstallTaskCreate,
> skipFailure);
> List underlyingTasks = response.getTasks();
> {code}
> {code}
> /**
> * Build a request status response.
> *
> * @return a {@link
> org.apache.ambari.server.controller.RequestStatusResponse} for the request
> */
> public RequestStatusResponse getRequestStatusResponse() {
> RequestStatusResponse response = null;
> if (! stages.isEmpty()) {
> response = new RequestStatusResponse(id);
> List hostRoleCommands =
> actionManager.getRequestTasks(id);
> response.setRequestContext(actionManager.getRequestContext(id));
> List tasks = new ArrayList<>();
> for (HostRoleCommand hostRoleCommand : hostRoleCommands) {
> tasks.add(new ShortTaskStatus(hostRoleCommand));
> }
> response.setTasks(tasks);
> }
> return response;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21897) Fix NPE in InstallHostTask
[
https://issues.apache.org/jira/browse/AMBARI-21897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-21897:
---
Fix Version/s: (was: 3.0.0)
2.6.0
> Fix NPE in InstallHostTask
> --
>
> Key: AMBARI-21897
> URL: https://issues.apache.org/jira/browse/AMBARI-21897
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-21897.patch
>
>
> {code}
> Exception in thread "pool-4-thread-1" java.lang.NullPointerException
> at
> org.apache.ambari.server.topology.tasks.InstallHostTask.runTask(InstallHostTask.java:54)
> at
> org.apache.ambari.server.topology.tasks.TopologyHostTask.run(TopologyHostTask.java:51)
> at
> org.apache.ambari.server.topology.HostOfferResponse$1.run(HostOfferResponse.java:83)
> 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 seems to be because response can be null if stages is null and we don't
> have a check for it.
> {code}
> RequestStatusResponse response =
> clusterTopology.installHost(hostRequest.getHostName(), skipInstallTaskCreate,
> skipFailure);
> List underlyingTasks = response.getTasks();
> {code}
> {code}
> /**
> * Build a request status response.
> *
> * @return a {@link
> org.apache.ambari.server.controller.RequestStatusResponse} for the request
> */
> public RequestStatusResponse getRequestStatusResponse() {
> RequestStatusResponse response = null;
> if (! stages.isEmpty()) {
> response = new RequestStatusResponse(id);
> List hostRoleCommands =
> actionManager.getRequestTasks(id);
> response.setRequestContext(actionManager.getRequestContext(id));
> List tasks = new ArrayList<>();
> for (HostRoleCommand hostRoleCommand : hostRoleCommands) {
> tasks.add(new ShortTaskStatus(hostRoleCommand));
> }
> response.setTasks(tasks);
> }
> return response;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21898) Property provider in-memory maps are refreshed too slowly after config updates
[ https://issues.apache.org/jira/browse/AMBARI-21898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-21898: - Status: Patch Available (was: Open) > Property provider in-memory maps are refreshed too slowly after config updates > -- > > Key: AMBARI-21898 > URL: https://issues.apache.org/jira/browse/AMBARI-21898 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.0.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21898.patch > > > Building the hostComponentMap map for ProviderModule seems does unnecessary > computation going through the ResourceProvider layer. On every configuration > update, we call the reset on these maps which takes a long time to refresh. > Instead, relying on > org.apache.ambari.server.state.cluster.ClusterImpl#serviceComponentHosts will > lead to faster computation without overhead like stale config calculations > for every SCH. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21898) Property provider in-memory maps are refreshed too slowly after config updates
[ https://issues.apache.org/jira/browse/AMBARI-21898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-21898: - Attachment: AMBARI-21898.patch > Property provider in-memory maps are refreshed too slowly after config updates > -- > > Key: AMBARI-21898 > URL: https://issues.apache.org/jira/browse/AMBARI-21898 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.0.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21898.patch > > > Building the hostComponentMap map for ProviderModule seems does unnecessary > computation going through the ResourceProvider layer. On every configuration > update, we call the reset on these maps which takes a long time to refresh. > Instead, relying on > org.apache.ambari.server.state.cluster.ClusterImpl#serviceComponentHosts will > lead to faster computation without overhead like stale config calculations > for every SCH. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21898) Property provider in-memory maps are refreshed too slowly after config updates
Siddharth Wagle created AMBARI-21898: Summary: Property provider in-memory maps are refreshed too slowly after config updates Key: AMBARI-21898 URL: https://issues.apache.org/jira/browse/AMBARI-21898 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.0.0 Reporter: Siddharth Wagle Assignee: Siddharth Wagle Priority: Critical Fix For: 2.6.0 Building the hostComponentMap map for ProviderModule seems does unnecessary computation going through the ResourceProvider layer. On every configuration update, we call the reset on these maps which takes a long time to refresh. Instead, relying on org.apache.ambari.server.state.cluster.ClusterImpl#serviceComponentHosts will lead to faster computation without overhead like stale config calculations for every SCH. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21895) Upgrades: Ranger & KMS should be stopped before backup
[ https://issues.apache.org/jira/browse/AMBARI-21895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156013#comment-16156013 ] Hudson commented on AMBARI-21895: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #152 (See [https://builds.apache.org/job/Ambari-branch-2.6/152/]) AMBARI-21895. Upgrades: Ranger & KMS should be stopped before backup (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=373d131ce8bd801a9cb204b597a3c3a7f73fa0d0]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.3.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.5.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.5.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.5.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.4.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.4.xml > Upgrades: Ranger & KMS should be stopped before backup > -- > > Key: AMBARI-21895 > URL: https://issues.apache.org/jira/browse/AMBARI-21895 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21895.patch > > > Story: > As the Database Administrator, > when performing an express upgrade, > I require Ranger & Ranger KMS to be stopped before performing the database > backup. > More notes: > - We are asked to backup the Ranger & Ranger KMS databases before they are > stopped. > - It's best to stop a service before doing database backups. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21897) Fix NPE in InstallHostTask
[
https://issues.apache.org/jira/browse/AMBARI-21897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-21897:
---
Attachment: AMBARI-21897.patch
> Fix NPE in InstallHostTask
> --
>
> Key: AMBARI-21897
> URL: https://issues.apache.org/jira/browse/AMBARI-21897
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: AMBARI-21897.patch
>
>
> {code}
> Exception in thread "pool-4-thread-1" java.lang.NullPointerException
> at
> org.apache.ambari.server.topology.tasks.InstallHostTask.runTask(InstallHostTask.java:54)
> at
> org.apache.ambari.server.topology.tasks.TopologyHostTask.run(TopologyHostTask.java:51)
> at
> org.apache.ambari.server.topology.HostOfferResponse$1.run(HostOfferResponse.java:83)
> 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 seems to be because response can be null if stages is null and we don't
> have a check for it.
> {code}
> RequestStatusResponse response =
> clusterTopology.installHost(hostRequest.getHostName(), skipInstallTaskCreate,
> skipFailure);
> List underlyingTasks = response.getTasks();
> {code}
> {code}
> /**
> * Build a request status response.
> *
> * @return a {@link
> org.apache.ambari.server.controller.RequestStatusResponse} for the request
> */
> public RequestStatusResponse getRequestStatusResponse() {
> RequestStatusResponse response = null;
> if (! stages.isEmpty()) {
> response = new RequestStatusResponse(id);
> List hostRoleCommands =
> actionManager.getRequestTasks(id);
> response.setRequestContext(actionManager.getRequestContext(id));
> List tasks = new ArrayList<>();
> for (HostRoleCommand hostRoleCommand : hostRoleCommands) {
> tasks.add(new ShortTaskStatus(hostRoleCommand));
> }
> response.setTasks(tasks);
> }
> return response;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21897) Fix NPE in InstallHostTask
[
https://issues.apache.org/jira/browse/AMBARI-21897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-21897:
---
Status: Patch Available (was: Open)
> Fix NPE in InstallHostTask
> --
>
> Key: AMBARI-21897
> URL: https://issues.apache.org/jira/browse/AMBARI-21897
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: AMBARI-21897.patch
>
>
> {code}
> Exception in thread "pool-4-thread-1" java.lang.NullPointerException
> at
> org.apache.ambari.server.topology.tasks.InstallHostTask.runTask(InstallHostTask.java:54)
> at
> org.apache.ambari.server.topology.tasks.TopologyHostTask.run(TopologyHostTask.java:51)
> at
> org.apache.ambari.server.topology.HostOfferResponse$1.run(HostOfferResponse.java:83)
> 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 seems to be because response can be null if stages is null and we don't
> have a check for it.
> {code}
> RequestStatusResponse response =
> clusterTopology.installHost(hostRequest.getHostName(), skipInstallTaskCreate,
> skipFailure);
> List underlyingTasks = response.getTasks();
> {code}
> {code}
> /**
> * Build a request status response.
> *
> * @return a {@link
> org.apache.ambari.server.controller.RequestStatusResponse} for the request
> */
> public RequestStatusResponse getRequestStatusResponse() {
> RequestStatusResponse response = null;
> if (! stages.isEmpty()) {
> response = new RequestStatusResponse(id);
> List hostRoleCommands =
> actionManager.getRequestTasks(id);
> response.setRequestContext(actionManager.getRequestContext(id));
> List tasks = new ArrayList<>();
> for (HostRoleCommand hostRoleCommand : hostRoleCommands) {
> tasks.add(new ShortTaskStatus(hostRoleCommand));
> }
> response.setTasks(tasks);
> }
> return response;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21897) Fix NPE in InstallHostTask
Jayush Luniya created AMBARI-21897:
--
Summary: Fix NPE in InstallHostTask
Key: AMBARI-21897
URL: https://issues.apache.org/jira/browse/AMBARI-21897
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 3.0.0
Reporter: Jayush Luniya
Assignee: Jayush Luniya
Priority: Blocker
Fix For: 3.0.0
{code}
Exception in thread "pool-4-thread-1" java.lang.NullPointerException
at
org.apache.ambari.server.topology.tasks.InstallHostTask.runTask(InstallHostTask.java:54)
at
org.apache.ambari.server.topology.tasks.TopologyHostTask.run(TopologyHostTask.java:51)
at
org.apache.ambari.server.topology.HostOfferResponse$1.run(HostOfferResponse.java:83)
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 seems to be because response can be null if stages is null and we don't
have a check for it.
{code}
RequestStatusResponse response =
clusterTopology.installHost(hostRequest.getHostName(), skipInstallTaskCreate,
skipFailure);
List underlyingTasks = response.getTasks();
{code}
{code}
/**
* Build a request status response.
*
* @return a {@link org.apache.ambari.server.controller.RequestStatusResponse}
for the request
*/
public RequestStatusResponse getRequestStatusResponse() {
RequestStatusResponse response = null;
if (! stages.isEmpty()) {
response = new RequestStatusResponse(id);
List hostRoleCommands =
actionManager.getRequestTasks(id);
response.setRequestContext(actionManager.getRequestContext(id));
List tasks = new ArrayList<>();
for (HostRoleCommand hostRoleCommand : hostRoleCommands) {
tasks.add(new ShortTaskStatus(hostRoleCommand));
}
response.setTasks(tasks);
}
return response;
}
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21894) PATCH and MAINT Repositories Should Indicate that they can be Reverted
[
https://issues.apache.org/jira/browse/AMBARI-21894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-21894:
-
Description:
In the current PU UI, the revert button is shown for any PATCH type repository.
The backend should compute whether a version can be reverted.
The backed should return a value, such as
{{ClusterStackVersions/supports_revert}} which clients, such as the web client,
can use.
{code:title=Example REST Changes}
{
"ClusterStackVersions": {
"cluster_name": "c1",
"id": 51,
"repository_version": 51,
"revert_upgrade_id": 1,
"stack": "HDP",
"supports_revert": true,
"version": "2.6"
}
}
{code}
was:
In the current PU UI, the revert button is shown for any PATCH type repository.
The backend should compute whether a version can be reverted.
The backed should return a value, such as
{{ClusterStackVersions/supports_revert}} which clients, such as the web client,
can use.
> PATCH and MAINT Repositories Should Indicate that they can be Reverted
> --
>
> Key: AMBARI-21894
> URL: https://issues.apache.org/jira/browse/AMBARI-21894
> Project: Ambari
> Issue Type: Task
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-21894.patch
>
>
> In the current PU UI, the revert button is shown for any PATCH type
> repository. The backend should compute whether a version can be reverted.
> The backed should return a value, such as
> {{ClusterStackVersions/supports_revert}} which clients, such as the web
> client, can use.
> {code:title=Example REST Changes}
> {
> "ClusterStackVersions": {
> "cluster_name": "c1",
> "id": 51,
> "repository_version": 51,
> "revert_upgrade_id": 1,
> "stack": "HDP",
> "supports_revert": true,
> "version": "2.6"
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21894) PATCH and MAINT Repositories Should Indicate that they can be Reverted
[
https://issues.apache.org/jira/browse/AMBARI-21894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-21894:
-
Attachment: AMBARI-21894.patch
> PATCH and MAINT Repositories Should Indicate that they can be Reverted
> --
>
> Key: AMBARI-21894
> URL: https://issues.apache.org/jira/browse/AMBARI-21894
> Project: Ambari
> Issue Type: Task
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-21894.patch
>
>
> In the current PU UI, the revert button is shown for any PATCH type
> repository. The backend should compute whether a version can be reverted.
> The backed should return a value, such as
> {{ClusterStackVersions/supports_revert}} which clients, such as the web
> client, can use.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21894) PATCH and MAINT Repositories Should Indicate that they can be Reverted
[
https://issues.apache.org/jira/browse/AMBARI-21894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-21894:
-
Status: Patch Available (was: Open)
> PATCH and MAINT Repositories Should Indicate that they can be Reverted
> --
>
> Key: AMBARI-21894
> URL: https://issues.apache.org/jira/browse/AMBARI-21894
> Project: Ambari
> Issue Type: Task
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.0
>
>
> In the current PU UI, the revert button is shown for any PATCH type
> repository. The backend should compute whether a version can be reverted.
> The backed should return a value, such as
> {{ClusterStackVersions/supports_revert}} which clients, such as the web
> client, can use.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21895) Upgrades: Ranger & KMS should be stopped before backup
[ https://issues.apache.org/jira/browse/AMBARI-21895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-21895: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Upgrades: Ranger & KMS should be stopped before backup > -- > > Key: AMBARI-21895 > URL: https://issues.apache.org/jira/browse/AMBARI-21895 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21895.patch > > > Story: > As the Database Administrator, > when performing an express upgrade, > I require Ranger & Ranger KMS to be stopped before performing the database > backup. > More notes: > - We are asked to backup the Ranger & Ranger KMS databases before they are > stopped. > - It's best to stop a service before doing database backups. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21896) Ambari should honor permissions specified for dfs.datanode.data.dir.perm when creating datanode dir's
Sanjeev created AMBARI-21896:
Summary: Ambari should honor permissions specified for
dfs.datanode.data.dir.perm when creating datanode dir's
Key: AMBARI-21896
URL: https://issues.apache.org/jira/browse/AMBARI-21896
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.1
Environment: Ambari 2.5.1
Reporter: Sanjeev
Priority: Minor
Give this:
dfs.datanode.data.dir.perm
750
Ambari reports as changing permission from 750 to 755 on the data dirs:
2017-09-01 16:39:28,877 - Forcefully ensuring existence and permissions of the
directory: /hadoop01/data
2017-09-01 16:39:28,878 - Directory['/hadoop01/data'] {'group': 'hadoop',
'cd_access': 'a', 'create_parents': True, 'ignore_failures': True, 'mode':
0755, 'owner': 'hdfs'}
2017-09-01 16:39:28,878 - Changing permission for /hadoop01/data from 750 to
755
2017-09-01 16:39:28,879 - Mount point for directory /hadoop02/data is /hadoop02
2017-09-01 16:39:28,880 - Forcefully ensuring existence and permissions of the
directory: /hadoop02/data
2017-09-01 16:39:28,880 - Directory['/hadoop02/data'] {'group': 'hadoop',
'cd_access': 'a', 'create_parents': True, 'ignore_failures': True, 'mode':
0755, 'owner': 'hdfs'}
2017-09-01 16:39:28,880 - Changing permission for /hadoop02/data from 750 to
755
2017-09-01 16:39:28,881 - Mount point for directory /hadoop03/data is /hadoop03
2017-09-01 16:39:28,881 - Forcefully ensuring existence and permissions of the
directory: /hadoop03/data
2017-09-01 16:39:28,882 - Directory['/hadoop03/data'] {'group': 'hadoop',
'cd_access': 'a', 'create_parents': True, 'ignore_failures': True, 'mode':
0755, 'owner': 'hdfs'}
2017-09-01 16:39:28,882 - Changing permission for /hadoop03/data from 750 to
755
2017-09-01 16:39:28,882 - Mount point for directory /hadoop04/data is /hadoop04
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21895) Upgrades: Ranger & KMS should be stopped before backup
[ https://issues.apache.org/jira/browse/AMBARI-21895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-21895: --- Attachment: AMBARI-21895.patch > Upgrades: Ranger & KMS should be stopped before backup > -- > > Key: AMBARI-21895 > URL: https://issues.apache.org/jira/browse/AMBARI-21895 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21895.patch > > > Story: > As the Database Administrator, > when performing an express upgrade, > I require Ranger & Ranger KMS to be stopped before performing the database > backup. > More notes: > - We are asked to backup the Ranger & Ranger KMS databases before they are > stopped. > - It's best to stop a service before doing database backups. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21895) Upgrades: Ranger & KMS should be stopped before backup
[ https://issues.apache.org/jira/browse/AMBARI-21895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-21895: --- Status: Patch Available (was: Open) > Upgrades: Ranger & KMS should be stopped before backup > -- > > Key: AMBARI-21895 > URL: https://issues.apache.org/jira/browse/AMBARI-21895 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21895.patch > > > Story: > As the Database Administrator, > when performing an express upgrade, > I require Ranger & Ranger KMS to be stopped before performing the database > backup. > More notes: > - We are asked to backup the Ranger & Ranger KMS databases before they are > stopped. > - It's best to stop a service before doing database backups. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21895) Upgrades: Ranger & KMS should be stopped before backup
Nate Cole created AMBARI-21895: -- Summary: Upgrades: Ranger & KMS should be stopped before backup Key: AMBARI-21895 URL: https://issues.apache.org/jira/browse/AMBARI-21895 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Priority: Critical Fix For: 2.6.0 Story: As the Database Administrator, when performing an express upgrade, I require Ranger & Ranger KMS to be stopped before performing the database backup. More notes: - We are asked to backup the Ranger & Ranger KMS databases before they are stopped. - It's best to stop a service before doing database backups. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21894) PATCH and MAINT Repositories Should Indicate that they can be Reverted
Jonathan Hurley created AMBARI-21894:
Summary: PATCH and MAINT Repositories Should Indicate that they
can be Reverted
Key: AMBARI-21894
URL: https://issues.apache.org/jira/browse/AMBARI-21894
Project: Ambari
Issue Type: Task
Affects Versions: 2.6.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Priority: Blocker
Fix For: 2.6.0
In the current PU UI, the revert button is shown for any PATCH type repository.
The backend should compute whether a version can be reverted.
The backed should return a value, such as
{{ClusterStackVersions/supports_revert}} which clients, such as the web client,
can use.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21871) Add new graphs to HBase RegionServer dashboard in Grafana
[ https://issues.apache.org/jira/browse/AMBARI-21871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155813#comment-16155813 ] Hudson commented on AMBARI-21871: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8008 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8008/]) AMBARI-21871 : Add new graphs to HBase RegionServer dashboard in (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=54d4d5e62d836d926bca79fea6b48503803db8fb]) * (edit) ambari-metrics/ambari-metrics-timelineservice/conf/unix/metrics_whitelist * (edit) ambari-metrics/ambari-metrics-timelineservice/conf/windows/metrics_whitelist * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-hbase-regionservers.json > Add new graphs to HBase RegionServer dashboard in Grafana > - > > Key: AMBARI-21871 > URL: https://issues.apache.org/jira/browse/AMBARI-21871 > Project: Ambari > Issue Type: Task >Affects Versions: 2.6.0 >Reporter: Josh Elser >Assignee: Aravindan Vijayan > Fix For: 2.6.0 > > Attachments: AMBARI-21871.patch, HBase - RegionServers-1504152031247 > > > HBASE-15160 and HBASE-18184 added some new HDFS-level metrics to HBase > RegionServers which would be good to expose in the HBase RegionServers > dashboard in grafana. > I'll attach a modified version of the JSON exported from my locally modified > dashboard. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21883) Upgrade to Ambari 2.6.0 fails with DB constraint violation on fk_sc_history_upgrade_id
[
https://issues.apache.org/jira/browse/AMBARI-21883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155814#comment-16155814
]
Hudson commented on AMBARI-21883:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8008 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8008/])
AMBARI-21883. Upgrade to Ambari 2.6.0 fails with DB constraint violation
(dlysnichenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0c45d48f5d82edbe096461c51832aa90d97593a4])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelper.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog260.java
> Upgrade to Ambari 2.6.0 fails with DB constraint violation on
> fk_sc_history_upgrade_id
> --
>
> Key: AMBARI-21883
> URL: https://issues.apache.org/jira/browse/AMBARI-21883
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-21883.patch
>
>
> When performing an Ambari upgrade to Ambari 2.6.0 using {{ambari-server
> upgrade}}, the process fails with the following error:
> {noformat}
> 01 Sep 2017 14:36:24,340 ERROR [main] DBAccessorImpl:882 - Error executing
> query: DELETE FROM upgrade
> org.postgresql.util.PSQLException: ERROR: update or delete on table "upgrade"
> violates foreign key constraint "fk_sc_history_upgrade_id" on table
> "servicecomponent_history"
> Detail: Key (upgrade_id)=(1) is still referenced from table
> "servicecomponent_history".
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2161)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1890)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:559)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:403)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:395)
> at
> org.apache.ambari.server.orm.DBAccessorImpl.executeQuery(DBAccessorImpl.java:879)
> at
> org.apache.ambari.server.orm.DBAccessorImpl.executeQuery(DBAccessorImpl.java:871)
> at
> org.apache.ambari.server.orm.DBAccessorImpl.clearTable(DBAccessorImpl.java:1502)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog260.updateUpgradeTable(UpgradeCatalog260.java:225)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog260.executeDDLUpdates(UpgradeCatalog260.java:153)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:923)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:197)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:415)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21883) Upgrade to Ambari 2.6.0 fails with DB constraint violation on fk_sc_history_upgrade_id
[
https://issues.apache.org/jira/browse/AMBARI-21883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155792#comment-16155792
]
Hudson commented on AMBARI-21883:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #147 (See
[https://builds.apache.org/job/Ambari-branch-2.6/147/])
AMBARI-21883. Upgrade to Ambari 2.6.0 fails with DB constraint violation
(dlysnichenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8187ecddaedeaf0621f14f2fcca0c492d9372380])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog260.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelper.java
> Upgrade to Ambari 2.6.0 fails with DB constraint violation on
> fk_sc_history_upgrade_id
> --
>
> Key: AMBARI-21883
> URL: https://issues.apache.org/jira/browse/AMBARI-21883
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-21883.patch
>
>
> When performing an Ambari upgrade to Ambari 2.6.0 using {{ambari-server
> upgrade}}, the process fails with the following error:
> {noformat}
> 01 Sep 2017 14:36:24,340 ERROR [main] DBAccessorImpl:882 - Error executing
> query: DELETE FROM upgrade
> org.postgresql.util.PSQLException: ERROR: update or delete on table "upgrade"
> violates foreign key constraint "fk_sc_history_upgrade_id" on table
> "servicecomponent_history"
> Detail: Key (upgrade_id)=(1) is still referenced from table
> "servicecomponent_history".
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2161)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1890)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:559)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:403)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:395)
> at
> org.apache.ambari.server.orm.DBAccessorImpl.executeQuery(DBAccessorImpl.java:879)
> at
> org.apache.ambari.server.orm.DBAccessorImpl.executeQuery(DBAccessorImpl.java:871)
> at
> org.apache.ambari.server.orm.DBAccessorImpl.clearTable(DBAccessorImpl.java:1502)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog260.updateUpgradeTable(UpgradeCatalog260.java:225)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog260.executeDDLUpdates(UpgradeCatalog260.java:153)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:923)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:197)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:415)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21871) Add new graphs to HBase RegionServer dashboard in Grafana
[ https://issues.apache.org/jira/browse/AMBARI-21871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155791#comment-16155791 ] Hudson commented on AMBARI-21871: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #147 (See [https://builds.apache.org/job/Ambari-branch-2.6/147/]) AMBARI-21871 : Add new graphs to HBase RegionServer dashboard in (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9e3030517a75fd3c8c0b6bb604b57992e745914a]) * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-hbase-regionservers.json * (edit) ambari-metrics/ambari-metrics-timelineservice/conf/unix/metrics_whitelist * (edit) ambari-metrics/ambari-metrics-timelineservice/conf/windows/metrics_whitelist > Add new graphs to HBase RegionServer dashboard in Grafana > - > > Key: AMBARI-21871 > URL: https://issues.apache.org/jira/browse/AMBARI-21871 > Project: Ambari > Issue Type: Task >Affects Versions: 2.6.0 >Reporter: Josh Elser >Assignee: Aravindan Vijayan > Fix For: 2.6.0 > > Attachments: AMBARI-21871.patch, HBase - RegionServers-1504152031247 > > > HBASE-15160 and HBASE-18184 added some new HDFS-level metrics to HBase > RegionServers which would be good to expose in the HBase RegionServers > dashboard in grafana. > I'll attach a modified version of the JSON exported from my locally modified > dashboard. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21884) Installation should ignore OS that are not managed by Ambari
[
https://issues.apache.org/jira/browse/AMBARI-21884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155758#comment-16155758
]
Hudson commented on AMBARI-21884:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8007 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8007/])
AMBARI-21884. Installation should ignore OS that are not managed by (ncole:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=249bb97a864c0f18278d37d87c2c3117809e5ca4])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/agent/CommandRepository.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/RepositoryVersionHelper.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProviderTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProvider.java
* (edit)
ambari-common/src/main/python/resource_management/libraries/functions/repository_util.py
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostStackVersionResourceProvider.java
* (edit) ambari-server/src/main/resources/version_definition.xsd
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariCustomCommandExecutionHelperTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariCustomCommandExecutionHelper.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/actionmanager/ExecutionCommandWrapperTest.java
> Installation should ignore OS that are not managed by Ambari
>
>
> Key: AMBARI-21884
> URL: https://issues.apache.org/jira/browse/AMBARI-21884
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21884.patch
>
>
> The new {{repositoryFile}} structure should ignore OS that are not managed by
> Ambari on initial startup.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21893) NameNode Heap Usage (Daily) metric alert status flips to UNKNOWN intermittently when AMS HTTPS is enabled.
[ https://issues.apache.org/jira/browse/AMBARI-21893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-21893: --- Status: Patch Available (was: Open) > NameNode Heap Usage (Daily) metric alert status flips to UNKNOWN > intermittently when AMS HTTPS is enabled. > -- > > Key: AMBARI-21893 > URL: https://issues.apache.org/jira/browse/AMBARI-21893 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.6.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.6.0 > > Attachments: AMBARI-21893.patch > > > Underlying Issue > This issue is because of AMS HTTPS + HA scenario. The CA cert file > (/etc/ambari-metrics-monitor/conf/ca.pem) found on every host is generated by > fetching a specific metric collector host's certificate from the truststore. > This certificate file is being used by alert script, service check and even > monitors to talk to collector. > * For example, in a cluster with hosts H1 to H5, let's say there are 2 > collectors - H1 & H2. > * On a node H3, let's say the ca.pem file was constructed using the > certificate for collector H2. > * Service check or metric monitor on H3 will NOT be able to talk to H1 since > it does not have the certificate for that host. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21893) NameNode Heap Usage (Daily) metric alert status flips to UNKNOWN intermittently when AMS HTTPS is enabled.
[ https://issues.apache.org/jira/browse/AMBARI-21893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-21893: --- Attachment: AMBARI-21893.patch > NameNode Heap Usage (Daily) metric alert status flips to UNKNOWN > intermittently when AMS HTTPS is enabled. > -- > > Key: AMBARI-21893 > URL: https://issues.apache.org/jira/browse/AMBARI-21893 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.6.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.6.0 > > Attachments: AMBARI-21893.patch > > > Underlying Issue > This issue is because of AMS HTTPS + HA scenario. The CA cert file > (/etc/ambari-metrics-monitor/conf/ca.pem) found on every host is generated by > fetching a specific metric collector host's certificate from the truststore. > This certificate file is being used by alert script, service check and even > monitors to talk to collector. > * For example, in a cluster with hosts H1 to H5, let's say there are 2 > collectors - H1 & H2. > * On a node H3, let's say the ca.pem file was constructed using the > certificate for collector H2. > * Service check or metric monitor on H3 will NOT be able to talk to H1 since > it does not have the certificate for that host. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21884) Installation should ignore OS that are not managed by Ambari
[
https://issues.apache.org/jira/browse/AMBARI-21884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155726#comment-16155726
]
Hudson commented on AMBARI-21884:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #146 (See
[https://builds.apache.org/job/Ambari-branch-2.6/146/])
AMBARI-21884. Installation should ignore OS that are not managed by (ncole:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=78f1ee56c1677f09125ba8b7dca279c15b4976b3])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariCustomCommandExecutionHelperTest.java
* (edit)
ambari-common/src/main/python/resource_management/libraries/functions/repository_util.py
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostStackVersionResourceProvider.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProviderTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/agent/CommandRepository.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariCustomCommandExecutionHelper.java
* (edit) ambari-server/src/main/resources/version_definition.xsd
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProvider.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/RepositoryVersionHelper.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/actionmanager/ExecutionCommandWrapperTest.java
> Installation should ignore OS that are not managed by Ambari
>
>
> Key: AMBARI-21884
> URL: https://issues.apache.org/jira/browse/AMBARI-21884
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21884.patch
>
>
> The new {{repositoryFile}} structure should ignore OS that are not managed by
> Ambari on initial startup.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21892) Unable to proceed to Choose services step
[
https://issues.apache.org/jira/browse/AMBARI-21892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155725#comment-16155725
]
Hudson commented on AMBARI-21892:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #146 (See
[https://builds.apache.org/job/Ambari-branch-2.6/146/])
AMBARI-21892. Unable to proceed to Choose services step (akovalenko)
(akovalenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=fbf7a104c00a9afa6c1b11e3cb68cc26e5d2a6ab])
* (edit) ambari-web/app/controllers/installer.js
> Unable to proceed to Choose services step
> -
>
> Key: AMBARI-21892
> URL: https://issues.apache.org/jira/browse/AMBARI-21892
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-21892_branch-2.6.patch, AMBARI-21892.patch
>
>
> JS error happens while transiting from Install Options to Confirm Hosts page.
> {noformat}
> Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.setSelected (app.js:3630)
> at Class.getSupportedOSListSuccessCallback (app.js:4022)
> at Class.opt.success (app.js:171617)
> at fire (vendor.js:1141)
> at Object.fireWith [as resolveWith] (vendor.js:1252)
> at done (vendor.js:8178)
> at XMLHttpRequest.callback (vendor.js:8702)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21893) NameNode Heap Usage (Daily) metric alert status flips to UNKNOWN intermittently when AMS HTTPS is enabled.
Aravindan Vijayan created AMBARI-21893: -- Summary: NameNode Heap Usage (Daily) metric alert status flips to UNKNOWN intermittently when AMS HTTPS is enabled. Key: AMBARI-21893 URL: https://issues.apache.org/jira/browse/AMBARI-21893 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.6.0 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 2.6.0 Underlying Issue This issue is because of AMS HTTPS + HA scenario. The CA cert file (/etc/ambari-metrics-monitor/conf/ca.pem) found on every host is generated by fetching a specific metric collector host's certificate from the truststore. This certificate file is being used by alert script, service check and even monitors to talk to collector. * For example, in a cluster with hosts H1 to H5, let's say there are 2 collectors - H1 & H2. * On a node H3, let's say the ca.pem file was constructed using the certificate for collector H2. * Service check or metric monitor on H3 will NOT be able to talk to H1 since it does not have the certificate for that host. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21883) Upgrade to Ambari 2.6.0 fails with DB constraint violation on fk_sc_history_upgrade_id
[
https://issues.apache.org/jira/browse/AMBARI-21883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-21883:
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed
To https://git-wip-us.apache.org/repos/asf/ambari.git
9e3030517a..8187ecddae branch-2.6 -> branch-2.6
54d4d5e62d..0c45d48f5d trunk -> trunk
> Upgrade to Ambari 2.6.0 fails with DB constraint violation on
> fk_sc_history_upgrade_id
> --
>
> Key: AMBARI-21883
> URL: https://issues.apache.org/jira/browse/AMBARI-21883
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-21883.patch
>
>
> When performing an Ambari upgrade to Ambari 2.6.0 using {{ambari-server
> upgrade}}, the process fails with the following error:
> {noformat}
> 01 Sep 2017 14:36:24,340 ERROR [main] DBAccessorImpl:882 - Error executing
> query: DELETE FROM upgrade
> org.postgresql.util.PSQLException: ERROR: update or delete on table "upgrade"
> violates foreign key constraint "fk_sc_history_upgrade_id" on table
> "servicecomponent_history"
> Detail: Key (upgrade_id)=(1) is still referenced from table
> "servicecomponent_history".
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2161)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1890)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:559)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:403)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:395)
> at
> org.apache.ambari.server.orm.DBAccessorImpl.executeQuery(DBAccessorImpl.java:879)
> at
> org.apache.ambari.server.orm.DBAccessorImpl.executeQuery(DBAccessorImpl.java:871)
> at
> org.apache.ambari.server.orm.DBAccessorImpl.clearTable(DBAccessorImpl.java:1502)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog260.updateUpgradeTable(UpgradeCatalog260.java:225)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog260.executeDDLUpdates(UpgradeCatalog260.java:153)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:923)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:197)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:415)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21871) Add new graphs to HBase RegionServer dashboard in Grafana
[ https://issues.apache.org/jira/browse/AMBARI-21871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-21871: --- Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to branch-2.6 and trunk. > Add new graphs to HBase RegionServer dashboard in Grafana > - > > Key: AMBARI-21871 > URL: https://issues.apache.org/jira/browse/AMBARI-21871 > Project: Ambari > Issue Type: Task >Affects Versions: 2.6.0 >Reporter: Josh Elser >Assignee: Aravindan Vijayan > Fix For: 2.6.0 > > Attachments: AMBARI-21871.patch, HBase - RegionServers-1504152031247 > > > HBASE-15160 and HBASE-18184 added some new HDFS-level metrics to HBase > RegionServers which would be good to expose in the HBase RegionServers > dashboard in grafana. > I'll attach a modified version of the JSON exported from my locally modified > dashboard. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21891) Fix AmbariServerTest
[
https://issues.apache.org/jira/browse/AMBARI-21891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155673#comment-16155673
]
Hudson commented on AMBARI-21891:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8006 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8006/])
AMBARI-21891. Fix AmbariServerTest.(vbrodetskyi) (vbrodetskyi:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f3232d20436bf3944ae0b8359e71d840a6d132ac])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelper.java
> Fix AmbariServerTest
>
>
> Key: AMBARI-21891
> URL: https://issues.apache.org/jira/browse/AMBARI-21891
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21891.patch
>
>
> AmbariServerTest fails with:
> {code}
> Error occurred in starting fork, check output in log
> Process Exit Code: 1
> Crashed tests:
> org.apache.ambari.server.controller.AmbariServerTest
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:292)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:243)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1077)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:907)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:785)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(Mave
> Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The
> forked VM terminated without properly saying goodbye. VM crash or System.exit
> called?
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21884) Installation should ignore OS that are not managed by Ambari
[
https://issues.apache.org/jira/browse/AMBARI-21884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole updated AMBARI-21884:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Installation should ignore OS that are not managed by Ambari
>
>
> Key: AMBARI-21884
> URL: https://issues.apache.org/jira/browse/AMBARI-21884
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21884.patch
>
>
> The new {{repositoryFile}} structure should ignore OS that are not managed by
> Ambari on initial startup.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21892) Unable to proceed to Choose services step
[
https://issues.apache.org/jira/browse/AMBARI-21892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1611#comment-1611
]
Hudson commented on AMBARI-21892:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8003 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8003/])
AMBARI-21892. Unable to proceed to Choose services step (akovalenko)
(akovalenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8de9b06d93765f81487f5dc27f2b175bf475b0cb])
* (edit) ambari-web/app/controllers/installer.js
> Unable to proceed to Choose services step
> -
>
> Key: AMBARI-21892
> URL: https://issues.apache.org/jira/browse/AMBARI-21892
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-21892_branch-2.6.patch, AMBARI-21892.patch
>
>
> JS error happens while transiting from Install Options to Confirm Hosts page.
> {noformat}
> Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.setSelected (app.js:3630)
> at Class.getSupportedOSListSuccessCallback (app.js:4022)
> at Class.opt.success (app.js:171617)
> at fire (vendor.js:1141)
> at Object.fireWith [as resolveWith] (vendor.js:1252)
> at done (vendor.js:8178)
> at XMLHttpRequest.callback (vendor.js:8702)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21891) Fix AmbariServerTest
[
https://issues.apache.org/jira/browse/AMBARI-21891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-21891:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.6
> Fix AmbariServerTest
>
>
> Key: AMBARI-21891
> URL: https://issues.apache.org/jira/browse/AMBARI-21891
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21891.patch
>
>
> AmbariServerTest fails with:
> {code}
> Error occurred in starting fork, check output in log
> Process Exit Code: 1
> Crashed tests:
> org.apache.ambari.server.controller.AmbariServerTest
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:292)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:243)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1077)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:907)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:785)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(Mave
> Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The
> forked VM terminated without properly saying goodbye. VM crash or System.exit
> called?
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21325) Ability to switch Quick Links to use Service URL through Knox or given proxy
[ https://issues.apache.org/jira/browse/AMBARI-21325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-21325: --- Attachment: AMBARI-21325-rebased.patch > Ability to switch Quick Links to use Service URL through Knox or given proxy > > > Key: AMBARI-21325 > URL: https://issues.apache.org/jira/browse/AMBARI-21325 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk, 2.5.2, 2.5.3 >Reporter: Jeffrey E Rodriguez >Assignee: Chandana Mirashi > Attachments: 21325_test_results.zip, AMBARI-21325.patch, > AMBARI-21325-rebased.patch > > Original Estimate: 336h > Remaining Estimate: 336h > > Knox has the ability to proxy Hadoop user interfaces URL. Having the ability > to setup Quicklinks through Knox so instead of for example going to "Hbase > Master UI" directly we can proxy through Knox for example: > http://hdpjeff1.fyre.ibm.com:16010/master-status > can be instead go through: > https://hdpjeff1.fyre.ibm.com:8443/gateway/default/hbase/hbaseui/master-status > Here https://hdpjeff1.fyre.ibm.com:8443/gateway is the Knox gateway URL. > This will bring authentication to the UI access and would secure the UI > access. > Ideally this behavior can be set as secure going through proxy by default or > it can be turn off to go directly by Ambari Admin. > Changes added: > 1. Add new json properties knox_url, knox_path, supports_knox >a. knox_url: template to be used for urls that are proxied through Knox >b. knox_path: Knox gateway path that will be added to the proxy url. >c. supports_knox: whether link will be redirected through Knox > 2. Add above json properties to quicklinks.json > 3. Add HDFSUI & DATANODE,YARNUI & NODEUI, JOBHISTORYUI, HBASEUI, OOZIEUI, > SPARKUI services to Knox topology template. > 4. Automate protocol and port added to Knox topology file. Based on whether > SSL is enabled for the services listed above, the port and protocol in > params_linux.py will be updated. > 5. Update quick_view_link_view.js so that when Knox is installed and > support_knox is true, quicklink url follows knox url template specified in > the quicklinks.json for the service/component. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21892) Unable to proceed to Choose services step
[
https://issues.apache.org/jira/browse/AMBARI-21892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155508#comment-16155508
]
Aleksandr Kovalenko commented on AMBARI-21892:
--
committed to trunk and branch-2.6
> Unable to proceed to Choose services step
> -
>
> Key: AMBARI-21892
> URL: https://issues.apache.org/jira/browse/AMBARI-21892
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21892_branch-2.6.patch, AMBARI-21892.patch
>
>
> JS error happens while transiting from Install Options to Confirm Hosts page.
> {noformat}
> Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.setSelected (app.js:3630)
> at Class.getSupportedOSListSuccessCallback (app.js:4022)
> at Class.opt.success (app.js:171617)
> at fire (vendor.js:1141)
> at Object.fireWith [as resolveWith] (vendor.js:1252)
> at done (vendor.js:8178)
> at XMLHttpRequest.callback (vendor.js:8702)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21892) Unable to proceed to Choose services step
[
https://issues.apache.org/jira/browse/AMBARI-21892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Kovalenko updated AMBARI-21892:
-
Priority: Blocker (was: Critical)
> Unable to proceed to Choose services step
> -
>
> Key: AMBARI-21892
> URL: https://issues.apache.org/jira/browse/AMBARI-21892
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-21892_branch-2.6.patch, AMBARI-21892.patch
>
>
> JS error happens while transiting from Install Options to Confirm Hosts page.
> {noformat}
> Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.setSelected (app.js:3630)
> at Class.getSupportedOSListSuccessCallback (app.js:4022)
> at Class.opt.success (app.js:171617)
> at fire (vendor.js:1141)
> at Object.fireWith [as resolveWith] (vendor.js:1252)
> at done (vendor.js:8178)
> at XMLHttpRequest.callback (vendor.js:8702)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21892) Unable to proceed to Choose services step
[
https://issues.apache.org/jira/browse/AMBARI-21892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Kovalenko updated AMBARI-21892:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Unable to proceed to Choose services step
> -
>
> Key: AMBARI-21892
> URL: https://issues.apache.org/jira/browse/AMBARI-21892
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21892_branch-2.6.patch, AMBARI-21892.patch
>
>
> JS error happens while transiting from Install Options to Confirm Hosts page.
> {noformat}
> Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.setSelected (app.js:3630)
> at Class.getSupportedOSListSuccessCallback (app.js:4022)
> at Class.opt.success (app.js:171617)
> at fire (vendor.js:1141)
> at Object.fireWith [as resolveWith] (vendor.js:1252)
> at done (vendor.js:8178)
> at XMLHttpRequest.callback (vendor.js:8702)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21892) Unable to proceed to Choose services step
[
https://issues.apache.org/jira/browse/AMBARI-21892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155496#comment-16155496
]
Aleksandr Kovalenko commented on AMBARI-21892:
--
no unit tests required to change
> Unable to proceed to Choose services step
> -
>
> Key: AMBARI-21892
> URL: https://issues.apache.org/jira/browse/AMBARI-21892
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21892_branch-2.6.patch, AMBARI-21892.patch
>
>
> JS error happens while transiting from Install Options to Confirm Hosts page.
> {noformat}
> Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.setSelected (app.js:3630)
> at Class.getSupportedOSListSuccessCallback (app.js:4022)
> at Class.opt.success (app.js:171617)
> at fire (vendor.js:1141)
> at Object.fireWith [as resolveWith] (vendor.js:1252)
> at done (vendor.js:8178)
> at XMLHttpRequest.callback (vendor.js:8702)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21892) Unable to proceed to Choose services step
[
https://issues.apache.org/jira/browse/AMBARI-21892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155484#comment-16155484
]
Hadoop QA commented on AMBARI-21892:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12885599/AMBARI-21892.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12150//console
This message is automatically generated.
> Unable to proceed to Choose services step
> -
>
> Key: AMBARI-21892
> URL: https://issues.apache.org/jira/browse/AMBARI-21892
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21892_branch-2.6.patch, AMBARI-21892.patch
>
>
> JS error happens while transiting from Install Options to Confirm Hosts page.
> {noformat}
> Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.setSelected (app.js:3630)
> at Class.getSupportedOSListSuccessCallback (app.js:4022)
> at Class.opt.success (app.js:171617)
> at fire (vendor.js:1141)
> at Object.fireWith [as resolveWith] (vendor.js:1252)
> at done (vendor.js:8178)
> at XMLHttpRequest.callback (vendor.js:8702)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21891) Fix AmbariServerTest
[
https://issues.apache.org/jira/browse/AMBARI-21891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155465#comment-16155465
]
Hudson commented on AMBARI-21891:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #136 (See
[https://builds.apache.org/job/Ambari-branch-2.6/136/])
AMBARI-21891. Fix AmbariServerTest.(vbrodetskyi) (vbrodetskyi:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=345031f526c7bf675866856683863ec368d69d1c])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelper.java
> Fix AmbariServerTest
>
>
> Key: AMBARI-21891
> URL: https://issues.apache.org/jira/browse/AMBARI-21891
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21891.patch
>
>
> AmbariServerTest fails with:
> {code}
> Error occurred in starting fork, check output in log
> Process Exit Code: 1
> Crashed tests:
> org.apache.ambari.server.controller.AmbariServerTest
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:292)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:243)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1077)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:907)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:785)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(Mave
> Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The
> forked VM terminated without properly saying goodbye. VM crash or System.exit
> called?
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21892) Unable to proceed to Choose services step
[
https://issues.apache.org/jira/browse/AMBARI-21892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155444#comment-16155444
]
Andrii Babiichuk commented on AMBARI-21892:
---
+1 for the patch
> Unable to proceed to Choose services step
> -
>
> Key: AMBARI-21892
> URL: https://issues.apache.org/jira/browse/AMBARI-21892
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21892_branch-2.6.patch, AMBARI-21892.patch
>
>
> JS error happens while transiting from Install Options to Confirm Hosts page.
> {noformat}
> Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.setSelected (app.js:3630)
> at Class.getSupportedOSListSuccessCallback (app.js:4022)
> at Class.opt.success (app.js:171617)
> at fire (vendor.js:1141)
> at Object.fireWith [as resolveWith] (vendor.js:1252)
> at done (vendor.js:8178)
> at XMLHttpRequest.callback (vendor.js:8702)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21892) Unable to proceed to Choose services step
[
https://issues.apache.org/jira/browse/AMBARI-21892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Kovalenko updated AMBARI-21892:
-
Attachment: AMBARI-21892_branch-2.6.patch
> Unable to proceed to Choose services step
> -
>
> Key: AMBARI-21892
> URL: https://issues.apache.org/jira/browse/AMBARI-21892
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21892_branch-2.6.patch, AMBARI-21892.patch
>
>
> JS error happens while transiting from Install Options to Confirm Hosts page.
> {noformat}
> Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.setSelected (app.js:3630)
> at Class.getSupportedOSListSuccessCallback (app.js:4022)
> at Class.opt.success (app.js:171617)
> at fire (vendor.js:1141)
> at Object.fireWith [as resolveWith] (vendor.js:1252)
> at done (vendor.js:8178)
> at XMLHttpRequest.callback (vendor.js:8702)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21892) Unable to proceed to Choose services step
[
https://issues.apache.org/jira/browse/AMBARI-21892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Kovalenko updated AMBARI-21892:
-
Attachment: AMBARI-21892.patch
> Unable to proceed to Choose services step
> -
>
> Key: AMBARI-21892
> URL: https://issues.apache.org/jira/browse/AMBARI-21892
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21892_branch-2.6.patch, AMBARI-21892.patch
>
>
> JS error happens while transiting from Install Options to Confirm Hosts page.
> {noformat}
> Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.setSelected (app.js:3630)
> at Class.getSupportedOSListSuccessCallback (app.js:4022)
> at Class.opt.success (app.js:171617)
> at fire (vendor.js:1141)
> at Object.fireWith [as resolveWith] (vendor.js:1252)
> at done (vendor.js:8178)
> at XMLHttpRequest.callback (vendor.js:8702)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21892) Unable to proceed to Choose services step
[
https://issues.apache.org/jira/browse/AMBARI-21892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Kovalenko updated AMBARI-21892:
-
Status: Patch Available (was: Open)
> Unable to proceed to Choose services step
> -
>
> Key: AMBARI-21892
> URL: https://issues.apache.org/jira/browse/AMBARI-21892
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21892_branch-2.6.patch, AMBARI-21892.patch
>
>
> JS error happens while transiting from Install Options to Confirm Hosts page.
> {noformat}
> Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.setSelected (app.js:3630)
> at Class.getSupportedOSListSuccessCallback (app.js:4022)
> at Class.opt.success (app.js:171617)
> at fire (vendor.js:1141)
> at Object.fireWith [as resolveWith] (vendor.js:1252)
> at done (vendor.js:8178)
> at XMLHttpRequest.callback (vendor.js:8702)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21882) Throw an error if unsupported database JDBC driver is configured for HDP services
[
https://issues.apache.org/jira/browse/AMBARI-21882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Toader updated AMBARI-21882:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Throw an error if unsupported database JDBC driver is configured for HDP
> services
> -
>
> Key: AMBARI-21882
> URL: https://issues.apache.org/jira/browse/AMBARI-21882
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
> Fix For: 2.6.0
>
> Attachments: AMBARI-21882.v1.patch
>
>
> Ambari supports a couple of RDBMSes which can be set up via {{ambari-server
> setup}} in order to have JDBC drivers available for agents. Agent will
> download the JDBC driver from the server for HDP services that needs access
> to a RDBMS.
> The start scripts of these HDP service component checks the service
> configuration for the type of JDBC driver and will use the appropriate JDBC
> driver.
> In case the service configuration refers to a JDBC driver type that is not
> supported by Ambari the start script should fail with an error that
> explicitly informs the user that an unsupported JDBC driver type has been
> specified.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21892) Unable to proceed to Choose services step
Aleksandr Kovalenko created AMBARI-21892:
Summary: Unable to proceed to Choose services step
Key: AMBARI-21892
URL: https://issues.apache.org/jira/browse/AMBARI-21892
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.6.0
Reporter: Aleksandr Kovalenko
Assignee: Aleksandr Kovalenko
Priority: Critical
Fix For: 2.6.0
JS error happens while transiting from Install Options to Confirm Hosts page.
{noformat}
Uncaught TypeError: Cannot read property 'get' of undefined
at Class.setSelected (app.js:3630)
at Class.getSupportedOSListSuccessCallback (app.js:4022)
at Class.opt.success (app.js:171617)
at fire (vendor.js:1141)
at Object.fireWith [as resolveWith] (vendor.js:1252)
at done (vendor.js:8178)
at XMLHttpRequest.callback (vendor.js:8702)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21882) Throw an error if unsupported database JDBC driver is configured for HDP services
[
https://issues.apache.org/jira/browse/AMBARI-21882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155412#comment-16155412
]
Hudson commented on AMBARI-21882:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #135 (See
[https://builds.apache.org/job/Ambari-branch-2.6/135/])
AMBARI-21882. Throw an error if unsupported database JDBC driver is (stoader:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a86e16185c012b3929532527aed286c1a5050276])
* (edit)
ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/params.py
* (edit)
ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/package/scripts/params_linux.py
* (add)
ambari-server/src/test/python/common-services/RANGER/test_db_flavor_config.py
* (add)
ambari-server/src/test/python/common-services/configs/ranger_admin_unsupported_db_flavor.json
* (edit)
ambari-common/src/main/python/resource_management/libraries/functions/setup_ranger_plugin_xml.py
* (edit) ambari-server/src/main/resources/custom_actions/scripts/check_host.py
* (edit)
ambari-server/src/main/resources/common-services/RANGER_KMS/0.5.0.2.3/package/scripts/params.py
* (add) ambari-server/src/test/python/common-services/configs/sqoop_default.json
* (add)
ambari-server/src/test/python/common-services/SQOOP/test_jdbc_driver_config.py
* (add)
ambari-server/src/test/python/common-services/HIVE/test_jdbc_driver_config.py
* (add)
ambari-server/src/test/python/common-services/configs/sqoop_unsupported_jdbc_driver.json
* (edit) ambari-server/src/test/python/custom_actions/TestCheckHost.py
* (edit)
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py
* (add)
ambari-server/src/test/python/common-services/configs/ranger_kms_unsupported_db_flavor.json
* (add)
ambari-server/src/test/python/common-services/RANGER_KMS/test_db_flavor_config.py
* (add) ambari-server/src/test/python/common-services/configs/hive_default.json
* (add)
ambari-server/src/test/python/common-services/configs/ranger_kms_default.json
* (add)
ambari-server/src/test/python/common-services/configs/hive_unsupported_jdbc_type.json
* (add)
ambari-server/src/test/python/common-services/configs/ranger_admin_default.json
> Throw an error if unsupported database JDBC driver is configured for HDP
> services
> -
>
> Key: AMBARI-21882
> URL: https://issues.apache.org/jira/browse/AMBARI-21882
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
> Fix For: 2.6.0
>
> Attachments: AMBARI-21882.v1.patch
>
>
> Ambari supports a couple of RDBMSes which can be set up via {{ambari-server
> setup}} in order to have JDBC drivers available for agents. Agent will
> download the JDBC driver from the server for HDP services that needs access
> to a RDBMS.
> The start scripts of these HDP service component checks the service
> configuration for the type of JDBC driver and will use the appropriate JDBC
> driver.
> In case the service configuration refers to a JDBC driver type that is not
> supported by Ambari the start script should fail with an error that
> explicitly informs the user that an unsupported JDBC driver type has been
> specified.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21891) Fix AmbariServerTest
[
https://issues.apache.org/jira/browse/AMBARI-21891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-21891:
---
Description:
AmbariServerTest fails with:
{code}
Error occurred in starting fork, check output in log
Process Exit Code: 1
Crashed tests:
org.apache.ambari.server.controller.AmbariServerTest
at
org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494)
at
org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441)
at
org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:292)
at
org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:243)
at
org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1077)
at
org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:907)
at
org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:785)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
at org.apache.maven.cli.MavenCli.main(Mave
Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The
forked VM terminated without properly saying goodbye. VM crash or System.exit
called?
{code}
> Fix AmbariServerTest
>
>
> Key: AMBARI-21891
> URL: https://issues.apache.org/jira/browse/AMBARI-21891
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21891.patch
>
>
> AmbariServerTest fails with:
> {code}
> Error occurred in starting fork, check output in log
> Process Exit Code: 1
> Crashed tests:
> org.apache.ambari.server.controller.AmbariServerTest
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:292)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:243)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1077)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:907)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:785)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(Mav
[jira] [Commented] (AMBARI-21882) Throw an error if unsupported database JDBC driver is configured for HDP services
[
https://issues.apache.org/jira/browse/AMBARI-21882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155347#comment-16155347
]
Hudson commented on AMBARI-21882:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8002 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8002/])
AMBARI-21882. Throw an error if unsupported database JDBC driver is (stoader:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=680f1148e8e0dac064b7b77f9fba77d7d5a3c448])
* (edit)
ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/package/scripts/params_linux.py
* (edit) ambari-server/src/main/resources/custom_actions/scripts/check_host.py
* (add)
ambari-server/src/test/python/common-services/RANGER_KMS/test_db_flavor_config.py
* (edit)
ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/params.py
* (add)
ambari-server/src/test/python/common-services/configs/ranger_kms_default.json
* (edit)
ambari-server/src/main/resources/common-services/HIVE/2.1.0.3.0/package/scripts/params_linux.py
* (edit)
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py
* (add)
ambari-server/src/test/python/common-services/SQOOP/test_jdbc_driver_config.py
* (add)
ambari-server/src/test/python/common-services/configs/ranger_kms_unsupported_db_flavor.json
* (add)
ambari-server/src/test/python/common-services/RANGER/test_db_flavor_config.py
* (add)
ambari-server/src/test/python/common-services/configs/sqoop_unsupported_jdbc_driver.json
* (edit) ambari-server/src/test/python/custom_actions/TestCheckHost.py
* (edit)
ambari-server/src/main/resources/common-services/RANGER/1.0.0.3.0/package/scripts/params.py
* (add)
ambari-server/src/test/python/common-services/HIVE/test_jdbc_driver_config.py
* (edit)
ambari-common/src/main/python/resource_management/libraries/functions/setup_ranger_plugin_xml.py
* (add) ambari-server/src/test/python/common-services/configs/hive_default.json
* (add)
ambari-server/src/test/python/common-services/configs/hive_unsupported_jdbc_type.json
* (add)
ambari-server/src/test/python/common-services/configs/ranger_admin_default.json
* (edit)
ambari-server/src/main/resources/common-services/RANGER_KMS/0.5.0.2.3/package/scripts/params.py
* (add)
ambari-server/src/test/python/common-services/configs/ranger_admin_unsupported_db_flavor.json
* (edit)
ambari-server/src/main/resources/common-services/SQOOP/1.4.4.3.0/package/scripts/params_linux.py
* (add) ambari-server/src/test/python/common-services/configs/sqoop_default.json
* (edit)
ambari-server/src/main/resources/common-services/RANGER_KMS/1.0.0.3.0/package/scripts/params.py
> Throw an error if unsupported database JDBC driver is configured for HDP
> services
> -
>
> Key: AMBARI-21882
> URL: https://issues.apache.org/jira/browse/AMBARI-21882
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
> Fix For: 2.6.0
>
> Attachments: AMBARI-21882.v1.patch
>
>
> Ambari supports a couple of RDBMSes which can be set up via {{ambari-server
> setup}} in order to have JDBC drivers available for agents. Agent will
> download the JDBC driver from the server for HDP services that needs access
> to a RDBMS.
> The start scripts of these HDP service component checks the service
> configuration for the type of JDBC driver and will use the appropriate JDBC
> driver.
> In case the service configuration refers to a JDBC driver type that is not
> supported by Ambari the start script should fail with an error that
> explicitly informs the user that an unsupported JDBC driver type has been
> specified.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21891) Fix AmbariServerTest
[ https://issues.apache.org/jira/browse/AMBARI-21891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-21891: --- Status: Patch Available (was: Open) > Fix AmbariServerTest > > > Key: AMBARI-21891 > URL: https://issues.apache.org/jira/browse/AMBARI-21891 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21891.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21891) Fix AmbariServerTest
[ https://issues.apache.org/jira/browse/AMBARI-21891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-21891: --- Attachment: AMBARI-21891.patch > Fix AmbariServerTest > > > Key: AMBARI-21891 > URL: https://issues.apache.org/jira/browse/AMBARI-21891 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21891.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21891) Fix AmbariServerTest
Vitaly Brodetskyi created AMBARI-21891: -- Summary: Fix AmbariServerTest Key: AMBARI-21891 URL: https://issues.apache.org/jira/browse/AMBARI-21891 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.6.0 Reporter: Vitaly Brodetskyi Priority: Critical Fix For: 2.6.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-21891) Fix AmbariServerTest
[ https://issues.apache.org/jira/browse/AMBARI-21891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi reassigned AMBARI-21891: -- Assignee: Vitaly Brodetskyi > Fix AmbariServerTest > > > Key: AMBARI-21891 > URL: https://issues.apache.org/jira/browse/AMBARI-21891 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.6.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21890) Ambari Files View - browser going to hung state while opening a HDFS folder which has huge number of files(>10000)
[ https://issues.apache.org/jira/browse/AMBARI-21890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21890: Attachment: AMBARI-21890-trunk.patch > Ambari Files View - browser going to hung state while opening a HDFS folder > which has huge number of files(>1) > -- > > Key: AMBARI-21890 > URL: https://issues.apache.org/jira/browse/AMBARI-21890 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.0 >Reporter: venkat >Assignee: venkat >Priority: Blocker > Fix For: 2.6.0 > > Attachments: AMBARI-21890-trunk.patch > > > A configurable limit have been imposed on the no of files being retrieved > from the server and the limit by default is set to 5000. > Search has been provided to find the file faster. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21890) Ambari Files View - browser going to hung state while opening a HDFS folder which has huge number of files(>10000)
venkat created AMBARI-21890: --- Summary: Ambari Files View - browser going to hung state while opening a HDFS folder which has huge number of files(>1) Key: AMBARI-21890 URL: https://issues.apache.org/jira/browse/AMBARI-21890 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.6.0 Reporter: venkat Assignee: venkat Priority: Blocker Fix For: 2.6.0 A configurable limit have been imposed on the no of files being retrieved from the server and the limit by default is set to 5000. Search has been provided to find the file faster. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21889) MaxBackupIndex does not work with DailyRollingFileAppender in Ranger
[ https://issues.apache.org/jira/browse/AMBARI-21889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-21889: - Status: Patch Available (was: In Progress) > MaxBackupIndex does not work with DailyRollingFileAppender in Ranger > > > Key: AMBARI-21889 > URL: https://issues.apache.org/jira/browse/AMBARI-21889 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar > Fix For: 2.6.0 > > Attachments: AMBARI-21889.patch > > > Ranger uses DailyRollingFileAppender and "maxbackupindex" is not in that > class so need to remove the same from admin-log4j config. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21889) MaxBackupIndex does not work with DailyRollingFileAppender in Ranger
[ https://issues.apache.org/jira/browse/AMBARI-21889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-21889: - Fix Version/s: 2.6.0 > MaxBackupIndex does not work with DailyRollingFileAppender in Ranger > > > Key: AMBARI-21889 > URL: https://issues.apache.org/jira/browse/AMBARI-21889 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar > Fix For: 2.6.0 > > Attachments: AMBARI-21889.patch > > > Ranger uses DailyRollingFileAppender and "maxbackupindex" is not in that > class so need to remove the same from admin-log4j config. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21889) MaxBackupIndex does not work with DailyRollingFileAppender in Ranger
[ https://issues.apache.org/jira/browse/AMBARI-21889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-21889: - Affects Version/s: 2.5.2 > MaxBackupIndex does not work with DailyRollingFileAppender in Ranger > > > Key: AMBARI-21889 > URL: https://issues.apache.org/jira/browse/AMBARI-21889 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar > Fix For: 2.6.0 > > Attachments: AMBARI-21889.patch > > > Ranger uses DailyRollingFileAppender and "maxbackupindex" is not in that > class so need to remove the same from admin-log4j config. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21876) Remove hive.custom-extensions.root from Hive Properties.
[ https://issues.apache.org/jira/browse/AMBARI-21876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155241#comment-16155241 ] Hudson commented on AMBARI-21876: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #132 (See [https://builds.apache.org/job/Ambari-branch-2.6/132/]) AMBARI-21876. Remove hive.custom-extensions.root from Hive (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=48ad866e37016b60001226a4712b4b3b7fa5ca18]) * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2.5/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/hive-site.xml * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2.5/upgrades/nonrolling-upgrade-to-hdp-2.6.xml * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2/upgrades/nonrolling-upgrade-to-hdp-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/scripts/custom_extensions.py > Remove hive.custom-extensions.root from Hive Properties. > > > Key: AMBARI-21876 > URL: https://issues.apache.org/jira/browse/AMBARI-21876 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Blocker > Fix For: 2.6.0 > > Attachments: AMBARI-21876.patch > > > Remove hive.custom-extensions.root from hive properties. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21876) Remove hive.custom-extensions.root from Hive Properties.
[ https://issues.apache.org/jira/browse/AMBARI-21876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155236#comment-16155236 ] Hudson commented on AMBARI-21876: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8001 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8001/]) AMBARI-21876. Remove hive.custom-extensions.root from Hive (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=202eaed6fb98da59d17d4f41d35ce8c576baf48a]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/hive-site.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/scripts/custom_extensions.py > Remove hive.custom-extensions.root from Hive Properties. > > > Key: AMBARI-21876 > URL: https://issues.apache.org/jira/browse/AMBARI-21876 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Blocker > Fix For: 2.6.0 > > Attachments: AMBARI-21876.patch > > > Remove hive.custom-extensions.root from hive properties. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21889) MaxBackupIndex does not work with DailyRollingFileAppender in Ranger
[ https://issues.apache.org/jira/browse/AMBARI-21889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-21889: - Attachment: AMBARI-21889.patch > MaxBackupIndex does not work with DailyRollingFileAppender in Ranger > > > Key: AMBARI-21889 > URL: https://issues.apache.org/jira/browse/AMBARI-21889 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar > Attachments: AMBARI-21889.patch > > > Ranger uses DailyRollingFileAppender and "maxbackupindex" is not in that > class so need to remove the same from admin-log4j config. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21889) MaxBackupIndex does not work with DailyRollingFileAppender in Ranger
Mugdha Varadkar created AMBARI-21889: Summary: MaxBackupIndex does not work with DailyRollingFileAppender in Ranger Key: AMBARI-21889 URL: https://issues.apache.org/jira/browse/AMBARI-21889 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Mugdha Varadkar Assignee: Mugdha Varadkar Ranger uses DailyRollingFileAppender and "maxbackupindex" is not in that class so need to remove the same from admin-log4j config. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21888) Upgrade History Should Show Advertised Versions
[ https://issues.apache.org/jira/browse/AMBARI-21888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155196#comment-16155196 ] Hudson commented on AMBARI-21888: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #131 (See [https://builds.apache.org/job/Ambari-branch-2.6/131/]) AMBARI-21888. Upgrade History Should Show Advertised Versions (aantonenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4a8b85df38b023ab605e24f479ea2ce442aa9435]) * (edit) ambari-web/test/views/main/admin/stack_upgrade/upgrade_history_view_test.js * (edit) ambari-web/app/views/main/admin/stack_upgrade/upgrade_history_view.js > Upgrade History Should Show Advertised Versions > --- > > Key: AMBARI-21888 > URL: https://issues.apache.org/jira/browse/AMBARI-21888 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21888_branch26.patch, AMBARI-21888_trunk.patch > > > The upgrade history section seems to show the hadoop versions of each service > instead of the advertised version. This doesn't seem very useful, especially > when patches and maintenance releases may not change the hadoop version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21876) Remove hive.custom-extensions.root from Hive Properties.
[ https://issues.apache.org/jira/browse/AMBARI-21876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-21876: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.6 > Remove hive.custom-extensions.root from Hive Properties. > > > Key: AMBARI-21876 > URL: https://issues.apache.org/jira/browse/AMBARI-21876 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Blocker > Fix For: 2.6.0 > > Attachments: AMBARI-21876.patch > > > Remove hive.custom-extensions.root from hive properties. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21888) Upgrade History Should Show Advertised Versions
[ https://issues.apache.org/jira/browse/AMBARI-21888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155187#comment-16155187 ] Hudson commented on AMBARI-21888: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8000 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8000/]) AMBARI-21888. Upgrade History Should Show Advertised Versions (aantonenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e1f4d2e658d64dbdfc185dc8bdf33675289e2c1b]) * (edit) ambari-web/app/templates/main/admin/stack_upgrade/upgrade_history.hbs * (edit) ambari-web/app/views/main/admin/stack_upgrade/upgrade_history_view.js * (edit) ambari-web/app/styles/stack_versions.less * (edit) ambari-web/test/views/main/admin/stack_upgrade/upgrade_history_view_test.js > Upgrade History Should Show Advertised Versions > --- > > Key: AMBARI-21888 > URL: https://issues.apache.org/jira/browse/AMBARI-21888 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21888_branch26.patch, AMBARI-21888_trunk.patch > > > The upgrade history section seems to show the hadoop versions of each service > instead of the advertised version. This doesn't seem very useful, especially > when patches and maintenance releases may not change the hadoop version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21863) Ranger should handle external Zookeeper properly
[ https://issues.apache.org/jira/browse/AMBARI-21863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155167#comment-16155167 ] Hudson commented on AMBARI-21863: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #130 (See [https://builds.apache.org/job/Ambari-branch-2.6/130/]) AMBARI-21863. Ranger should handle external Zookeeper properly (mgergely: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=47f97bbfaee5795b5b7e0c3695cab4f3966c7ff8]) * (edit) ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/params.py > Ranger should handle external Zookeeper properly > > > Key: AMBARI-21863 > URL: https://issues.apache.org/jira/browse/AMBARI-21863 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.6.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.6.0 > > Attachments: AMBARI-21863.patch > > > Ranger tries to create it's configurations using the local ambari-infra Solr > even if it is specified to use an external one. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21881) Fix Log Search upgrade to 3.0.0
[ https://issues.apache.org/jira/browse/AMBARI-21881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155143#comment-16155143 ] Hudson commented on AMBARI-21881: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7999 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7999/]) AMBARI-21881. Fix Log Search upgrade to 3.0.0 (mgergely) (mgergely: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0034da609c3587df662278d2bf613b3ca92c276e]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog300Test.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog300.java > Fix Log Search upgrade to 3.0.0 > --- > > Key: AMBARI-21881 > URL: https://issues.apache.org/jira/browse/AMBARI-21881 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 3.0.0 > > Attachments: AMBARI-21881.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21888) Upgrade History Should Show Advertised Versions
[ https://issues.apache.org/jira/browse/AMBARI-21888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21888: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.6 > Upgrade History Should Show Advertised Versions > --- > > Key: AMBARI-21888 > URL: https://issues.apache.org/jira/browse/AMBARI-21888 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21888_branch26.patch, AMBARI-21888_trunk.patch > > > The upgrade history section seems to show the hadoop versions of each service > instead of the advertised version. This doesn't seem very useful, especially > when patches and maintenance releases may not change the hadoop version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21888) Upgrade History Should Show Advertised Versions
[ https://issues.apache.org/jira/browse/AMBARI-21888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155132#comment-16155132 ] Andrii Babiichuk commented on AMBARI-21888: --- +1 for the patch > Upgrade History Should Show Advertised Versions > --- > > Key: AMBARI-21888 > URL: https://issues.apache.org/jira/browse/AMBARI-21888 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21888_branch26.patch, AMBARI-21888_trunk.patch > > > The upgrade history section seems to show the hadoop versions of each service > instead of the advertised version. This doesn't seem very useful, especially > when patches and maintenance releases may not change the hadoop version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21888) Upgrade History Should Show Advertised Versions
[
https://issues.apache.org/jira/browse/AMBARI-21888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155118#comment-16155118
]
Hadoop QA commented on AMBARI-21888:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12885561/AMBARI-21888_trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12149//console
This message is automatically generated.
> Upgrade History Should Show Advertised Versions
> ---
>
> Key: AMBARI-21888
> URL: https://issues.apache.org/jira/browse/AMBARI-21888
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21888_branch26.patch, AMBARI-21888_trunk.patch
>
>
> The upgrade history section seems to show the hadoop versions of each service
> instead of the advertised version. This doesn't seem very useful, especially
> when patches and maintenance releases may not change the hadoop version.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21863) Ranger should handle external Zookeeper properly
[ https://issues.apache.org/jira/browse/AMBARI-21863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155082#comment-16155082 ] Hudson commented on AMBARI-21863: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7998 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7998/]) AMBARI-21863. Ranger should handle external Zookeeper properly (mgergely: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6e69f214c8e45926cdf6757848f0bc42dc9b4917]) * (edit) ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/params.py > Ranger should handle external Zookeeper properly > > > Key: AMBARI-21863 > URL: https://issues.apache.org/jira/browse/AMBARI-21863 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.6.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.6.0 > > Attachments: AMBARI-21863.patch > > > Ranger tries to create it's configurations using the local ambari-infra Solr > even if it is specified to use an external one. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21888) Upgrade History Should Show Advertised Versions
[ https://issues.apache.org/jira/browse/AMBARI-21888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21888: - Status: Patch Available (was: In Progress) > Upgrade History Should Show Advertised Versions > --- > > Key: AMBARI-21888 > URL: https://issues.apache.org/jira/browse/AMBARI-21888 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21888_branch26.patch, AMBARI-21888_trunk.patch > > > The upgrade history section seems to show the hadoop versions of each service > instead of the advertised version. This doesn't seem very useful, especially > when patches and maintenance releases may not change the hadoop version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21888) Upgrade History Should Show Advertised Versions
[ https://issues.apache.org/jira/browse/AMBARI-21888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21888: - Attachment: AMBARI-21888_trunk.patch > Upgrade History Should Show Advertised Versions > --- > > Key: AMBARI-21888 > URL: https://issues.apache.org/jira/browse/AMBARI-21888 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21888_branch26.patch, AMBARI-21888_trunk.patch > > > The upgrade history section seems to show the hadoop versions of each service > instead of the advertised version. This doesn't seem very useful, especially > when patches and maintenance releases may not change the hadoop version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21888) Upgrade History Should Show Advertised Versions
[ https://issues.apache.org/jira/browse/AMBARI-21888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21888: - Attachment: AMBARI-21888_branch26.patch > Upgrade History Should Show Advertised Versions > --- > > Key: AMBARI-21888 > URL: https://issues.apache.org/jira/browse/AMBARI-21888 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21888_branch26.patch, AMBARI-21888_trunk.patch > > > The upgrade history section seems to show the hadoop versions of each service > instead of the advertised version. This doesn't seem very useful, especially > when patches and maintenance releases may not change the hadoop version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-21888) Upgrade History Should Show Advertised Versions
[ https://issues.apache.org/jira/browse/AMBARI-21888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-21888: Assignee: Antonenko Alexander > Upgrade History Should Show Advertised Versions > --- > > Key: AMBARI-21888 > URL: https://issues.apache.org/jira/browse/AMBARI-21888 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > > The upgrade history section seems to show the hadoop versions of each service > instead of the advertised version. This doesn't seem very useful, especially > when patches and maintenance releases may not change the hadoop version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21888) Upgrade History Should Show Advertised Versions
Antonenko Alexander created AMBARI-21888: Summary: Upgrade History Should Show Advertised Versions Key: AMBARI-21888 URL: https://issues.apache.org/jira/browse/AMBARI-21888 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.6.0 Reporter: Antonenko Alexander Priority: Critical Fix For: 2.6.0 The upgrade history section seems to show the hadoop versions of each service instead of the advertised version. This doesn't seem very useful, especially when patches and maintenance releases may not change the hadoop version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21887) Unable to compile amabari-admin and ambari-web
ketan kunde created AMBARI-21887:
Summary: Unable to compile amabari-admin and ambari-web
Key: AMBARI-21887
URL: https://issues.apache.org/jira/browse/AMBARI-21887
Project: Ambari
Issue Type: Bug
Components: ambari-admin, ambari-web
Affects Versions: 2.5.1
Environment: arch : s390x
OS : ub 16.04
maven : 3.3.9
JDK : openjdk8
Reporter: ketan kunde
Priority: Blocker
while building ambari-web i get the below logs on doing a mvn clean install -fn
[INFO] Running 'yarn install ignore-engines pure-lockfile' in
/home/apache-ambari-2.5.1-src/ambari-web
[ERROR] /home/apache-ambari-2.5.1-src/ambari-web/node/node: 1:
/home/apache-ambari-2.5.1-src/ambari-web/node/node: Syntax error: "(" unexpected
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 03:17 min
[INFO] Finished at: 2017-09-06T09:15:56+00:00
[INFO] Final Memory: 11M/27M
**
The below logs are while executing ambari-admin
Installed node locally.
[INFO] NPM 2.15.0 is already installed.
[INFO]
[INFO] --- frontend-maven-plugin:1.3:npm (npm install) @ ambari-admin ---
[INFO] Running 'npm install' in
/home/apache-ambari-2.5.1-src/ambari-admin/src/main/resources/ui/admin-web
[ERROR]
/home/apache-ambari-2.5.1-src/ambari-admin/src/main/resources/ui/admin-web/node/node:
1:
/home/apache-ambari-2.5.1-src/ambari-admin/src/main/resources/ui/admin-web/node/node:
Syntax error: "(" unexpected
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 01:55 min
[INFO] Finished at: 2017-09-06T09:21:12+00:00
[INFO] Final Memory: 12M/30M
Ned help to this fixed
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21881) Fix Log Search upgrade to 3.0.0
[ https://issues.apache.org/jira/browse/AMBARI-21881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-21881: Resolution: Fixed Status: Resolved (was: Patch Available) > Fix Log Search upgrade to 3.0.0 > --- > > Key: AMBARI-21881 > URL: https://issues.apache.org/jira/browse/AMBARI-21881 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 3.0.0 > > Attachments: AMBARI-21881.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21881) Fix Log Search upgrade to 3.0.0
[
https://issues.apache.org/jira/browse/AMBARI-21881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155025#comment-16155025
]
Miklos Gergely commented on AMBARI-21881:
-
committed to trunk:
{code:java}
commit 0034da609c3587df662278d2bf613b3ca92c276e
Author: Miklos Gergely
Date: Wed Sep 6 10:52:41 2017 +0200
AMBARI-21881. Fix Log Search upgrade to 3.0.0 (mgergely)
Change-Id: I5557892cfd528616697a6c8ffa4b5b2b6f4fc80a
{code}
> Fix Log Search upgrade to 3.0.0
> ---
>
> Key: AMBARI-21881
> URL: https://issues.apache.org/jira/browse/AMBARI-21881
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 3.0.0
>
> Attachments: AMBARI-21881.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21863) Ranger should handle external Zookeeper properly
[ https://issues.apache.org/jira/browse/AMBARI-21863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-21863: Resolution: Fixed Status: Resolved (was: Patch Available) > Ranger should handle external Zookeeper properly > > > Key: AMBARI-21863 > URL: https://issues.apache.org/jira/browse/AMBARI-21863 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.6.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.6.0 > > Attachments: AMBARI-21863.patch > > > Ranger tries to create it's configurations using the local ambari-infra Solr > even if it is specified to use an external one. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21863) Ranger should handle external Zookeeper properly
[
https://issues.apache.org/jira/browse/AMBARI-21863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155021#comment-16155021
]
Miklos Gergely commented on AMBARI-21863:
-
committed to trunk:
{code:java}
commit 6e69f214c8e45926cdf6757848f0bc42dc9b4917
Author: Miklos Gergely
Date: Wed Sep 6 10:46:26 2017 +0200
AMBARI-21863. Ranger should handle external Zookeeper properly (mgergely)
Change-Id: I751eb3f014b2b5151537456a1b2ee2e9c96578e3
{code}
committed to branch-2.6:
{code:java}
commit 47f97bbfaee5795b5b7e0c3695cab4f3966c7ff8
Author: Miklos Gergely
Date: Wed Sep 6 10:48:15 2017 +0200
AMBARI-21863. Ranger should handle external Zookeeper properly (mgergely)
Change-Id: I8b58e719699b176516d0a012ece19f594cf6adef
{code}
> Ranger should handle external Zookeeper properly
>
>
> Key: AMBARI-21863
> URL: https://issues.apache.org/jira/browse/AMBARI-21863
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: 2.6.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.6.0
>
> Attachments: AMBARI-21863.patch
>
>
> Ranger tries to create it's configurations using the local ambari-infra Solr
> even if it is specified to use an external one.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
