[NETVIRT-223] Ping not working on ODL Boron SR1 when Application Coexistence is configured Created: 28/Oct/16  Updated: 09/Mar/18  Resolved: 01/Nov/16

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

Type: Bug
Reporter: Brady Johnson Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 7059
Priority: Highest

 Description   

We have just tested Boron SR1 in OPNFV with an SFC patch and we see the classifier flows appearing in table=11. However, the ping to VMs is not working (using floating IPs or even without floating IPs). I checked the flow tables in the compute and the controller (we are only trying with two nodes) and I am seeing this:

table=31, n_packets=202, n_bytes=18044, priority=0 actions=goto_table:32
table=32, n_packets=202, n_bytes=18044, priority=0 actions=resubmit(,39),resubmit(,40)
table=41, n_packets=0, n_bytes=0, priority=0 actions=goto_table:51

Table 39 and table 40 don’t exist. Looking at the table numbers, perhaps something breaks when applying the coexistence? I checked and the coexistence is active:

root@node-6:~# curl -u admin:admin -H 'Content-type: application/json' -X GET http://192.168.0.52:8181/restconf/config/netvirt-providers-config:netvirt-providers-config
{"netvirt-providers-config":{"table-offset":1}}

root@node-6:~# curl -u admin:admin -H 'Content-type: application/json' -X GET http://192.168.0.52:8181/restconf/config/sfc-of-renderer:sfc-of-renderer-config
{"sfc-of-renderer-config":

{"sfc-of-table-offset":150,"sfc-of-app-egress-table-offset":11}

}

 Comments   
Comment by Brady Johnson [ 28/Oct/16 ]

There are more comments in this email thread:

https://lists.opendaylight.org/pipermail/netvirt-dev/2016-October/001926.html

Comment by A H [ 30/Oct/16 ]

A patch was submitted to fix this bug in Boron SR1: https://git.opendaylight.org/gerrit/#/c/47746/

To better assess the impact of this bug and fix, could someone from your team please help us identify the following:
Regression: Is this bug a regression of functionality/performance/feature compared to Boron?
Severity: Could you elaborate on the severity of this bug? Is this a BLOCKER such that we cannot release Boron-SR1 without it? Is there a workaround such that we can write a release note?
Testing: Could you also elaborate on the testing of this patch? How extensively has this patch been tested? Is it covered by any unit tests or system tests?
Impact: Does this fix impact any dependent projects?

Comment by Sam Hague [ 30/Oct/16 ]

(In reply to A H from comment #2)
> A patch was submitted to fix this bug in Boron SR1:
> https://git.opendaylight.org/gerrit/#/c/47746/
>
> To better assess the impact of this bug and fix, could someone from your
> team please help us identify the following:
> Regression: Is this bug a regression of functionality/performance/feature
> compared to Boron?
This is a regression. When SFC is used there is an offset in the OpenFlow tables used to allow application coexistence. Recent changes to the pipeline did not account for the table offset.
> Severity: Could you elaborate on the severity of this bug? Is this a
> BLOCKER such that we cannot release Boron-SR1 without it?
It is a blocker in that SFC integration will not work. That also blocks opnfv.
Is there a
> workaround such that we can write a release note?
There is no workaround.
> Testing: Could you also elaborate on the testing of this patch? How
> extensively has this patch been tested? Is it covered by any unit tests or
> system tests?
The CSIT tests shows the proper pipeline accounting for the table offset.
> Impact: Does this fix impact any dependent projects?
Yes, it fixes the SFC integration.

Comment by Brady Johnson [ 30/Oct/16 ]

Fixed

Comment by A H [ 01/Nov/16 ]

Has this bug been verified as fixed in the latest Boron SR1 Build 20161030?

Comment by Venkatrangan Govindarajan [ 01/Nov/16 ]

(In reply to A H from comment #5)
> Has this bug been verified as fixed in the latest Boron SR1 Build 20161030?

yes, Just tested with offset:3
https://logs.opendaylight.org/sandbox/jenkins091/netvirt-csit-1node-openstack-mitaka-openstack-boron/14/archives/log.html.gz#s1-s1-s1

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