Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory #63195

Open
1 task done
j5k opened this issue Dec 5, 2022 · 3 comments
Labels
arch-linux affects this operating system Bug broken, incorrect, or confusing behavior needs-triage

Comments

@j5k
Copy link

j5k commented Dec 5, 2022

Description
Everytime I run salt, the following warning is shown:
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory

Setup
Salt is running on a Lenovo Thinkpad which apparently does not support IPMI

  • on-prem machine

Steps to Reproduce the behavior
Run salt-call state.highstate or any other call

Expected behavior
Not using ipmitool on systems which doesn't support it

Versions Report

salt --versions-report
Salt Version:
          Salt: 3005.1
 
Dependency Versions:
          cffi: 1.15.1
      cherrypy: Not Installed
      dateutil: Not Installed
     docker-py: Not Installed
         gitdb: Not Installed
     gitpython: Not Installed
        Jinja2: 3.1.2
       libgit2: Not Installed
      M2Crypto: 0.38.0
          Mako: Not Installed
       msgpack: 1.0.4
  msgpack-pure: Not Installed
  mysql-python: Not Installed
     pycparser: 2.21
      pycrypto: Not Installed
  pycryptodome: 3.12.0
        pygit2: Not Installed
        Python: 3.10.8 (main, Nov  1 2022, 14:18:21) [GCC 12.2.0]
  python-gnupg: Not Installed
        PyYAML: 6.0
         PyZMQ: 24.0.1
         smmap: Not Installed
       timelib: Not Installed
       Tornado: 4.5.3
           ZMQ: 4.3.4
 
System Versions:
          dist: arch
        locale: utf-8
       machine: x86_64
       release: 6.0.11-arch1-1
        system: Linux
       version: Arch Linux
@j5k j5k added Bug broken, incorrect, or confusing behavior needs-triage labels Dec 5, 2022
@OrangeDog
Copy link
Contributor

Can you show a full debug log with the warning?

@OrangeDog OrangeDog added the info-needed waiting for more info label Dec 5, 2022
@j5k
Copy link
Author

j5k commented Dec 5, 2022

(Sensitive data redacted with XXX)

# salt-call state.highstate --log-level=debug
/usr/lib/python3.10/site-packages/_distutils_hack/__init__.py:33: UserWarning: Setuptools is replacing distutils.
  warnings.warn("Setuptools is replacing distutils.")
[DEBUG   ] Reading configuration from /etc/salt/minion
[DEBUG   ] Using cached minion ID from /etc/salt/minion_id: XXX
[WARNING ] Insecure logging configuration detected! Sensitive data may be logged.
[DEBUG   ] Configuration file path: /etc/salt/minion
[DEBUG   ] Grains refresh requested. Refreshing grains.
[DEBUG   ] Reading configuration from /etc/salt/minion
[DEBUG   ] The functions from module 'XXX' are being loaded by dir() on the loaded module
[DEBUG   ] Failed to import grains XXX:
Traceback (most recent call last):
  File "/usr/lib/python3.10/site-packages/salt/loader/lazy.py", line 768, in _load_module
    mod = self.run(spec.loader.load_module)
  File "/usr/lib/python3.10/site-packages/salt/loader/lazy.py", line 1228, in run
    return self._last_context.run(self._run_as, _func_or_method, *args, **kwargs)
  File "/usr/lib/python3.10/site-packages/salt/loader/lazy.py", line 1243, in _run_as
    return _func_or_method(*args, **kwargs)
  File "<frozen importlib._bootstrap_external>", line 548, in _check_name_wrapper
  File "<frozen importlib._bootstrap_external>", line 1063, in load_module
  File "<frozen importlib._bootstrap_external>", line 888, in load_module
  File "<frozen importlib._bootstrap>", line 290, in _load_module_shim
  File "<frozen importlib._bootstrap>", line 719, in _load
  File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 883, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "/var/cache/salt/minion/extmods/grains/XXX.py", line 7, in <module>
    import pymysql
ModuleNotFoundError: No module named 'pymysql'
[DEBUG   ] The functions from module 'core' are being loaded by dir() on the loaded module
[DEBUG   ] The functions from module 'disks' are being loaded by dir() on the loaded module
[DEBUG   ] The functions from module 'extra' are being loaded by dir() on the loaded module
[DEBUG   ] The functions from module 'lvm' are being loaded by dir() on the loaded module
[DEBUG   ] The functions from module 'mdadm' are being loaded by dir() on the loaded module
[DEBUG   ] The functions from module 'minion_process' are being loaded by dir() on the loaded module
[DEBUG   ] The functions from module 'opts' are being loaded by dir() on the loaded module
[DEBUG   ] Override  __utils__: <module 'salt.loaded.int.grains.zfs' from '/usr/lib/python3.10/site-packages/salt/grains/zfs.py'>
[DEBUG   ] The functions from module 'zfs' are being loaded by dir() on the loaded module
[DEBUG   ] Unable to resolve address XXX: [Errno 1] Unknown host
[DEBUG   ] Elapsed time getting FQDNs: 0.04444527626037598 seconds
[DEBUG   ] Unable to derive osmajorrelease from osrelease_info '('Timestamp: 2022-12-05 08:44 | Kernel: 6', 0, 11)'. The osmajorrelease grain will not be set.
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory
[DEBUG   ] The functions from module 'zfs' are being loaded by dir() on the loaded module
[DEBUG   ] LazyLoaded zfs.is_supported
[DEBUG   ] Master URI: tcp://XXX:4506
[DEBUG   ] Master URI: tcp://XXX:4506
[DEBUG   ] Connecting to master. Attempt 1 of 1
[DEBUG   ] Master URI: tcp://XXX:4506
[DEBUG   ] Initializing new AsyncAuth for ('/etc/salt/pki/minion', 'XXX', 'tcp://XXX:4506')
[DEBUG   ] Generated random reconnect delay between '1000ms' and '11000ms' (1499)
[DEBUG   ] Setting zmq_reconnect_ivl to '1499ms'
...

ipmitool itself gives the same error:

# ipmitool
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory

@OrangeDog
Copy link
Contributor

OK, so it's not actually a warning, it's the raw output from the tool.
That should be captured properly and not just printed.

I don't see where it's called though...

@OrangeDog OrangeDog added arch-linux affects this operating system and removed info-needed waiting for more info labels Dec 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
arch-linux affects this operating system Bug broken, incorrect, or confusing behavior needs-triage
Projects
None yet
Development

No branches or pull requests

2 participants