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
cron.rm_job and cron.rm_special do nothing (state cron.absent also broken) #55078
Comments
@James00001, any logs? Do You can add |
cron.raw_cron and cron.list_tab both seem to work perfectly With further testing, I figured out what is causing this bug. (or at least what condition triggers it, and how to work around it) I had been getting a warning like this:
Everything else other than the cron module was working perfectly, so I didn't pay enough attention to it at first. After doing Perhaps this is just a bug in the sense that the deprecation of minitornado should be an "ERROR" instead of a "WARNING"? Perhaps a dependency on tornado needs to be declared? |
Hmm. Weird. Yeah, those commands are literally executing I guess we'll let a maintainer figure out what the best course of action for this is then. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue. |
This needs to be triaged. |
Thank you for updating this issue. It is no longer marked as stale. |
Although I can investigate this, I'm going to ping @dwoz on this since he has more tornado experience than I - he may be able to shed some light on the dep warning... |
I can confirm that rm_special isn't removing the cron job too. |
Description of Issue
The cron module's features for removing cron jobs appears to be broken in salt 2019.2.1
Neither cron.rm_job nor cron.rm_special seems to do anything at all. They don't report any failure, but the don't remove the matching job either.
the cron.absent state also fails, always acting as if the cron job doesn't exist, when actually it does.
Setup
Plain default out-of-the-box salt 2019.2.1 on Debian 10
Steps to Reproduce Issue
Create a new cron job, this part will work...
``
`sudo salt "debian-salt-minion" cron.set_special jamesp '@hourly' 'date >> ~/crontest.log' identifier="TESTJOB"
sudo salt "debian-salt-minion" cron.rm_special jamesp '@hourly' 'date >> ~/crontest.log' identifier="TESTJOB"
sudo salt "debian-salt-minion" cron.ls jamesp
Salt Version:
Salt: 2019.2.1
Dependency Versions:
cffi: Not Installed
cherrypy: Not Installed
dateutil: 2.7.3
docker-py: Not Installed
gitdb: 2.0.5
gitpython: 2.1.11
ioflo: Not Installed
Jinja2: 2.10
libgit2: 0.27.7
libnacl: Not Installed
M2Crypto: Not Installed
Mako: Not Installed
msgpack-pure: Not Installed
msgpack-python: 0.5.6
mysql-python: Not Installed
pycparser: 2.19
pycrypto: 2.6.1
pycryptodome: Not Installed
pygit2: 0.27.4
Python: 3.7.3 (default, Apr 3 2019, 05:39:12)
python-gnupg: Not Installed
PyYAML: 3.13
PyZMQ: 17.1.2
RAET: Not Installed
smmap: 2.0.5
timelib: Not Installed
Tornado: 4.5.3
ZMQ: 4.3.1
System Versions:
dist: debian 10.1
locale: UTF-8
machine: x86_64
release: 4.19.0-6-amd64
system: Linux
version: debian 10.1
The text was updated successfully, but these errors were encountered: