You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Actual behavior leap upgrade does not create a BOOT entry in /boot/grub2/grub.cfg required for BIOS machines pick the Centos7 to AlmaLinux conversion.
To Reproduce
Deploy a Gen1 server in Azure (they use BIOS boot), use ELevate to migrate from CentOS7 to AlmaLinux8, follow the normal process: leapp upgrade, reboot, and the machine will boot into the regular kernel.
Expected behavior
After running sudo leapp upgrade boot into the ELevate temporary image and perform the in-place upgrade, however the /boot/grub2/grub.cfg is not updated to reflect the new initramfs.
System information (please complete the following information):
[azureuser@centos7i ~]$ cat /etc/system*
cat: /etc/systemd: Is a directory
CentOS Linux release 7.9.2009 (Core)
cpe:/o:centos:centos:7
uname -a : Linux centos7i 3.10.0-1160.118.1.el7.x86_64 #1 SMP Wed Apr 24 16:01:50 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
# rpm -qa "leapp*"
[azureuser@centos7i ~]$ rpm -qa |grep leapp
leapp-upgrade-el7toel8-deps-0.16.0-6.el7.elevate.20.noarch
leapp-0.14.0-1.el7.noarch
leapp-deps-0.14.0-1.el7.noarch
leapp-upgrade-el7toel8-0.16.0-6.el7.elevate.20.noarch
leapp-data-almalinux-0.2-5.el7.noarch
python2-leapp-0.14.0-1.el7.noarch
Azure image name: : openlogic:centos-lvm:7-lvm:latest
Attach (or provide link to) log files if applicable (optional - may contain confidential information):
All files in /var/log/leapp
/var/lib/leapp/leapp.db
journalctl
If you want, you can optionally send anything else would you like to provide (e.g. storage info)
For your convenience you can pack all logs with this command:
# tar -czf leapp-logs.tar.gz /var/log/leapp /var/lib/leapp/leapp.db
Then you may attach only the leapp-logs.tar.gz file.
Additional context
original file split into 8 parts with the split command, just concatenate all files and use: tar -xvf file.tar.xz
Actual behavior
leap upgrade
does not create a BOOT entry in /boot/grub2/grub.cfg required for BIOS machines pick the Centos7 to AlmaLinux conversion.To Reproduce
Deploy a Gen1 server in Azure (they use BIOS boot), use ELevate to migrate from CentOS7 to AlmaLinux8, follow the normal process: leapp upgrade, reboot, and the machine will boot into the regular kernel.
[azureuser@centos7i ~]$ history
1 sudo yum update -y
2 sudo reboot
3 sudo yum install -y http://repo.almalinux.org/elevate/elevate-release-latest-el$(rpm --eval %rhel).noarch.rpm
4 sudo yum install -y leapp-upgrade leapp-data-almalinux
5 sudo leapp preupgrade
6 vi /var/log/leapp/leapp-report.txt
7 sudo vi /var/log/leapp/leapp-report.txt
8 sudo leapp answer --section remove_pam_pkcs11_module_check.confirm=True
9 sudo leapp upgrade
10 reboot
Expected behavior
After running
sudo leapp upgrade
boot into the ELevate temporary image and perform the in-place upgrade, however the /boot/grub2/grub.cfg is not updated to reflect the new initramfs.System information (please complete the following information):
Attach (or provide link to) log files if applicable (optional - may contain confidential information):
For your convenience you can pack all logs with this command:
# tar -czf leapp-logs.tar.gz /var/log/leapp /var/lib/leapp/leapp.db
Then you may attach only the
leapp-logs.tar.gz
file.Additional context
original file split into 8 parts with the split command, just concatenate all files and use: tar -xvf file.tar.xz
xah.txt
xag.txt
xaf.txt
xae.txt
xad.txt
xac.txt
xab.txt
xaa.txt
The text was updated successfully, but these errors were encountered: