Created attachment 810123 [details]
Spec file to create scenario

Description of problem: A client is certificate V1-only capable. When the entitlement is issued, the content set count is < the limit [185]. Content sets are added to the associated product in excess of 185 and the /entitlements/product/#{product_id} is called. All entitlements for that product will be marked dirty. When either the /entitlements/#{entitlement_id} or /consumers/#{uuid}/entitlements are called, the dirty entitlements should be regenerated. Because of the exceeded limit, none of them will be. The certs will still be the same on both the client and server. They will not change to reflect any other changes made to the products.


Version-Release number of selected component (if applicable):0.8.28


How reproducible:

Steps to Reproduce:
1. See attached file. Run with rspec as 'buildr spec features=client_v1_size run_after_hook=false'

It will create the product and entitlement, add excessive content to the product, and mark the entitlement dirty. It also confirms that the entitlement is not on the CRL. The last flag will keep the data on the system.


Actual results:

Entitlements cannot be regenerated for the consumer


Expected results:

Only the entitlement with excessive content should remain frozen. The rest should behave as normal.


Additional info:


The entitlement can be deleted with DELETE /entitlements/{dbid}. This will remove it as a blocker to refreshing the other entitlements.