Project

General

Profile

Bug #32209

REX core tries to register task launchers too early

Added by Adam Ruzicka over 1 year ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Difficulty:
Triaged:
No
Bugzilla link:

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

Associated revisions

Revision a37de881 (diff)
Added by Adam Růžička over 1 year ago

Fixes #32209 - Try to require task launcher registry in advance (#573)

  • Fixes #32209 - Try to require task launcher registry in advance

There is no guarantee that it was loaded by something else at the point where we
try to use it. It is safer to try loading it.

History

#1 Updated by Adam Ruzicka over 1 year ago

  • Target version set to foreman_remote_execution_core 1.4.1

#2 Updated by The Foreman Bot over 1 year ago

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

#3 Updated by The Foreman Bot over 1 year ago

  • Fixed in Releases foreman_remote_execution 4.1.1 added

#4 Updated by Anonymous over 1 year ago

  • Status changed from Ready For Testing to Closed

#5 Updated by Adam Ruzicka over 1 year ago

  • Fixed in Releases foreman_remote_execution_core 1.4.1 added
  • Fixed in Releases deleted (foreman_remote_execution 4.1.1)

Also available in: Atom PDF