Bug 117338 - Sat. & Client not in sync after registration
Summary: Sat. & Client not in sync after registration
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Server
Version: unspecified
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
Assignee: Mihai Ibanescu
QA Contact: Fanny Augustin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-03-02 22:21 UTC by Pete Graner
Modified: 2007-07-31 14:31 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-09-23 21:30:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Pete Graner 2004-03-02 22:21:16 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Gecko/20031114

Description of problem:
I have a few machines that have successfully installed all updates
from the Satellite server.  

When the up2date client is ran they are reporting fully updated.  

For some reason the satellite server continues to report packages that
have not been updated.  

I was able to issue the "up2date -p" command on one of these
workstations and clear the count on the satellite server but I had to
know that the workstation and server were out of sync.  



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

How reproducible:
Sometimes

Steps to Reproduce:
1. register system to the satellite server with activaction key
2. run up2date -uf on said system
3. 
    

Actual Results:  Going to the satellite GUI shows the system out of date. 

Expected Results:  Both satellite and client should have the same view
of package status

Additional info:

up2date -p brings both back into sysnc. Should not have to do that. I
would only expect to do that if I manually add RPMS to the system
without using up2date. This is not the case here.

Comment 1 Mihai Ibanescu 2004-03-12 23:42:30 UTC
Is taskomatic running on the satellite?


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