timeout issue when installing packages on windows

[Ch3LL]

Description of Issue/Question

when attempting to run the following sls file:

winpkgs:
  pkg.installed:
    - pkgs:
      - chrome
      - firefox
      - adobereader

I continue to get the following error: minion did not return even when i change the timeout to 1000 (-t 1000). It actually installs the packages correctly but I would expect for salt to wait until the packages have been installed before timeing out.

Setup

1. (1) windows minion and linux master
2. /srv/salt/pkg.sls:

winpkgs:
  pkg.installed:
    - pkgs:
      - chrome
      - firefox
      - adobereader

Steps to Reproduce Issue

1. salt 'win*' state.sls windows.pkg -t30

Then it will return with minion did not return. I am expecting it to wait until the packages are installed adn then report back when that has occurred.

Versions Report

win2012:
    Salt Version:
               Salt: 2015.8.11

    Dependency Versions:
             Jinja2: 2.7.3
           M2Crypto: Not Installed
               Mako: Not Installed
             PyYAML: 3.11
              PyZMQ: 14.7.0
             Python: 2.7.12 (v2.7.12:d33e0cf91556, Jun 27 2016, 15:24:40) [MSC v.1500 64 bit (AMD64)]
               RAET: Not Installed
            Tornado: 4.2.1
                ZMQ: 4.1.2
               cffi: Not Installed
           cherrypy: Not Installed
           dateutil: 2.4.2
              gitdb: Not Installed
          gitpython: Not Installed
              ioflo: Not Installed
            libgit2: Not Installed
            libnacl: Not Installed
       msgpack-pure: Not Installed
     msgpack-python: 0.4.6
       mysql-python: Not Installed
          pycparser: Not Installed
           pycrypto: 2.6.1
             pygit2: Not Installed
       python-gnupg: 0.3.7
              smmap: Not Installed
            timelib: Not Installed

    System Versions:
               dist:   
            machine: AMD64
            release: 8
             system: 8 6.2.9200 SP0 Multiprocessor Free

[TheBigBear]

I believe this is linked? #34872

[cbuechler]

I don't think this is related to #34872, as my circumstance there works fine in the 2015.8 version shown as affected here, it's only 2016.3 that's affected by that.

[TheBigBear]

@cbuechler you sure it is not common or shared code in the latest 2015.8.11 and 2016.3 as 2015.8.11 was released after 2016.3 was out?
In other words on which exact point release of the 2015.8 series did it last test OK on?

[cbuechler]

Looks like the last version that I used that worked was 2015.8.10, that was the last 2015.x version that was in FreeBSD packages. So I guess in theory it could be a regression between 2015.8.10 and .11, though that seems unlikely, I can't confirm or deny that.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.