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.
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 1RHEL 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.
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: