Bug 156310 - docs: patch installation timestamps
docs: patch installation timestamps
Status: CLOSED NOTABUG
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Docs Reference Guide (Show other bugs)
500
All Linux
medium Severity medium
: ---
: ---
Assigned To: John Ha
Steve Salevan
: Documentation
Depends On:
Blocks: 456984
  Show dependency treegraph
 
Reported: 2005-04-28 16:23 EDT by Máirín Duffy
Modified: 2014-08-04 18:15 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-10-28 16:27:39 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Máirín Duffy 2005-04-28 16:23:39 EDT
If a patch / (maybe patchset / package?) is installed on Solaris via RHN, then
we can track and display the date of the last installation in the lists that
display patches for a particular system.

However, if a patch (patchset / package??) has been installed on Solaris without
RHN, directly on the machine, then we cannot track the date of the last install.
In this situation, we will display "not available."

It may be nice to have a note about what this "not available" means in the
documentation.
Comment 1 Máirín Duffy 2005-04-28 17:19:12 EDT
I have confirmed with shughes that this issue applies to patchsets and packages
on Solaris systems as well.
Comment 2 Mark Johnson 2005-07-20 14:48:59 EDT
punting this doc bug to 4.1 b/c there is a bigger problem in that the "Patch
Type" and "Last Installed" fields read "unknown" and "Not Available", resp, even
in the case where the patches/clusters *are* installed via RHN. 

See http://lacrosse.corp.redhat.com/~mjohnson/RHN/unix/figs/patch-foo.png for a
visual example of what we're talking about here.

jmartin is filing a bug report on this issue.
Comment 3 Max Spevack 2005-07-27 16:35:38 EDT
new Sol component created/QA contact should be mspevack if not already
Comment 4 Max Spevack 2005-08-12 10:54:03 EDT
please see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=163843
Comment 5 Beth Nackashi 2006-04-22 14:10:32 EDT
bperkins is QA contact for all Solaris bugs
Comment 6 Melissa Goldin 2006-05-04 09:13:27 EDT
Mass adding keyword 'Documentation' to all bugs
Comment 7 Melissa Goldin 2006-07-11 12:23:05 EDT
This has been punted to rhn420-solaris.  Also aligning with the Ref Guide for 420.
Comment 8 Melissa Goldin 2007-02-05 13:59:38 EST
Removing from the RHN 500 Hosted release, because rhn420-solaris now points to
rhn510s-triage.
Comment 9 Michael Hideo 2007-06-06 00:44:22 EDT
Adding 'cc ecs-dev-list@redhat.com for tracking
Comment 10 Michael Hideo 2007-06-19 21:30:59 EDT
Moving Bugs to John Ha and assigning.

Re-prioritization meeting on June 20, 7PM EST.
Comment 11 John Ha 2007-08-04 09:36:46 EDT
acking for 510 release.
Comment 12 Michael Hideo 2007-10-22 22:45:18 EDT
Removing automation notification
Comment 13 John Ha 2007-12-20 18:57:12 EST
Is what is stated in Comment #2 still valid? Is there still a documentation need
for this issue as it seems to affect all packages/patches regardless of whether
they were installed by RHN or not.

Either way, we don't have time put this in the 5.1.0 release :(
Comment 14 Brandon Perkins 2008-02-08 09:57:13 EST
I don't personally think we need it... but as mizmo was the one to report it,
I'll let her decide.
Comment 15 Máirín Duffy 2008-02-08 10:05:28 EST
wow blast from the past!!

if it affects all patches regardless of how they were installed then it's
definitely not needed. back when i filed that we didn't have a standard method
of doing contextual tool tip thingys but now that we do i think if the behavior
did differ, it'd be better to put a tooltip below the patch list rather than put
the info in the docs. so feel free to close this :)
Comment 16 John Ha 2008-10-28 16:27:39 EDT
Performing 5.3.0 cleanups. Closing this as the reporter sees no docs need for it.

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