Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-29671

Perform grub2-install also on ppc64le systems with prepboot partition

    • None
    • None
    • rhel-sst-upgrades
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None

      What were you trying to do that didn't work?

      Install RHEL-7.9 on ppc64le system with prepboot partition and upgrade the system to RHEL-8 using leapp tool. The system was upgraded but booted with RHEL-7 kernel.

      Please provide the package NVR for which bug is seen:

      leapp-0.17.0-1.el7_9.noarch
      leapp-deps-0.17.0-1.el7_9.noarch
      leapp-upgrade-el7toel8-0.20.0-2.el7_9.noarch
      leapp-upgrade-el7toel8-deps-0.20.0-2.el7_9.noarch
      python2-leapp-0.17.0-1.el7_9.noarch

      How reproducible:

      always

      Steps to reproduce

      1. Obtain POWER8 kvm VM (or POWER10 PowerVM) system
      2. Install RHEL-7 on this system (the prepboot partition is created by default)
      3. Perform all the necessary steps before upgrade in resolve all inhibitors
      4. Run leapp upgrade and reboot
      5. Wait for system to boot into the upgraded system

      Expected results

      System upgrades and boots to the new RHEL-8 kernel

      Actual results

      System upgrades and boots to the old RHEL-7 kernel

      Additional information:

       

      parted -l
      Error: /dev/mapper/rhel_ibm--p10--01--lp04-swap: unrecognised disk label
      Error: /dev/mapper/rhel_ibm--p10--01--lp04-root: unrecognised disk label
      Model: AIX VDASD (scsi)
      Disk /dev/sda: 42.9GB
      Sector size (logical/physical): 4096B/4096B
      Partition Table: msdos
      Disk Flags: 
      
      Number  Start   End     Size    Type     File system  Flags
       1      1049kB  5243kB  4194kB  primary               boot, prep
       2      5243kB  1079MB  1074MB  primary
       3      1079MB  42.9GB  41.9GB  primary               lvm

      There's a high risk message from the leapp:

      Stamp: 2024-03-15T15:45:03.335033Z
      Actor: check_grub_core
      Phase: Checks
      Type: Report
      Message_data:
      {
          "report": {
              "audience": "sysadmin",
              "detail": {
                  "remediations": [
                      {
                          "context": "Please run \"grub2-install <GRUB_DEVICE> command manually after the upgrade",
                          "type": "hint"
                      }
                  ]
              },
              "groups": [
                  "boot"
              ],
              "key": "41f46d9b1691373b0846e6297fb98d010cf21864",
              "severity": "high",
              "summary": "We assumed GRUB2 core is located on the same device(s) as /boot, however Leapp could not detect GRUB2 on the device(s). GRUB2 core needs to be updated maually on legacy (BIOS) systems. ",
              "title": "Leapp could not identify where GRUB2 core is located"
          }
      }

       

              leapp-notifications leapp-notifications
              pholica@redhat.com Pavel Holica
              leapp-notifications leapp-notifications
              RHEL Upgrades QE Team RHEL Upgrades QE Team
              Miriam Portman Miriam Portman
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: