Bug 1990534

Summary:	Can't specify log file for security group logging
Product:	Red Hat OpenStack	Reporter:	Alex Katz <akatz>
Component:	python-networking-ovn	Assignee:	OSP Team <rhos-maint>
Status:	CLOSED NOTABUG	QA Contact:	Eran Kuris <ekuris>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	16.2 (Train)	CC:	apevec, egarciar, gurpsing, jamsmith, jlibosva, lhh, lsvaty, majopela, mariel, mtomaska, rbruzzon, rhos-maint, scohen, tfreger
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---	Flags:	gurpsing: needinfo-
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Known Issue
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-04-17 15:04:39 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:	1619266

Description Alex Katz 2021-08-05 15:29:23 UTC

Description of problem:
In ml2/OVN security group logging feature there is no option to specify a logfile. All the logs will be written to the /var/log/containers/stdouts/ovn_controller.log file (in containerized deployment). There is such an option in ml2/OVS.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Ihar Hrachyshka 2021-10-06 21:23:44 UTC

This is not a feature for core OVN to implement. The log format is not standard anyway between networking drivers. I believe if we want to store the logs in a separate file, there should be a separate component (container?) that would process the ovn log file and filter out the messages that belong to SG logging. We discussed this matter with Daniel and we don't believe it's high priority. I'm lowering the priority here to reflect that.

Comment 3 Ihar Hrachyshka 2021-11-29 18:44:25 UTC

This bug won't be solved in python-networking-ovn / neutron / OVN. The option to choose log file location is driver specific in neutron, and OVN logs hits with standard OS mechanisms (syslog). If we are interested in driver agnostic way to extract SG logging messages, we'll need to add a new component to do that (perhaps also normalizing the messages to some defined format).

This bug should be reconsidered / moved to tripleo (?), if at all. Resetting the assignee / removing Triaged flag to repeat prioritization.

Comment 5 Jakub Libosvar 2021-11-30 14:33:34 UTC

Note that the file logging is a config option specific for OVS driver and is not backend agnostic nor part of the API - https://github.com/openstack/neutron/blob/master/neutron/services/logapi/drivers/openvswitch/ovs_firewall_log.py#L49

imho this is not a parity bug

Comment 23 Red Hat Bugzilla 2023-12-02 04:25:19 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days