Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
The FDP team is no longer accepting new bugs in Bugzilla. Please report your issues under FDP project in Jira. Thanks.

Bug 2108614

Summary: Logical switch port types 'localnet' and 'l2gateway' are not accessible through other ports on the switch
Product: Red Hat Enterprise Linux Fast Datapath Reporter: Ehsan Elahi <eelahi>
Component: OVNAssignee: OVN Team <ovnteam>
Status: CLOSED NOTABUG QA Contact: Ehsan Elahi <eelahi>
Severity: high Docs Contact:
Priority: high    
Version: FDP 22.FCC: ctrautma, jiji, mmichels, nusiddiq
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-08-16 14:57:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2066261    

Comment 1 Mark Michelson 2022-07-22 13:38:58 UTC
Hi Ehsan, is this a regression, or is this a new test that QE has written?

Comment 2 Ehsan Elahi 2022-07-25 10:10:01 UTC
(In reply to Mark Michelson from comment #1)
> Hi Ehsan, is this a regression, or is this a new test that QE has written?

It's a regression, Mark. This test has been part of QE coverage since ovn-2021-21.06.0-17.el8fdp. No issue was seen in ovn2.13-20.12.0-195.el8fdp. It was also OK before ovn-2021-21.12.0-30.el8fdp.x86_64.

Comment 3 Numan Siddique 2022-08-11 03:48:58 UTC
I don't think this is a bug.

localnet and l2gateway ports are not VIF ports.  They can't be associated to a VM/container/ovs port etc.
If you see the ovn-controller logs,  it will not claim sw0-lp if its type is localnet and l2gateway.
When you set the type to "",  it is claimed by ovn-controller.  It is working as expected.

Maybe it was a bug earlier and now it seems to be fixed.

Comment 4 Mark Michelson 2022-08-16 14:57:34 UTC
Based on Numan's comments, I think this is not a bug, so I am closing the issue.