Guest

Preview Tool

Cisco Bug: CSCvt48894 - AA: ESC service can fail to go operational after performing escadm stop then start

Last Modified

Jun 01, 2020

Products (1)

  • Cisco Elastic Services Controller

Known Affected Releases

5.0 5.1

Description (partial)

Symptom:
Performing escadm stop then start on an AA node (e.g. as required to latch an ESC configuration change) can result in an ESC manager startup failure.  The deadlock is a result of the ESC HA monitoring service (elector) failing to be stopped when escadm stop is initiated which is then causing the ESC startup flow to lock.

Conditions:
Any ESC maintenance/configuration operation that requires escadm stop/start to apply.  In incidence of the deadlock can increase if stop/start is performed simultaneously on multiple AA cluster nodes.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.