Use UUID to ensure the uniqueness of job template name #16672
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When we create job template (and inventory) to run a playbook, a timestamp was appended to the name to ensure the name uniqueness at the tower side. For the setup reported in the BZ after multiple VM provisioning completed they all tried to run the same playbook at the same second, causing a naming collision.
The solution is to replace the timestamp with a UUID.
fixes https://bugzilla.redhat.com/show_bug.cgi?id=1525683