This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 1995265 - The "Documentation" button on "Domains" page is pointing to "Administering Red Hat Satellite" doc
Summary: The "Documentation" button on "Domains" page is pointing to "Administering Re...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Branding
Version: 6.10.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Akhil Jha
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-18 17:23 UTC by Kshitij
Modified: 2024-06-06 01:03 UTC (History)
8 users (show)

Fixed In Version: tfm-rubygem-foreman_theme_satellite-8.0.1.7-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 01:03:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-19876 0 None Migrated None 2024-06-06 01:03:28 UTC

Description Kshitij 2021-08-18 17:23:37 UTC
Description of problem:

The "Documentation" button on "Domains" page is pointing to "Administering Red Hat Satellite" doc for satellite 6.10 

Version-Release number of selected component (if applicable):

6.10

How reproducible:

Always

Steps to Reproduce:

On Red Hat Satellite Web UI >> Infrastructure >> Domains >> Help >> Click on Documentation.

Actual results:

Points to: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.10/html/administering_red_hat_satellite/index

Expected results:

Should point to 

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.10/html-single/provisioning_guide/index#Configuring_Networking-Adding_a_Domain_to_the_Satellite_Server

Comment 1 Brad Buckingham 2021-10-01 13:01:53 UTC
Moving to MODIFIED as there was an MR attached.

Comment 14 Ewoud Kohl van Wijngaarden 2024-04-18 13:01:01 UTC
I think the problem comes from a poor link in the Foreman code, which then can't properly be branded. In https://github.com/theforeman/foreman-documentation/issues/2957#issuecomment-2063801577 I wrote a longer story but the tl;dr is that https://github.com/theforeman/foreman/blob/bf03a259a7e6fd65207b9a40639bb99e0e507dd8/app/views/domains/welcome.html.erb#L9 links to Networking but so does https://github.com/theforeman/foreman/blob/bf03a259a7e6fd65207b9a40639bb99e0e507dd8/app/views/subnets/welcome.html.erb#L9 which means branding needs to pick one of the two.

I think Foreman itself should be fixed to point to some documentation (or remove the button) so branding can unambiguously rewrite the link.

Comment 16 Eric Helms 2024-06-06 01:03:30 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.


Note You need to log in before you can comment on or make changes to this bug.