Actions
Bug #13130
closedOnly one template invocation is created per one job invocation
Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Difficulty:
Triaged:
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