Bug 177739 - Constantly showing pending updates when there aren't any.
Constantly showing pending updates when there aren't any.
Product: Red Hat Network
Classification: Red Hat
Component: RHN/Web Site (Show other bugs)
RHN Stable
All Linux
medium Severity high
: ---
: ---
Assigned To: Jesus M. Rodriguez
Red Hat Satellite QA List
Depends On:
  Show dependency treegraph
Reported: 2006-01-13 12:10 EST by Dave Miller
Modified: 2008-10-15 11:43 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-10-15 11:43:29 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Dave Miller 2006-01-13 12:10:18 EST
Description of problem:
We are very frequently getting machines (often lots of them at once) showing up
with a "pending actions" icon in the RHN overview screens.  Clicking on the icon
to view the pending events reveals "no events pending".

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

How reproducible:
Every week or two.

Steps to Reproduce:
1. Look at your system overview in RHN
2. many machines have a "clock" (pending update) icon.
3. click the icon, view "no updates pending" on resulting screen.
Actual results:
lots of incorrect "pending update" icons.

Expected results:
machines listed with correct state.

Additional info:
The only way I've found to clear this is to log into every affected machine and
run up2date -p.

I reported this via email several months ago (with screenshots) via our support
rep but it still hasn't been fixed and it seems to be getting worse (dozens of
machines affected at a time now instead of only a few) and I don't see a bug
filed on it.

Logging as high because it's damn annoying and makes it hard to get an accurate
assessment of your system states (because if it's pending you can't tell if it's
up to date or not).
Comment 1 Amanda Carter 2008-10-15 11:43:29 EDT
This bug has been closed due to inactivity.  Please open a new bug with specific details if this problem is still occurring or if an enhancement is needed.

Note You need to log in before you can comment on or make changes to this bug.