RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 810290 - Next Update date makes no sense
Summary: Next Update date makes no sense
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: subscription-manager
Version: 6.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Shwetha Kallesh
QA Contact: Entitlement Bugs
URL:
Whiteboard:
Depends On:
Blocks: 738066
TreeView+ depends on / blocked
 
Reported: 2012-04-05 14:29 UTC by J.C. Molet
Modified: 2012-06-20 13:08 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 13:08:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
next-update (718.07 KB, image/png)
2012-04-05 14:29 UTC, J.C. Molet 		no flags Details
next-update date (115.16 KB, image/png)
2012-04-11 09:10 UTC, Shwetha Kallesh 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0804 0 normal SHIPPED_LIVE subscription-manager bug fix and enhancement update 2012-06-19 19:51:31 UTC

Description J.C. Molet 2012-04-05 14:29:15 UTC 
Description of problem:
The Next update date given in the rhsm-gui doesn't seem to add up.  If I add up the frequencies of the rhsmcertd for either the autoheal or the cert refresh to the current date, I'll get a completely different date than what it says the next update will be.

Version-Release number of selected component (if applicable):
python-rhsm-0.99.7-1.git.1.e68bc91.el6.noarch
subscription-manager-gnome-0.99.12-1.git.18.188dde8.el6.x86_64
subscription-manager-0.99.12-1.git.18.188dde8.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. Set your rhsmcertd to refresh on a small interval (for maximum effect)
2. Restart the service
3. Start up subscription manager
  
Actual results:
The Next Update date seems to come out of nowhere

Expected results:
The Next Update would be a combination of the last date it updated (or the current date if it never updated) plus the refresh frequency

Additional info:
see screenshot.
Comment 1 J.C. Molet 2012-04-05 14:29:44 UTC 
Created attachment 575450 [details]
next-update
Comment 2 Chris Duryee 2012-04-09 19:44:35 UTC 
It appears that the interval is being added as hours instead of minutes from the conf file. I'm still looking for where this is going awry though.
Comment 3 Chris Duryee 2012-04-10 15:20:13 UTC 
7442a1b master 1.0.1+
Comment 5 Chris Duryee 2012-04-10 15:32:27 UTC 
almost forgot the branch!

517c24d RHEL6.3 0.99.14+
Comment 6 Shwetha Kallesh 2012-04-11 09:10:15 UTC 
Created attachment 576715 [details]
next-update date

verfied against

[root@dhcp201-196 ~]# rpm -qa | grep subscription-manager
subscription-manager-1.0.0-1.git.11.f42a186.el6.x86_64
subscription-manager-migration-data-1.12.1.2-1.git.2.99d0c10.el6.noarch
subscription-manager-debuginfo-0.99.13-1.el6.x86_64
subscription-manager-migration-1.0.0-1.git.11.f42a186.el6.x86_64
subscription-manager-gnome-1.0.0-1.git.11.f42a186.el6.x86_64
subscription-manager-firstboot-1.0.0-1.git.11.f42a186.el6.x86_64


[root@dhcp201-196 ~]# cat /etc/rhsm/rhsm.conf | grep rhsmcertd -A 4
[rhsmcertd]
# Frequency of certificate refresh (in minutes):
certFrequency = 240
# Frequency of autoheal check (1440 min = 1 day):
healFrequency = 1440
Comment 8 errata-xmlrpc 2012-06-20 13:08:54 UTC 
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-0804.html
Note You need to log in before you can comment on or make changes to this bug.