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.disable doesn't work in 2019.2.0 #51825

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

Comments

@OrangeDog
Copy link
Contributor

commented Feb 26, 2019

Master and minion on 2019.2.0.
Either schedule.disable doesn't work at all, or the application of a schedule.present state turns it back on.
This is a very annoying change in behaviour from 2018.3.3.

@garethgreenaway

This comment has been minimized.

Copy link
Member

commented Feb 26, 2019

@OrangeDog To confirm, are you talking about disable which disables the entire scheduler or disable_job which disables one schedule job?

@garethgreenaway garethgreenaway self-assigned this Feb 26, 2019
@garethgreenaway garethgreenaway added this to the Blocked milestone Feb 26, 2019
@OrangeDog

This comment has been minimized.

Copy link
Contributor Author

commented Feb 26, 2019

are you talking about disable which disables the entire scheduler

Yes

@garethgreenaway

This comment has been minimized.

Copy link
Member

commented Feb 26, 2019

@OrangeDog Thanks! That definitely shouldn't be happening. Will take a look.

@garethgreenaway

This comment has been minimized.

Copy link
Member

commented Mar 25, 2019

Closing out as this is fixed in the 2019.2 branch and will be available in the 2019.2.1 release.

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