Bug 2105257 - Can't set log verbosity level for virt-operator pod
Summary: Can't set log verbosity level for virt-operator pod
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Virtualization
Version: 4.11.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.12.0
Assignee: Itamar Holder
QA Contact: zhe peng
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-08 11:21 UTC by zhe peng
Modified: 2023-01-24 13:39 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-01-24 13:37:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CNV-19727 0 None None None 2022-12-15 08:43:13 UTC
Red Hat Product Errata RHSA-2023:0408 0 None None None 2023-01-24 13:39:23 UTC

Description zhe peng 2022-07-08 11:21:37 UTC
Description of problem:
Can't set log verbosity level for virt-operator pod

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

How reproducible:
always

Steps to Reproduce:
1.set log verbosity in HCO 
spec:
  logVerbosityConfig:
    kubevirt:
      virtOperator: 8
      
2.check virt-operator pods
$ oc logs virt-operator-cf86f858d-bwfsm | grep verbosity
$(no output)

Actual results:
no output

Expected results:
should like other virt components pods
$oc logs virt-controller-5d5bf5f97-ls5wx| grep verbosity
{"component":"virt-controller","level":"info","msg":"set log verbosity to 2","pos":"application.go:405","timestamp":"2022-07-06T02:53:46.5414

Additional info:

Comment 1 Kedar Bidarkar 2022-07-12 16:02:22 UTC
For reference, https://kubevirt.io/api-reference/master/definitions.html#_v1_logverbosity

Comment 2 Kedar Bidarkar 2022-07-13 12:04:47 UTC
We need the following info:
1) HCO CR
2) KV CR
3) virt-operator deployment manifest.

Comment 6 Itamar Holder 2022-09-15 16:33:08 UTC
Kubevirt PR: https://github.com/kubevirt/kubevirt/pull/8476

Comment 7 Itamar Holder 2022-09-21 07:31:23 UTC
PR merged upstream

Comment 8 zhe peng 2022-10-17 06:23:12 UTC
verify with build:
v4.12.0-585

step:
1.set log verbosity in HCO cr
....
spec:
  logVerbosityConfig:
    kubevirt:
      virtOperator: 8
....

2. check two operator pod's log
$ oc logs virt-operator-69ff4ffc96-r6p49 -n openshift-cnv| grep verbosity
{"component":"virt-operator","level":"info","msg":"set log verbosity to 8","pos":"application.go:459","timestamp":"2022-10-17T06:17:42.925115Z"}
$ oc logs virt-operator-69ff4ffc96-t7h9m -n openshift-cnv | grep verbosity
{"component":"virt-operator","level":"info","msg":"set log verbosity to 8","pos":"application.go:459","timestamp":"2022-10-17T06:17:42.925233Z"}

move to verified.

Comment 12 errata-xmlrpc 2023-01-24 13:37:46 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 (Important: OpenShift Virtualization 4.12.0 Images 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-2023:0408


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