Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error on Inbound routing entry create on BMv2; P4 #345

Closed
aputriax opened this issue Feb 17, 2023 · 11 comments
Closed

Error on Inbound routing entry create on BMv2; P4 #345

aputriax opened this issue Feb 17, 2023 · 11 comments
Assignees
Labels
bug Something isn't working

Comments

@aputriax
Copy link
Collaborator

There is an error on inbound routing create on BMv2:
[bmv2] [E] [thread 15] [P4Runtime] Invalid match type

This behavior is introduced by PR #194.
And after a closer look at this PR we found one more issue:
In the pipeline, inbound_routing is applied right after choosing a direction with direction_lookup. We don’t have any ENI associated with the packet at this stage. And the packet eventually would be dropped, no matter what we configured.

In the main branch all inbound related tests are disabled. So I've created a branch for reproducing this issue. It contains a single extra test module - DASH/test/test-cases/functional/ptf/saidasheni_in.py. Here is the link. Use standard procedure to run the tests. But instead of make run-all-tests do the following:

make run-saithrift-client-bash
cd functional/ptf
ptf --test-dir . --pypath /SAI/ptf --interface 0@veth1 --interface 1@veth3 saidasheni_in

In the switch tab you'll see the error I mentioned:
[04:57:51.621] [bmv2] [E] [thread 17] [P4Runtime] Invalid match type

NOTE: This issue is opened as a follow up for the Issue #233

@chrispsommers
Copy link
Collaborator

@marian-pritsak Can you provide an explanation for this error and is there a work item or potential remedy? it breaks test cases and we have to skip them. Thanks.

@chrispsommers
Copy link
Collaborator

@marian-pritsak Didn't you fix this in a PR?

@KrisNey-MSFT
Copy link
Collaborator

Hi @r12f - given our Inbound Routing convo recently, is this one still an issue?
TY, Kristina

@KrisNey-MSFT
Copy link
Collaborator

Discuss w/Community whether this is still a problem. Originally from PLVision; @ashutosh-agrawal do you guys still want to own this Issue?

@ashutosh-agrawal
Copy link
Collaborator

@KrisNey-MSFT I'll take a look at this issue in the next couple of days and will get back to you.

@KrisNey-MSFT
Copy link
Collaborator

@KrisNey-MSFT I'll take a look at this issue in the next couple of days and will get back to you.

thank you!

@KrisNey-MSFT
Copy link
Collaborator

still needed; bug in P4 code

@KrisNey-MSFT KrisNey-MSFT added the bug Something isn't working label Mar 1, 2024
@ashutosh-agrawal
Copy link
Collaborator

I ran this test yesterday and the P4 issue is fixed but the test is still failing. I fixed some initial issues, but it needs further debugging. @KrisNey-MSFT You can assign this issue to me.

@KrisNey-MSFT KrisNey-MSFT changed the title Error on Inbound routing entry create on BMv2 Error on Inbound routing entry create on BMv2; P4 Mar 4, 2024
@ashutosh-agrawal
Copy link
Collaborator

Opened this PR that fixes the issue with programming of inbound routing table.

@KrisNey-MSFT
Copy link
Collaborator

Opened this PR that fixes the issue with programming of inbound routing table.

So ok to close this one @ashutosh-agrawal ?

@ashutosh-agrawal
Copy link
Collaborator

My PR #534 fixed this issue for tests in saidasheni.py and PR #545 will take of remaining tests in saidashvnet.py. I think we can close it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants