In some cases we do not detect grub devices correctly (like in case of RHEL-29671 - prepboot partition). In such a cases we already generate the report informing people they need to install new grub core image manually after the upgrade. However, the summary does not provide enough detail about the impact. And in this case, the impact is that the upgraded boots by default using old kernel boot entry. (e.g. el7 instead of el8 one).

Extend the summary, informing people about the impact, so they understand also why they booted to the old kernel instead of the new one.

• Current msg (raw format)

  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"
      }
  }