Project

General

Custom queries

Profile

Actions
Copy link

Feature #18757

closed

Move foreman-tasks service to Foreman

Added by Daniel Lobato Garcia about 8 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Daniel Lobato Garcia
Category:
Foreman modules
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
Pull request:
https://github.com/theforeman/puppet-foreman/pull/530, https://github.com/theforeman/puppet-foreman/pull/602
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

As per #18618, the dynflow executor is moving over to Foreman, in order to support ActiveJob. Tasks will provide an UI and persistence layer for Dynflow, but Foreman should be able to run jobs without it too.

Part of this effort includes moving the Dynflow executor over to Foreman, which at the moment is managed by the foreman-tasks service.

Related issues 1 (0 open — 1 closed)

Has duplicate Installer - Feature #17467: Configure tasks by defaultDuplicateIvan Necas11/23/2016Actions

Added by Ewoud Kohl van Wijngaarden about 7 years ago

Revision ee1b7b47 (diff)

Fixes #18757 - Handle dynflow service in foreman core

The dynflow service was moved into core with 1.17. That renamed it to
dynflowd and means the service should be started by default.

For compatibility parameters are provided. This means we must move the
service name detection to the jobs.pp file because that's the only place
we know the actual value.

Actions
Copy link

Also available in: Atom PDF