ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebastian Toader (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-15489) Configuration with tag 'TOPOLOGY_RESOLVED' exists for 'cluster-env' error when creating Kerberized cluster with Blueprints
Date Mon, 21 Mar 2016 13:19:25 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-15489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sebastian Toader updated AMBARI-15489:
--------------------------------------
    Fix Version/s: 2.4.0

> Configuration with tag 'TOPOLOGY_RESOLVED' exists for 'cluster-env' error when creating
Kerberized cluster with Blueprints
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-15489
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15489
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.2.2
>            Reporter: Sebastian Toader
>            Assignee: Sebastian Toader
>            Priority: Critical
>             Fix For: 2.4.0, 2.2.2
>
>         Attachments: AMBARI-15489.v1.patch
>
>
> Configuration with tag 'TOPOLOGY_RESOLVED' exists for 'cluster-env' error when creating
Kerberized cluster with Blueprints.
> {noformat}
> 17 Mar 2016 21:17:51,611  INFO [pool-9-thread-1] AmbariManagementControllerImpl:1471
- Applying configuration with tag 'TOPOLOGY_RESOLVED' to cluster 'c1'  for configuration type
cluster-env
> 17 Mar 2016 21:17:51,611 ERROR [pool-9-thread-1] TopologyManager:766 - TopologyManager.ConfigureClusterTask:
An exception occurred while attempting to process cluster configs and set on cluster:
> java.lang.RuntimeException: Failed to set configurations on cluster: org.apache.ambari.server.AmbariException:
Configuration with tag 'TOPOLOGY_RESOLVED' exists for 'cluster-env'
>         at org.apache.ambari.server.topology.AmbariContext.setConfigurationOnCluster(AmbariContext.java:390)
>         at org.apache.ambari.server.topology.ClusterConfigurationRequest.setConfigurationsOnCluster(ClusterConfigurationRequest.java:416)
>         at org.apache.ambari.server.topology.ClusterConfigurationRequest.setConfigurationsOnCluster(ClusterConfigurationRequest.java:336)
>         at org.apache.ambari.server.topology.ClusterConfigurationRequest.process(ClusterConfigurationRequest.java:145)
>         at org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:764)
>         at org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:738)
>         at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
>         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)
> Caused by: org.apache.ambari.server.AmbariException: Configuration with tag 'TOPOLOGY_RESOLVED'
exists for 'cluster-env'
>         at org.apache.ambari.server.utils.RetryHelper.executeWithRetry(RetryHelper.java:110)
>         at org.apache.ambari.server.topology.AmbariContext.setConfigurationOnCluster(AmbariContext.java:381)
>         ... 11 more
> Caused by: org.apache.ambari.server.AmbariException: Configuration with tag 'TOPOLOGY_RESOLVED'
exists for 'cluster-env'
>         at org.apache.ambari.server.controller.AmbariManagementControllerImpl.createConfiguration(AmbariManagementControllerImpl.java:754)
>         at org.apache.ambari.server.controller.AmbariManagementControllerImpl.updateCluster(AmbariManagementControllerImpl.java:1477)
>         at org.apache.ambari.server.controller.AmbariManagementControllerImpl.updateClusters(AmbariManagementControllerImpl.java:1337)
>         at org.apache.ambari.server.topology.AmbariContext$5.call(AmbariContext.java:384)
>         at org.apache.ambari.server.utils.RetryHelper.executeWithRetry(RetryHelper.java:95)
>         ... 12 more
> 17 Mar 2016 21:17:51,611  INFO [pool-3-thread-1] AsyncCallableService:111 - Exception
during task execution:
> java.util.concurrent.ExecutionException: java.lang.Exception: java.lang.RuntimeException:
Failed to set configurations on cluster: org.apache.ambari.server.AmbariException: Configuration
with tag 'TOPOLOGY_RESOLVED' exists for 'cluste
> r-env'
>         at java.util.concurrent.FutureTask.report(FutureTask.java:122)
>         at java.util.concurrent.FutureTask.get(FutureTask.java:206)
>         at org.apache.ambari.server.topology.AsyncCallableService.taskCompleted(AsyncCallableService.java:103)
>         at org.apache.ambari.server.topology.AsyncCallableService.call(AsyncCallableService.java:74)
>         at org.apache.ambari.server.topology.AsyncCallableService.call(AsyncCallableService.java:37)
>         at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>         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)
> Caused by: java.lang.Exception: java.lang.RuntimeException: Failed to set configurations
on cluster: org.apache.ambari.server.AmbariException: Configuration with tag 'TOPOLOGY_RESOLVED'
exists for 'cluster-env'
>         at org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:770)
>         at org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:738)
>         at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
>         ... 3 more
> Caused by: java.lang.RuntimeException: Failed to set configurations on cluster: org.apache.ambari.server.AmbariException:
Configuration with tag 'TOPOLOGY_RESOLVED' exists for 'cluster-env'
>         at org.apache.ambari.server.topology.AmbariContext.setConfigurationOnCluster(AmbariContext.java:390)
>         at org.apache.ambari.server.topology.ClusterConfigurationRequest.setConfigurationsOnCluster(ClusterConfigurationRequest.java:416)
>         at org.apache.ambari.server.topology.ClusterConfigurationRequest.setConfigurationsOnCluster(ClusterConfigurationRequest.java:336)
>         at org.apache.ambari.server.topology.ClusterConfigurationRequest.process(ClusterConfigurationRequest.java:145)
>         at org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:764)
>         ... 7 more
> Caused by: org.apache.ambari.server.AmbariException: Configuration with tag 'TOPOLOGY_RESOLVED'
exists for 'cluster-env'
>         at org.apache.ambari.server.utils.RetryHelper.executeWithRetry(RetryHelper.java:110)
>         at org.apache.ambari.server.topology.AmbariContext.setConfigurationOnCluster(AmbariContext.java:381)
>         ... 11 more
> Caused by: org.apache.ambari.server.AmbariException: Configuration with tag 'TOPOLOGY_RESOLVED'
exists for 'cluster-env'
>         at org.apache.ambari.server.controller.AmbariManagementControllerImpl.createConfiguration(AmbariManagementControllerImpl.java:754)
>         at org.apache.ambari.server.controller.AmbariManagementControllerImpl.updateCluster(AmbariManagementControllerImpl.java:1477)
>         at org.apache.ambari.server.controller.AmbariManagementControllerImpl.updateClusters(AmbariManagementControllerImpl.java:1337)
>         at org.apache.ambari.server.topology.AmbariContext$5.call(AmbariContext.java:384)
>         at org.apache.ambari.server.utils.RetryHelper.executeWithRetry(RetryHelper.java:95)
>         ... 12 more
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message