[NETVIRT-284] missing Napt rules as part of ovs restart Created: 21/Nov/16  Updated: 19/Oct/17  Resolved: 11/Dec/16

Status: Resolved
Project: netvirt
Component/s: General
Affects Version/s: Boron
Fix Version/s: None

Type: Bug
Reporter: zan cohen Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Attachments: Text File Report.txt     Text File after_restart.txt     Text File before_restart.txt    
External issue ID: 7213

 Description   

Description:
************
1.Load Devstuck setup(no vm's configure).
2.Dump controler+compute ovs pipeline to file.(see before_restart.txt file).
3.ovs-restart
3.Dump controler+compute ovs pipeline to file.(see after_restart.txt file).

Defect
******
Diff for both before and after ovs restart there are 2 missing rules(see comparison file):

Missing rule 1:
***************
table=21 priority=42 ip metadata=0x222e2/0xfffffffe nw_dst=10.64.200.10 actions=goto_table:44

implication:10.64.200.10 is router ip.in case of this rule missing,traffic that came from Napt will be broken.
___________________________________________________________________________
Missing rule 2:
***************
table=26 priority=5 ip metadata=0x222e0/0xfffffffe actions=goto_table:46

implication:in case of this rule missing,Traffic to internet without fip is broken.



 Comments   
Comment by zan cohen [ 21/Nov/16 ]

Attachment before_restart.txt has been added with description: Pipe_line before_ovs restart

Comment by zan cohen [ 21/Nov/16 ]

Attachment after_restart.txt has been added with description: Pipe_line after_ovs restart

Comment by zan cohen [ 21/Nov/16 ]

Attachment Report.txt has been added with description: Diff before and after ovs restart

Comment by Olga Schukin [ 11/Dec/16 ]

I think it was fixed recently, I can't reproduce this issue.
Zan,
if this still reoccur, please reopen the bug.

Generated at Wed Feb 07 20:21:10 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.