Minion unable to start after upgrade to 2014.1.0

[octo47]

It fails with exception:

2014-03-05 17:44:45,805 [salt.log.setup   ][ERROR   ] An un-handled exception was caught by salt's global exception handler:
StopIteration:
Traceback (most recent call last):
  File "/usr/bin/salt-minion", line 14, in <module>
    salt_minion()
  File "/usr/lib/pymodules/python2.7/salt/scripts.py", line 35, in salt_minion
    minion.start()
  File "/usr/lib/pymodules/python2.7/salt/__init__.py", line 224, in start
    self.minion.tune_in()
  File "/usr/lib/pymodules/python2.7/salt/minion.py", line 501, in tune_in
    minion['generator'].next()
StopIteration

salt-minion --versions-report
Salt: 2014.1.0
Python: 2.7.3 (default, Feb 27 2014, 19:58:35)
Jinja2: 2.7-dev
M2Crypto: 0.21.1
msgpack-python: 0.1.10
msgpack-pure: Not Installed
pycrypto: 2.4.1
PyYAML: 3.10
PyZMQ: 13.0.0
ZMQ: 3.2.2

[octo47]

Thats happens when master in minion config specified as master: [ some.host ]

[juniorctl]

I have the same error since the upgrade to 2014.1.0 but I can track it down to when the master configuration in /etc/salt/minion spans more than one line. For example:

# cat /etc/salt/minion
master: 
  - salt.master.example.com
id: salt.minion.example.com

# salt-minion -l debug
...
[ERROR   ] An un-handled exception was caught by salt's global exception handler:
StopIteration: 
Traceback (most recent call last):
  File "/usr/bin/salt-minion", line 14, in <module>
    salt_minion()
  File "/usr/lib/python2.6/site-packages/salt/scripts.py", line 35, in salt_minion
    minion.start()
  File "/usr/lib/python2.6/site-packages/salt/__init__.py", line 224, in start
    self.minion.tune_in()
  File "/usr/lib/python2.6/site-packages/salt/minion.py", line 501, in tune_in
    minion['generator'].next()
StopIteration

When the master configuration is all on one line as shown below everything works fine.

# cat /etc/salt/minion
master: salt.master.example.com
id: salt.minion.example.com

# salt-minion --versions-report
           Salt: 2014.1.0
         Python: 2.6.9 (unknown, Oct 29 2013, 19:58:13)
         Jinja2: 2.6
       M2Crypto: 0.20.2
 msgpack-python: 0.1.13
   msgpack-pure: Not Installed
       pycrypto: 2.6.1
         PyYAML: 3.10
          PyZMQ: 2.2.0.1
            ZMQ: 3.2.4

[basepi]

Right, both of these are a known issue, which has since been fixed. (Fix will be in 2014.1.1) Basically, when you define the master configuration option, it triggers multi-master functionality, which had a regression in 2014.1.0. Fixed in #10868 and #10937.

[cachedout]

#10937 is the correct fix, for what it's worth.