Juniper Openstack

SNAT traffic does not go through on a series of compute node reboots

Bug #1398116 reported by Rudra Rugge on 2014-12-01

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Juniper Openstack	Fix Committed	Critical	Nipa	Juniper Openstack r2.1-fcs
	R2.0	Fix Committed	Undecided	Nipa	Juniper Openstack r2.0-fcs

Bug Description

SNAT traffic does not go through if compute nodes hosting the netns are rebooted. It causes ECMP routes to be created since control node still holds on to the old VM links for netns.

Tags:

Rudra Rugge (rrugge) on 2014-12-01

Changed in juniperopenstack:
milestone:	none → r2.0-fcs
importance:	Undecided → Critical
tags:	added: blocker
Changed in juniperopenstack:
assignee:	nobody → Nipa (nipak)

Ashish Ranjan (aranjan-n) on 2014-12-02

information type:

Proprietary → Public

Nagabhushana R (bhushana) on 2014-12-03

tags:

added: vrouter

Revision history for this message

Nipa (nipak) wrote on 2014-12-03:

commit 974a6cfc93e6edba4608d2a6c28b1936cc5d087d
Author: Nipa Kumar <email address hidden>
Date: Mon Dec 1 15:19:49 2014 -0800

Nipa (nipak) on 2014-12-04

Changed in juniperopenstack:
status:	New → Fix Committed

OpenContrail Admin (ci-admin-f) on 2014-12-04

Changed in juniperopenstack:
milestone:	r2.0-fcs → r2.1-fcs

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.