cmd.run unreliable

[Mrten]

I run salt '*' -b 25% cmd.run 'apt-get update' and I get this as output:

root@salt-master:/home/salt/conf/machine/apt/apt-cacher-ng# salt '*' -b 25% cmd.run 'apt-get update'
[deleted 'detected messages']
Executing run on ['web-5', 'web-4', 'web-3', 'web-2', 'web-1', 'upload', 'tunnel', 'tap-0017', 'tap-0016', 'tap-0012', 'tahoe']

tahoe:
    ----------
tap-0012:
    ----------
tunnel:
    ----------
upload:
    ----------
web-4:
    ----------
web-5:
    ----------
tap-0017:
    ----------
web-1:
    ----------
web-2:
    Get:1 http://security.ubuntu.com precise-security Release.gpg [198 B]
    Get:2 http://repo.percona.com precise Release.gpg [198 B]
   [...]
web-3:
    ----------
tap-0016:
    ----------

See the empty returns? This is not possible, apt-get update always returns something.If you run it manually on one of those, it returns OK:

root@salt-master:/home/salt/conf/machine/apt/apt-cacher-ng# salt 'web-3' -b 25% cmd.run 'apt-get update'
web-3 Detected for this batch run

Executing run on ['web-3']

web-3:
    Hit http://archive.ubuntu.com precise Release.gpg
    Hit http://192.168.84.15 precise Release.gpg
    Hit http://archive.ubuntu.com precise-updates Release.gpg
    Hit http://archive.ubuntu.com precise-backports Release.gpg
    Hit http://ppa.launchpad.net precise Release.gpg
    [...]

[basepi]

Another one I would attribute to broken batch mode. I would be interested to know if you can reproduce it without batch mode: #6456

[Mrten]

Hard to say, I end up with 36 'minion did not return's (out of 50 or so minions) as in #8647.

[cachedout]

I'm nearly certain this was was resolved in the recent round of batch mode fixing. @Mrten
could you re-test this against a more recent release?

[Mrten]

Seems to work OK in 2014.1.3.

[cachedout]

Thank you for testing this for us, @Mrten! I'll go ahead and close this issue. If anybody else sees it in a recent release, leave a comment and we'll re-open it.