Bug 1227994 - [Branding] Foreman error tells to open a bug with foreman issue tracking system
Summary: [Branding] Foreman error tells to open a bug with foreman issue tracking system
Keywords:
Status: CLOSED DUPLICATE of bug 1129393
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.8
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: Unspecified
Assignee: Ohad Levy
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-04 03:24 UTC by David Joo
Modified: 2017-02-23 19:57 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-12 13:38:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Screenshot of error page (25.19 KB, image/png)
2015-06-04 03:24 UTC, David Joo
no flags Details

Description David Joo 2015-06-04 03:24:15 UTC
Created attachment 1034551 [details]
Screenshot of error page

Description of problem:
When Satellite 6 faces an issue, it shows a page saying to open an issue with;
"If you feel this is an error with Satellite 6 itself, please open a new issue with Foreman ticketing system, You would probably need to attach the Full trace and relevant log entries."

Version-Release number of selected component (if applicable):
Satellite 6.0.8
foreman-1.6.0.53-1.el6sat.noarch

How reproducible:
Every time


Steps to Reproduce:
1. Create a puppet product
2. Upload a puppet module
3. Delete the module from CLI /etc/puppet/environments/<env>/<module>
4. Try to promote CV
5. The promotion will be "paused", try to "unlock" then "resume"

It will show the error page

Actual results:
The page asks to open an issue with Foreman.org


Expected results:
It should say to open a case with access.redhat.com rather than foreman


Additional info:

Comment 1 RHEL Program Management 2015-06-04 03:42:31 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 3 Brad Buckingham 2015-06-12 13:38:38 UTC
Closing this bug as a duplicate of bug 1129393, which is fixed with Satellite 6.1.

*** This bug has been marked as a duplicate of bug 1129393 ***


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