Red Hat Bugzilla – Bug 503096
preupgrade leaves old yum metadata laying around
Last modified: 2014-01-21 18:09:46 EST
Description of problem: preupgrade leaves old yum metadata laying around. Doing a yum update shortly after a preupgrade can cause yum to try to download and install the rpm's for the last release instead of the newly upgraded to release. Version-Release number of selected component (if applicable): 1.0.1-2.fc10 (from memory) How reproducible: probably always, but difficult to retest Steps to Reproduce: 1. on f10 system: yum update 2. preupgrade 3. yum update Actual results: Yum picks up new f10 updates -- eg. from old system Expected results: Yum picks up new f11 updates -- eg. from new system Additional info: Yum did try to load the f11 respmod.xml (name from memory), but it was older than the f10 one already downloaded so it continued to use the old f10 version. It would be good for preupgrade to do a yum clean metadata as one of the last things it does, or the installation instructions need to mention that the user needs to do this as one of the first orders of business before doing anything significant with yum.
when you say 'preupgrade' do you mean run preupgrade and then reboot and do the upgrade? or do you mean just run preupgrade?
Oh, sorry, I wasn't clear. I meant preupgrade and then hit the on-screen reboot button and run the upgrade, then let it boot into the upgraded system and then do a "yum update" from the newly upgraded-to release.
That probably still wasn't very clear. Let me try again. After upgrading from f10 to f11 and running f11 I did a "yum update -y". What I saw (from memory) "repmod.xml is older than the one we have. Using ours." somerpm-12345.fc10 otherrpm-23454.fc10 Eg. Yum was still trying to download the fc10 rpm's instead of the fc11 ones. After a "yum clean metadata" yum downloaded an fc11 repmod.xml and all was well.
reassigning to anaconda - since this is something it would have to do.
This should be fixed in the next build of anaconda. Thanks for the bug report.