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 1292039 - GUI: "Next checkin Time" field in about window should be cleared and set to "Unknown" on a system that is registered and unregistered again
Summary: GUI: "Next checkin Time" field in about window should be cleared and set to "...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: subscription-manager
Version: 6.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: William Poteat
QA Contact: John Sefler
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-16 10:09 UTC by Shwetha Kallesh
Modified: 2016-01-04 14:49 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-04 14:49:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Next system Check-in field (128.37 KB, image/png)
2015-12-16 10:09 UTC, Shwetha Kallesh 		no flags Details
View All

Description Shwetha Kallesh 2015-12-16 10:09:08 UTC 
Created attachment 1106348 [details]
Next system Check-in field

Description of problem:
GUI: "Next checkin Time" field in about window should be cleared and set to "Unknown" on a system that is registered and unregistered again

Version-Release number of selected component (if applicable):

[root@dell-pe1850-04 ~]# subscription-manager version
server type: This system is currently not registered.
subscription management server: 2.0.10-1
subscription management rules: 5.19
subscription-manager: 1.16.6-1.el6
python-rhsm: 1.16.4-1.el6

How reproducible:


Steps to Reproduce:
a) Register a system
b) Launch GUI , go to Help -----> about ----> note the "Next checkin Time" 
c) Close the window and unregister the system
d) go to Help -----> about ----> note the "Next checkin Time" , its not cleared and notice that the value noted down in step b) still persists
e) close the GUI window and launch GUI again
f) go to Help -----> about ----> note the "Next checkin Time" , its not cleared and notice that the value noted down in step b) still persists

Actual results:
Value set before unregistering the system,
P.S Attachment

Expected results:

Value should be cleared after system is unregistered and set to "Unknown" or "System is not registered yet" or something similar

Additional info:
Comment 2 William Poteat 2016-01-04 14:49:06 UTC 
The cycle and running of rhsmcertd is not based on the status of the system. Unregistering just appears on the client side as a lack of consumer cert. rhsmcertd will start as indicated and then realize that the cert is absent and then reset its time and stop.

There is a use case where the consumer cert is created at the Portal/Satellite and  copied to the machine. The next check in time would be important information during this process.
Note You need to log in before you can comment on or make changes to this bug.