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.
I have confirmed with shughes that this issue applies to patchsets and packages on Solaris systems as well.
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.
new Sol component created/QA contact should be mspevack if not already
please see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=163843
bperkins is QA contact for all Solaris bugs
Mass adding keyword 'Documentation' to all bugs
This has been punted to rhn420-solaris. Also aligning with the Ref Guide for 420.
Removing from the RHN 500 Hosted release, because rhn420-solaris now points to rhn510s-triage.
Adding 'cc ecs-dev-list for tracking
Moving Bugs to John Ha and assigning. Re-prioritization meeting on June 20, 7PM EST.
acking for 510 release.
Removing automation notification
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 :(
I don't personally think we need it... but as mizmo was the one to report it, I'll let her decide.
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 :)
Performing 5.3.0 cleanups. Closing this as the reporter sees no docs need for it.