Preview Tool

Cisco Bug: CSCus89273 - EASService doesn't fail when ECSnode pubsub is not created

Last Modified

Jun 08, 2017

Products (1)

  • Headend System Releases

Known Affected Releases


Description (partial)

EASService did not fail when ECSnode pubsub is not created

1. ECSnode is not created. Because AlertManager was not installed or because the "Create a pubsub node for ECS" was not set to yes when AlertManager was installed
2. Install EASService. It goes In Service without complaining about ECSnode. It should have gone Out Of Service
Bug details contain sensitive information and therefore require a 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.