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

ScheduledJobs created under 1.x not correctly migrated to 2.x #4676

Closed
glennmatthews opened this issue Oct 18, 2023 · 0 comments · Fixed by #4682
Closed

ScheduledJobs created under 1.x not correctly migrated to 2.x #4676

glennmatthews opened this issue Oct 18, 2023 · 0 comments · Fixed by #4682
Assignees
Labels
emergent Unplanned work that is brought into a sprint after it's started. type: bug Something isn't working as expected

Comments

@glennmatthews
Copy link
Contributor

Environment

  • Nautobot version (Docker tag too if applicable): 1.6.x --> 2.0.x

Steps to Reproduce

  1. Under Nautobot 1.x (e.g. 1.6.4) schedule a job to create a ScheduledJob record

Screenshot 2023-10-18 at 10 20 47 AM

  1. Migrate to Nautobot 2.0.x (e.g. 2.0.3) and view this scheduled job

Expected Behavior

The job_class parameter should be migrated to its 2.0 equivalent task value, as seen in the below screenshot from an equivalent ScheduledJob created afresh under 2.0:

Screenshot 2023-10-18 at 10 35 23 AM

Observed Behavior

Instead, the migrated record loses its job_class and its task remains at its 1.x value of nautobot.extras.jobs.scheduled_job_handler, which is not correct:

Screenshot 2023-10-18 at 10 34 43 AM

This appears to be the result of a misalignment between extras migrations 0091 (which updates the job_class to the new module path needed for 2.0) and 0093 (which removes the job_class in favor of task but does not update task to the new/corrected value).

@glennmatthews glennmatthews added type: bug Something isn't working as expected emergent Unplanned work that is brought into a sprint after it's started. labels Oct 18, 2023
@HanlinMiao HanlinMiao self-assigned this Oct 19, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 18, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
emergent Unplanned work that is brought into a sprint after it's started. type: bug Something isn't working as expected
Projects
No open projects
Status: Done
2 participants