Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Compared to Satellite 6.3.5.1, Satellite 6.5.0 can not set a service level of "Self-Support" or "none" for Products that aren't contained on the official Red Hat manifest.
Description of problem:
Compared to Satellite 6.3.5.1, Satellite 6.5.0 can not set a service level of "Self-Support" or "none" for any products. This reduces the functionality of the Satellite product in-comparison to the upstream Katello/Foreman projects, and appears to be a step backwards (towards vendor lock-in?).
It's understandable that Red Hat doesn't support downstream CentOS distributions, however this appears to intentionally prevent the same functionality present in upstream projects.
Version-Release number of selected component (if applicable):
satellite-6.5.0-11.el7sat.noarch
candlepin-2.5.15-1.el7sat.noarch
katello-3.10.0-0.6.rc1.el7sat.noarch
How reproducible: 100% reproducible
Steps to Reproduce:
1. Create a product.
2. Create an activation-key tied to the product.
3. Attempt to set a service level to "none" or "Self-Support"
Actual results:
[root@satellite_6_5_0 ~]# hammer activation-key update --name "NESSUS" --organization="EPA-LAB" --service-level="none"
Could not update the activation key:
Task 3c5d4ff2-c580-43ea-a1bc-a9810fd22a60: Katello::Errors::CandlepinError: Service level "none" is not available to units of organization EPA-LAB.
Expected results:
[root@satellite_6_3_5_1 ~]# hammer activation-key update --name "NESSUS" --organization="EPA" --service-level="none"
Activation key updated
Additional Info:
This appears to be related to the following changes made in BZ https://bugzilla.redhat.com/show_bug.cgi?id=1650974
I'm reaching out for clarification on this change as it's reduced functionality of Satellite 6 and preventing us from upgrading beyond 6.3.5.1.
"Kevin Howell 2018-11-29 15:59:44 UTC
Because we will soften SLA requirements in Candlepin, for Satellite 6.5 and forward, this will not be an issue. If the customer attempts to register with an SLA that they don't have access to on an older Satellite, their registration will be blocked. This is working as SLA was originally designed. If the customer wishes to use RHEL8 with an older Satellite, then they must either set SLA properly or not set
For subscription-manager, the real issue is bug 1621783, which must be fixed in order to have RHEL8 SLA values match expected SLA values for older Satellite.
There is a related change in Candlepin (server-side) to tolerate mismatching SLA; this is a behavior change in newer version of Candlepin, and will be present in Satellite 6.5 and later (and will be deployed to hosted soon).
Please reach out if you need clarification on this.
*** This bug has been marked as a duplicate of bug 1621783 ***"
Hi Aaron,
Thank you opening the bug. The service level validation might be causing the issue here and its not intend to be a lock-in mechanism. Can you please describe your use case in more detail. This will help us identify the exact problem that you are seeing.
thanks,
Rehana
Hi Rehana,
On the version 6.3 you can create an activation key for CentOs(or none RedHat products) and specify in "Service Level: none" instead "Premium" or "Standard". When we upgraded to 6.7 this functionality is missing and we can't use the activation key. The "service Level" option has only two options "Primium" or "Standard" and the "none" is removed. I am attaching two screenshots one from the version 6.3 and one from 6.7. Please let me know if you need more info to reproduce the issue.