Project

General

Profile

Bug #30859

Jobs get stuck after processing first batch, remaining hosts remain in N/A

Added by Adam Ruzicka almost 2 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Foreman
Difficulty:
Triaged:
No
Bugzilla link:

Associated revisions

Revision 2d1bb488 (diff)
Added by Adam Růžička almost 2 years ago

Fixes #30859 - Prevent job from getting stuck after first batch (#535)

By accounting for missing hosts in a job we broke running jobs on hosts past
first batch. There is a module which periodically polls states of sub-tasks and
overwrites then numbers we were using to decide whether to spawn next batch or
not.

With this change we store the expected total count under a different key in
task's output so it won't get overwritten by the included polling module. For
compatibility with already existing jobs we use the value under the original key
in task's output in case the task doesn't have the value set under the new key.

History

#1 Updated by The Foreman Bot almost 2 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman_remote_execution/pull/535 added

#2 Updated by The Foreman Bot almost 2 years ago

  • Fixed in Releases added

#3 Updated by Anonymous almost 2 years ago

  • Status changed from Ready For Testing to Closed

#4 Updated by Adam Ruzicka almost 2 years ago

  • Fixed in Releases foreman_remote_execution 4.2.0 added
  • Fixed in Releases deleted ()

Also available in: Atom PDF