Hide Forgot
Description of problem: When partially subscribed to a future entitlement (with no current entitlements), Subscription Assistant does not include that produce in its product list. Version-Release number of selected component (if applicable): python-rhsm-0.96.13-1.git.0.a237980.el6.noarch subscription-manager-firstboot-0.96.14-1.git.0.51fc69c.el6.x86_64 subscription-manager-0.96.14-1.git.0.51fc69c.el6.x86_64 subscription-manager-gnome-0.96.14-1.git.0.51fc69c.el6.x86_64 candlepin: {:version "0.4.19", :result true, :release "1"} @ commit 2fe099e481ebfca893b5384a8e1d1e6de8973a70 How reproducible: Always Steps to Reproduce: 1. Have a single product associated with a stackable subscription (I used 100000000000002.pem in the candlepin TESTDATA) 2. Make sure you have enough sockets so that you need multiple subscriptions to satisfy the product. 3. Register your rhsm 4. partially subscribe to a future subscription (that is: add a year+ to your search filter and only subscribe with quantity=1) 5. Open subscription assistant and search on today's date (default date). Actual results: No products are listed in the product list Expected results: Your product is shown in the product list as it doesn't have a current/valid entitlement. Additional info: Could be a candlepin issue?
Another issue, if I bind with quantity 1 my status switches from red to yellow, even though my entitlement doesn't start until 2012. This should still be red, we examine compliance status for today...
So it looks like two issues at play: 1. cert sorter thinks a system with partially valid entitlements for the future is in yellow state. it should be red, we have no valid entitlements *right now*. 2. subscription assistant does not look at partially entitled, it only looks at unentitled.
Appears to be fixed as a result of the work on bug #740377. Status stays red after getting the partial future entitlement. The subscription assistant then still lists subscription and finds appropriate pools for today's date. The quantity suggested was 1 instead of 2 in sub assistant, but I believe this is because of bug #745995. (quantity suggestion is not date aware) Moving to modified.
Created attachment 541533 [details] future_entitlement tested against versions: subscription-manager-0.98.5-1.git.2.cd86f84.el5_7 subscription-manager-firstboot-0.98.5-1.git.2.cd86f84.el5_7 subscription-manager-gnome-0.98.5-1.git.2.cd86f84.el5_7 In regards to comment 1 , the overall cert status is good in both the facts and the icon. The individual status for the product, however, has been blanked out. See attached screenshot.
Created attachment 541535 [details] quantity The subscriptions are now showing in the subscription assistant, but the quantity value is now wrong. It looks like it is calculating it like: Quantity = (Quantity need to fulfill need) - (Current entitlement Quantity) -(Future Entitlement Quantity) The future entitlement quantity should not be taken into account here, only the current ones, and this could cause interesting things like the quantity being zero (see screen shot) which causes an error.
Due to comment 6 and comment 7, I'm throwing this back.
Created attachment 542694 [details] future entitlements
comment 7 resolved in bug 745995
Future entitlements status icon no longer blanking out. Fixed in master branch: 4c5f0be9c90b94a1eb9e3ec5ca8ab56b80418f14
Created attachment 549081 [details] icon works subscription-manager-gnome-0.99.2-1.git.10.c47a606.el5_7 Attachment shows that the partial future entitlments still show an icon. marking VERIFIED.
moving back to MODIFIED awaiting verification against subscription-manager-gnome-0.98
Committed into 5.8 branch: 4b51014699fb650e59cbc4ce797c8570dd0f64b4
Following steps and rpm used for verification subscription-manager-firstboot-0.98.9-1.el5 subscription-manager-0.98.9-1.el5 subscription-manager-gnome-0.98.9-1.el5 subscription-manager-debuginfo-0.98.9-1.el5 subscription-manager-migration-data-1.6-1.el5 subscription-manager-migration-0.98.9-1.el5 used 4 cpu kvm machine subscribed 2 subscription to make this partial subscribe. Displays future entitlement as per JC comment 12 marking this defect verified attached screenshot Selection_0012
Created attachment 549667 [details] Selection_012 defect resolve screenshot
Moving bug to new. icon is still blanking out.Pls find the screenshot in attachment. RPM used: subscription-manager-migration-0.98.9-1.el5 subscription-manager-gnome-0.98.9-1.el5 subscription-manager-debuginfo-0.98.9-1.el5 subscription-manager-firstboot-0.98.9-1.el5 subscription-manager-0.98.9-1.el5
Created attachment 549799 [details] icon is blanking out for future subscription
The fix from comment 14 is not included in: 0.98.9-1 This will have to be tested using the latest code from the RHEL5.8 branch, or once the next 5.8 build is done. Moving back to MODIFIED so it can be reverified.
Can now be verified with 0.98.10-1
Created attachment 550631 [details] Icon is not blanking out anymore
Created attachment 550632 [details] Error while subscribing the product for a future date RPM used: [root@tiger ~]# rpm -qa | grep subscription-manager subscription-manager-0.98.10-1.el5 subscription-manager-firstboot-0.98.10-1.el5 subscription-manager-migration-data-1.4-1.el5 subscription-manager-debuginfo-0.98.10-1.el5 subscription-manager-gnome-0.98.10-1.el5 subscription-manager-migration-0.98.10-1.el5
Subscription is successful,but an error message is getting displayed as in attachment 550632 [details]
It looks as though your version of python-rhsm is out of date. Please update to version >= 0.98.9-1 and re-verify.
subscription-manager-gnome-0.98.10-1.git.4.71f8f71.el5 subscription-manager-0.98.10-1.git.4.71f8f71.el5 python-rhsm-0.98.9-1.git.0.81c61d5.el5 subscription-manager-firstboot-0.98.10-1.git.4.71f8f71.el5 Tested again against above versions ^ It checks out.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: No description necessary
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. http://rhn.redhat.com/errata/RHBA-2012-0154.html