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

UUID validation of jobRef breaks bulk import of jobs in clean instance of RunDeck #4471

Closed
ajxb opened this issue Feb 8, 2019 · 1 comment

Comments

@ajxb
Copy link

commented Feb 8, 2019

We often have to build out new instances of RunDeck from scratch from a set of templates that include a number of projects and jobs as part of our development workflow with the tool. As part of this build process a new, clean instance of RunDeck is spun up, and project / job data is imported from an archive created using the rd cli tool.

The tools first create the projects from the exported data, they then iterate over each project in turn and import the yaml associated with each job for each project. Prior to v3.0.13 this import did no checking of UUID integrity, so would succeed in importing the jobs no matter what order this is done. I think that the following changes introduced UUID checking for jobRefs:

This breaks the job import into a clean system unless we import the jobs in the reverse order to when they are referenced. We have hundreds of jobs with many references between them over multiple projects so working out the order is going to be difficult, is there any way that we can import the data ignoring the jobRef UUID checks given that the data will have been exported from a known good working system?

My Rundeck detail

  • Rundeck version: 3.0.13
  • install type: rpm
  • OS Name/version: CentOS 6.9
  • DB Type/version: mysq 5.7

To Reproduce

  1. Create a new, clean instance of RunDeck (no data, projects, jobs in system)
  2. Create a project
  3. Using the CLI tool import a job that has a jobRef, without having imported the job that it references

This results in the error :
:Workflow has one or more invalid steps: [1: [Job Name does not correspond to the UUID]] Invalid Option definition: Domain: Workflow has one or more invalid steps: [1: [Job Name does not correspond to the UUID]] Invalid Option definition: Live_URL: Workflow has one or more invalid steps: [1: [Job Name does not correspond to the UUID]];Invalid Option definition: Domain: Workflow has one or more invalid steps: [1: [Job Name does not correspond to the UUID]] Invalid Option definition: Next_URL: Workflow has one or more invalid steps: [1: [Job Name does not correspond to the UUID]];Invalid Option definition: Domain: Workflow has one or more invalid steps: [1: [Job Name does not correspond to the UUID]];Invalid Option definition: Live_URL: Workflow has one or more invalid steps: [1: [Job Name does not correspond to the UUID]];Invalid Option definition: Domain: Workflow has one or more invalid steps: [1: [Job Name does not correspond to the UUID]]

Expected behavior

Jobs can be imported without the need for me to work out the order for which they have to be imported (we have hundreds of jobs with dependencies on others).

@gtsteffaniak

This comment has been minimized.

Copy link

commented Feb 12, 2019

@gschueler Can we get this tagged for the next build?

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