[jira] [Commented] (AMBARI-21430) Allow Multiple Versions of Stack Tools to Co-Exist
[
https://issues.apache.org/jira/browse/AMBARI-21430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078955#comment-16078955
]
Hudson commented on AMBARI-21430:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7741 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7741/])
AMBARI-21430 - Allow Multiple Versions of Stack Tools to Co-Exist (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f33a250c0e7624b6cbc0a11ffce12506eaa95d9a])
* (edit)
ambari-server/src/test/python/stacks/2.6/configs/ranger-admin-default.json
* (edit) ambari-server/src/test/python/common-services/configs/hawq_default.json
* (edit)
ambari-server/src/test/python/stacks/2.5/configs/ranger-kms-default.json
* (edit)
ambari-server/src/main/resources/stacks/PERF/1.0/properties/stack_features.json
* (edit)
ambari-server/src/test/python/stacks/2.5/configs/ranger-admin-default.json
* (edit)
ambari-common/src/main/python/resource_management/libraries/script/script.py
* (edit) ambari-server/src/test/python/stacks/utils/RMFTestCase.py
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariActionExecutionHelper.java
* (edit) ambari-server/src/main/resources/host_scripts/alert_version_select.py
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/topology/AmbariContext.java
* (edit) ambari-server/src/main/resources/host_scripts/alert_disk_space.py
* (edit)
ambari-server/src/main/resources/stacks/PERF/1.0/configuration/cluster-env.xml
* (edit) ambari-server/src/test/python/host_scripts/TestAlertDiskSpace.py
* (edit)
ambari-common/src/main/python/resource_management/libraries/functions/stack_features.py
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.0.6/configuration/cluster-env.xml
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java
* (edit)
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/alerts/alert_hive_metastore.py
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java
* (edit)
ambari-server/src/test/python/stacks/2.5/configs/ranger-kms-secured.json
* (edit)
ambari-common/src/main/python/resource_management/libraries/functions/stack_tools.py
* (edit)
ambari-server/src/main/resources/stacks/PERF/1.0/properties/stack_tools.json
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/topology/ClusterConfigurationRequestTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog252.java
* (edit)
ambari-server/src/test/python/stacks/2.5/configs/ranger-admin-secured.json
* (edit)
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/alerts/alert_check_oozie_server.py
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.0.6/properties/stack_features.json
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProviderTest.java
* (edit)
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/alerts/alert_llap_app_status.py
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.0.6/properties/stack_tools.json
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProvider.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/api/query/JpaPredicateVisitor.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/ActionExecutionContext.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/ConfigHelper.java
* (edit)
ambari-server/src/test/python/stacks/2.6/configs/ranger-admin-secured.json
> Allow Multiple Versions of Stack Tools to Co-Exist
> --
>
> Key: AMBARI-21430
> URL: https://issues.apache.org/jira/browse/AMBARI-21430
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21430.patch
>
>
> Currently, the stack tools:
> - {{cluster-env/stack_features}}
> - {{cluster-env/stack_tools}}
> - {{cluster-env/stack_root}}
> Are bound to the {{cluster-env}} without any sort of scoping. This prevents 2
> sets of stack tools from co-existing. Although Ambari doesn't support more
> than a single stack in 2.x, we do support upgrades from one stack vendor to
> another. Therefore, we need this support to send the right tools on the
> commands.
> This will involve the following work:
> - Changing the existing stack tools/features/root to have a stack name as the
> key in the JSON
> - Altering the existing {{cluster-env}} tools on upgrade
> - Ensuring that the stack tools
[jira] [Commented] (AMBARI-20861) BE: Extend Ambari REST API to Support User Account Management Improvements
[
https://issues.apache.org/jira/browse/AMBARI-20861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078941#comment-16078941
]
Hadoop QA commented on AMBARI-20861:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12876086/AMBARI-20861_branch-feature-AMBARI-20859_02.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11759//console
This message is automatically generated.
> BE: Extend Ambari REST API to Support User Account Management Improvements
> --
>
> Key: AMBARI-20861
> URL: https://issues.apache.org/jira/browse/AMBARI-20861
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: rest_api, security
> Fix For: 3.0.0
>
> Attachments: AMBARI-20861_branch-feature-AMBARI-20859_01.patch,
> AMBARI-20861_branch-feature-AMBARI-20859_02.patch
>
>
> Update the Ambari REST API to allow for GET, POST, PUT, and DELETE operations
> on the authentication sources related to an Ambari user account.
> Add the following entry points:
> * {{/api/v1/users/:USER_ID}}
> ** Get a user
> ** Modify a user
> * * {{/api/v1/users/:USERNAME/sources}}
> ** List a user’s authentication sources
> ** Add a new authentication source for a user
> * {{/api/v1/users/:USERNAME/sources/:SOURCE_ID}}
> ** Get details on a specific authentication source for a user
> ** Modify details for a specific authentication source for a user
> * {{/api/v1/users/:USER_ID/sources}}
> ** List a user’s authentication sources
> ** Add a new authentication source for a user
> * {{/api/v1/users/:USER_ID/sources/:SOURCE_ID}}
> ** Get details on a specific authentication source for a user
> ** Modify details for a specific authentication source for a user
> Update the following entry points, ensuring backwards compatibility where
> possible:
> * {{/api/v1/users}}
> ** List all users
> ** Add a new user
> ** Backward compatibility: Set password should create or update the
> appropriate user_authentication record.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21427) Assigning hosts concurrently to same config group may fail with "org.apache.ambari.server.controller.spi.ResourceAlreadyExistsException: Config group already exist'
[
https://issues.apache.org/jira/browse/AMBARI-21427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078940#comment-16078940
]
Hadoop QA commented on AMBARI-21427:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12876106/AMBARI-21427.v1.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11758//console
This message is automatically generated.
> Assigning hosts concurrently to same config group may fail with
> "org.apache.ambari.server.controller.spi.ResourceAlreadyExistsException:
> Config group already exist'
> -
>
> Key: AMBARI-21427
> URL: https://issues.apache.org/jira/browse/AMBARI-21427
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
> Fix For: 2.5.2
>
> Attachments: AMBARI-21427.v1.patch
>
>
> Assigning hosts concurrently to the same config group may fail due to a race
> condition causing the config group to be created twice:
> {noformat}
> 05 Jul 2017 18:50:44,742 INFO [pool-5-thread-2]
> RegisterWithConfigGroupTask:45 - HostRequest: Executing CONFIGURE task for
> host: w1.internal
> 05 Jul 2017 18:50:44,884 ERROR [pool-5-thread-2] AmbariContext:655 - Failed
> to create new configuration group:
> org.apache.ambari.server.controller.spi.ResourceAlreadyExistsException:
> Config group already exists with the same name and tag, clusterName =
> mycluster, groupName = myblueprint:group1, tag = HDFS
> 05 Jul 2017 18:50:44,885 ERROR [pool-5-thread-2] AmbariContext:342 - Unable
> to register config group for host:
> java.lang.RuntimeException: Failed to create new configuration group:
> org.apache.ambari.server.controller.spi.ResourceAlreadyExistsException:
> Config group already exists with the same name and tag, clusterName =
> mycluster, groupName = myblueprint:group1, tag = HDFS
> at
> org.apache.ambari.server.topology.AmbariContext.createConfigGroupsAndRegisterHost(AmbariContext.java:656)
> at
> org.apache.ambari.server.topology.AmbariContext.registerHostWithConfigGroup(AmbariContext.java:339)
> at
> org.apache.ambari.server.topology.tasks.RegisterWithConfigGroupTask.runTask(RegisterWithConfigGroupTask.java:46)
> 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:748)
> Caused by:
> org.apache.ambari.server.controller.spi.ResourceAlreadyExistsException:
> Config group already exists with the same name and tag, clusterName =
> mycluster, groupName = myblueprint:group1, tag = HDFS
> at
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.createResources(AbstractResourceProvider.java:282)
> at
> org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider.createResources(ConfigGroupResourceProvider.java:276)
> at
> org.apache.ambari.server.topology.AmbariContext.createConfigGroupsAndRegisterHost(AmbariContext.java:653)
> ... 7 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21430) Allow Multiple Versions of Stack Tools to Co-Exist
[
https://issues.apache.org/jira/browse/AMBARI-21430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-21430:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Allow Multiple Versions of Stack Tools to Co-Exist
> --
>
> Key: AMBARI-21430
> URL: https://issues.apache.org/jira/browse/AMBARI-21430
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21430.patch
>
>
> Currently, the stack tools:
> - {{cluster-env/stack_features}}
> - {{cluster-env/stack_tools}}
> - {{cluster-env/stack_root}}
> Are bound to the {{cluster-env}} without any sort of scoping. This prevents 2
> sets of stack tools from co-existing. Although Ambari doesn't support more
> than a single stack in 2.x, we do support upgrades from one stack vendor to
> another. Therefore, we need this support to send the right tools on the
> commands.
> This will involve the following work:
> - Changing the existing stack tools/features/root to have a stack name as the
> key in the JSON
> - Altering the existing {{cluster-env}} tools on upgrade
> - Ensuring that the stack tools/features for a repository's stack exist when
> distributing that stack
> - Changing any Python code which references the stack tools (stack_tools.py,
> alerts, etc)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21430) Allow Multiple Versions of Stack Tools to Co-Exist
[
https://issues.apache.org/jira/browse/AMBARI-21430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-21430:
-
Status: Patch Available (was: In Progress)
> Allow Multiple Versions of Stack Tools to Co-Exist
> --
>
> Key: AMBARI-21430
> URL: https://issues.apache.org/jira/browse/AMBARI-21430
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21430.patch
>
>
> Currently, the stack tools:
> - {{cluster-env/stack_features}}
> - {{cluster-env/stack_tools}}
> - {{cluster-env/stack_root}}
> Are bound to the {{cluster-env}} without any sort of scoping. This prevents 2
> sets of stack tools from co-existing. Although Ambari doesn't support more
> than a single stack in 2.x, we do support upgrades from one stack vendor to
> another. Therefore, we need this support to send the right tools on the
> commands.
> This will involve the following work:
> - Changing the existing stack tools/features/root to have a stack name as the
> key in the JSON
> - Altering the existing {{cluster-env}} tools on upgrade
> - Ensuring that the stack tools/features for a repository's stack exist when
> distributing that stack
> - Changing any Python code which references the stack tools (stack_tools.py,
> alerts, etc)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21430) Allow Multiple Versions of Stack Tools to Co-Exist
[
https://issues.apache.org/jira/browse/AMBARI-21430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-21430:
-
Attachment: AMBARI-21430.patch
> Allow Multiple Versions of Stack Tools to Co-Exist
> --
>
> Key: AMBARI-21430
> URL: https://issues.apache.org/jira/browse/AMBARI-21430
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21430.patch
>
>
> Currently, the stack tools:
> - {{cluster-env/stack_features}}
> - {{cluster-env/stack_tools}}
> - {{cluster-env/stack_root}}
> Are bound to the {{cluster-env}} without any sort of scoping. This prevents 2
> sets of stack tools from co-existing. Although Ambari doesn't support more
> than a single stack in 2.x, we do support upgrades from one stack vendor to
> another. Therefore, we need this support to send the right tools on the
> commands.
> This will involve the following work:
> - Changing the existing stack tools/features/root to have a stack name as the
> key in the JSON
> - Altering the existing {{cluster-env}} tools on upgrade
> - Ensuring that the stack tools/features for a repository's stack exist when
> distributing that stack
> - Changing any Python code which references the stack tools (stack_tools.py,
> alerts, etc)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21405) Create custom action to force-remove packages
[ https://issues.apache.org/jira/browse/AMBARI-21405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-21405: --- Resolution: Done Status: Resolved (was: Patch Available) Committed to [branch-feature-AMBARI-21348|http://git-wip-us.apache.org/repos/asf/ambari/commit/b6c5d78ac6]. > Create custom action to force-remove packages > - > > Key: AMBARI-21405 > URL: https://issues.apache.org/jira/browse/AMBARI-21405 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila >Priority: Blocker > Fix For: 2.5.2 > > Attachments: AMBARI-21405.patch > > > Create a custom action which forcefully removes some packages from all hosts, > possibly leaving broken dependencies. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21424) BigInsight stack upgrade XML files should prevent downgrade
[
https://issues.apache.org/jira/browse/AMBARI-21424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-21424:
---
Resolution: Done
Status: Resolved (was: Patch Available)
Committed to
[branch-feature-AMBARI-21348|http://git-wip-us.apache.org/repos/asf/ambari/commit/85d7c196fa].
> BigInsight stack upgrade XML files should prevent downgrade
> ---
>
> Key: AMBARI-21424
> URL: https://issues.apache.org/jira/browse/AMBARI-21424
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 2.5.2
>
> Attachments: AMBARI-21424.patch
>
>
> The BI upgrade XML files need to prevent downgrades. This can be done by
> adding the {{downgrade-allowed}} element.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21150) Mpack API and DB Schema changes
[ https://issues.apache.org/jira/browse/AMBARI-21150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-21150: --- Component/s: ambari-server > Mpack API and DB Schema changes > --- > > Key: AMBARI-21150 > URL: https://issues.apache.org/jira/browse/AMBARI-21150 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Attachments: AMBARI-21150_v1.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21425) Software Registry REST API
[ https://issues.apache.org/jira/browse/AMBARI-21425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-21425: --- Component/s: (was: ambari-admin) ambari-server > Software Registry REST API > -- > > Key: AMBARI-21425 > URL: https://issues.apache.org/jira/browse/AMBARI-21425 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21427) Assigning hosts concurrently to same config group may fail with "org.apache.ambari.server.controller.spi.ResourceAlreadyExistsException: Config group already exist'
[
https://issues.apache.org/jira/browse/AMBARI-21427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Toader updated AMBARI-21427:
--
Attachment: AMBARI-21427.v1.patch
> Assigning hosts concurrently to same config group may fail with
> "org.apache.ambari.server.controller.spi.ResourceAlreadyExistsException:
> Config group already exist'
> -
>
> Key: AMBARI-21427
> URL: https://issues.apache.org/jira/browse/AMBARI-21427
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
> Fix For: 2.5.2
>
> Attachments: AMBARI-21427.v1.patch
>
>
> Assigning hosts concurrently to the same config group may fail due to a race
> condition causing the config group to be created twice:
> {noformat}
> 05 Jul 2017 18:50:44,742 INFO [pool-5-thread-2]
> RegisterWithConfigGroupTask:45 - HostRequest: Executing CONFIGURE task for
> host: w1.internal
> 05 Jul 2017 18:50:44,884 ERROR [pool-5-thread-2] AmbariContext:655 - Failed
> to create new configuration group:
> org.apache.ambari.server.controller.spi.ResourceAlreadyExistsException:
> Config group already exists with the same name and tag, clusterName =
> mycluster, groupName = myblueprint:group1, tag = HDFS
> 05 Jul 2017 18:50:44,885 ERROR [pool-5-thread-2] AmbariContext:342 - Unable
> to register config group for host:
> java.lang.RuntimeException: Failed to create new configuration group:
> org.apache.ambari.server.controller.spi.ResourceAlreadyExistsException:
> Config group already exists with the same name and tag, clusterName =
> mycluster, groupName = myblueprint:group1, tag = HDFS
> at
> org.apache.ambari.server.topology.AmbariContext.createConfigGroupsAndRegisterHost(AmbariContext.java:656)
> at
> org.apache.ambari.server.topology.AmbariContext.registerHostWithConfigGroup(AmbariContext.java:339)
> at
> org.apache.ambari.server.topology.tasks.RegisterWithConfigGroupTask.runTask(RegisterWithConfigGroupTask.java:46)
> 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:748)
> Caused by:
> org.apache.ambari.server.controller.spi.ResourceAlreadyExistsException:
> Config group already exists with the same name and tag, clusterName =
> mycluster, groupName = myblueprint:group1, tag = HDFS
> at
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.createResources(AbstractResourceProvider.java:282)
> at
> org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider.createResources(ConfigGroupResourceProvider.java:276)
> at
> org.apache.ambari.server.topology.AmbariContext.createConfigGroupsAndRegisterHost(AmbariContext.java:653)
> ... 7 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21427) Assigning hosts concurrently to same config group may fail with "org.apache.ambari.server.controller.spi.ResourceAlreadyExistsException: Config group already exist'
[
https://issues.apache.org/jira/browse/AMBARI-21427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Toader updated AMBARI-21427:
--
Status: Patch Available (was: In Progress)
> Assigning hosts concurrently to same config group may fail with
> "org.apache.ambari.server.controller.spi.ResourceAlreadyExistsException:
> Config group already exist'
> -
>
> Key: AMBARI-21427
> URL: https://issues.apache.org/jira/browse/AMBARI-21427
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
> Fix For: 2.5.2
>
> Attachments: AMBARI-21427.v1.patch
>
>
> Assigning hosts concurrently to the same config group may fail due to a race
> condition causing the config group to be created twice:
> {noformat}
> 05 Jul 2017 18:50:44,742 INFO [pool-5-thread-2]
> RegisterWithConfigGroupTask:45 - HostRequest: Executing CONFIGURE task for
> host: w1.internal
> 05 Jul 2017 18:50:44,884 ERROR [pool-5-thread-2] AmbariContext:655 - Failed
> to create new configuration group:
> org.apache.ambari.server.controller.spi.ResourceAlreadyExistsException:
> Config group already exists with the same name and tag, clusterName =
> mycluster, groupName = myblueprint:group1, tag = HDFS
> 05 Jul 2017 18:50:44,885 ERROR [pool-5-thread-2] AmbariContext:342 - Unable
> to register config group for host:
> java.lang.RuntimeException: Failed to create new configuration group:
> org.apache.ambari.server.controller.spi.ResourceAlreadyExistsException:
> Config group already exists with the same name and tag, clusterName =
> mycluster, groupName = myblueprint:group1, tag = HDFS
> at
> org.apache.ambari.server.topology.AmbariContext.createConfigGroupsAndRegisterHost(AmbariContext.java:656)
> at
> org.apache.ambari.server.topology.AmbariContext.registerHostWithConfigGroup(AmbariContext.java:339)
> at
> org.apache.ambari.server.topology.tasks.RegisterWithConfigGroupTask.runTask(RegisterWithConfigGroupTask.java:46)
> 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:748)
> Caused by:
> org.apache.ambari.server.controller.spi.ResourceAlreadyExistsException:
> Config group already exists with the same name and tag, clusterName =
> mycluster, groupName = myblueprint:group1, tag = HDFS
> at
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.createResources(AbstractResourceProvider.java:282)
> at
> org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider.createResources(ConfigGroupResourceProvider.java:276)
> at
> org.apache.ambari.server.topology.AmbariContext.createConfigGroupsAndRegisterHost(AmbariContext.java:653)
> ... 7 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21430) Allow Multiple Versions of Stack Tools to Co-Exist
Jonathan Hurley created AMBARI-21430:
Summary: Allow Multiple Versions of Stack Tools to Co-Exist
Key: AMBARI-21430
URL: https://issues.apache.org/jira/browse/AMBARI-21430
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.2
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Priority: Blocker
Fix For: 2.5.2
Currently, the stack tools:
- {{cluster-env/stack_features}}
- {{cluster-env/stack_tools}}
- {{cluster-env/stack_root}}
Are bound to the {{cluster-env}} without any sort of scoping. This prevents 2
sets of stack tools from co-existing. Although Ambari doesn't support more than
a single stack in 2.x, we do support upgrades from one stack vendor to another.
Therefore, we need this support to send the right tools on the commands.
This will involve the following work:
- Changing the existing stack tools/features/root to have a stack name as the
key in the JSON
- Altering the existing {{cluster-env}} tools on upgrade
- Ensuring that the stack tools/features for a repository's stack exist when
distributing that stack
- Changing any Python code which references the stack tools (stack_tools.py,
alerts, etc)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21429) Log Search UI: implement dynamic loading of options for filters
[ https://issues.apache.org/jira/browse/AMBARI-21429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-21429: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-feature-logsearch-ui > Log Search UI: implement dynamic loading of options for filters > --- > > Key: AMBARI-21429 > URL: https://issues.apache.org/jira/browse/AMBARI-21429 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-21429.patch > > > Options for logs list filters should be loaded dynamically based on real > application data. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21429) Log Search UI: implement dynamic loading of options for filters
[ https://issues.apache.org/jira/browse/AMBARI-21429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-21429: -- Status: Patch Available (was: Open) > Log Search UI: implement dynamic loading of options for filters > --- > > Key: AMBARI-21429 > URL: https://issues.apache.org/jira/browse/AMBARI-21429 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-21429.patch > > > Options for logs list filters should be loaded dynamically based on real > application data. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21429) Log Search UI: implement dynamic loading of options for filters
[ https://issues.apache.org/jira/browse/AMBARI-21429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-21429: -- Attachment: AMBARI-21429.patch > Log Search UI: implement dynamic loading of options for filters > --- > > Key: AMBARI-21429 > URL: https://issues.apache.org/jira/browse/AMBARI-21429 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-21429.patch > > > Options for logs list filters should be loaded dynamically based on real > application data. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21429) Log Search UI: implement dynamic loading of options for filters
Andrii Babiichuk created AMBARI-21429: - Summary: Log Search UI: implement dynamic loading of options for filters Key: AMBARI-21429 URL: https://issues.apache.org/jira/browse/AMBARI-21429 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 3.0.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Fix For: 3.0.0 Options for logs list filters should be loaded dynamically based on real application data. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21400) Upgrade Infra Solr version from 5.5.2 to 6.6.x
[ https://issues.apache.org/jira/browse/AMBARI-21400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078112#comment-16078112 ] Hudson commented on AMBARI-21400: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7740 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7740/]) AMBARI-21400. Upgrade Infra Solr version from 5.5.2 to 6.6.x (oleewere) (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a795f38cd49c2c55c837b0daecaa63a67015d0eb]) * (edit) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/dao/SolrSchemaFieldDao.java * (edit) ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/package/scripts/setup_infra_solr.py * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/properties/service_logs-solrconfig.xml.j2 * (edit) ambari-logsearch/ambari-logsearch-server/src/main/configsets/history/conf/solrconfig.xml * (edit) ambari-infra/ambari-infra-assembly/src/main/resources/solr * (edit) ambari-logsearch/ambari-logsearch-server/src/main/configsets/hadoop_logs/conf/solrconfig.xml * (edit) ambari-infra/ambari-infra-solr-client/src/main/java/org/apache/ambari/infra/solr/AmbariSolrCloudClient.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog300.java * (edit) ambari-infra/pom.xml * (edit) ambari-logsearch/pom.xml * (edit) ambari-server/src/test/python/stacks/2.4/AMBARI_INFRA/test_infra_solr.py * (edit) ambari-infra/ambari-infra-solr-client/src/main/java/org/apache/ambari/infra/solr/AmbariSolrCloudCLI.java * (edit) ambari-logsearch/docker/Dockerfile * (edit) ambari-common/src/main/python/resource_management/libraries/functions/solr_cloud_util.py * (edit) ambari-infra/ambari-infra-solr-client/src/main/java/org/apache/ambari/infra/solr/commands/SetClusterPropertyZkCommand.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog300Test.java * (add) ambari-infra/ambari-infra-solr-client/src/main/java/org/apache/ambari/infra/solr/commands/RemoveAdminHandlersCommand.java * (edit) ambari-infra/ambari-infra-solr-plugin/src/test/java/org/apache/ambari/infra/security/InfraRuleBasedAuthorizationPluginTest.java * (edit) ambari-logsearch/docker/bin/start.sh * (edit) ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/package/scripts/params.py * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/properties/audit_logs-solrconfig.xml.j2 * (edit) ambari-logsearch/ambari-logsearch-server/src/main/configsets/audit_logs/conf/solrconfig.xml > Upgrade Infra Solr version from 5.5.2 to 6.6.x > -- > > Key: AMBARI-21400 > URL: https://issues.apache.org/jira/browse/AMBARI-21400 > Project: Ambari > Issue Type: Bug > Components: ambari-infra, ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 3.0.0 > > Original Estimate: 96h > Remaining Estimate: 96h > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21415) Fix execution/custom_commands/custom_actions/service_checks. Send clusterHostInfo
[ https://issues.apache.org/jira/browse/AMBARI-21415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-21415: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-3.0-perf > Fix execution/custom_commands/custom_actions/service_checks. Send > clusterHostInfo > - > > Key: AMBARI-21415 > URL: https://issues.apache.org/jira/browse/AMBARI-21415 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0 > > Attachments: AMBARI-21415.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-20861) BE: Extend Ambari REST API to Support User Account Management Improvements
[
https://issues.apache.org/jira/browse/AMBARI-20861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-20861:
--
Attachment: AMBARI-20861_branch-feature-AMBARI-20859_02.patch
> BE: Extend Ambari REST API to Support User Account Management Improvements
> --
>
> Key: AMBARI-20861
> URL: https://issues.apache.org/jira/browse/AMBARI-20861
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: rest_api, security
> Fix For: 3.0.0
>
> Attachments: AMBARI-20861_branch-feature-AMBARI-20859_01.patch,
> AMBARI-20861_branch-feature-AMBARI-20859_02.patch
>
>
> Update the Ambari REST API to allow for GET, POST, PUT, and DELETE operations
> on the authentication sources related to an Ambari user account.
> Add the following entry points:
> * {{/api/v1/users/:USER_ID}}
> ** Get a user
> ** Modify a user
> * * {{/api/v1/users/:USERNAME/sources}}
> ** List a user’s authentication sources
> ** Add a new authentication source for a user
> * {{/api/v1/users/:USERNAME/sources/:SOURCE_ID}}
> ** Get details on a specific authentication source for a user
> ** Modify details for a specific authentication source for a user
> * {{/api/v1/users/:USER_ID/sources}}
> ** List a user’s authentication sources
> ** Add a new authentication source for a user
> * {{/api/v1/users/:USER_ID/sources/:SOURCE_ID}}
> ** Get details on a specific authentication source for a user
> ** Modify details for a specific authentication source for a user
> Update the following entry points, ensuring backwards compatibility where
> possible:
> * {{/api/v1/users}}
> ** List all users
> ** Add a new user
> ** Backward compatibility: Set password should create or update the
> appropriate user_authentication record.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-21400) Upgrade Infra Solr version from 5.5.2 to 6.6.x
[
https://issues.apache.org/jira/browse/AMBARI-21400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó resolved AMBARI-21400.
---
Resolution: Fixed
committed to trunk:
{code:java}
commit a795f38cd49c2c55c837b0daecaa63a67015d0eb
Author: oleewere
Date: Thu Jul 6 20:28:11 2017 +0200
AMBARI-21400. Upgrade Infra Solr version from 5.5.2 to 6.6.x (oleewere)
{code}
> Upgrade Infra Solr version from 5.5.2 to 6.6.x
> --
>
> Key: AMBARI-21400
> URL: https://issues.apache.org/jira/browse/AMBARI-21400
> Project: Ambari
> Issue Type: Bug
> Components: ambari-infra, ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 3.0.0
>
> Original Estimate: 96h
> Remaining Estimate: 96h
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-20861) BE: Extend Ambari REST API to Support User Account Management Improvements
[
https://issues.apache.org/jira/browse/AMBARI-20861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078069#comment-16078069
]
Hadoop QA commented on AMBARI-20861:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12876082/AMBARI-20861_branch-feature-AMBARI-20859_01.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11757//console
This message is automatically generated.
> BE: Extend Ambari REST API to Support User Account Management Improvements
> --
>
> Key: AMBARI-20861
> URL: https://issues.apache.org/jira/browse/AMBARI-20861
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: rest_api, security
> Fix For: 3.0.0
>
> Attachments: AMBARI-20861_branch-feature-AMBARI-20859_01.patch
>
>
> Update the Ambari REST API to allow for GET, POST, PUT, and DELETE operations
> on the authentication sources related to an Ambari user account.
> Add the following entry points:
> * {{/api/v1/users/:USER_ID}}
> ** Get a user
> ** Modify a user
> * * {{/api/v1/users/:USERNAME/sources}}
> ** List a user’s authentication sources
> ** Add a new authentication source for a user
> * {{/api/v1/users/:USERNAME/sources/:SOURCE_ID}}
> ** Get details on a specific authentication source for a user
> ** Modify details for a specific authentication source for a user
> * {{/api/v1/users/:USER_ID/sources}}
> ** List a user’s authentication sources
> ** Add a new authentication source for a user
> * {{/api/v1/users/:USER_ID/sources/:SOURCE_ID}}
> ** Get details on a specific authentication source for a user
> ** Modify details for a specific authentication source for a user
> Update the following entry points, ensuring backwards compatibility where
> possible:
> * {{/api/v1/users}}
> ** List all users
> ** Add a new user
> ** Backward compatibility: Set password should create or update the
> appropriate user_authentication record.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21339) logviewer is not being started in the node where nimbus is hosted
[ https://issues.apache.org/jira/browse/AMBARI-21339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078036#comment-16078036 ] Hudson commented on AMBARI-21339: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7739 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7739/]) AMBARI-21339 logviewer started along with nimbus if supervisor is not (lpuskas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=1939dabcd7f6eeff3bb93e4d6f718b8a32351bd2]) * (edit) ambari-server/src/test/python/stacks/2.1/configs/secured-storm-start.json * (edit) ambari-server/src/test/python/stacks/2.1/configs/default-storm-start.json * (edit) ambari-server/src/test/python/stacks/2.1/configs/default.json * (edit) ambari-server/src/test/python/stacks/2.1/configs/secured.json * (edit) ambari-server/src/main/resources/common-services/STORM/0.9.1/package/scripts/nimbus.py * (edit) ambari-server/src/test/python/stacks/2.1/STORM/test_storm_nimbus.py > logviewer is not being started in the node where nimbus is hosted > - > > Key: AMBARI-21339 > URL: https://issues.apache.org/jira/browse/AMBARI-21339 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Sandeep Nemuri >Assignee: Laszlo Puskas > Attachments: AMBARI-21339.b-2.5.v2.patch, > AMBARI-21339.b-2.5.v3.patch, AMBARI-21339.patch, storm1.png, storm2.png > > > Ambari is not starting the logviewer deamon in the host where nimbus is > running. Hence users are unable to view the nimbus log from the UI. > !storm1.png|align=center,|height=750%,width=750&! > !storm2.png|align=center,|height=750%,width=750&! > Need to start logviewer where nimbus is hosted to view the nimbus logs form > storm UI. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-20861) BE: Extend Ambari REST API to Support User Account Management Improvements
[
https://issues.apache.org/jira/browse/AMBARI-20861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-20861:
--
Attachment: AMBARI-20861_branch-feature-AMBARI-20859_01.patch
> BE: Extend Ambari REST API to Support User Account Management Improvements
> --
>
> Key: AMBARI-20861
> URL: https://issues.apache.org/jira/browse/AMBARI-20861
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: rest_api, security
> Fix For: 3.0.0
>
> Attachments: AMBARI-20861_branch-feature-AMBARI-20859_01.patch
>
>
> Update the Ambari REST API to allow for GET, POST, PUT, and DELETE operations
> on the authentication sources related to an Ambari user account.
> Add the following entry points:
> * {{/api/v1/users/:USER_ID}}
> ** Get a user
> ** Modify a user
> * * {{/api/v1/users/:USERNAME/sources}}
> ** List a user’s authentication sources
> ** Add a new authentication source for a user
> * {{/api/v1/users/:USERNAME/sources/:SOURCE_ID}}
> ** Get details on a specific authentication source for a user
> ** Modify details for a specific authentication source for a user
> * {{/api/v1/users/:USER_ID/sources}}
> ** List a user’s authentication sources
> ** Add a new authentication source for a user
> * {{/api/v1/users/:USER_ID/sources/:SOURCE_ID}}
> ** Get details on a specific authentication source for a user
> ** Modify details for a specific authentication source for a user
> Update the following entry points, ensuring backwards compatibility where
> possible:
> * {{/api/v1/users}}
> ** List all users
> ** Add a new user
> ** Backward compatibility: Set password should create or update the
> appropriate user_authentication record.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-20861) BE: Extend Ambari REST API to Support User Account Management Improvements
[
https://issues.apache.org/jira/browse/AMBARI-20861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-20861:
--
Attachment: (was: AMBARI-20861_branch-feature-AMBARI-20859_01.patch)
> BE: Extend Ambari REST API to Support User Account Management Improvements
> --
>
> Key: AMBARI-20861
> URL: https://issues.apache.org/jira/browse/AMBARI-20861
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: rest_api, security
> Fix For: 3.0.0
>
> Attachments: AMBARI-20861_branch-feature-AMBARI-20859_01.patch
>
>
> Update the Ambari REST API to allow for GET, POST, PUT, and DELETE operations
> on the authentication sources related to an Ambari user account.
> Add the following entry points:
> * {{/api/v1/users/:USER_ID}}
> ** Get a user
> ** Modify a user
> * * {{/api/v1/users/:USERNAME/sources}}
> ** List a user’s authentication sources
> ** Add a new authentication source for a user
> * {{/api/v1/users/:USERNAME/sources/:SOURCE_ID}}
> ** Get details on a specific authentication source for a user
> ** Modify details for a specific authentication source for a user
> * {{/api/v1/users/:USER_ID/sources}}
> ** List a user’s authentication sources
> ** Add a new authentication source for a user
> * {{/api/v1/users/:USER_ID/sources/:SOURCE_ID}}
> ** Get details on a specific authentication source for a user
> ** Modify details for a specific authentication source for a user
> Update the following entry points, ensuring backwards compatibility where
> possible:
> * {{/api/v1/users}}
> ** List all users
> ** Add a new user
> ** Backward compatibility: Set password should create or update the
> appropriate user_authentication record.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-20861) BE: Extend Ambari REST API to Support User Account Management Improvements
[
https://issues.apache.org/jira/browse/AMBARI-20861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-20861:
--
Status: Patch Available (was: Open)
> BE: Extend Ambari REST API to Support User Account Management Improvements
> --
>
> Key: AMBARI-20861
> URL: https://issues.apache.org/jira/browse/AMBARI-20861
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: rest_api, security
> Fix For: 3.0.0
>
> Attachments: AMBARI-20861_branch-feature-AMBARI-20859_01.patch
>
>
> Update the Ambari REST API to allow for GET, POST, PUT, and DELETE operations
> on the authentication sources related to an Ambari user account.
> Add the following entry points:
> * {{/api/v1/users/:USER_ID}}
> ** Get a user
> ** Modify a user
> * * {{/api/v1/users/:USERNAME/sources}}
> ** List a user’s authentication sources
> ** Add a new authentication source for a user
> * {{/api/v1/users/:USERNAME/sources/:SOURCE_ID}}
> ** Get details on a specific authentication source for a user
> ** Modify details for a specific authentication source for a user
> * {{/api/v1/users/:USER_ID/sources}}
> ** List a user’s authentication sources
> ** Add a new authentication source for a user
> * {{/api/v1/users/:USER_ID/sources/:SOURCE_ID}}
> ** Get details on a specific authentication source for a user
> ** Modify details for a specific authentication source for a user
> Update the following entry points, ensuring backwards compatibility where
> possible:
> * {{/api/v1/users}}
> ** List all users
> ** Add a new user
> ** Backward compatibility: Set password should create or update the
> appropriate user_authentication record.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-20861) BE: Extend Ambari REST API to Support User Account Management Improvements
[
https://issues.apache.org/jira/browse/AMBARI-20861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-20861:
--
Attachment: AMBARI-20861_branch-feature-AMBARI-20859_01.patch
> BE: Extend Ambari REST API to Support User Account Management Improvements
> --
>
> Key: AMBARI-20861
> URL: https://issues.apache.org/jira/browse/AMBARI-20861
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: rest_api, security
> Fix For: 3.0.0
>
> Attachments: AMBARI-20861_branch-feature-AMBARI-20859_01.patch
>
>
> Update the Ambari REST API to allow for GET, POST, PUT, and DELETE operations
> on the authentication sources related to an Ambari user account.
> Add the following entry points:
> * {{/api/v1/users/:USER_ID}}
> ** Get a user
> ** Modify a user
> * * {{/api/v1/users/:USERNAME/sources}}
> ** List a user’s authentication sources
> ** Add a new authentication source for a user
> * {{/api/v1/users/:USERNAME/sources/:SOURCE_ID}}
> ** Get details on a specific authentication source for a user
> ** Modify details for a specific authentication source for a user
> * {{/api/v1/users/:USER_ID/sources}}
> ** List a user’s authentication sources
> ** Add a new authentication source for a user
> * {{/api/v1/users/:USER_ID/sources/:SOURCE_ID}}
> ** Get details on a specific authentication source for a user
> ** Modify details for a specific authentication source for a user
> Update the following entry points, ensuring backwards compatibility where
> possible:
> * {{/api/v1/users}}
> ** List all users
> ** Add a new user
> ** Backward compatibility: Set password should create or update the
> appropriate user_authentication record.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21428) Host Versions Page Doesn't Show Stacks From Different Vendors
[ https://issues.apache.org/jira/browse/AMBARI-21428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21428: -- Status: Patch Available (was: Open) > Host Versions Page Doesn't Show Stacks From Different Vendors > - > > Key: AMBARI-21428 > URL: https://issues.apache.org/jira/browse/AMBARI-21428 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.5.2 > > Attachments: AMBARI-21428.patch > > > After registering a repository from a vendor which is different from the > installed stack, the stacks and versions page doesn't show the new stack > (even though it is compatible with the existing stack. > STR: > - Install non-HDP stack > - Upgrade to Ambari 2.5.2 > - Register a new repository for HDP 2.6 > - Navigate to the Host Versions page -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21428) Host Versions Page Doesn't Show Stacks From Different Vendors
[ https://issues.apache.org/jira/browse/AMBARI-21428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16077917#comment-16077917 ] Andrii Tkach commented on AMBARI-21428: --- committed to branch-feature-AMBARI-21348 > Host Versions Page Doesn't Show Stacks From Different Vendors > - > > Key: AMBARI-21428 > URL: https://issues.apache.org/jira/browse/AMBARI-21428 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.5.2 > > Attachments: AMBARI-21428.patch > > > After registering a repository from a vendor which is different from the > installed stack, the stacks and versions page doesn't show the new stack > (even though it is compatible with the existing stack. > STR: > - Install non-HDP stack > - Upgrade to Ambari 2.5.2 > - Register a new repository for HDP 2.6 > - Navigate to the Host Versions page -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21428) Host Versions Page Doesn't Show Stacks From Different Vendors
[ https://issues.apache.org/jira/browse/AMBARI-21428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21428: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Host Versions Page Doesn't Show Stacks From Different Vendors > - > > Key: AMBARI-21428 > URL: https://issues.apache.org/jira/browse/AMBARI-21428 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.5.2 > > Attachments: AMBARI-21428.patch > > > After registering a repository from a vendor which is different from the > installed stack, the stacks and versions page doesn't show the new stack > (even though it is compatible with the existing stack. > STR: > - Install non-HDP stack > - Upgrade to Ambari 2.5.2 > - Register a new repository for HDP 2.6 > - Navigate to the Host Versions page -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21428) Host Versions Page Doesn't Show Stacks From Different Vendors
[ https://issues.apache.org/jira/browse/AMBARI-21428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16077902#comment-16077902 ] Andrii Babiichuk commented on AMBARI-21428: --- +1 for the patch > Host Versions Page Doesn't Show Stacks From Different Vendors > - > > Key: AMBARI-21428 > URL: https://issues.apache.org/jira/browse/AMBARI-21428 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.5.2 > > Attachments: AMBARI-21428.patch > > > After registering a repository from a vendor which is different from the > installed stack, the stacks and versions page doesn't show the new stack > (even though it is compatible with the existing stack. > STR: > - Install non-HDP stack > - Upgrade to Ambari 2.5.2 > - Register a new repository for HDP 2.6 > - Navigate to the Host Versions page -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21428) Host Versions Page Doesn't Show Stacks From Different Vendors
[ https://issues.apache.org/jira/browse/AMBARI-21428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16077899#comment-16077899 ] Andrii Tkach commented on AMBARI-21428: --- 30381 passing (26s) 157 pending > Host Versions Page Doesn't Show Stacks From Different Vendors > - > > Key: AMBARI-21428 > URL: https://issues.apache.org/jira/browse/AMBARI-21428 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.5.2 > > Attachments: AMBARI-21428.patch > > > After registering a repository from a vendor which is different from the > installed stack, the stacks and versions page doesn't show the new stack > (even though it is compatible with the existing stack. > STR: > - Install non-HDP stack > - Upgrade to Ambari 2.5.2 > - Register a new repository for HDP 2.6 > - Navigate to the Host Versions page -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21428) Host Versions Page Doesn't Show Stacks From Different Vendors
[ https://issues.apache.org/jira/browse/AMBARI-21428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21428: -- Attachment: AMBARI-21428.patch > Host Versions Page Doesn't Show Stacks From Different Vendors > - > > Key: AMBARI-21428 > URL: https://issues.apache.org/jira/browse/AMBARI-21428 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.5.2 > > Attachments: AMBARI-21428.patch > > > After registering a repository from a vendor which is different from the > installed stack, the stacks and versions page doesn't show the new stack > (even though it is compatible with the existing stack. > STR: > - Install non-HDP stack > - Upgrade to Ambari 2.5.2 > - Register a new repository for HDP 2.6 > - Navigate to the Host Versions page -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21428) Host Versions Page Doesn't Show Stacks From Different Vendors
Andrii Tkach created AMBARI-21428: - Summary: Host Versions Page Doesn't Show Stacks From Different Vendors Key: AMBARI-21428 URL: https://issues.apache.org/jira/browse/AMBARI-21428 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.2 Reporter: Andrii Tkach Assignee: Andrii Tkach Priority: Blocker Fix For: 2.5.2 After registering a repository from a vendor which is different from the installed stack, the stacks and versions page doesn't show the new stack (even though it is compatible with the existing stack. STR: - Install non-HDP stack - Upgrade to Ambari 2.5.2 - Register a new repository for HDP 2.6 - Navigate to the Host Versions page -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21409) Ambari agent not starting in latest PPC build
[ https://issues.apache.org/jira/browse/AMBARI-21409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16077842#comment-16077842 ] Hudson commented on AMBARI-21409: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7738 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7738/]) AMBARI-21409. Ambari agent not starting in latest PPC build (aonishuk) (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6832ed93a156b33178e62d6f8279faea8e414cba]) * (edit) ambari-common/src/main/python/ambari_commons/resources/os_family.json > Ambari agent not starting in latest PPC build > - > > Key: AMBARI-21409 > URL: https://issues.apache.org/jira/browse/AMBARI-21409 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.2 > > Attachments: AMBARI-21409.patch > > > Build: > > > > > http://s3.amazonaws.com/dev.hortonworks.com/ambari/centos7-ppc/2.x/BUILDS/2.5.2.0-95 > > > > > INFO 2017-07-03 08:53:46,092 NetUtil.py:70 - Connecting to > https://nat-r7-kwtu-flumeng-5.openstacklocal:8440/connection_info > INFO 2017-07-03 08:53:46,167 security.py:93 - SSL Connect being called.. > connecting to the server > INFO 2017-07-03 08:53:46,257 security.py:60 - SSL connection established. > Two-way SSL authentication is turned off on the server. > ERROR 2017-07-03 08:53:46,266 Controller.py:190 - Cannot register host > with not supported os type, hostname=nat-r7-kwtu-flumeng-5.openstacklocal, > serverOsType=redhat-ppc7, agentOsType=redhat-ppc7 > INFO 2017-07-03 08:53:46,266 Controller.py:516 - Registration response > from nat-r7-kwtu-flumeng-5.openstacklocal was FAILED > INFO 2017-07-03 08:53:46,266 Controller.py:531 - Registration response > from %s didn't contain 'response' as a key > INFO 2017-07-03 08:53:46,266 Controller.py:503 - Finished heartbeating > and registering cycle > INFO 2017-07-03 08:53:46,266 Controller.py:509 - Controller thread has > successfully finished > INFO 2017-07-03 08:53:47,959 ExitHelper.py:56 - Performing cleanup before > exiting... > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21427) Assigning hosts concurrently to same config group may fail with "org.apache.ambari.server.controller.spi.ResourceAlreadyExistsException: Config group already exist'
Sebastian Toader created AMBARI-21427:
-
Summary: Assigning hosts concurrently to same config group may
fail with
"org.apache.ambari.server.controller.spi.ResourceAlreadyExistsException: Config
group already exist'
Key: AMBARI-21427
URL: https://issues.apache.org/jira/browse/AMBARI-21427
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.0
Reporter: Sebastian Toader
Assignee: Sebastian Toader
Fix For: 2.5.2
Assigning hosts concurrently to the same config group may fail due to a race
condition causing the config group to be created twice:
{noformat}
05 Jul 2017 18:50:44,742 INFO [pool-5-thread-2] RegisterWithConfigGroupTask:45
- HostRequest: Executing CONFIGURE task for host: w1.internal
05 Jul 2017 18:50:44,884 ERROR [pool-5-thread-2] AmbariContext:655 - Failed to
create new configuration group:
org.apache.ambari.server.controller.spi.ResourceAlreadyExistsException: Config
group already exists with the same name and tag, clusterName = mycluster,
groupName = myblueprint:group1, tag = HDFS
05 Jul 2017 18:50:44,885 ERROR [pool-5-thread-2] AmbariContext:342 - Unable to
register config group for host:
java.lang.RuntimeException: Failed to create new configuration group:
org.apache.ambari.server.controller.spi.ResourceAlreadyExistsException: Config
group already exists with the same name and tag, clusterName = mycluster,
groupName = myblueprint:group1, tag = HDFS
at
org.apache.ambari.server.topology.AmbariContext.createConfigGroupsAndRegisterHost(AmbariContext.java:656)
at
org.apache.ambari.server.topology.AmbariContext.registerHostWithConfigGroup(AmbariContext.java:339)
at
org.apache.ambari.server.topology.tasks.RegisterWithConfigGroupTask.runTask(RegisterWithConfigGroupTask.java:46)
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:748)
Caused by:
org.apache.ambari.server.controller.spi.ResourceAlreadyExistsException: Config
group already exists with the same name and tag, clusterName = mycluster,
groupName = myblueprint:group1, tag = HDFS
at
org.apache.ambari.server.controller.internal.AbstractResourceProvider.createResources(AbstractResourceProvider.java:282)
at
org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider.createResources(ConfigGroupResourceProvider.java:276)
at
org.apache.ambari.server.topology.AmbariContext.createConfigGroupsAndRegisterHost(AmbariContext.java:653)
... 7 more
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21409) Ambari agent not starting in latest PPC build
[ https://issues.apache.org/jira/browse/AMBARI-21409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16077825#comment-16077825 ] Hudson commented on AMBARI-21409: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1660 (See [https://builds.apache.org/job/Ambari-branch-2.5/1660/]) AMBARI-21409. Ambari agent not starting in latest PPC build (aonishuk) (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=065dd9c50163b8a93b15d94a8a2bb73e8f210715]) * (edit) ambari-common/src/main/python/ambari_commons/resources/os_family.json > Ambari agent not starting in latest PPC build > - > > Key: AMBARI-21409 > URL: https://issues.apache.org/jira/browse/AMBARI-21409 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.2 > > Attachments: AMBARI-21409.patch > > > Build: > > > > > http://s3.amazonaws.com/dev.hortonworks.com/ambari/centos7-ppc/2.x/BUILDS/2.5.2.0-95 > > > > > INFO 2017-07-03 08:53:46,092 NetUtil.py:70 - Connecting to > https://nat-r7-kwtu-flumeng-5.openstacklocal:8440/connection_info > INFO 2017-07-03 08:53:46,167 security.py:93 - SSL Connect being called.. > connecting to the server > INFO 2017-07-03 08:53:46,257 security.py:60 - SSL connection established. > Two-way SSL authentication is turned off on the server. > ERROR 2017-07-03 08:53:46,266 Controller.py:190 - Cannot register host > with not supported os type, hostname=nat-r7-kwtu-flumeng-5.openstacklocal, > serverOsType=redhat-ppc7, agentOsType=redhat-ppc7 > INFO 2017-07-03 08:53:46,266 Controller.py:516 - Registration response > from nat-r7-kwtu-flumeng-5.openstacklocal was FAILED > INFO 2017-07-03 08:53:46,266 Controller.py:531 - Registration response > from %s didn't contain 'response' as a key > INFO 2017-07-03 08:53:46,266 Controller.py:503 - Finished heartbeating > and registering cycle > INFO 2017-07-03 08:53:46,266 Controller.py:509 - Controller thread has > successfully finished > INFO 2017-07-03 08:53:47,959 ExitHelper.py:56 - Performing cleanup before > exiting... > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21423) Add REST end point for the documentation of the Log Feeder shipper properties
[
https://issues.apache.org/jira/browse/AMBARI-21423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16077810#comment-16077810
]
Hadoop QA commented on AMBARI-21423:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12876007/AMBARI-21423.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-logsearch/ambari-logsearch-config-api
ambari-logsearch/ambari-logsearch-config-zookeeper
ambari-logsearch/ambari-logsearch-logfeeder
ambari-logsearch/ambari-logsearch-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11756//console
This message is automatically generated.
> Add REST end point for the documentation of the Log Feeder shipper properties
> -
>
> Key: AMBARI-21423
> URL: https://issues.apache.org/jira/browse/AMBARI-21423
> Project: Ambari
> Issue Type: Task
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 3.0.0
>
> Attachments: AMBARI-21423.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21385) Selected hosts are not dropped event if some of the selected hosts was deleted
[ https://issues.apache.org/jira/browse/AMBARI-21385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16077787#comment-16077787 ] Hudson commented on AMBARI-21385: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7737 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7737/]) AMBARI-21385. Selected hosts are not dropped event if some of the (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ac5eaae59673740a43b56b54978948e73cd71a54]) * (edit) ambari-web/app/controllers/main/host/bulk_operations_controller.js * (edit) ambari-web/app/utils/db.js * (edit) ambari-web/app/views/main/host.js * (edit) ambari-web/app/controllers/main/host/details.js * (edit) ambari-web/test/views/main/host_test.js * (edit) ambari-web/app/mappers/hosts_mapper.js > Selected hosts are not dropped event if some of the selected hosts was deleted > -- > > Key: AMBARI-21385 > URL: https://issues.apache.org/jira/browse/AMBARI-21385 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 3.0.0 > > Attachments: AMBARI-21385.patch > > > *STR* > * Selected two hosts on the Hosts page via checkboxes > * Delete one of the selected hosts > * After page refresh bulk-dropdown menu shows that two hosts are selected > (however hosts-table doesn't contain deleted host and only one checkbox is > checked) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21384) Message for deleted hosts is confusing
[ https://issues.apache.org/jira/browse/AMBARI-21384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16077786#comment-16077786 ] Hudson commented on AMBARI-21384: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7737 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7737/]) AMBARI-21384. Message for deleted hosts is confusing (alexantonenko) (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f17d317b725012ccc687ee070b1e1dbc604e8d12]) * (edit) ambari-web/app/controllers/main/host/bulk_operations_controller.js * (edit) ambari-web/app/messages.js > Message for deleted hosts is confusing > -- > > Key: AMBARI-21384 > URL: https://issues.apache.org/jira/browse/AMBARI-21384 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 3.0.0 > > Attachments: AMBARI-21384.patch > > > Message in the popup is about deleted hosts. However list of deleted > components is shown. > See screenshot attached -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21388) Can't delete hosts components via bulk-menu
[ https://issues.apache.org/jira/browse/AMBARI-21388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16077788#comment-16077788 ] Hudson commented on AMBARI-21388: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7737 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7737/]) AMBARI-21388. Can't delete hosts components via bulk-menu (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7029e7fa0c3e2ebd8e6eea7eef1f965234018586]) * (edit) ambari-web/app/controllers/main/host/bulk_operations_controller.js * (edit) ambari-web/app/messages.js * (edit) ambari-web/app/templates/main/host/delete_hosts_result_popup.hbs > Can't delete hosts components via bulk-menu > --- > > Key: AMBARI-21388 > URL: https://issues.apache.org/jira/browse/AMBARI-21388 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 3.0.0 > > Attachments: AMBARI-21388.patch > > > *STR* > * Select two hosts via checkboxes > * On the bulk-menu select "Selected Hosts" -> "Datanodes" (or any other > available component) -> "Delete" > * Confirmation popup appears. Click OK > * Nothing happens. Only gray background appears -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21424) BigInsight stack upgrade XML files should prevent downgrade
[
https://issues.apache.org/jira/browse/AMBARI-21424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1605#comment-1605
]
Hadoop QA commented on AMBARI-21424:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12876016/AMBARI-21424.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11755//console
This message is automatically generated.
> BigInsight stack upgrade XML files should prevent downgrade
> ---
>
> Key: AMBARI-21424
> URL: https://issues.apache.org/jira/browse/AMBARI-21424
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 2.5.2
>
> Attachments: AMBARI-21424.patch
>
>
> The BI upgrade XML files need to prevent downgrades. This can be done by
> adding the {{downgrade-allowed}} element.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21426) Apply ZEPPELIN-2698 related changes in Ambari
[
https://issues.apache.org/jira/browse/AMBARI-21426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1602#comment-1602
]
Hadoop QA commented on AMBARI-21426:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12876037/AMBARI-21426_trunk_v1.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:red}-1 core tests{color}. The test build failed in
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/11754//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11754//console
This message is automatically generated.
> Apply ZEPPELIN-2698 related changes in Ambari
> -
>
> Key: AMBARI-21426
> URL: https://issues.apache.org/jira/browse/AMBARI-21426
> Project: Ambari
> Issue Type: Improvement
>Reporter: Prabhjyot Singh
>Assignee: Prabhjyot Singh
> Attachments: AMBARI-21426_trunk_v1.patch
>
>
> With the merge of ZEPPELIN-2698, LAUNCH_KERBEROS_REFRESH_INTERVAL is renamed
> to KERBEROS_REFRESH_INTERVAL.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21409) Ambari agent not starting in latest PPC build
[ https://issues.apache.org/jira/browse/AMBARI-21409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-21409: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.5 > Ambari agent not starting in latest PPC build > - > > Key: AMBARI-21409 > URL: https://issues.apache.org/jira/browse/AMBARI-21409 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.2 > > Attachments: AMBARI-21409.patch > > > Build: > > > > > http://s3.amazonaws.com/dev.hortonworks.com/ambari/centos7-ppc/2.x/BUILDS/2.5.2.0-95 > > > > > INFO 2017-07-03 08:53:46,092 NetUtil.py:70 - Connecting to > https://nat-r7-kwtu-flumeng-5.openstacklocal:8440/connection_info > INFO 2017-07-03 08:53:46,167 security.py:93 - SSL Connect being called.. > connecting to the server > INFO 2017-07-03 08:53:46,257 security.py:60 - SSL connection established. > Two-way SSL authentication is turned off on the server. > ERROR 2017-07-03 08:53:46,266 Controller.py:190 - Cannot register host > with not supported os type, hostname=nat-r7-kwtu-flumeng-5.openstacklocal, > serverOsType=redhat-ppc7, agentOsType=redhat-ppc7 > INFO 2017-07-03 08:53:46,266 Controller.py:516 - Registration response > from nat-r7-kwtu-flumeng-5.openstacklocal was FAILED > INFO 2017-07-03 08:53:46,266 Controller.py:531 - Registration response > from %s didn't contain 'response' as a key > INFO 2017-07-03 08:53:46,266 Controller.py:503 - Finished heartbeating > and registering cycle > INFO 2017-07-03 08:53:46,266 Controller.py:509 - Controller thread has > successfully finished > INFO 2017-07-03 08:53:47,959 ExitHelper.py:56 - Performing cleanup before > exiting... > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
