Bug 1418282

Summary:	[RFE] allow activation keys to have an undefined (null) SLA
Product:	Red Hat Customer Portal	Reporter:	Rich Jerrido <rjerrido>
Component:	Subscriptions/RHSM	Assignee:	Thomas "Shea" DeAntonio <tdeanton>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jon Allen <jallen>
Severity:	urgent	Docs Contact:	Anni Bond <anbond>
Priority:	high
Version:	unspecified	CC:	ealcaniz, it-eng-bz, jeperry, rblackbu, sjr, smcdowel, timoran
Target Milestone:	Needs Grooming	Flags:	ealcaniz: release-blocker?
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-05-30 20:21:56 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 Rich Jerrido 2017-02-01 12:54:43 UTC

Description of problem:


When creating an activation key using the activation key page (https://access.redhat.com/management/activation_keys), I would like the ability to not have to set an SLA. Today, the current UI forces me to select an SLA (Premium|Standard|Self-Support).

This can have unintended effects as the activation key that is defined on the key sets the SLA on the consumer. And if the consumer is a virtual guest you will have unpredictable behavior when it is migrated to a host with a different SLA. 

Also, Candlepin matches SLA exactly, so setting an SLA of Standard means 'exactly standard', not 'standard or better', which is confusing to the end user.

Comment 3 smcdowel 2017-05-30 20:21:56 UTC

This has been released to Production today as part of RHSM Web 14.2.0.