Project

General

Profile

Actions

Bug #13130

closed

Only one template invocation is created per one job invocation

Added by Marek Hulán about 8 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

During digging around job_name refactoring I realized that template invocations are not being created as expected. Job composer creates one template invocation that works as a template (does not have host_id yet, that is correct), then when planning the RunHostJob the same template is passed as an argument, during plan host_id is set. Unfortunately for all RunHostJob the same template is used, so each sub task is changing the only one template invocation that exist. We should expand the template as part of RunHostsJob so it passes new object to RunHostJob. I guess the update was part of RunHostJob plan phase, since that's in transaction.

Actions #1

Updated by Marek Hulán about 8 years ago

  • Status changed from New to Assigned
Actions #2

Updated by The Foreman Bot about 8 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/foreman_remote_execution/pull/117 added
Actions #3

Updated by Marek Hulán about 8 years ago

  • translation missing: en.field_release set to 109
Actions #4

Updated by Marek Hulán about 8 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF