Guest

Preview Tool

Cisco Bug: CSCvt01476 - ISSM 19.3 to 19.5: lb01 and lb02 /etc/hosts pointing to wrong installer ip

Last Modified

May 26, 2020

Products (1)

  • Cisco Policy Suite for Mobile

Known Affected Releases

19.5.1

Description (partial)

Customer using two cluster manager approach during ISSM. As both  cluster manager have different IPs. so post deployment of LB VMs it contains correct installer IP but when execute the step enable set, then it copies the backed up /etc/hosts file during disable set to LB VMs. As the older /etc/hosts  containing the installer ip of older cluman so LB VMs were pointing to older installer and after enable set step completed.

Symptom:
Customer using two cluster manager approach during ISSM. As both  cluster manager have different IPs. so post deployment of LB VMs it contains correct installer IP but when execute the step enable set, then it copies the backed up /etc/hosts file during disable set to LB VMs. As the older /etc/hosts  containing the installer ip of older cluman so LB VMs were pointing to older installer and after enable set step completed.

Conditions:
RCA - Customer using two cluster manager approach during ISSM. As both  cluster manager have different IPs. so post deployment of LB VMs it contains correct installer IP but when execute the step enable set, then it copies the backed up /etc/hosts file during disable set to LB VMs. As the older /etc/hosts  containing the installer ip of older cluman so LB VMs were pointing to older installer and after enable set step completed.

Fix - Removed the code to backup and restore the /etc/hosts file during disable and enable set step.

Test - Execute disable set and enable set step and found that it does not create hosts file in backup tar and enable set step does not throw any error for the file not found.
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.