Bug 2002713 - CNO: OVN logs should have millisecond resolution
Summary: CNO: OVN logs should have millisecond resolution
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.9
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.10.0
Assignee: Christoph Stäbler
QA Contact: Anurag saxena
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-09 14:54 UTC by Ilya Maximets
Modified: 2022-03-12 04:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-12 04:38:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-network-operator pull 1196 0 None Draft Bug 2002713: Add millisecond resolution to OVN logs 2021-09-13 18:37:18 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-12 04:38:28 UTC

Description Ilya Maximets 2021-09-09 14:54:26 UTC
Currently OVN databases and ovn-northd are started with
'-vconsole:${OVN_LOG_LEVEL} -vfile:off'.  This means that logs are going only
to the console.  But console (unlike files) has no millisecond resolution by
default.  This makes it hard to debug time-sensitive issues.

'-vPATTERN:console:%D{%Y-%m-%dT%H:%M:%S.###Z}|%05N|%c%T|%p|%m' should be added
to the command line in order to have milliseconds printed to the console log.

Comment 6 errata-xmlrpc 2022-03-12 04:38:07 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 (Moderate: OpenShift Container Platform 4.10.3 security update), 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/RHSA-2022:0056


Note You need to log in before you can comment on or make changes to this bug.