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

Scheduler No Longer List after Disable or Enable #62795

Closed
sramsey822 opened this issue Oct 1, 2022 · 3 comments · Fixed by #62803
Closed

Scheduler No Longer List after Disable or Enable #62795

sramsey822 opened this issue Oct 1, 2022 · 3 comments · Fixed by #62803
Labels
Bug broken, incorrect, or confusing behavior needs-triage Phosphorus v3005.0 Release code name and version Regression The issue is a bug that breaks functionality known to work in previous releases.

Comments

@sramsey822
Copy link

Description of Issue

Seeing an ugly issue with the Scheduler: Apparently, a couple of versions (ie: years ago) the Scheduler would no longer perform a listing AFTER the user issued: schedule.enable or schedule.disable. If the user attempts to issue schedule.list an error is generated
"Passed invalid arguments: 'bool' object does not support item assignment."

Setup

salt tradingpost schedule.add job1 function="cmd.script" job_args="['salt://files/mlx_apt_confirm.sh']" seconds=10

Steps to Reproduce Issue

  1. Create schedule job
  2. salt minion1 schedule.list
  3. salt minion1 schedule.disable
  4. salt minion1 schedule.enable
  5. salt minion1 schedule.list
    Error Message:

minion1:
Passed invalid arguments to schedule.list: 'bool' object does not support item assignment

    List the jobs currently scheduled on the minion

    CLI Example:

    .. code-block:: bash

        salt '*' schedule.list

        # Show all jobs including hidden internal jobs
        salt '*' schedule.list show_all=True

        # Hide disabled jobs from list of jobs
        salt '*' schedule.list show_disabled=False

salt-log.txt

Versions Report

Both the master / minion are running the same versions Salt - 3005+ds-2
salt --versions-report
Salt Version:
Salt: 3005

Dependency Versions:
cffi: Not Installed
cherrypy: unknown
dateutil: 2.7.3
docker-py: Not Installed
gitdb: 2.0.6
gitpython: 3.0.7
Jinja2: 2.10.1
libgit2: Not Installed
M2Crypto: Not Installed
Mako: Not Installed
msgpack: 0.6.2
msgpack-pure: Not Installed
mysql-python: Not Installed
pycparser: Not Installed
pycrypto: Not Installed
pycryptodome: 3.6.1
pygit2: Not Installed
Python: 3.8.10 (default, Jun 22 2022, 20:18:18)
python-gnupg: 0.4.5
PyYAML: 5.3.1
PyZMQ: 20.0.0
smmap: 2.0.5
timelib: Not Installed
Tornado: 4.5.3
ZMQ: 4.3.2

System Versions:
dist: ubuntu 20.04 focal
locale: utf-8
machine: x86_64
release: 5.4.0-126-generic
system: Linux
version: Ubuntu 20.04 focal

@welcome
Copy link

welcome bot commented Oct 1, 2022

Hi there! Welcome to the Salt Community! Thank you for making your first contribution. We have a lengthy process for issues and PRs. Someone from the Core Team will follow up as soon as possible. In the meantime, here’s some information that may help as you continue your Salt journey.
Please be sure to review our Code of Conduct. Also, check out some of our community resources including:

There are lots of ways to get involved in our community. Every month, there are around a dozen opportunities to meet with other contributors and the Salt Core team and collaborate in real time. The best way to keep track is by subscribing to the Salt Community Events Calendar.
If you have additional questions, email us at saltproject@vmware.com. We’re glad you’ve joined our community and look forward to doing awesome things with you!

@OrangeDog OrangeDog added Bug broken, incorrect, or confusing behavior needs-triage labels Oct 3, 2022
@OrangeDog
Copy link
Contributor

There were some changes to schedule storage in the past that ended up being not compatible, especially if you were using an old syntax.

Try schedule.purge and recreating the schedule. It should clear out any leftover old attributes.

@garethgreenaway
Copy link
Contributor

Looks like this broke with this PR, #61683

@OrangeDog OrangeDog added Regression The issue is a bug that breaks functionality known to work in previous releases. Phosphorus v3005.0 Release code name and version labels Oct 3, 2022
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 needs-triage Phosphorus v3005.0 Release code name and version Regression The issue is a bug that breaks functionality known to work in previous releases.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants