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

Invalid keyword 'str' for variable 'master_type' #26291

Closed
mikepietruszka opened this issue Aug 13, 2015 · 2 comments
Closed

Invalid keyword 'str' for variable 'master_type' #26291

mikepietruszka opened this issue Aug 13, 2015 · 2 comments

Comments

@mikepietruszka
Copy link

Hello,

I'm getting the following error when master_type: str is set in /etc/salt/minion:

2015-08-13 11:55:09,537 [salt.cli.daemons ][INFO    ][2349] Setting up the Salt Minion "hostname"
2015-08-13 11:55:09,650 [salt.cli.daemons                         ][INFO    ][2349] The salt minion is shut down
2015-08-13 11:55:09,652 [salt.cli.daemons                         ][INFO    ][2355] The salt minion is shut down
2015-08-13 11:55:09,865 [salt.minion                              ][ERROR   ][2357] Invalid keyword 'str' for variable 'master_type'
2015-08-13 11:55:09,866 [salt.cli.daemons                         ][INFO    ][2357] The salt minion is shut down

This seems to happen after running bootstrap_salt.sh as well as when manually editing the minion config file. Setting master_type: failover appears to finally start the salt-minion daemon.

$ salt-minion --versions-report
           Salt: 2015.5.3
         Python: 2.6.6 (r266:84292, Jul 23 2015, 15:22:56)
         Jinja2: unknown
       M2Crypto: 0.20.2
 msgpack-python: 0.4.6
   msgpack-pure: Not Installed
       pycrypto: 2.0.1
        libnacl: Not Installed
         PyYAML: 3.10
          ioflo: Not Installed
          PyZMQ: 14.3.1
           RAET: Not Installed
            ZMQ: 3.2.5
           Mako: Not Installed
        Tornado: Not Installed
@mikepietruszka
Copy link
Author

Seems like this was fixed in #25704 and #25703

@rallytime
Copy link
Contributor

@maschinetheist - You are correct that this is a duplicate and has been fixed. We're working on getting a release out with this fix very soon. Thanks very much for filing this and following up!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants