salt: Scheduled highstates from Windows-minions not returning to master

Description of Issue/Question

This issue was something we’ve run into in the past (#38371) and was fixed in #38923. On Linux, this works fine. The “workaround returner” I created and to used to workaround this in the past was no longer necessary.

However, we recently installed a few Windows machines with Salt and noticed that it was showing the very same behavior as with the previous issue:

  • A salt-call state.highstate properly returns the salt/job/* event to the master
  • A scheduled state.highstate does not return the salt/job/* event to the master

Setup

  • Master on Ubuntu 16.04
  • Minion on Windows Server 2016

Steps to Reproduce Issue

  • Run Salt-minion on Windows
  • Setup a schedule to do a highstate every X minutes
  • Wait for the schedule to execute
  • Listen to the eventsbus on the master salt-run state.event pretty=True
  • Notice that only the minion/refresh/* and salt/auth events are being returned but no salt/job/* events for scheduled highstates
  • Run a manual highstate salt-call state.highstate on the Windows minion
  • Notice that the event is being returned to the master

Versions Report

Master

Salt Version:
           Salt: 2018.3.2
 
Dependency Versions:
           cffi: Not Installed
       cherrypy: Not Installed
       dateutil: 2.4.2
      docker-py: Not Installed
          gitdb: 0.6.4
      gitpython: 1.0.1
          ioflo: Not Installed
         Jinja2: 2.8
        libgit2: Not Installed
        libnacl: 1.6.1
       M2Crypto: Not Installed
           Mako: 1.0.3
   msgpack-pure: Not Installed
 msgpack-python: 0.4.6
   mysql-python: 1.3.7
      pycparser: Not Installed
       pycrypto: 2.6.1
   pycryptodome: Not Installed
         pygit2: Not Installed
         Python: 2.7.12 (default, Dec  4 2017, 14:50:18)
   python-gnupg: 0.3.8
         PyYAML: 3.11
          PyZMQ: 15.2.0
           RAET: Not Installed
          smmap: 0.9.0
        timelib: Not Installed
        Tornado: 4.2.1
            ZMQ: 4.1.4
 
System Versions:
           dist: Ubuntu 16.04 xenial
         locale: UTF-8
        machine: x86_64
        release: 4.4.0-1031-aws
         system: Linux
        version: Ubuntu 16.04 xenial

Minion

Salt Version:
           Salt: 2018.3.2

Dependency Versions:
           cffi: 1.10.0
       cherrypy: 10.2.1
       dateutil: 2.6.1
      docker-py: Not Installed
          gitdb: 2.0.3
      gitpython: 2.1.3
          ioflo: Not Installed
         Jinja2: 2.9.6
        libgit2: Not Installed
        libnacl: Not Installed
       M2Crypto: Not Installed
           Mako: 1.0.6
   msgpack-pure: Not Installed
 msgpack-python: 0.4.8
   mysql-python: Not Installed
      pycparser: 2.17
       pycrypto: 2.6.1
   pycryptodome: Not Installed
         pygit2: Not Installed
         Python: 2.7.14 (v2.7.14:84471935ed, Sep 16 2017, 20:25:58) [MSC v.1500 64 bit (AMD64)]
   python-gnupg: 0.4.1
         PyYAML: 3.12
          PyZMQ: 16.0.3
           RAET: Not Installed
          smmap: 2.0.3
        timelib: 0.2.4
        Tornado: 4.5.1
            ZMQ: 4.1.6

System Versions:
           dist:
         locale: cp1252
        machine: AMD64
        release: 2016Server
         system: Windows
        version: 2016Server 10.0.14393  Multiprocessor Free

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Comments: 29 (16 by maintainers)

Most upvoted comments

Up.

I suspect this is a duplicate or part of the problem. #51621 Master calling find_job every 10 seconds, Windows takes 10 seconds to execute it depending on how schedule works.

Unfortunately, I no longer work for SaltStack, so someone from @saltstack/team-triage will need to take over managing this issue.