Description of problem: Hello. I just upgraded one of my servers from Mageia 1 to Mageia 2 using the mgaonline tool. The upgrade seemed to be successfull and it offered me a reboot. But as no kernel was installed, the old vmlinuz-server-2.6.33 was chosen and I got kernel panic (since it's too old for Mageia 2) and had to rescue the system. Please, check, if the following upgrade procedures work reliably: 1.) MGA1 -> MGA2 2.) MDV2010.2 -> MGA1 -> MGA2 Version-Release number of selected component (if applicable): mgaonline-2.77.30-1.mga1
It was working without any issue with the test make by the QA so please add more details
Keywords: (none) => NEEDINFO
Hi Manuel. It's hard to guess what details might be relevant in this case. Maybe the server kernel? Moreover some dependencies were totally screwed up ... I had to uninstall and reinstall a half of the distro to make some of the apps working again. For example drakconf / rpmdrake didn't work at all ... saying that some png image is broken or missing (while it was there as well as 2 different versions of libpng). I couldn't open that image even in eog (and I reinstalled the drakxtools package containing the image + both versions (12 & 15) of libpng libraries for both architectures ... so there was something totally wrong) I experienced similar issues in case of all updates to Mageia 2. The issue probably appears on long time alive systems upgraded many times from prehistoric Mandriva versions, having way too many packages installed, where the deps could be messed up + obsolete packages still present). I'm pretty sure QA has tested that with laboratory-clean environment, but I believe the issues come with "dirty" systems. Regards, Jaromir.
for the drakconf/rpmdrake bug it was in the errata: https://wiki.mageia.org/en/Mageia_2_Errata#Drakconf_issue
That's not related to mgaonline. I temporary affect it to urpmi but the real issue is probably a packaging issue. We need logs (should be in your ~/.MgaOnline)
CC: (none) => thierry.vignaudSource RPM: mgaonline-2.77.30-1.mga1.src.rpm => urpmi
Did you have kernel-destop-latest installed?
Hi Thierry. I believe I had the kernel-server-latest installed, but the package was missing after the upgrade for some reason. Anyway, the upgrade tool should take care of that even if it isn't installed. If the new system can't run without more recent kernel, then an installation of the minimum required kernel version should be forced by the upgrade tool (or some meta package). It has no sense to leave the system with unusable kernel. My ~/.MgaOnline directory contains just the mgaonline config file and I've never seen any logs in that directory in my life :] Do I need to activate the logging first? Thanks and regards, Jaromir.
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => WONTFIX