What happened?
We see errors from ebs-plugin after enabling EBS detailed metrics(.node.enableMetrics) via Helm chart. The device /dev/nvme1n1 in the log below is actually an instance storage device, which we use Local Persistence Volume Static Provisioner to create PV from local disk(s).
ebs-plugin E1120 06:33:26.589419 1 nvme.go:194] Error collecting metrics for device /dev/nvme1n1: getNVMEMetrics: error reading log page nvmeReadLogPage: ioctl command failed with status 8457 │
│ ebs-plugin E1120 06:33:41.589690 1 nvme.go:194] Error collecting metrics for device /dev/nvme1n1: getNVMEMetrics: error reading log page nvmeReadLogPage: ioctl command failed with status 8457 ││ ebs-plugin E1120 06:33:56.589671 1 nvme.go:194] Error collecting metrics for device /dev/nvme1n1: getNVMEMetrics: error reading log page nvmeReadLogPage: ioctl command failed with status 8457 │
│ ebs-plugin E1120 06:34:11.588992 1 nvme.go:194] Error collecting metrics for device /dev/nvme1n1: getNVMEMetrics: error reading log page nvmeReadLogPage: ioctl command failed with status 8457 ││ ebs-plugin E1120 06:34:26.589688 1 nvme.go:194] Error collecting metrics for device /dev/nvme1n1: getNVMEMetrics: error reading log page nvmeReadLogPage: ioctl command failed with status 8457 │
│ ebs-plugin E1120 06:34:41.589761 1 nvme.go:194] Error collecting metrics for device /dev/nvme1n1: getNVMEMetrics: error reading log page nvmeReadLogPage: ioctl command failed with status 8457
What you expected to happen?
We should not see this error or we should bypass instance storage device.
How to reproduce it (as minimally and precisely as possible)?
/kind bug
What happened? We see errors from ebs-plugin after enabling EBS detailed metrics(
.node.enableMetrics
) via Helm chart. The device/dev/nvme1n1
in the log below is actually an instance storage device, which we use Local Persistence Volume Static Provisioner to create PV from local disk(s).What you expected to happen? We should not see this error or we should bypass instance storage device.
How to reproduce it (as minimally and precisely as possible)?
Anything else we need to know?:
Environment
kubectl version
): 1.30