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

snapm: support bootable snapshot sets that do not include the root file system

Linking RHIVOS CVEs to...Migration: Automation ...Sync from "Extern...XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • snapm
    • None
    • None
    • rhel-storage-management
    • None
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • Unspecified
    • Unspecified
    • Unspecified

      Currently `snapm` restricts the use of `-boot` and `-revert` to snapshot sets that include the root file system:

      ```python
      def _find_snapset_root(snapset):
      """
      Find the device that backs the root filesystem for snapshot set ``snapset``.

      If the snapset does not include the root volume look the device up via the
      fstab.
      """
      for snapshot in snapset.snapshots:
      if snapshot.mount_point == "/":
      return snapshot

      1. Note: add fstab lookup for non-root snapsets
      2. needs either root=UUID/LABEL support in boom or a lookup to resolve any
      3. UUID/LABEL found in the file.
        raise SnapmNotFoundError(f"Could not find root device for snapset {snapset.name}

        ")
        ```

      To ensure the correct root device is selected `root=UUID=` and `root=LABEL=` notation should be resolved to a device path when generating the boot entry mount list (Fedora/RHEL10 have switched to using `root=UUID=` for LVM2 volumes since storaged-project/blivet@7aa07083dbc90b0fabea063ca5a19ee3d154b1b2)

              rhn-support-bmr Bryn Reeves
              tgill@redhat.com Todd Gill
              Bryn Reeves Bryn Reeves
              Filip Suba Filip Suba
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: