Bug 629670

Testing Version...
[root@jsefler-onprem03 entitlement]# rpm -qa | grep subscription-manager
subscription-manager-0.95.1-1.git.17.4a23267.el6.x86_64
subscription-manager-firstboot-0.95.1-1.git.17.4a23267.el6.x86_64
subscription-manager-gnome-0.95.1-1.git.17.4a23267.el6.x86_64
[root@jsefler-onprem03 entitlement]# rpm -q python-rhsm
python-rhsm-0.95.3-1.git.0.4d0ef8e.el6.noarch


Our test strategy using an onpremise candlepin deployed with TESTDAT=1 and a rhel61 client with subscription-manager installed was...
1. install only ONE of the generated product certs (27060.pem)

2. register and subscribe to "Awesome OS Workstation Bits" - that will make the system compliant:
[root@jsefler-onprem03 entitlement]# subscription-manager facts --list | grep compliant
system.compliant: True

3. Note the validity period and warning period of the entitlement
[root@jsefler-onprem03 entitlement]# openssl x509 -text -in /etc/pki/entitlement/52129848558823871.pem | grep -A1 1.3.6.1.4.1.2312.9.4.12
            1.3.6.1.4.1.2312.9.4.12: 
                ..30
                  ^^ warning_period is 30 days
[root@jsefler-onprem03 entitlement]# openssl x509 -text -in /etc/pki/entitlement/52129848558823871.pem | grep -A2 Validity
        Validity
            Not Before: Feb 23 18:26:28 2011 GMT
            Not After : Feb 23 00:00:00 2012 GMT

4. restart the process for rhsm-compliance-icon with 3 second check-period
# rhsm-compliance-icon -c 3&

5. use the system clock on the box to change the date to...
- a date after the Not After date
    PASSED - rhsm-compliance-icon appears
- a date 31 days before the Not After date
    PASSED - rhsm-compliance-icon disappears
- a date before the Not Before date
    FAILED - rhsm-compliance-icon should appear
- a date within 30 days before the Not After date
    FAILED - rhsm-compliance-icon should appear
- a date after the Not After date
    PASSED - rhsm-compliance-icon appears

moving back to ASSIGNED

I've got a patch for the 'within' 30 days case (looks like we had a regression after a refactor). For the 'date before the Not Before date', can you open a separate bug for that? it's a different issue, and i'm not certain if we want to treat that case identically to having expired/no entitlements.

displaying a warning when you're within the warning_period is now fixed in both master and rhel6 branches. should be available in 0.96.2 and 0.95.4 builds.

bug https://bugzilla.redhat.com/show_bug.cgi?id=682772 has been opened at the request of comment #5

Created attachment 482949 [details]
screenshot shows fix for test case - a date within 30 days before the Not After date

Verified Version...
[root@jsefler-onprem03 ~]# rpm -qa | grep subscription-manager
subscription-manager-gnome-0.95.3-1.git.15.e70d002.el6.x86_64
subscription-manager-firstboot-0.95.3-1.git.15.e70d002.el6.x86_64
subscription-manager-0.95.3-1.git.15.e70d002.el6.x86_64


In the attached screenshot, you will see the date is set to "30 days" before the "Not After" Validity date which means that the rhsm-compliance-icon should appear with a message stating "Some of the system's subscriptions are about to expire".  And now this works as evidenced in the screenshot.

- a date within 30 days before the Not After date
    PASSED - rhsm-compliance-icon should appear

moving to VERIFIED

Can someone please change the compon

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2011-0611.html