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 1978719

Summary:	[RFE][ovn-controller] Document and propagate one external_id key from LSP/Port_Binding to OVS interface.
Product:	Red Hat Enterprise Linux Fast Datapath	Reporter:	Dumitru Ceara <dceara>
Component:	OVN	Assignee:	OVN Team <ovnteam>
Status:	CLOSED DUPLICATE	QA Contact:	Jianlin Shi <jishi>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	FDP 20.H	CC:	ctrautma, dcbw, jiji
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-08-30 07:55:47 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:

Description Dumitru Ceara 2021-07-02 14:58:33 UTC

Description of problem:

For the purpose of making the CMS's life easier, it would help if a specific NB.Logical_Switch_Port.external_ids key, e.g., "ovn-cms-options", would be propagated by OVN to the OVS Interface record of the interface that actually binds that logical port.

Today, ovn-northd already propagates all external IDs from NB.Logical_Switch_Port.external_ids to SB.Port_Binding.external_ids.

The missing part is ovn-controller to propagate one Port_Binding external_id, e.g., "ovn-cms-options", to the OVS Interface that binds it.

Comment 1 Dumitru Ceara 2021-08-30 07:55:47 UTC

This has been taken care of through bug 1995333.

*** This bug has been marked as a duplicate of bug 1995333 ***