Bug 1144042
Summary: | [RFE] API Missing activation key listing available service_levels | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Peter Vreman <peter.vreman> |
Component: | API - Content | Assignee: | Christine Fouant <cfouant> |
Status: | CLOSED ERRATA | QA Contact: | Jitendra Yejare <jyejare> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.0.4 | CC: | bbuckingham, bkearney, cwelton, dgoodwin, jduncan, jyejare, mmccune, peter.vreman, xdmoon |
Target Milestone: | Unspecified | Keywords: | FutureFeature, Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
URL: | http://projects.theforeman.org/issues/8407 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-02-21 12:28:04 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1122832 |
Description
Peter Vreman
2014-09-18 13:55:22 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release. Created redmine issue http://projects.theforeman.org/issues/8407 from this bug So, the service levels are actually tied to the organization to which an activation key is created; thus, querying an activation key for the service levels available doesn't quite make sense because the service levels are not scoped by the activation key. However, we do show the service level attached to a key within its information. Would an API call to show service levels for an organization be a sufficient fix for your request? It shall have the same results as shown by the WebUI in the selection list. If the WebUI is based on the service_levels at the organization level, then having a service_levels API call at organization level is good. The documentation can have a cross reference from the activation key service_level field to the organization API call that lists the valid service_levels. Candlepin API for this call is: GET /owners/{key}/servicelevels Switching this bug to an RFE for activation key's service level agreement choices to reflect the options in its attached subscriptions. There will be API and CLI calls for an activation key which will list only the appropriate choices for an activation key based on the subscriptions attached to the key. The UI will also only show choices based on the attached subscriptions per key. As it currently stands, service levels are shown by the API to show an organization. Upstream bug component is API - Content Upstream bug component is API Upstream bug component is API - Content This should address customer's needs: Service Levels field has been added into call for `hammer organization info`. API results for organization's info also lists service levels available. Verified ! @Satellite 6.3 snap 26 Steps : According to comment 15, info organization from CLI and API that will show available service levels. Observed: From Hammer CLI: # hammer organization info --id 80 . . . . . Domains: rhq.lab.eng.bos.redhat.com Environments: Hostgroups: hg1 Parameters: Created at: 2017/11/21 10:53:39 Updated at: 2017/11/21 10:53:39 Label: Default_Organization Description: Red Hat Repository URL: https://cdn.redhat.com Service Levels: Self-Support ------------------------------------- From API: Snippet -> "service_levels":["Self-Support"],"service_level":null The organization that doesnt have subscription it shows empty list from API [] and blank from CLI. Hence closing the bug as Verified. 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. https://access.redhat.com/errata/RHSA-2018:0336 |