Red Hat Bugzilla – Bug 747399
if consumer does not have architecture then we should not check for it
Last modified: 2015-05-14 11:22:39 EDT
Description of problem:
Unable to bind cloud subscriptions to rhui consumers
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Login to the https://rails-fte.gss.devlab.phx1.redhat.com/management/
2. User--rhn-cservice-acarter pw-redhat
3. Create a rhui consumer and try to bind a subscription to a consumer.
The cloud provider subscriptions do not bind to the consumer
The cloud provider subscription should bind to a consumer.
(1) Do you want all consumers with no architecture to be able to bypass this check? Or should this be a specific exception for consumer type "rhui". (is that the exact consumer type label?)
(2) Is this just specific to architecture, or do we have other rules to worry about? (virt_only, sockets, etc)
This should apply to any consumer with no arch set -- today this would include RHUI, Domain and SAM -- CloudForms later.
We've already updated the JS rules to not check for socket limit if it is not present. An email was just sent about not checking on required consumer type for 'export enabled = true' consumer types also. Essentially, 'export enabled = true' consumers should not check on anything, other than limiting virt pool display, at this time (ie we want you to be able to put all subscriptions on them).
I don't think there are any other filtering checks from the web perspective since we're not using 'installed product'. When that rolls out, we may need to revisit rules?
Fixed in master: 0d0094e620efc179afdf84fae8b4ff07b9fe1282
Any consumer without an arch fact and whose type is not system will be allowed to pass the rule.
Verified that this is fixed from our side in Dev2 with the new build.