Bug 459726 - update package via rhn web interface doesn't log warning messages anywhere
Summary: update package via rhn web interface doesn't log warning messages anywhere
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: up2date
Version: 4.6
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Pradeep Kilambi
QA Contact: Ken Reilly
URL:
Whiteboard:
Depends On: 459725
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-08-21 15:56 UTC by Katerina Novotna
Modified: 2012-06-20 13:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 13:20:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Katerina Novotna 2008-08-21 15:56:04 UTC
+++ This bug was initially created as a clone of Bug #459725 +++

Description of the problem:

I tried to update package which produced some warnings messages during installation via rhn web interface.
When I tried run rhn_check manually on the test machine -> warnings messages were displayed in terminal.
When rhnsd daemon runs rhn_check automatically no messages were logged.(not /var/log/up2date). 

Steps to Reproduce:
1. update package which produced warning messages from rhn web interface

Actual results:
no messages for end user

Expected results:
messages into log file or rhn website

Additional info:
It requires for tools which are able to installing/updating packages to log all
meaningful messages for end user.

Comment 4 Jiri Pallich 2012-06-20 13:20:30 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.


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