Project

General

Profile

Actions

Refactor #22980

closed

foreman-maintain should use dynflowd instead of foreman-tasks

Added by Evgeni Golov about 6 years ago. Updated 3 months ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
easy
Triaged:
Fixed in Releases:
Found in Releases:

Description

foreman-tasks.service has been renamed to dynflowd.service in foreman 1.17. I think k-service should honour this rename (even tho it still works at the moment, as dynflowd provides an alias for foreman-tasks).

Actions #1

Updated by John Mitsch about 6 years ago

Since this is moving to foreman_maintain and getting close to being merged, can you open up a BZ against foreman_maintain and we can fix it there?

PR: https://github.com/theforeman/foreman_maintain/pull/151

Actions #2

Updated by Evgeni Golov about 6 years ago

  • Project changed from Katello to Foreman
  • Subject changed from katello-service should use dynflowd instead of foreman-tasks to formain-maintaain should use dynflowd instead of foreman-tasks
  • Category deleted (Tooling)
Actions #3

Updated by Evgeni Golov about 6 years ago

  • Subject changed from formain-maintaain should use dynflowd instead of foreman-tasks to formain-maintain should use dynflowd instead of foreman-tasks
Actions #4

Updated by John Mitsch about 6 years ago

  • Project changed from Foreman to Foreman Maintain
Actions #5

Updated by Ewoud Kohl van Wijngaarden about 6 years ago

  • Subject changed from formain-maintain should use dynflowd instead of foreman-tasks to foreman-maintain should use dynflowd instead of foreman-tasks
Actions #6

Updated by Eric Helms 3 months ago

  • Status changed from New to Rejected
Actions

Also available in: Atom PDF