Description of problem: When against the stage environment, the contract numbers in the contract selection selection dialog are blank. Version-Release number of selected component (if applicable): python-rhsm-1.1.4-1.git.0.57fc0de.el6.x86_64 subscription-manager-gui-1.1.5-1.git.14.ae9fffd.el6.x86_64 subscription-manager-1.1.5-1.git.14.ae9fffd.el6.x86_64 How reproducible: always? Steps to Reproduce: I have not seen this outside of the stage env, so I will show the steps for that... 1. Install rhsm on your virtual machine 2. Set your rhsm.conf thusly: [server] hostname=subscription.rhn.stage.redhat.com prefix=/subscription port=443 3. Have the rhel server product pem installed (69.pem) <-- optional 4. Register your system: subscription-manager register --user stage_test_12 5. Start up subscription-manager-gui 6. Click on the "All Available Subscriptions" tab and update your search 7. Click on the available subscription and click 'subscribe' Actual results: The 'contract' column is completely void of data Expected results: The contract numbers should show. Additional info: These numbers show properly AFTER you subscribe to the entitlement in the "My Subscriptions" tab.
Created attachment 640853 [details] missing contract numbers screenshot!
Doesn't look like this is client side. I can reproduce but: curl -u stage_test_12:redhat -k https://subscription.rhn.stage.redhat.com/subscription/pools/8a99f9843a7a3a9d013a8c036c383788 | json.py | less Which means the server is not populating this somehow. And yet if I subscribe, the resulting entitlement cert has an appropriate contract number.... [root@rhel6-dev ~]# subscription-manager subscribe --pool=8a99f9843a7a3a9d013a8c036c383788 [root@rhel6-dev ~]# subscription-manager list --consumed +-------------------------------------------+ Consumed Subscriptions +-------------------------------------------+ Subscription Name: Red Hat Enterprise Linux Server, Premium (8 sockets) (Up to 4 guests) Provides: Red Hat Enterprise Linux Server Red Hat Beta SKU: RH0103708 Contract: 10011052 Account: 5206751 Serial Number: 5066229454596988618 Active: True Quantity Used: 1 Service Level: Premium Service Type: L1-L3 Starts: 12/31/2011 Ends: 12/31/2012 This indicates that the candlepin pool has no subscription ID, but the backing subscription does. (now) Talking to Amanda it seems there is a known issue where some subscriptions did not have contract IDs which is now fixed. Looking at the code I don't think this triggers as a change during refresh pools. So this is a server side but, not client side, and we need to fix refresh pools to detect a changing contract ID as a change and update the pool in CP.
Ok we're boxed in here again by javascript limitations. The javascript rules are responsible for detecting changes to pools and updating them, see Pool namespace method updatePools. The correct fix for this would be to update PoolUpdate to add a new field for contract changed, or perhaps make one of the existing fields more generic so we don't need one per change. However we cannot do this because the rules will then go into a manifest, and out to older candlepins, which do not have this change to PoolUpdate and the rules will break. However since this is definitely a server side bug and we're focusing on client right now, re-aligning this to Candlepin and setting back to NEW for now.
I believe this is a dupe of 949684. I am moving this to ON_QA to be verified. commit 0ce7d02f7f1dc3df90f3cf4f583cb4fdda6c6dd7 Author: Bryan Kearney <bkearney> Date: Mon Apr 15 10:24:14 2013 -0400 949684: Update the contract information on pools when subcriptions changed.
Automation exists for this bug $ git show commit 7d75a30e231e410e2f12a0b3a95dbdf526f1e7bc Author: Sharath Nagaraj Dwaral <fsharath> Date: Fri Oct 11 17:20:37 2013 -0400 Automation for Bug 874624 - Contract Numbers are not showing in contract selection dialog Test path: /src/rhsm/gui/tests/subscribe_tests.clj Test name: check_contract_number This test passes for the below version: # subscription-manager version server type: Red Hat Subscription Management subscription management server: 0.8.29-1 subscription-manager: 1.9.9-1.el6 python-rhsm: 1.9.6-1.el6 VERIFIED
These bugs were fixed during 7.0 but not moved to CLOSED. They have been delivered