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 971014 - Branding: references to reporting bugs should be integrated with RH tracking
Summary: Branding: references to reporting bugs should be integrated with RH tracking
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Provisioning
Version: Nightly
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: Sam Kottler
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-05 13:16 UTC by Corey Welton
Modified: 2019-09-26 13:41 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-04-24 17:07:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Corey Welton 2013-06-05 13:16:24 UTC
Description of problem:
When user lands on some error pages, it indicates that user should report issues upstream. While this may be the case for the open source/upstream product, it's not appropriate for the enterprise product.

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


How reproducible:


Steps to Reproduce:
1.  Do *something* which lands on an error page.  Currently you can follow the steps in bug #971012
2.  View the resulting error page.


Actual results:

Error page which reads:
If you feel this is an error with Foreman itself, please open a new issue with Foreman ticketing system, You would probably need to attach the Full trace and relevant log entries.

Expected results:
Point to RH bugzilla and/or RH support mechanisms.

Additional info:

Comment 5 Corey Welton 2013-10-18 16:13:28 UTC
Can't presently trigger an error to assure it renders, but can at least confirm it's in the build

[root@qe-blade-09 ~]# grep Bugzilla /usr/share/foreman/app/views/about/index.html.erb 

<%= link_to _("Submit a bug to Red Hat's Bugzilla"),"https://bugzilla.redhat.com/enter_bug.cgi?product=Red%20Hat%20Satellite%206", :rel => "external" %>


QA verified Satellite-6.0.2-RHEL-6-20131016.0

Comment 6 Sam Kottler 2013-10-18 16:16:29 UTC
You can just go to the about page and see the content there.

Comment 9 Bryan Kearney 2014-04-24 17:07:11 UTC
This was verified and delivered with MDP2. Closing it out.


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