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 682311

Summary: rhsm-compliance icon pegs the cpu at 100%
Product: Red Hat Enterprise Linux 6 Reporter: J.C. Molet <jmolet>
Component: subscription-managerAssignee: Chris Duryee <cduryee>
Status: CLOSED ERRATA QA Contact: J.C. Molet <jmolet>
Severity: unspecified 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:
: 682895 (view as bug list) Environment:
Last Closed: 2011-05-19 13:39:59 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    

Description J.C. Molet 2011-03-04 20:03:50 UTC
Description of problem:
The rhsm-compliance icon gets stuck in a loop somehow (when frequently polling for status updates possibly) and fully utilizes a cpu.

Version-Release number of selected component (if applicable):
subscription-manager-gnome-0.95.3-1.git.10.4ec14b7.el6.x86_64
subscription-manager-0.95.3-1.git.10.4ec14b7.el6.x86_64
subscription-manager-firstboot-0.95.3-1.git.10.4ec14b7.el6.x86_64
python-rhsm-0.95.3-1.git.0.4d0ef8e.el6.noarch

How reproducible:
sometimes?

Steps to Reproduce:
I'm not 100% sure on the way to reproduce this.  I've been basically just using the rhsm-gui and going through the menus and running searches, etc.  Simplest way to reproduce:
1. Start up firstboot
2. Hit forward a bunch of times
3. Go back and forth through the rhsm parts of firstboot
  
Actual results:
The refreshes of the icon cause it to max my cpu.

Expected results:
Status updates are handled normally and doesn't max out my cpu.

Comment 1 Chris Duryee 2011-03-08 16:04:14 UTC
master 0.96.2+ 111ed64ff73c40a4d9147466933cb2a0a11ce932

rhel6 0.95.4+ ae5400b5bfac94931c8e982d7ce5899a080ec4fd

Comment 4 J.C. Molet 2011-03-09 21:08:56 UTC
Tested this on version:
 subscription-manager-gnome-0.95.4-1

# rpm -q subscription-manager-gnome-0.95.4-1.git.1.bb03d4e.el6.x86_64 --changelog | grep 682311
- 682311: rhsm-compliance icon pegs the cpu at 100% (cduryee)

I have not been able to reproduce this issue on the above version.  It looks like the fix works.  Moving to verified.

Comment 5 errata-xmlrpc 2011-05-19 13:39:59 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