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.

Bug 1328857

Summary:	ISE on accessing Insights -> Manage, Help with Any context
Product:	Red Hat Satellite	Reporter:	Roman Plevka <rplevka>
Component:	RH Cloud - Insights	Assignee:	Lindani Phiri <lphiri>
Status:	CLOSED ERRATA	QA Contact:	Roman Plevka <rplevka>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.2.0	CC:	bbuckingham, bkearney, lphiri
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rubygem-foreman-redhat_access-1.0.6-2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-27 11:01:58 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Roman Plevka 2016-04-20 12:35:16 UTC

Description of problem:
When trying to access Insights pages with no Organization context selected, all pages display "Organization Selection Required" message but one - "Manage" page renders an error "Organization not found or invalid"

Version-Release number of selected component (if applicable):
sat 6.2.0 snap 8.2

How reproducible:
always

Steps to Reproduce:
1. switch context to "any context"
2. navigate to Red Hat Insights > Manage

Actual results:
500 - Organization not found or invalid

Expected results:
200 - Organization Selection Required

Comment 1 Roman Plevka 2016-04-20 12:40:17 UTC

- happens on other Insights pages as well, One might need to switch the context while on the page

Comment 5 Roman Plevka 2016-05-10 09:31:29 UTC

It works now on sat6.2.0 Beta (GA 10.1) and it displays a message "Organization selection required" for all Insight pages. Which leads me to a question -> Can't we simply hide the whole "Red Hat Insights" menu for Any Context? As right now, the menu is useless.

Comment 6 Roman Plevka 2016-05-10 09:36:08 UTC

Idea #2 - Or, to make it consistent with behaviour of other pages at least, display the Organization Selector.

Comment 7 Lindani Phiri 2016-05-10 10:44:15 UTC

There is an existing a bug for organization selection behaviour ( https://bugzilla.redhat.com/show_bug.cgi?id=1269663 ).

The ISE bug is an unrelated issue that should be validated separately.

Comment 8 Roman Plevka 2016-05-11 08:42:01 UTC

(In reply to Lindani Phiri from comment #7)
> There is an existing a bug for organization selection behaviour (
> https://bugzilla.redhat.com/show_bug.cgi?id=1269663 ).
> 
> The ISE bug is an unrelated issue that should be validated separately.

Fair enough, thanks for pointing to that BZ.
I can put this bug to VERIFIED now

Comment 11 Bryan Kearney 2016-07-27 11:01:58 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1501