-
Notifications
You must be signed in to change notification settings - Fork 35
Issue when starting salt-master and minion after switching to RAET #67
Comments
Thats what it looks like for the string .decode method. Changed in version 2.7: Support for keyword arguments added. |
Removed that argument, and master now stays running, but now the minions keep crashing with this stack trace: Process Process-1: |
Anyone have any insight? |
Hi, It seemed that I have install the last salt 2016.3.4 with RAET enabled.
In this issue it show it has been fix ? saltstack/salt#25858
This is my
|
|
I've got all the dependencies installed added RAET transport to the master and minion configs. When I try to restart both the salt-minion and master, it crashes and I get this stack trace:
Traceback (most recent call last):
File "/usr/bin/salt-call", line 11, in
salt_call()
File "/usr/lib/python2.6/site-packages/salt/scripts.py", line 227, in salt_call
client.run()
File "/usr/lib/python2.6/site-packages/salt/cli/call.py", line 59, in run
caller = salt.cli.caller.Caller.factory(self.config)
File "/usr/lib/python2.6/site-packages/salt/cli/caller.py", line 71, in factory
return RAETCaller(opts, **kwargs)
File "/usr/lib/python2.6/site-packages/salt/cli/caller.py", line 282, in init
self.stack = self._setup_caller_stack(opts)
File "/usr/lib/python2.6/site-packages/salt/cli/caller.py", line 352, in _setup_caller_stack
stackname = 'caller' + nacling.uuid(size=18)
File "/usr/lib/python2.6/site-packages/raet/nacling.py", line 576, in uuid
return ((front + back)[:size]).decode(encoding='ISO-8859-1')
TypeError: decode() takes no keyword arguments
Any ideas? I feel like Python 2.6 over 2.7 might be a part of this issue.
The text was updated successfully, but these errors were encountered: