Excessive warnings about dmidecode not found from nvme backend

Bug #1812441 reported by Matt Riedemann
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
os-brick
New
Undecided
Unassigned

Bug Description

Seen all over the nova-compute logs:

http://logs.openstack.org/77/615677/20/check/tempest-full/a411aa1/controller/logs/screen-n-cpu.txt.gz?level=WARNING#_Jan_16_22_53_17_023562

Jan 16 22:53:17.023562 ubuntu-bionic-vexxhost-sjc1-0001754945 nova-compute[11622]: WARNING os_brick.initiator.connectors.nvme [None req-f4a2825e-4f39-4dda-9a78-28e111ea65cb tempest-AttachVolumeNegativeTest-133543851 tempest-AttachVolumeNegativeTest-133543851] Unable to locate dmidecode. For Cinder RSD Backend, please make sure it is installed: [Errno 2] No such file or directory
Jan 16 22:53:17.023562 ubuntu-bionic-vexxhost-sjc1-0001754945 nova-compute[11622]: Command: dmidecode
Jan 16 22:53:17.023562 ubuntu-bionic-vexxhost-sjc1-0001754945 nova-compute[11622]: Exit code: -
Jan 16 22:53:17.023562 ubuntu-bionic-vexxhost-sjc1-0001754945 nova-compute[11622]: Stdout: None
Jan 16 22:53:17.023562 ubuntu-bionic-vexxhost-sjc1-0001754945 nova-compute[11622]: Stderr: None: ProcessExecutionError: [Errno 2] No such file or directory

If you're not using this type of volume, we shouldn't warn about this all the time. Either warn once and cache per process or drop that down to a debug statement or something less annoying than constant warnings since they clutter up the logs.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.