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

scheduled highstate ignores blackout #50562

soostdijck opened this issue Nov 19, 2018 · 1 comment


None yet
2 participants
Copy link

commented Nov 19, 2018

Description of Issue/Question

A scheduled job that runs state.highstate ignores blackout mode. I'm 99% sure this is a change since upgrading from 2018.3.2


$ salt 'parrot*' schedule.add test_blacko function='state.highstate' seconds=20
        Added job: test_blacko to schedule.
$ salt 'parrot*' grains.setval minion_blackout true

Wait for highstate...

$ salt 'parrot*' grains.item minion_blackout

p.s. In this case the blackout grain is being unset by my something in the highstate, this is expected behaviour because the in highstate I have a stanza like this:

    - name: minion_blackout
    - value: false

Of course the issue is that the highstate should not be running in the first place...

Versions Report

Both master and minions are on:

Salt Version:
           Salt: 2018.3.3

Dependency Versions:
           cffi: 1.6.0
       cherrypy: unknown
       dateutil: 1.5
      docker-py: Not Installed
          gitdb: 0.6.4
      gitpython: 1.0.1
          ioflo: Not Installed
         Jinja2: 2.7.2
        libgit2: 0.26.3
        libnacl: Not Installed
       M2Crypto: Not Installed
           Mako: Not Installed
   msgpack-pure: Not Installed
 msgpack-python: 0.5.1
   mysql-python: Not Installed
      pycparser: 2.14
       pycrypto: 2.6.1
   pycryptodome: Not Installed
         pygit2: 0.26.4
         Python: 2.7.5 (default, Apr 11 2018, 07:36:10)
   python-gnupg: Not Installed
         PyYAML: 3.11
          PyZMQ: 15.3.0
           RAET: Not Installed
          smmap: 0.9.0
        timelib: Not Installed
        Tornado: 4.2.1
            ZMQ: 4.1.4

System Versions:
           dist: centos 7.5.1804 Core
         locale: UTF-8
        machine: x86_64
        release: 3.10.0-862.3.3.el7.x86_64
         system: Linux
        version: CentOS Linux 7.5.1804 Core

This comment has been minimized.

Copy link

commented Jan 9, 2019

Closing this out, if the problem persists please comment & we'll re-open the issue or feel free to open a new issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.