You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened?
Unable to get klog.V(x) logs from k8s.io/mount-utils even cli flag --v=5 is set.
What you expected to happen?
After setting --v=5 logs we should be able to see all V(x) logs from k8s.io/mount-utils.
How to reproduce it (as minimally and precisely as possible)?
Modify the ebs-csi-node daemonset, for the ebs-plugin container change/add cli flag --v=5, wait until all ebs-csi-node pods are restarted.
Restart a deployment (or statefulset) which mounting an ebs volume through the csi driver.
Find the ebs-csi-node pod on the same node of the pod from previous step, check its ebs-plugin container logs, cannot find any V(x) logs from k8s.io/mount-utils.
Anything else we need to know?:
In cmd/options.go, it is initialized with klog but k8s.io/mount-utils uses klog/v2, I am not an expect but doesn't that mean klog/v2 is not initialized and the level is the default value (0) even cli flag --v=5 is set?
Environment
Kubernetes version (use kubectl version): v1.20
Driver version: v1.9.0
The text was updated successfully, but these errors were encountered:
/kind bug
What happened?
Unable to get klog.V(x) logs from k8s.io/mount-utils even cli flag
--v=5
is set.What you expected to happen?
After setting
--v=5
logs we should be able to see all V(x) logs from k8s.io/mount-utils.How to reproduce it (as minimally and precisely as possible)?
--v=5
, wait until all ebs-csi-node pods are restarted.Anything else we need to know?:
In cmd/options.go, it is initialized with klog but k8s.io/mount-utils uses klog/v2, I am not an expect but doesn't that mean klog/v2 is not initialized and the level is the default value (0) even cli flag
--v=5
is set?Environment
kubectl version
): v1.20The text was updated successfully, but these errors were encountered: