[NETVIRT-113] Tunnel Flow Entry Failed to be added in one compute Node leading to VM instance Ping Failure Created: 31/Aug/16  Updated: 09/Mar/18  Resolved: 19/Sep/16

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

Type: Bug
Reporter: Venkatrangan Govindarajan Assignee: Bertrand Low
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: Zip Archive log.zip     Zip Archive odl1_karaf.zip     Zip Archive odl2_karaf.zip     Zip Archive odl3_karaf.zip    
External issue ID: 6601
Priority: High

 Description   

The CSIT jobs for clustering (L2) failed in one ping for one of the instances. When we analyzed the flow entries observed that the tunnel entry to reach sone instance was not getting added in one of the compute nodes.

Tunnel Flow entries are added to table:110 termed as Unicast entries per VM instance.

 Comments   
Comment by Venkatrangan Govindarajan [ 31/Aug/16 ]

Attachment log.zip has been added with description: Log.html from the sandbox run

Comment by Venkatrangan Govindarajan [ 31/Aug/16 ]

Attachment odl1_karaf.zip has been added with description: ODL1 Logs

Comment by Venkatrangan Govindarajan [ 31/Aug/16 ]

Attachment odl2_karaf.zip has been added with description: ODL2 Logs

Comment by Venkatrangan Govindarajan [ 31/Aug/16 ]

Attachment odl3_karaf.zip has been added with description: ODL3 Logs

Comment by Venkatrangan Govindarajan [ 31/Aug/16 ]

the log.html added is a unique one which records the flow entries in all the openstack nodes. the setup had 3 Openstack nodes. one control and 2 compute nodes. the VM's always get created in only the compute nodes.

Please let me know if any other explanation is needed on this bug.

Comment by Bertrand Low [ 16/Sep/16 ]

This bug is not reproducible. The attached logs from the sandbox run show that in the non-failover L2 tests, the VMs can be pinged but ssh does not work. This could indicate some temporary network issues that occurred during this particular sandbox run.

The logs do not conclusively indicate a root cause.

Closed due to bug not being reproducible and attached-logs being inconclusive.

Comment by Ravit Peretz [ 18/Sep/16 ]

This issue was fixed in https://bugs.opendaylight.org/show_bug.cgi?id=6666

Comment by Hideyuki Tai [ 18/Sep/16 ]

The NETVIRT-123 and the patch for the NETVIRT-123 is about new NetVirt. On the other hand, this bug report (NETVIRT-113) is about the Legacy NetVirt. Therefore, I don't think this bug is a duplicate of NETVIRT-123. So I've reverted the Resolution from DUPLICATE to WORKSFORME.

Comment by Ravit Peretz [ 19/Sep/16 ]

This update was done as a result of the link between the bugs..
It shouldn't have affect this ticket.

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