Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1600246

Summary: Satellite UI setting and candlepin db entry for Organization SLA can get out of sync.
Product: Red Hat Satellite 6 Reporter: mharris <mharris>
Component: Activation KeysAssignee: satellite6-bugs <satellite6-bugs>
Status: NEW --- QA Contact: Perry Gagne <pgagne>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.3.2CC: jdickers, mharris
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
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: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description mharris 2018-07-11 20:08:27 UTC
Description of problem:

After completing a full upgrade of Red Hat Satellite 6.3.1 to 6.3.2 AND after updating the certs from SHA1 to SHA2 (using the directions at https://access.redhat.com/solutions/2887861 ). We attempted to register systems to the satellite server once again.

This customer is set with all subscriptions being "Premium level support" for their subscriptions. There are no standard/unsupported subscriptions available to the customer.

When the customer attempted to register a system, the error message: 

"Service level 'Standard' is not available to units of organization <ORG NAME>"

When looking at the activation key, used for the system, it was found, that it had a blank/empty setting for "Service Level" yet, it didn't default to what was available (subscription-wise).

We are thinking that there is a mismatch between the webui and the candlepin db on the SLA setting, but we need some help troubleshooting.

After setting the value to Premium, saving that option on the activation key, and then setting the value back to empty, it started working again, and we were then able to register systems to the satellite server.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Jason Dickerson 2018-07-12 03:45:10 UTC
Originally the customer had a mix of Standard and Premium Subscriptions, until May of this year.  We are unsure if the customer set the organization SLA preference to Standard in the past.  The Activation keys all had the SLA "unset".  After the aforementioned upgrades, it was noticed that no systems could be registered, due to the error.  This may have been the case since the Standard Subscriptions were removed, it is hard to say at this point.  When we investigated, it was determined that the Organization default SLA in the Satellite UI was set to No preference; however, the candlepin owner db entry was set to Standard.  At this point we set the org default to Premium, saved, set it back to no preference, and saved again.  This cleared the entry in the candlepin db, essentially "unsetting it".  This resolved the issue.  

This bz is to address situations where the UI and the candlepin db entries for Org SLA preference are not in sync.