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 1687775

Summary:	[RFE] allow configurable logging levels during startup of openvswich
Product:	Red Hat Enterprise Linux Fast Datapath	Reporter:	Timothy Redaelli <tredaelli>
Component:	openvswitch2.11	Assignee:	Timothy Redaelli <tredaelli>
Status:	CLOSED ERRATA	QA Contact:	Rick Alongi <ralongi>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	FDP 19.B	CC:	ctrautma, jhsiao, kfida, pvauter, ralongi, tli
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openvswitch2.11-2.11.0-3.el7fdn	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-04-23 08:26:35 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Timothy Redaelli 2019-03-12 11:08:32 UTC

This bug was initially created as a copy of Bug #1664794

I am copying this bug because: 
It's also needed on OVS2.11


Description of problem:
The logging levels are hard coded in ovs-ctl but should be user configurable to enable additional log details during startup. 

Version-Release number of selected component (if applicable):
Currently working with openvswitch-2.9.0-56.el7fdp.x86_64


How reproducible:
100%


Steps to Reproduce:
1. attempt to enable non-default logging
2.
3.

Actual results:


Expected results:


Additional info:

Comment 7 errata-xmlrpc 2019-04-23 08:26:35 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:0799