Bug 1138793 - Fix the "Oops, we're sorry but something went wrong" to remove foreman reference
Summary: Fix the "Oops, we're sorry but something went wrong" to remove foreman reference
Keywords:
Status: CLOSED DUPLICATE of bug 1129393
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Ohad Levy
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-05 16:03 UTC by sthirugn@redhat.com
Modified: 2017-02-23 20:59 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-08 07:29:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
foreman reference in error page (39.03 KB, application/octet-stream)
2014-09-05 16:03 UTC, sthirugn@redhat.com
no flags Details

Description sthirugn@redhat.com 2014-09-05 16:03:00 UTC
Description of problem:
Fix the "Oops, we're sorry but something went wrong" to remove foreman reference

Version-Release number of selected component (if applicable):
GA Snap 7 - Satellite-6.0.4-RHEL-6-20140829.0

* apr-util-ldap-1.3.9-3.el6_0.1.x86_64
* candlepin-0.9.23-1.el6_5.noarch
* candlepin-common-1.0.1-1.el6_5.noarch
* candlepin-scl-1-5.el6_4.noarch
* candlepin-scl-quartz-2.1.5-5.el6_4.noarch
* candlepin-scl-rhino-1.7R3-1.el6_4.noarch
* candlepin-scl-runtime-1-5.el6_4.noarch
* candlepin-selinux-0.9.23-1.el6_5.noarch
* candlepin-tomcat6-0.9.23-1.el6_5.noarch
* elasticsearch-0.90.10-6.el6sat.noarch
* foreman-1.6.0.42-1.el6sat.noarch
* foreman-compute-1.6.0.42-1.el6sat.noarch
* foreman-gce-1.6.0.42-1.el6sat.noarch
* foreman-libvirt-1.6.0.42-1.el6sat.noarch
* foreman-ovirt-1.6.0.42-1.el6sat.noarch
* foreman-postgresql-1.6.0.42-1.el6sat.noarch
* foreman-proxy-1.6.0.30-1.el6sat.noarch
* foreman-selinux-1.6.0.14-1.el6sat.noarch
* foreman-vmware-1.6.0.42-1.el6sat.noarch
* katello-1.5.0-30.el6sat.noarch
* katello-ca-1.0-1.noarch
* katello-certs-tools-1.5.6-1.el6sat.noarch
* katello-installer-0.0.62-1.el6sat.noarch
* openldap-2.4.23-34.el6_5.1.x86_64
* openldap-devel-2.4.23-34.el6_5.1.x86_64
* pulp-katello-0.3-4.el6sat.noarch
* pulp-nodes-common-2.4.1-0.5.rc1.el6sat.noarch
* pulp-nodes-parent-2.4.1-0.5.rc1.el6sat.noarch
* pulp-puppet-plugins-2.4.1-0.5.rc1.el6sat.noarch
* pulp-puppet-tools-2.4.1-0.5.rc1.el6sat.noarch
* pulp-rpm-plugins-2.4.1-0.5.rc1.el6sat.noarch
* pulp-selinux-2.4.1-0.5.rc1.el6sat.noarch
* pulp-server-2.4.1-0.5.rc1.el6sat.noarch
* python-ldap-2.3.10-1.el6.x86_64
* ruby193-rubygem-net-ldap-0.3.1-3.el6sat.noarch
* ruby193-rubygem-runcible-1.1.0-2.el6sat.noarch

How reproducible:
Always

Steps to Reproduce:
1. Create a role
2. Click New Filter
3. Select Resource type = Content Host
4. Select few permissions like create_content_hosts, edit_content_hosts, destroy_content_hosts
5. Uncheck Unlimited?
6. Type a hostname in Search box
7. Click Submit


Actual results: (see screenshot)

Oops, we're sorry but something went wrong
 
Error
Katello::System(id: integer, uuid: string, name: string, description: text, location: string, environment_id: integer, created_at: datetime, updated_at: datetime, type: string, content_view_id: integer, host_id: integer) doesn't have column :organization_id.

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.


Expected results:
Fix this page to remove "Foreman ticketing system" reference

Additional info:
I will file an other bug to actually fix this error scenario.  This bug is more for fixing this error page to remove foreman reference.

Comment 1 RHEL Program Management 2014-09-05 16:03:16 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 2 sthirugn@redhat.com 2014-09-05 16:03:29 UTC
Created attachment 934866 [details]
foreman reference in error page

Comment 4 Corey Welton 2014-09-05 16:59:59 UTC
There may be a bz somewhere about this particular error message (it keeps rearing its ugly head every once in a while).  Can look for it later.

Comment 5 Dominic Cleal 2014-09-08 07:29:29 UTC

*** 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.