RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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:
At the moment the help button is displayed for every GUI screen in Anaconda unconditionally, while there are cases where no help content is needed for a given screen.

We hit this case with Anaconda progress hub in RHEL 8.3, as it no longer hosts any spokes after the Anaconda rebase, just shows installation progress. It's pretty much self documenting and no help content needs to be provided, yet we don't currently have a way to disable the help button for just this one screen.

This feature would be also useful for customer developed Addons and layered products if they don't want to provide documentation for one or multiple screens.

At the moment help content is assigned to spokes & hubs via class attribute, so it seems like the best solution is to introduce a second help related attribute that would control if the help button is to be shown. 

At the moment I don't think we need this to be dynamic (eq. help button showable/hideable at runtime) so just checking this attribute once when the spoke/hub is first initialized should be enough.

PR with changes: https://github.com/rhinstaller/anaconda/pull/2919

*** Bug 1893398 has been marked as a duplicate of this bug. ***

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 (anaconda bug fix and enhancement update), 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/RHBA-2021:1844