Description of problem: After updating the kernel-2.4.21-4.0.2.EL via the up2date GUI the "Installing Packages" window hangs (w/hourglass cursor) when the progress bar shows completed (all the way to the right). The Back and Forward buttons remain grayed out. The GUI remained in this state overnight. It appears to have completed the install (see additional info below). Version-Release number of selected component (if applicable): up2date-4.0.1-1 up2date-gnome-4.0.1-1 How reproducible: It happend twice on two different machines, each on the kernel update for clean installs. Steps to Reproduce: 1. Install RHEL WS 2. Get initial updates including new kernel package Actual results: Expected results: Additional info: Running up2date on the command line "up2date -uf" produces the following: -- begin -- Fetching package list for channel: rhel-i386-ws-3... ######################################## Fetching Obsoletes list for channel: rhel-i386-ws-3... Name Version Rel ---------------------------------------------------------- kernel 2.4.21 4.0.2.EL i686 Testing package set / solving RPM inter-dependencies... ######################################## RPM package conflict error. The message was: Test install failed because of package conflicts: package kernel-2.4.21-4.0.2.EL is already installed -- end --
I have the same problem with Fedora Core 2. I notice that this only happens with certain sites. For instance: mirror.eas.muohio.edu/fedora/linux/core/updates/2/i386 This site seems to be down and when I see that this mirror is being used I always get the progress bar all the way to the right. I then cancel the operation and try until I get a different mirror site. The sunsite seems to always work.
This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you.