Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 676377

Summary: rhsm-compliance-icon's status can be a day out of sync
Product: Red Hat Enterprise Linux 6 Reporter: John Sefler <jsefler>
Component: subscription-managerAssignee: Chris Duryee <cduryee>
Status: CLOSED ERRATA QA Contact: John Sefler <jsefler>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.1CC: cduryee, 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: 2011-05-19 13:39:45 UTC Type: ---
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: 568421    
Attachments:
Description Flags
Am I compliant or not? none

Description John Sefler 2011-02-09 17:00:45 UTC
Created attachment 477860 [details]
Am I compliant or not?

Description of problem:
While rhsm-compliance-icon is running with its default --check-period (once-a-day), it is easy to run subscription-manager cli/gui and autosubscribe yourself into compliance.  Yet the rhsm-compliance-icon remains in a non-compliant state.  

See attached screenshot.

This situation is confusing for the user who will not have the patience or knowledge that if they just wait one day, the rhsm-compliance-icon will disappear.  Yes... I know clicking it will zap it out of site, but that's not such a great usability feature either.

Changing the default --check-period to something smaller (like 5 seconds) would be a quick fix, but it's not too elegant.

It would be nicer if...
<jbowes> the client apps (the cli/gui) might also have to be smart enough to tell this daemon to recheck, so it can emit compliance change signals right after they've done something


Version-Release number of selected component (if applicable):
[root@jsefler-betastage-1 ~]# rpm -qa | grep subscription-manager
subscription-manager-firstboot-0.93.19-1.el6.x86_64
subscription-manager-0.93.19-1.el6.x86_64
subscription-manager-gnome-0.93.19-1.el6.x86_64


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Related bug: https://bugzilla.redhat.com/show_bug.cgi?id=642705

Comment 2 John Sefler 2011-02-15 15:03:08 UTC
Another related bug: https://bugzilla.redhat.com/show_bug.cgi?id=642816

Comment 6 John Sefler 2011-03-08 22:12:26 UTC
[root@jsefler-onprem03 bug629670]# rpm -qa | grep subscription-manager
subscription-manager-gnome-0.95.4-1.git.0.1fb5ee4.el6.x86_64
subscription-manager-firstboot-0.95.4-1.git.0.1fb5ee4.el6.x86_64
subscription-manager-0.95.4-1.git.0.1fb5ee4.el6.x86_64

Testing transition from compliance to non-compliance with a single subscribable product configured, the following is a summary of my test case results:

GUI---------------------------------
subscription-manager-gui subscribe
  PASS

subscription-manager-gui unsubscribe
  PASS

subscription-manager-gui register with autosubscribe
  PASS

subscription-manager-gui unregister
  PASS

CLI---------------------------------
subscription-manager subscribe --auto
  PASS

subscription-manager unsubscribe --all
  PASS

subscription-manager subscribe --pool=
  PASS

subscription-manager unsubscribe --serial=
  PASS

subscription-manager unsubscribe --serial=
  PASS

subscription-manager register --autosubscribe
  FAIL

subscription-manager unregister
  FAIL


moving back to ASSIGNED to fix the cli cases for register and unregister

Comment 7 Chris Duryee 2011-03-10 19:13:29 UTC
master ee42888 0.96.2+

rhel6 0.95.5+ 4721154845145a82ec9e00260d64817abf11cf93

Comment 8 John Sefler 2011-03-10 21:12:31 UTC
Verifying Version...
[root@jsefler-onprem03 bug629670]# rpm -qa | grep subscription-manager
subscription-manager-0.95.4-1.git.4.4721154.el6.x86_64
subscription-manager-firstboot-0.95.4-1.git.4.4721154.el6.x86_64
subscription-manager-gnome-0.95.4-1.git.4.4721154.el6.x86_64
[root@jsefler-onprem03 pki]# rpm -q subscription-manager --changelog | grep 676377
- 676377: rhsm-compliance-icon's status can be a day out of sync

The two failed cases in comment #6 are now passing:

subscription-manager register --autosubscribe
  PASS

subscription-manager unregister
  PASS

moving to VERIFIED

Comment 9 errata-xmlrpc 2011-05-19 13:39:45 UTC
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