Project

General

Profile

Actions
Copy link

Bug #32209

closed

REX core tries to register task launchers too early

Added by Adam Ruzicka over 3 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Adam Ruzicka
Category:
-
Target version:
foreman_remote_execution_core 1.4.1
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
https://github.com/theforeman/foreman_remote_execution/pull/573
Fixed in Releases:
foreman_remote_execution_core 1.4.1
Found in Releases:
Red Hat JIRA:

Description

This is fine in deployments where smart_proxy_dynflow_core runs as a standalone service, because the launcher registry is always loaded before rex core. In all-in-one deployment, there is no guarantee about smart_proxy_dynflow_core being loaded before rex core and may lead to task launcher not being registered in the registry

Actions
Copy link

Also available in: Atom PDF