networking-sfc doesn't change table flows after vnf has been migrated

Bug #1781696 reported by TianZhang He
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tacker
Won't Fix
Undecided
Unassigned

Bug Description

Start with:
VNFFG/SFC: Client->VNF1->Server in one compute node (compute0)

nova live-migration --block-migrate $VDU-name-of-VNF1 $dst_node

After Live migration VNF1 from compute0 to compute1:
VNFFG/SFC: Client(compute0)->VNF1(compute1)->Server(compute0)

The port chain created by Tacker by using networking-sfc is not updated as checking the flow tables in br-int. Therefore, the VNFFG is broken.

Version: Ocata
openstack-tacker.noarch 0.7.0-1.el7 @centos-openstack-ocata
python2-networking-sfc.noarch 4.0.0-1.el7 @centos-openstack-ocata

Revision history for this message
Cong Phuoc Hoang (hoangphuoc) wrote :

I don't think we can do it now. You can do it with these steps: delete VNFFG --> migrate VNFs --> re-create VNFFG.

Yasufumi Ogawa (yasufum)
Changed in tacker:
status: New → Won't Fix
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.