Actions
Bug #32209
closed
REX core tries to register task launchers too early
Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Difficulty:
Triaged:
No
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
Updated by Adam Ruzicka about 3 years ago
- Target version set to foreman_remote_execution_core 1.4.1
Updated by The Foreman Bot about 3 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman_remote_execution/pull/573 added
Updated by The Foreman Bot about 3 years ago
- Fixed in Releases foreman_remote_execution 4.1.1 added
Updated by Anonymous about 3 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman_plugin|a37de8812199c9bd2f44082ffd87ac1e63c5efe4.
Updated by Adam Ruzicka about 3 years ago
- Fixed in Releases foreman_remote_execution_core 1.4.1 added
- Fixed in Releases deleted (
foreman_remote_execution 4.1.1)
Actions