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

After schedule.disable all jobs reported individually disabled intead of just the scheduler #54848

Closed
OrangeDog opened this issue Oct 2, 2019 · 2 comments
Assignees
Labels
Bug broken, incorrect, or confusing behavior
Milestone

Comments

@OrangeDog
Copy link
Contributor

OrangeDog commented Oct 2, 2019

Description of Issue

# salt-call schedule.list
local:
    schedule:
      enabled: true
      highstate:
        enabled: true
        function: state.apply
        jid_include: true
        kwargs:
          saltenv: base
        maxrunning: 1
        minutes: 15
        name: highstate
        returner: zabbix
        run_on_start: true
        splay: 60
# salt-call schedule.disable
local:
    ----------
    comment:
        Disabled schedule on minion.
    result:
        True
# salt-call schedule.list
local:
    schedule:
      enabled: false
      highstate:
        enabled: false
        function: state.apply
        jid_include: true
        kwargs:
          saltenv: base
        maxrunning: 1
        minutes: 15
        name: highstate
        returner: zabbix
        run_on_start: true
        splay: 60

Subsequent operations don't put them back

# salt-call schedule.enable
local:
    ----------
    comment:
        Enabled schedule on minion.
    result:
        True
# salt-call schedule.list
local:
    schedule:
      enabled: true
      highstate:
        enabled: false
        function: state.apply
        jid_include: true
        kwargs:
          saltenv: base
        maxrunning: 1
        minutes: 15
        name: highstate
        returner: zabbix
        run_on_start: true
        splay: 60

Related to #54820
https://gist.github.com/OrangeDog/fd08470a682752347efd52fe7a5b830d

@OrangeDog
Copy link
Contributor Author

Additionally, if this is eventually persisted via a schedule.present application, the __mine_interval job remains disabled and I'm not sure there's any way to turn it back on other than editing the file and restarting the minion.

Related: #54847

@dwoz dwoz added the Bug broken, incorrect, or confusing behavior label Oct 13, 2019
@garethgreenaway garethgreenaway added this to the Approved milestone Oct 14, 2019
@garethgreenaway garethgreenaway self-assigned this Oct 14, 2019
@OrangeDog
Copy link
Contributor Author

Fixed in 2019.2.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug broken, incorrect, or confusing behavior
Projects
None yet
Development

No branches or pull requests

3 participants