jiocloud-devops team mailing list archive

Thread
Date

[Bug 1449422] Re: vrouter service went bad on a particular node

To: jiocloud-devops@xxxxxxxxxxxxxxxxxxx
From: Mayank Kapoor <mayankkapoormail@xxxxxxxxx>
Date: Tue, 26 May 2015 08:22:39 -0000
Reply-to: Bug 1449422 <1449422@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Changed in: jio
     Assignee: Mayank (talktomgoyal) => Reliance Jio DevOps (jiocloud-devops)

** Changed in: jio
       Status: New => In Progress

-- 
You received this bug notification because you are a member of Reliance
Jio DevOps, which is a bug assignee.
https://bugs.launchpad.net/bugs/1449422

Title:
  vrouter service went bad on a particular node

Status in Jio:
  In Progress

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/jio/+bug/1449422/+subscriptions