Bug 54822
| Summary: | up2date failed to complete kernel 2.4.9-6 upgrade | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <long> |
| Component: | up2date | Assignee: | Adrian Likins <alikins> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Jay Turner <jturner> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.1 | CC: | andy.b, gafton, mihai.ibanescu, mikemech69, srevivo |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2001-12-04 10:03:08 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Need Real Name
2001-10-19 19:31:19 UTC
I have the same issue with the same internet config over a dedicated T1. Once lilo is hand edited the new kenel works fine, but why is this an issue??? Looks to be two seperate issues. An ssl connect error shouldnt have any impact on the state that the kernel package is left in. Everything is downloaded first, then installed as a transaction, then lilo.conf is updated. From looking at the logs, it seems that the packages installed succesfully, and nothing raised an error when updating lilo.conf. Do you happen to have a copy of the lilo.conf before or after up2date ran? I'd like to take a look at them and see what happened and add the lilo.confs to the test suite if need be. Here is lilo.conf from before I used up2date to upgrade from 2.4.3-12 -->
2.4.9-6 and also after up2date finished. Note that nothing in it was changed by
up2date:
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
message=/boot/message
linear
default=linux
image=/boot/vmlinuz-2.4.2-2
label=linux.bak
read-only
root=/dev/hda6
image=/boot/vmlinuz-2.4.3-12
label=linux
root=/dev/hda6
read-only
Note that when I used up2date to upgrade from 2.4.2-2 to 2.4.3.-12,
/var/log/up2date contained messages such as these when it updated lilo.conf:
[Thu Sep 27 15:20:33 2001] up2date Modifying lilo.conf to include the new kernel
info
[Thu Sep 27 15:20:33 2001] up2date Adding 2.4.3-12 to lilo.conf
[Thu Sep 27 15:20:33 2001] up2date Running lilo with the new configuration
[Thu Sep 27 15:20:33 2001] up2date Running "/sbin/mkinitrd --ifneeded
/boot/initrd-2.4.3-12.img 2.4.3-12"
[Thu Sep 27 15:20:33 2001] up2date No initrd was created by mkinitrd
[Thu Sep 27 15:20:33 2001] up2date renaming the lilo.conf entry for linux to
linux.bak
[Thu Sep 27 15:20:33 2001] up2date making a backup copy of /etc/lilo.conf as
/etc/lilo.conf.up2date-1001622601.16
[Thu Sep 27 15:20:33 2001] up2date writing out the new /etc/lilo.conf
[Thu Sep 27 15:20:33 2001] up2date Running " /sbin/lilo -t -r /" (lilo test
mode)
[Thu Sep 27 15:20:33 2001] up2date Running " /sbin/lilo -r / "
[Thu Sep 27 15:20:33 2001] up2date lilo updated succesfully
Have tried to update kernel and get the following:- [root@issus /boot]# up2date -p Updating package profile... [root@issus /boot]# up2date -l Retrieving list of all available packages... Removing installed packages from list of updates... ######################################## Removing packages marked to skip from list... ######################################## Getting headers for available packages... ######################################## Removing packages with files marked to skip from list... ######################################## Name Version Rel -------------------------------------------------------------- gdb 5.1 0.71 kernel 2.4.9 12 openssh 2.9p2 10.7 openssh-askpass 2.9p2 10.7 openssh-askpass-gnome 2.9p2 10.7 openssh-clients 2.9p2 10.7 openssh-server 2.9p2 10.7 [root@issus /boot]# up2date -u Retrieving list of all available packages... Removing installed packages from list of updates... ######################################## Removing packages marked to skip from list... ######################################## Getting headers for available packages... ######################################## Removing packages with files marked to skip from list... ######################################## Testing package set / solving RPM inter-dependencies... ######################################## Retrieving selected packages... gdb: ########################## Done. kernel: ########################## Done. openssh: ########################## Done. openssh-askpass: ########################## Done. openssh-askpass-gnome: ########################## Done. openssh-clients: ########################## Done. openssh-server: ########################## Done. Preparing... ########################################### [100%] 1:gdb ########################################### [ 14%] 2:kernel ########################################### [ 28%] 3:openssh ########################################### [ 42%] 4:openssh-askpass ########################################### [ 57%] 5:openssh-askpass-gnome ########################################### [ 71%] 6:openssh-clients ########################################### [ 85%] 7:openssh-server ########################################### [100%] Error installing lilo.conf The message was: test install of lilo failed [root@issus /boot]# I belive the current releases should have any kernel/bootloader issues resolved. If you still see this issue, please reopen this bug. |