5.2.4.2 SEPPUpgradeFailedAlert

Table 5-31 SEPPUpgradeFailedAlert

Field Details
Trigger Condition Rest API trigger at failure of Upgrade
Severity NA
Alert details provided

applicationname

alertname

servicename

releasename

namespace

oid

severity

vendor

sourcerelease

targetrelease
OID 1.3.6.1.4.1.323.5.3.46.1.2.8002
Metric Used NA
Resolution

If a success alert is generated then start and failure alerts will be cleared.

Possible resolutions:
  1. Check the pre or post upgrade logs in Kibana to analyze the cause of failure.
  2. Filter the upgrade logs using the pod name filter. Example: ocsepp-release-update-db.
  3. If the cause of upgrade failure is database or network connectivity issue, contact the system administrator.
  4. If the upgrade failure occurs during the preupgrade phase, resolve the issue, then perform an upgrade. Do not perform rollback because SEPP deployment remains in the source or older release.
  5. If the upgrade failure occurs during the postupgrade phase, for example, post upgrade hook failure due to target release pod not moving to ready state, then perform a rollback.