Lots of dynflow related warnings like 'do not serialize to JSON safely' observed after upgrading to Red Hat Satellite 6.14.2

Solution Verified - Updated

Environment

  • Red Hat Satellite 6.14.2 and later
  • Red Hat Satellite 6.15

Issue

  • After upgrading to Red Hat Satellite 6.14.2 or later, whenever any new tasks are being executed, The /var/log/messages file gets filled with many dynflow\sidekiq related warnings.

    Feb 21 14:44:06 satellite614 dynflow-sidekiq@orchestrator[18149]: 2024-02-21T09:14:06.322Z pid=18149 tid=gq1h WARN: Job arguments to Dynflow::Executors::Sidekiq::WorkerJobs::PerformWork do not serialize to JSON safely. This will raise an error in
    Feb 21 14:44:06 satellite614 dynflow-sidekiq@orchestrator[18149]: Sidekiq 7.0. See https://github.com/mperham/sidekiq/wiki/Best-Practices or raise an error today
    Feb 21 14:44:06 satellite614 dynflow-sidekiq@orchestrator[18149]: by calling `Sidekiq.strict_args!` during Sidekiq initialization.
    

Resolution

For more KB articles/solutions related to Red Hat Satellite 6.x Satellite Tasking System Issues, please refer to the Consolidated Troubleshooting Article for Red Hat Satellite 6.x Satellite Tasking System Issues

Root Cause

Red Hat Satellite 6.14.2 and later, comes with Sidekiq 6.5 installed and the warning happens due to some legacy code present in this version. For more details about the future implementations, please refer to the following links:

SBR
Product(s)
Components
Category

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.