Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

Dynflow Worker process is now part of the executor, meaning they can't be restarted independently. As a first step to improve scalability, following two stories will be implemented


1. As a satellite user doing an install or an upgrade, the installer should create both the orchestration and worker processes with sane defaults. Both processes will run on the same machine as the satellite. 

2. As a satellite admin, I should be able to restart a worker process without impacting the uptime of the satellite or losing data.

Verification steps will be added later when we know names of new services.

Verified with Sat 6.8 snap 7.0.

Sidekiq is now used. It's now possible to:
- change a number of workers, number of their threads, their queues
- view log using "journalctl -u 'dynflow-sidekiq@*'"
- restart a worker without getting to inconsistent state

Note that this intentionally does not apply to external capsules.

See this demo:
https://www.youtube.com/watch?v=8xomzg_FBIs&feature=youtu.be&t=485

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Satellite 6.8 release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:4366