Bug #30859: Jobs get stuck after processing first batch, remaining hosts remain in N/A - Foreman Remote Execution - Foreman

Actions

Bug #30859

closed

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

Added by Adam Ruzicka about 4 years ago. Updated about 4 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Foreman

Target version:

foreman_remote_execution 4.0.1

Difficulty:

Triaged:

No

Bugzilla link:

Pull request:

https://github.com/theforeman/foreman_remote_execution/pull/535

Fixed in Releases:

foreman_remote_execution 4.2.0

Found in Releases:

Red Hat JIRA:

Actions

#1

Updated by The Foreman Bot about 4 years ago

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

Actions

#2

Updated by The Foreman Bot about 4 years ago

Fixed in Releases added

Actions

#3

Updated by Anonymous about 4 years ago

Status changed from Ready For Testing to Closed

Applied in changeset foreman_plugin|2d1bb488360850a8014c079ece75d911fa85af16.

Actions

#4

Updated by Adam Ruzicka about 4 years ago

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

Actions

Also available in: Atom PDF