Project

General

Profile

Actions

Bug #36541

closed

inconsistent configuration for Redis as used by Dynflow

Added by Evgeni Golov over 1 year ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

Ohai,

in https://github.com/theforeman/puppet-foreman/blob/1d09876d7838bcd133add6266f4ba19b936ccb6c/manifests/config.pp#L14 we default to use localhost/6 as the Redis DB for Dynflow, which gets written to /etc/foreman/settings.yml in https://github.com/theforeman/puppet-foreman/blob/1d09876d7838bcd133add6266f4ba19b936ccb6c/templates/settings.yaml.erb#L97

however, the service itself is configured to use localhost/0 in https://github.com/theforeman/foreman/blob/539373dfa5d85149a9dddb6e73bb378a23e134cb/extras/systemd/dynflow-sidekiq%40.service#L14-L15 as seen during service startup:

Jun 28 09:02:00 katello.example.com dynflow-sidekiq@worker-hosts-queue-1[55989]: 2023-06-28T09:02:00.648Z pid=55989 tid=17vt INFO: Booting Sidekiq 6.3.1 with redis options {:url=>"redis://localhost:6379/0"}

I have no idea if those two must match, or they are two different/unrelated uses of Redis inside Dynflow. But it seems odd and I would expect to be able to configure it.

Actions #1

Updated by Eric Helms about 1 year ago

  • Project changed from Installer to Foreman
Actions #2

Updated by The Foreman Bot about 1 year ago

  • Fixed in Releases 3.9.0 added
Actions #3

Updated by Eric Helms about 1 year ago

  • Status changed from New to Closed
Actions

Also available in: Atom PDF