Red Hat Bugzilla – Bug 52986
After failure to download kernel, kernel was installed twice
Last modified: 2015-01-07 18:51:10 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)
Description of problem:
I ran up2date to update my system after this morning's drop. The up2date
seemed to be running along correctly, (the system name is
parrot.squawk.com) but then it got an access denied error on the kernel
I then restarted the up2date -u. The up2date restarted, it did not
download the packages already downloaded, but then it installed the kernel
I got a message about the initrd file in boot already existing.
Version-Release number of selected component (if applicable):
I had just had a failure with the rom database the other day and had
reinitialized it. Also:
[root@parrot root]# rpm -q kernel
If, in fact, this is just the multiple architecture kernel problem, and
this is the way things should work, instead of closing it "NOTABUG" please
change the component on this bug to mkinitrd, as grubby should probably
not add the exact same kernel stanza to the grub.conf twice.
This is a borderline NOTABUG, but annoying. It sounds like you have
two different arches of the kernel installed. The next version of
the client should avoid this problem.
Actually, I have two of the exact same architecture of the kernel installed, I
used up2date to do this like I said, I didn't run forces. The system name was
parrot.squawk.com, I did it the first day of the latest drop a few days ago.
While downloading the kernel, I got a 401. I restarted the up2date and it
picked up, but it installed the same kernel RPM, same architecture twice.