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

All referenced jobs show "Job Not Found" after upgrade #4785

Closed
biguphpc opened this issue May 4, 2019 · 3 comments

Comments

Projects
None yet
5 participants
@biguphpc
Copy link

commented May 4, 2019

Describe the bug
When a job references other job as steps, these steps show "Job Not Found". This is a pretty bad regression. it happens to ALL the jobs. Fortunately it seems like the steps are still running ok.

Happened since we upgraded Rundeck from 3.0.9 to 3.0.21.
image

My Rundeck detail

  • Rundeck version: 3.0.21-20190424
  • install type: [choose: deb
  • OS Name/version: ubuntu 16.04
  • DB Type/version: postgres

To Reproduce
Steps to reproduce the behavior:

  1. Select a job referencing other jobs as steps
  2. Click on 'Definition'
  3. All steps show an orange (Job not found)

Expected behavior
Jobs should be found

Desktop (please complete the following information):

  • OS: OSX
  • Browser: chrome

Additional context
Possible issue could be that when the job is edited, by default "UUID Use Jobs UUID to search jobs is selected" instead of "Name". This should be automatically figured out by rundeck on upgrade when a UUID is not present but the name is.

image

@biguphpc

This comment has been minimized.

Copy link
Author

commented May 4, 2019

Just wanted to confirm editing the step and switching back to "Name" makes it back to normal in the web UI (the job is found). It's just very scary to see all steps display "Job Not Found" for any reference not using UUID (there's 400+ jobs in this state for us)

@jessemarple jessemarple added this to the 3.0.22 milestone May 9, 2019

@gschueler gschueler added the bug label May 9, 2019

gschueler added a commit that referenced this issue May 10, 2019

@gtsteffaniak

This comment has been minimized.

Copy link

commented May 10, 2019

Again?

@gschueler

This comment has been minimized.

Copy link
Member

commented May 10, 2019

@gtsteffaniak if you are asking why two commits, it is because I cherry-picked the fix onto the 3.0.x branch as well as master (which is now 3.1.0 snapshot)

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