Cisco Bug: CSCvs66486 - Service stuck in INERT state when recovery attempted downstream up update and failover
May 31, 2020
- Cisco Elastic Services Controller
Known Affected Releases
Symptom: After recovery, Service is stuck in SERVICE_INERT State Conditions: The following work-flow can latch this condition: - ESC HA deployment - Service deployed and in-service - Service update is performed - ESC failover - Service recovery is performed. Recovery is successful, but service latches INERT state. - At this point further service operations initiated from the NB interface (e.g. update or recovery) will fail. Automated recovery procedures performed by ESC will continue to function successfully.
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