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
Copy file name to clipboardExpand all lines: support/azure/virtual-machines/linux/troubleshoot-red-hat-os-upgrade-issues.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -607,11 +607,11 @@ The mounting failure occurs because version 2 of the control group (cgroup v2) i
607
607
608
608
1. If that parameter is in one of those files, remove the parameter from the file, and then run the Leapp upgrade process again.
609
609
610
-
### Upgrade symptom 7: Leapp upgrade doesn't continue after reboot, VM boots into RHEL 8.10 instead
610
+
### Upgrade symptom 7: Leapp upgrade doesn't continue after reboot, and VM boots into RHEL 8.10 instead
611
611
612
612
If you run the Leapp upgrade from RHEL 8.10 to 9.4 or 9.5, the upgrade process might not continue after the required reboot. Instead, the VM boots back into RHEL 8.10 without loading the special upgrade initramfs.
613
613
614
-
The following setting in `/etc/default/grub`may cause this issue:
614
+
The following setting in `/etc/default/grub`might cause this issue:
615
615
616
616
```config
617
617
GRUB_DEFAULT=0
@@ -625,7 +625,7 @@ Since `GRUB_DEFAULT=0` forces the system to always boot the first menu entry in
625
625
1. Change `GRUB_DEFAULT=0` to `GRUB_DEFAULT=saved`:
626
626
627
627
> [!NOTE]
628
-
> In this example, `GRUB_DEFAULT` is set to 0, but in your environment, it might be 1 or another number. Ensure that you replace it accordingly in the `sed` command.
628
+
> In this example, `GRUB_DEFAULT` is set to `0`, but in your environment, it might be `1` or another number. Ensure that you replace it accordingly in the `sed` command.
629
629
630
630
631
631
```bash
@@ -652,7 +652,7 @@ Since `GRUB_DEFAULT=0` forces the system to always boot the first menu entry in
652
652
sudo reboot
653
653
```
654
654
655
-
After the reboot, if the fix is applied correctly, the VM will should into the Leapp upgrade initramfs, and you should see an output similar to the following lines in the serial console:
655
+
After the reboot, if the fix is applied correctly, the VM will go into the Leapp upgrade initramfs, and you should see an output similar to the following lines in the serial console:
656
656
657
657
```output
658
658
[ OK ] Reached target Remote File Systems.
@@ -677,7 +677,7 @@ Since `GRUB_DEFAULT=0` forces the system to always boot the first menu entry in
677
677
[ 21.581296] upgrade[677]: Mounting /usr with -o defaults,ro
678
678
```
679
679
680
-
This output indicates that the Leapp upgrade process has continued successfully. After completion, the VM should boot into RHEL 9.X.
680
+
This output indicates that the Leapp upgrade process has continued successfully. After completion, the VM should boot into RHEL 9.*x*.
681
681
682
682
> [!IMPORTANT]
683
683
> If the Leapp upgrade still fails without an obvious reason (such as when upgrading from version 7.9 to version 8.10 or from version 8.10 to version 9.5), don't upgrade to the latest version. Instead, try to upgrade to an intermediate version (such as from version 7.9 to version 8.8 or version 8.10 to version 9.4) by specifying the `--target x.y` flag. After the intermediate upgrade is successful, you can try to upgrade to the latest release.
0 commit comments