Bug 452833 - Omit backtrace as a "verbose output", it looks scary
Omit backtrace as a "verbose output", it looks scary
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: up2date (Show other bugs)
4.7
All Linux
low Severity low
: rc
: ---
Assigned To: Sayli Karmarkar
Fanny Augustin
: EasyFix
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-06-25 08:10 EDT by Michal Nowak
Modified: 2013-03-07 21:04 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-05-18 16:14:04 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 Michal Nowak 2008-06-25 08:10:09 EDT
Description of problem:

Tried to install package sos from non existing channel. The error message might
be more informative, like: "Provided channel is not valid." or "Package sos was
not found in channel 'sdsd'. List of channels can be received via up2date -l"


[root@xen65 ~]# up2date --channel=sdsd sos
An error has occurred:
This system may not be updated until it is associated with a channel.
See /var/log/up2date for more information

Please omit using backtrace in log when not necessary, simpler debug info with
more verbose information, would fit better.

[Wed Jun 25 14:00:15 2008] up2date This system may not be updated until it is
associated with a channel.
[Wed Jun 25 14:00:15 2008] up2date   File "/usr/sbin/up2date", line 1312, in ?
    sys.exit(main() or 0)
   File "/usr/sbin/up2date", line 592, in main
    rhnChannel.setChannels(tempchannels)
   File "/usr/share/rhn/up2date_client/rhnChannel.py", line 286, in setChannels
    return getChannels(label_whitelist=whitelist)
   File "/usr/share/rhn/up2date_client/rhnChannel.py", line 184, in getChannels
    raise up2dateErrors.NoChannelsError(_("This system may not be updated until
it is associated with a channel."))


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

4.7.1-17.el4

How reproducible: always
Comment 1 Jan Hutař 2008-09-25 08:04:49 EDT
Hello,
not sure if we want to omit the back-trace in the log (good for debugging), but definitely nicer error message would be useful.

# up2date --channel=sdsd sos
An error has occurred:
This system can not access this channel(s). Is it correctly registered in it?
See /var/log/up2date for more information
Comment 3 Jan Hutař 2008-10-08 09:18:45 EDT
Hello,
please could you comment on comment #1?
Comment 9 errata-xmlrpc 2009-05-18 16:14:04 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2009-0972.html

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