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

schedule.present state not idempotent in 2019.2.0 #51824

Closed
OrangeDog opened this issue Feb 26, 2019 · 2 comments
Closed

schedule.present state not idempotent in 2019.2.0 #51824

OrangeDog opened this issue Feb 26, 2019 · 2 comments
Assignees
Labels
Bug broken, incorrect, or confusing behavior fixed-pls-verify fix is linked, bug author to confirm fix P2 Priority 2 severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around
Milestone

Comments

@OrangeDog
Copy link
Contributor

Master and minion 2019.2.0 (with #51265).
Every alternating application of this state reports changes.

highstate:
  schedule.present:
    - enabled: true
    - function: state.apply
    - job_kwargs:
        saltenv: base
    - minutes: 10
    - returner: zabbix
    - run_on_start: true
          ID: highstate
    Function: schedule.present
      Result: True
     Comment: Modifying job highstate in schedule
     Started: 12:34:57.835010
    Duration: 27.769 ms
     Changes:
              ----------
              diff:
                  ---
                  +++
                  @@ -1,10 +1,9 @@
                   enabled:True
                   function:state.apply
                   jid_include:True
                  -kwargs:{'saltenv': 'base'}
                  +kwargs:OrderedDict([('saltenv', 'base')])
                   maxrunning:1
                   minutes:10
                   name:highstate
                   returner:zabbix
                   run_on_start:True
                  -splay:None
@garethgreenaway garethgreenaway self-assigned this Feb 26, 2019
@garethgreenaway garethgreenaway added this to the Approved milestone Feb 26, 2019
@garethgreenaway garethgreenaway added severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around P2 Priority 2 ZRELEASED - 2017.7.9 RETIRED LABEL Bug broken, incorrect, or confusing behavior and removed ZRELEASED - 2017.7.9 RETIRED LABEL labels Feb 26, 2019
@garethgreenaway garethgreenaway added the fixed-pls-verify fix is linked, bug author to confirm fix label Feb 26, 2019
@max-arnold
Copy link
Contributor

Duplicate of #51467

@garethgreenaway
Copy link
Contributor

Closing this out as the fix is in the 2019.2 and later branches, and will be available in the next minor releases. If the problem persists, let us know and we can reopen this issue.

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 fixed-pls-verify fix is linked, bug author to confirm fix P2 Priority 2 severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around
Projects
None yet
Development

No branches or pull requests

3 participants