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:
Legacy form doesn't really allow to set future or recurring execution
Version-Release number of selected component (if applicable):
6.13 snap 4
How reproducible:
Always
Steps to Reproduce:
1. I rex wizard, select "Use legacy for"
2. I schedule section, select either "Schedule future execution" or "Set up recurring execution"
Actual results:
No additional fields appear, browser console shows "Uncaught ReferenceError: trigger_form_selector_binds is not defined"
Expected results:
Fields for setting additional details should appear
Additional info:
workaroundable via the new wizard
When a user visits the legacy form, it tries to load some foreman-tasks assets.
It tries to pull them from $sat_fqdn/assets/foreman_tasks/* , which would correspond to /usr/share/foreman/public/assets/foreman_tasks/* . However /usr/share/foreman/public/assets/foreman_tasks does not exist. To make things more interesting, there is /usr/share/foreman/public/assets/foreman-tasks, which is a symlink to /usr/share/gems/gems/foreman-tasks-$version/public/assets/foreman-tasks. Sadly, not even this directory contains the assets that are requested. The assets live in /usr/share/gems/gems/foreman-tasks-$version/public/assets/foreman_tasks.
I'm not sure neither how the assets get build and placed into their location nor how the symlinks are created, but packaging feels like a good bet.
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.13 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-2023:2097