Bug 823659

Summary: Update SLA text in Settings to Service Level
Product: Red Hat Enterprise Linux 5 Reporter: Matt Reid <mreid>
Component: subscription-managerAssignee: William Poteat <wpoteat>
Status: CLOSED ERRATA QA Contact: Entitlement Bugs <entitlement-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 5.9CC: awood, fsharath, jmolet
Target Milestone: rc   
Target Release: 5.9   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-07 22:52:44 EST Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 771748, 827225    
Description Flags
settings_SLA none

Description Matt Reid 2012-05-21 15:48:09 EDT
Description of problem:
My mockups said SLA, so this is my fault, but the references to SLA in System Settings should be updated to just say Service Level.

System Service Level Agreement Preference: -> System Service Level Preference

Your system's SLA preference is followed when subscribing to new products. -> Your system's service level preference is followed when subscribing to new products.
Comment 1 William Poteat 2012-06-14 11:54:40 EDT
commit to master: 6e5d6b5362d3c52a56058c9128d719d246cf4116
Comment 2 RHEL Product and Program Management 2012-06-18 11:28:11 EDT
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release.  Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products.  This request is not yet committed for inclusion in
a release.
Comment 3 Sharath Dwaral 2012-06-25 09:12:44 EDT
Created attachment 594181 [details]


RHEL 5.9
# rpm -qa | egrep "subscription-manager|python-rhsm"

Bug Verified
Comment 5 errata-xmlrpc 2013-01-07 22:52:44 EST
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.