Hide Forgot
Description of problem: Version-Release number of selected component (if applicable): How reproducible: 3/3 Prerequisites: Rhel6.3 with following subscription-manager rpm subscription-manager-0.99.14-1.git.2.cf76d8e.el6_2.x86_64 subscription-manager-migration-data-1.12.1.3-1.git.0.1b05607.el6_2.noarch subscription-manager-migration-0.99.14-1.git.2.cf76d8e.el6_2.x86_64 subscription-manager-gnome-0.99.14-1.git.2.cf76d8e.el6_2.x86_64 subscription-manager-firstboot-0.99.14-1.git.2.cf76d8e.el6_2.x86_64 Steps to Repro : Client with 37060.pem register client to candlepin using cnsumer type candlepin via cli (no autosubscribe) set SLA preference premium in gui and press "autosubscribe" button. Expected REsult : It should display only premium SLA subscription to subscribe. Actual REsult : Autosubscribe subscribe Standard SLA subscription with preference Premium in gui . Attached error screenshot.
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.
As per comment 3 I'm going to close this as notabug.