Description of problem: Message displayed after you subscribe to a pool which has already expired needs to be changed Version-Release number of selected component (if applicable): [root@localhost ~]# subscription-manager version server type: Red Hat Subscription Management subscription management server: 0.8.4-1 subscription-manager: 1.8.6-1.git.1.da0bb05.el7 python-rhsm: 1.8.9-1.git.1.bbbb773.el7 How reproducible: Steps to Reproduce: 1.[root@localhost ~]# date Fri Apr 19 15:06:22 IST 2013 [root@localhost ~]# curl -k -u admin:admin https://10.70.35.193:8443/candlepin/pools/8ac6818a3e21268f013e2193f02418bd | python -mjson.tool | grep endDate % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 2640 0 2640 0 0 63207 0 --:--:-- --:--:-- --:--:-- 64390 "endDate": "2013-04-19T09:32:06.000+0000", [root@localhost ~]# subscription-manager subscribe --pool=8ac6818a3e21268f013e2193f02418bd Successfully attached a subscription for: Awesome OS Server Bundled (2 Sockets, Standard Support) [root@localhost ~]# ll /etc/pki/entitlement/ total 0 [root@localhost ~]# subscription-manager list --consumed No consumed subscription pools to list Actual results: Successfully attached a subscription for:<Subscription-Name> Expected results: Unable to entitle consumer to the pool with id '<pool Id>'.: Subscriptions for <Subscription-Name> Additional info:
Any reason we shouldn't just block users from attaching expired pools?
This appears to be fixed with latest subscription-manager and candlepin. I'm not sure eactly when, but exception handling in the client has undergone some changes. example: Unable to attach pool with ID '8a908740438be86501438cd57718376c'.: Subscriptions for awesomeos-onesocketib expired on: 1/13/14 1:21 PM.