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

Dmytro Grinenko updated AMBARI-22419:
-------------------------------------
    Attachment: AMBARI-22419.branch-2.6.patch

> Ambari upgrade failed
> ---------------------
>
>                 Key: AMBARI-22419
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22419
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-sever
>    Affects Versions: 2.6.0
>            Reporter: amarnath reddy pappu
>            Assignee: Dmytro Grinenko
>             Fix For: 2.6.2
>
>         Attachments: AMBARI-22419.branch-2.6.patch
>
>
> Ambari upgrade would fail during the DMLStatements execution if there is no 
> service definition in the stacks.
> For example: Customer database has entry for GANGLIA in alert_definition 
> table but there is no stack definition - hence its getting failed with below 
> exception.
> {noformat}
> org.apache.ambari.server.AmbariException: Service not found, 
> clusterName=comcastdrcluster, serviceName=GANGLIA 
> at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:234)
>  
> at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:424)
>  
> Caused by: org.apache.ambari.server.ServiceNotFoundException: Service not 
> found, clusterName=comcastdrcluster, serviceName=GANGLIA 
> at 
> org.apache.ambari.server.state.cluster.ClusterImpl.getService(ClusterImpl.java:864)
>  
> at 
> org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1240)
>  
> at 
> org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46)
>  
> at 
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:938)
>  
> at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:231)
>  
> ... 1 more
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to