Salt-minion/salt-call on OSX generate stack traces upon start/usage #4327

Closed
cmeisinger opened this Issue Mar 30, 2013 · 2 comments

Comments

Projects
None yet
2 participants

I've installed salt-minion on OSX 10.8.3, and I am using it to exec commands in a peer to peer setup. Upon initial startup of salt-minion, the following trace is generated, it should be noted though, that the salt-minion appears to work and has no connectivity issues with the master.

chrism:salt root# /usr/local/share/python/salt-minion         
[WARNING ] Both 'dmidecode' and 'lspci' failed to execute, either because they do not exist on the system of the   user running this instance does not have the necessary permissions to execute them. Grains output might not be accurate.
[CRITICAL] Failed to load grains defined in grain file core.ip4 in function <function ip4 at 0x109ecd230>, error:
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/site-packages/salt/loader.py", line 787, in gen_grains
    ret = fun()
  File "/usr/local/lib/python2.7/site-packages/salt/grains/core.py", line 747, in ip4
    ips = salt.utils.socket_util.ip4_addrs()
  File "/usr/local/lib/python2.7/site-packages/salt/utils/socket_util.py", line 307, in ip4_addrs  
ifaces = interfaces()
  File "/usr/local/lib/python2.7/site-packages/salt/utils/socket_util.py", line 298, in interfaces
    ifaces = _interfaces_ifconfig(cmd)
NameError: global name 'cmd' is not defined

Execing calls to other peers yield the exact same trace (although the calls do succeed).

Owner

thatch45 commented Apr 1, 2013

Thanks for the heads up, this should be an easy fix!

Owner

thatch45 commented Apr 23, 2013

fixed in 0119a55

thatch45 closed this Apr 23, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment