jiocloud-devops team mailing list archive

[Launchpad Bug Tracker <1449422@xxxxxxxxxxxxxxxxxx>]

Mayank Kapoor (mayankkapoor) has assigned this bug to you for Jio:

Symptoms:
- Monday 27/Apr/2015, 3 out of 10 internal floating IPs were not accessible.
- Amar observed all bad floating IPs were all on one node.
- He then created a new floating IP on that node A, and one on another node B.
- He found that floating IP on node A did not work. However, floating IP on node B worked.
- He has a plausible hypothesis that the vrouter on that node A is messed up. Recommended to restart vrouter service.
- After vrouter restart, the IPs were accessible again.

The node was cp-13.

** Affects: jio
     Importance: Critical
     Assignee: Reliance Jio DevOps (jiocloud-devops)
         Status: New


** Tags: build-failures network operational-issue
-- 
vrouter service went bad on a particular node
https://bugs.launchpad.net/bugs/1449422
You received this bug notification because you are a member of Reliance Jio DevOps, which is a bug assignee.