ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Nechiporenko (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-18895) Cluster install fails if user accidentally creates a config group
Date Tue, 15 Nov 2016 12:21:58 GMT

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

Oleg Nechiporenko updated AMBARI-18895:
---------------------------------------
    Attachment: AMBARI-18895.patch

> Cluster install fails if user accidentally creates a config group	
> ------------------------------------------------------------------
>
>                 Key: AMBARI-18895
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18895
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.4.0
>            Reporter: Oleg Nechiporenko
>            Assignee: Oleg Nechiporenko
>            Priority: Critical
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-18895.patch
>
>
> While installing a fresh cluster, a config group got created "accidentally" but no hosts
were associated with it.
> So, create the config group and save it but do not associate any hosts. 
> If you proceed, the install/start phase fails with the following:
> {code}
> org.apache.ambari.server.controller.spi.SystemException: An internal system exception
occurred: Config group not found, clusterName = c1, groupId = 1472253656242
> {code}
> Error in ambari server log:
> {code}
> 26 Aug 2016 23:22:30,473  INFO [ambari-client-thread-24] AbstractResourceProvider:377
- Component: ZOOKEEPER_SERVER, recovery_enabled from stack definition:false
> 26 Aug 2016 23:22:30,508 ERROR [ambari-client-thread-25] AbstractResourceProvider:343
- Caught AmbariException when modifying a resource
> org.apache.ambari.server.AmbariException: Config group not found, clusterName = c1, groupId
= 1472253656242
>         at org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider.updateConfigGroups(ConfigGroupResourceProvider.java:633)
>         at org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider.access$300(ConfigGroupResourceProvider.java:70)
>         at org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider$4.invoke(ConfigGroupResourceProvider.java:296)
>         at org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider$4.invoke(ConfigGroupResourceProvider.java:293)
>         at org.apache.ambari.server.controller.internal.AbstractResourceProvider.invokeWithRetry(AbstractResourceProvider.java:455)
>         at org.apache.ambari.server.controller.internal.AbstractResourceProvider.modifyResources(AbstractResourceProvider.java:336)
>         at org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider.updateResources(ConfigGroupResourceProvider.java:293)
>         at org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider.updateResourcesAuthorized(ConfigGroupResourceProvider.java:210)
>         at org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.updateResources(AbstractAuthorizedResourceProvider.java:301)
>         at org.apache.ambari.server.controller.internal.ClusterControllerImpl.updateResources(ClusterControllerImpl.java:319)
>         at org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.update(PersistenceManagerImpl.java:125)
>         at org.apache.ambari.server.api.handlers.UpdateHandler.persist(UpdateHandler.java:45)
>         at org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73)
> ...
> {code}



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

Mime
View raw message