lbaas: vip's fip ref is not set on si vmis

Bug #1501020 reported by Senthilnathan Murugappan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R2.20
Won't Fix
High
Rudra Rugge
Trunk
Fix Committed
High
Rudra Rugge

Bug Description

Was creating lbaas instances in a loop and observed that occasionally the fip on vip is not referenced in the vmis of the netns vm's
Hence the route for the fip is not updated.

Tags: config lbaas
tags: added: config
Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] master

Review in progress for https://review.opencontrail.org/14500
Submitter: Rudra Rugge (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : A change has been merged

Reviewed: https://review.opencontrail.org/14500
Committed: http://github.org/Juniper/contrail-controller/commit/33eb33df8d77937f8f8b16143a8cffe89480f3b9
Submitter: Zuul
Branch: master

commit 33eb33df8d77937f8f8b16143a8cffe89480f3b9
Author: Rudra Rugge <email address hidden>
Date: Fri Oct 16 14:25:00 2015 -0700

Floating-IP not set for LB VMs

Intermittently floating ip is not carried over from VIP
to the netns virtual machine interfaces. This is caused
when floating ip is configured on the VIP and the db messages
come out of order for service instance and floating ip.

Add code to handle fip to vmi association during launch of
service netns vm in addition to the specifiec fip handling
that already exists.

Change-Id: I73dbf1775e46f0f85fcdb293784d42e75384905c
Closes-Bug: #1501020

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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