Bug 956200 - setting system SLA to empty string should indicate use of org default SLA
Summary: setting system SLA to empty string should indicate use of org default SLA
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Subscription Management
Version: Nightly
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Bryan Kearney
QA Contact: Tazim Kolhar
URL:
Whiteboard:
Depends On:
Blocks: rhsm-rhel510
TreeView+ depends on / blocked
 
Reported: 2013-04-24 12:50 UTC by Tom McKay
Modified: 2019-09-26 18:20 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-18 21:19:00 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Tom McKay 2013-04-24 12:50:20 UTC 
Setting an organization's default service level to an empty string ("") indicates there is no SLA preference.

What should setting a system's SLA to empty string indicate? Should it A) Override the organization's default and set it to no preference?, or B) Indicate that the system use's the org's default?

I believe it should be B but candlepin currently treats it as A. When a system first registers, it gets the org's default SLA. However, if the SLA on the system is set directly (to either "" or any other value), that value persists and the org default is never available as a choice again.

--> Agreement on B as correct, hence this BZ.
Comment 1 Mike McCune 2013-04-26 22:28:26 UTC 
We probably need an upstream bug on this, not sure if dgoodwin will notice this Sat6 bug.
Comment 2 Bryan Kearney 2013-04-29 17:29:33 UTC 
https://github.com/candlepin/candlepin/pull/237
Comment 3 Bryan Kearney 2013-05-01 14:21:52 UTC 
commit f19a55dcac8d9184b48c972f12f1e2e5da04c148
Author: Bryan Kearney <bkearney>
Date:   Mon Apr 29 13:26:46 2013 -0400

    956200: Enable the owner default SLA usage if none is provided or defined on the consumer
Comment 4 Sam Kottler 2013-05-23 23:41:45 UTC 
Moving to ON_QA for drop 2.
Comment 5 Tazim Kolhar 2013-05-28 10:42:20 UTC 
VERIFIED :

# rpm -qa | grep katello
ruby193-rubygem-foreman-katello-engine-0.0.7-1.el6sat.noarch
katello-common-1.4.2-7.el6sat.noarch
katello-1.4.2-7.el6sat.noarch
katello-candlepin-cert-key-pair-1.0-1.noarch
ruby193-rubygem-katello_api-0.0.3-2.el6_4.noarch
katello-glue-candlepin-1.4.2-7.el6sat.noarch
katello-configure-foreman-1.4.3-10.el6sat.noarch
katello-qpid-broker-key-pair-1.0-1.noarch
katello-qpid-client-key-pair-1.0-1.noarch
katello-certs-tools-1.4.2-2.el6sat.noarch
katello-cli-1.4.2-6.el6sat.noarch
signo-katello-0.0.12-1.el6sat.noarch
katello-selinux-1.4.3-3.el6sat.noarch
katello-glue-pulp-1.4.2-7.el6sat.noarch
katello-all-1.4.2-7.el6sat.noarch
katello-foreman-all-1.4.2-7.el6sat.noarch
katello-cli-common-1.4.2-6.el6sat.noarch
katello-glue-elasticsearch-1.4.2-7.el6sat.noarch
katello-configure-1.4.3-10.el6sat.noarch
ruby193-rubygem-katello-foreman-engine-0.0.1-1.el6_4.noarch

Details as given below :

The SLA on the system is set directly (to either "" or any other value), that value does not persists.
The org default is available as a choice again.
Comment 6 Mike McCune 2013-07-18 21:19:00 UTC 
mass move to CLOSED:CURRENTRELEASE since MDP1 has been released.
Note You need to log in before you can comment on or make changes to this bug.