Comment 5 for bug 1836701

From a machine with actual ipmi support:
$ lsmod | grep ipmi
ipmi_ssif 36864 0
ipmi_si 65536 0
ipmi_devintf 20480 0
ipmi_msghandler 106496 3 ipmi_devintf,ipmi_si,ipmi_ssif

$ ll /dev/ipmi0 /dev/ipmi/0 /dev/ipmidev/0
ls: cannot access '/dev/ipmi/0': No such file or directory
ls: cannot access '/dev/ipmidev/0': No such file or directory
crw------- 1 root root 238, 0 Aug 24 06:27 /dev/ipmi0

$ sudo ipmitool lan print
Set in Progress : Set Complete
Auth Type Support :
Auth Type Enable : Callback :
...

But as one would expect without sudo:
$ ipmitool lan print
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory

But the same also triggers on systems without ipmi (obviously).
So when I run it in a container or VM for example.

So we now know this can happen:
a) without root permissions (user error)
b) on a system without ipmi (well, that is ok then)
c) odd error we need to find (this would be worth to debug).

Does your kernel create and populate any of these?
$ ls -laF /dev/ipmi0 /dev/ipmi/0 /dev/ipmidev/0
And which modules are loaded?
$ lsmod | grep ipmi

Adding a kernel task for your reply to be seen there