amarnath reddy pappu created AMBARI-23057:
---------------------------------------------
Summary: Upgrade fails because of Stale alert definitions.
Key: AMBARI-23057
URL: https://issues.apache.org/jira/browse/AMBARI-23057
Project: Ambari
Issue Type: Bug
Components: ambari-upgrade
Affects Versions: 2.6.0
Reporter: amarnath reddy pappu
Upgrade fails with below exception
{noformat}
06 Nov 2017 04:31:26,826 ERROR [main] SchemaUpgradeHelper:437 - Exception
occurred during upgrade, failed
org.apache.ambari.server.AmbariException: Service not found,
clusterName=usldwdevhdp, 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=usldwdevhdp, 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)
{noformat}
few customer are reporting this problem -reporting these stale alert
definitions in DBConsistency check would avoid upgrade failures.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
