Bug 957596
| Summary: | Multi-Attribute Stackable (16 cores, 4 sockets, 8GB RAM) is not listed in the consumed list after being attached | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Shwetha Kallesh <skallesh> | ||||
| Component: | subscription-manager | Assignee: | Michael Stead <mstead> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | IDM QE LIST <seceng-idm-qe-list> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 7.0 | CC: | jgalipea, jsefler, mstead, redakkan, skallesh, spandey | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-05-17 17:53:27 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 840995 | ||||||
| Attachments: |
|
||||||
|
Description
Shwetha Kallesh
2013-04-29 06:43:16 UTC
The subscription attached was about to expire,hence it was not attached Expected Result: message should be displayed if we try to attach an expired subscription or an expiring subscription saying you are trying to attach an expired subscription Please provide additional information about how this was tested. What were the current dates on the server and client? Was the subscription expired according to candlepin, or subscription manager, or both? Created attachment 747701 [details]
Creating expired pool
[root@localhost ~]# subscription-manager list --avail
+-------------------------------------------+
Available Subscriptions
+-------------------------------------------+
Subscription Name: Multi-Attribute Stackable (2 GB, 2 Cores)
SKU: 2cores-2ram-multiattr
Pool ID: 8ac6a3a23ea16c61013ea16d87a0040e
Quantity: 5
Service Level: Premium
Service Type: Level 3
Multi-Entitlement: Yes
Ends: 05/14/2014
System Type: Physical
Subscription Name: Multi-Stackable
SKU: multi-attribute
Pool ID: 8ac6a3a23ea16c61013ea322e8db1acd
Quantity: 20
Service Level:
Service Type:
Multi-Entitlement: Yes
Ends: 05/14/2013 <--- this pool is going to expire anytime today
System Type: Physical
[root@localhost ~]# subscription-manager attach --pool 8ac6a3a23ea16c61013ea322e8db1acd
Successfully attached a subscription for: Multi-Stackable
Moment I attach the pool it gets expired and I don't find it in consumed list
[root@localhost ~]# subscription-manager list --consumed
No consumed subscription pools to list
[root@localhost ~]# date
Tue May 14 18:44:39 IST 2013
[root@candlepin ~]# date
Tue May 14 18:44:36 IST 2013
This appears to behaving as expected. If an entitlement is not past its end date (expiry), we should be able to consume it regardless of how close you are to the end date. I'm not sure how benifitial it would be to display a warning that it is about to expire. I can attach a subscription that will expire in 60 sec, and list --consumed will show it. Once past the expiry, it will not be listed anymore. Attempting to re-attach will display an expiration error. I suggest that we close this BZ as NOTABUG. If we strongly feel that we should present a warning, I suggest that we put it on the backlog and tackle it later. Thoughts? |