Bug 1464202 - [paid] The "Support" link does not check for support entitlement before offering the https://access.redhat.com URL
[paid] The "Support" link does not check for support entitlement before offer...
Status: NEW
Product: OpenShift Online
Classification: Red Hat
Component: Unknown (Show other bugs)
Unspecified Unspecified
low Severity low
: ---
: ---
Assigned To: Abhishek Gupta
Xiaoli Tian
: OnlinePro
Depends On:
  Show dependency treegraph
Reported: 2017-06-22 11:59 EDT by Will Gordon
Modified: 2018-05-04 17:31 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Will Gordon 2017-06-22 11:59:11 EDT
Description of problem:

Users of the Pro clusters are offered the "Support" option per this Issue[1] and PR[2]. Not all users will have support entitlements, and should instead be directed to https://help.openshift.com. Additionally, it wouldn't be wrong to *always* offer the "Help" option directing users to https://help.openshift.com, and only adding the "Support" option of https://access.redhat.com for those users that actually have the support entitlement

[1] https://github.com/openshift/online/issues/1265
[2] https://github.com/openshift/online/pull/1266
Comment 1 Abhishek Gupta 2017-06-22 12:34:39 EDT
As of now, Basic support is being offered for free and hence this is not an issue. Going forward, we may continue offering Basic support for free indefinitely or, if not, we could relabel "Support" to something specific (Red Hat Support) and add a new entry in the drop-down for Help (or perhaps "Community Support)
Comment 2 Will Gordon 2017-06-22 13:12:12 EDT
But I believe it's still a case that user *must* actually select to add the support option, even though it's free. So I suspect it's possible that a user could *not* select the support option, and then have an issue.

Or are we forcibly adding the support option to all users on paid?

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