Bug 78621 - up2date crases with traceback on Kernel update
up2date crases with traceback on Kernel update
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: up2date (Show other bugs)
7.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Adrian Likins
Red Hat Satellite QA List
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-11-26 11:32 EST by Need Real Name
Modified: 2007-04-18 12:48 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-08-20 15:53:43 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 Need Real Name 2002-11-26 11:32:08 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.79 [en] (Windows NT 5.0; U)

Description of problem:


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


How reproducible:
Didn't try

Steps to Reproduce:
1.up2date -u
2.
3.
	

Actual Results:  [root@screamer48 /root]# up2date -u

Fetching package list for channel: redhat-linux-i386-7.1...
########################################

Fetching package list for channel: redhat-powertools-i386-7.1...
########################################

Fetching Obsoletes list for channel: redhat-linux-i386-7.1...
########################################

Fetching Obsoletes list for channel: redhat-powertools-i386-7.1...
########################################

Testing package set / solving RPM inter-dependencies...
########################################
kernel-2.4.18-18.7.x.i686.r ########################## Done.                   
kernel-2.4.18-18.7.x.src.rp ########################## Done.                   
Preparing...                ########################################### [100%]

Installing...
   1:kernel                 ########################################### [100%]
Traceback (innermost last):
  File "/usr/sbin/up2date", line 781, in ?
    main()
  File "/usr/sbin/up2date", line 569, in main
    pkgNames, fullUpdate, dryRun = dry_run))
  File "/usr/sbin/up2date", line 770, in batchRun
    up2date.installBootLoader(batch.kernelsToInstall)
  File "/usr/share/rhn/up2date_client/up2date.py", line 592, in installBootLoader
    __install_lilo(kernelList)
  File "/usr/share/rhn/up2date_client/up2date.py", line 611, in __install_lilo
    ret = lilocfg.installNewImages(kernelList,test=0)
  File "/usr/share/rhn/up2date_client/lilocfg.py", line 274, in installNewImages
    (default, tmptype, default_image,image_path,other,defaultIsOther) = findDefault(config,imagelist)
  File "/usr/share/rhn/up2date_client/lilocfg.py", line 215, in findDefault
    (imagetype, default_image,image_path,other) = config.getImage(default)
  File "/usr/share/rhn/up2date_client/lilo.py", line 140, in getImage
    raise IndexError, "unknown image %s" % (label)
IndexError: unknown image linux
[root@screamer48 /root]# 

Expected Results:  No traceback, no errors.

Additional info:

Could I be setup wrong for updating Kernels, if so, what is proper setup, either with my registration at RHN or my system.
Comment 1 Need Real Name 2002-11-26 11:37:45 EST
Here is a copy of my lilo.conf file:

[root@screamer48 /etc]# more lilo.conf
boot="/dev/sda"
map=/boot/map
install=/boot/boot.b
prompt
timeout="50"
message=/boot/message
linear
default=linux

image="/boot/vmlinuz-2.4.9-34"
        label="linux"
        initrd="/boot/initrd-2.4.9-34.img"
        read-only
        root="/dev/sda1"

[root@screamer48 /etc]# 
Comment 2 Adrian Likins 2002-12-13 17:33:31 EST
It seems to be the quotes, up2date isnt expecting lilo's to
have the image name quoted. 

lilo seems to be happy with it quoted or un quoted, though.
I'll see about making sure the next version understands both.
Comment 3 Need Real Name 2003-01-07 15:57:01 EST
affects us too.
Comment 4 Adrian Likins 2004-08-20 15:53:43 EDT
current versions should handle this (plus grub is now the default)

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