Cisco Bug: CSCvt48894 - AA: ESC service can fail to go operational after performing escadm stop then start
Jun 01, 2020
- Cisco Elastic Services Controller
Known Affected Releases
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)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases