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.
1. Proposed title of this feature request
[RFE] as part of an upgrade from 6.3 to 6.4, the /etc/sysconfig/foreman-tasks should get copied to /etc/sysconfig/dynflowd
3. What is the nature and description of the request?
Related to https://bugzilla.redhat.com/show_bug.cgi?id=1649433 , when you upgrade from 6.3 to 6.4, the /etc/sysconfig/dynflowd file should get created and populated with the contents from /etc/sysconfig/foreman-tasks
4. Why does the customer need this? (List the business requirements here)
Tunings set in foreman-tasks are lost during the upgrade
5. How would the customer like to achieve this? (List the functional
requirements here)
If you upgrade from 6.3 to 6.4 and the dynflowd file gets created with the correct tunings from the old foreman-tasks file
6. For each functional requirement listed, specify how Red Hat and the customer
can test to confirm the requirement is successfully implemented.
If you upgrade from 6.3 to 6.4 and the dynflowd file gets created with the correct tunings from the old foreman-tasks file, this is successfully implemented.
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
No
10. List any affected packages or components.
foreman-maintain, foreman
11. Would the customer be able to assist in testing this functionality if
implemented?
Yes
We need to add foreman-tasks's /etc/sysconfig/dynflowd to be managed by the installer and customized in the custom-heira.yaml file so we can preserve settings during upgrades (major and minor).
Comment 3Ewoud Kohl van Wijngaarden
2019-04-18 13:42:09 UTC
*** Bug 1667405 has been marked as a duplicate of this bug. ***
Comment 4Ewoud Kohl van Wijngaarden
2019-04-18 13:45:12 UTC
*** Bug 1700501 has been marked as a duplicate of this bug. ***
The release of Satellite 6.8 introduced Sidekiq based Dynflow which dropped the use of the dynflowd service and environment configuration file. I am therefore opting to close this current release.