Project

General

Profile

Actions
Copy link

Bug #35413

open

Make dynflow compatible with Sidekiq 7

Added by Adam Ruzicka over 2 years ago. Updated 21 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

2022-08-23T08:10:32.504Z pid=1316944 tid=s5cw WARN: Job arguments to Dynflow::Executors::Sidekiq::WorkerJobs::PerformWork do not serialize to JSON safely. This will raise an error in
Sidekiq 7.0. See https://github.com/mperham/sidekiq/wiki/Best-Practices or raise an error today
by calling `Sidekiq.strict_args!` during Sidekiq initialization.

tl;dr: symbols should not pass across process boundaries

Actions
Copy link
 #1

Updated by Et7f3 please_edit_me 7 months ago

Hello,

We are experiencing this bug today (and it flood our logs) can we silence this warning as workaround waiting this issue to be fixed ?
I don't know why we haven't that bug the other days.

I see it is fixed in 9.1.2 and satellite 6.15 have only 9.0.4 as per https://access.redhat.com/articles/1343683 and yum list with enabled repo

Cheers

Actions
Copy link
 #2

Updated by Jeff S 21 days ago

Same issue. Flooding our logs. We have 90,000 hosts, so its excessive. How can we put in a WAR?

Actions
Copy link
 #3

Updated by Adam Ruzicka 21 days ago

What is a "WAR"? Also, the logging should have been suppressed since dynflow-1.8.3

Actions
Copy link

Also available in: Atom PDF