Bug 589094 - RHEL 4 does not (?) send installation dates, yet the server shows the column "Installed" with data
Summary: RHEL 4 does not (?) send installation dates, yet the server shows the column ...
Keywords:
Status: CLOSED DUPLICATE of bug 615298
Alias: None
Product: Spacewalk
Classification: Community
Component: Server
Version: 1.0
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Michael Mráka
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space11 sat540-rpm-inst-date
TreeView+ depends on / blocked
 
Reported: 2010-05-05 11:45 UTC by Jan Pazdziora
Modified: 2012-03-06 09:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-07-19 09:06:55 UTC
Embargoed:


Attachments (Terms of Use)

Description Jan Pazdziora 2010-05-05 11:45:36 UTC
Description of problem:

When RHEL 4.8 get registered to the server (I tried Spacewalk 1.0 but I assume the same issue with next version of Satellite), installation dates are shown with packages. That is surprising, given that RHEL 4 does not send the installation dates.

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

Spacewalk 1.0
# rpm -qf /usr/sbin/up2date
up2date-4.8.1-33.el4_8.1

How reproducible:

Tried once.

Steps to Reproduce:
1. Have Spacewalk/Satellite server. Have RHEL 4 client machine.
2. Register the machine to the server.
3. Run up2date -p.
4. Look up the profile on the server and go to Software > Packages > List/Remove: /rhn/systems/details/packages/PackageList.do?sid=...
  
Actual results:

The "Installed" colum is filled with timestamps matching the registration / up2date -p time.

Expected results:

N/A shown there, as the client did not send the installation date.

Additional info:

Mirek says that RHEL 4 does not send the installation dates and that if the client does not send the info, the column should be empty or say N/A. Currently, false information is shown.

Comment 1 Miroslav Suchý 2010-07-19 09:06:55 UTC

*** This bug has been marked as a duplicate of bug 615298 ***


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