After installing mageia-prepare-upgrade, and rebooting, selecting the upgrade stanza, the /usr move is not done. The initrd in /boot is from May 12th, so dracut is not being called. Reproducible: Steps to Reproduce:
Mageia 3 has been removed from releases api until this problem is investigated.
CC: (none) => boklm
Manually running /usr/sbin/bootloader-config --action rebuild-initrds the only line added to syslog is systemd-tmpfile[3738]: Two or more conflicting lines for /var/run/user configured,
grep /var/run/user /etc/tmpfiles.d/* /etc/tmpfiles.d/mageia-prepare-upgrade.conf:d /var/run/user 0755 root root - I don't know where the conflicting line is.
Found it $ grep var/run/user /usr/lib/tmpfiles.d/* /usr/lib/tmpfiles.d/systemd.conf:d /var/run/user 0755 root root 10d
Created attachment 4008 [details] Compressed strace output from bootloader-config
Attachment 4008 mime type: text/plain => application/octet-stream
I've now confirmed the problem is that /usr/sbin/bootloader-config --action rebuild-initrds doesn't work on my system. The strace output shows it's reading the grub setup from /dev/sda, but I boot this install using gag on sdb, with grub in sdb1. In the past, installing kernel updates, I've always had to fix /boot/grub/device.map and menu.lst, before rebooting. Manually running dracut -f does add the convertfs to the initrd. I'll add an errata item, and ask for the api change to be put back in, since this is a very rare case. During testing, I was using sda, or vbox, which is why I didn't see this problem before.
I've added the errata item to https://wiki.mageia.org/en/Mageia_3_Errata#Upgrade_Issues
OK, so this seems like a fairly specialist case then? Can we add mga3 back into the list as per comment 1?
it was done for 1 hour (was request on #mageia-sysadmin this night)
This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. 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 2'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 2 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. -- The Mageia Bugsquad
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 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. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD
CC: boklm => (none)