Bug 812834
| Summary: | Subscription-manager not able to filter SLA for candlepin type consumer. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | spandey | ||||
| Component: | subscription-manager | Assignee: | William Poteat <wpoteat> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | IDM QE LIST <seceng-idm-qe-list> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 5.9 | CC: | bkearney, dgoodwin, jmolet, jsefler, kbanerje, skallesh, spandey | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-05-24 16:17:30 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: | 771748 | ||||||
| Attachments: |
|
||||||
|
Description
spandey
2012-04-16 11:48:45 UTC
Created attachment 577687 [details]
error screenshot
Because candlepin consumers are used to transfer subscriptions to downstream candlepin's via the manifest, they are exempt from JS rule checks so they can transfer anything. Indeed this is where the SLA filtering happens, so that explains why Candlepin consumers are not seeing this. However the use case of using subscription manager to register as a Candlepin consumer is not something any end user should actually do. (that functionality is purely for dev/QE purposes) Similarly I don't think a Candlepin consumer with an SLA assigned to it is something that should actually be done either. (they also would never use autosubscribe) As such I propose this is definitely not something to worry about for 6.3, it may not be something worth fixing at all, as I don't think there's an actual use case here. Moving to 5.9. 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. |