-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
None
-
rhel-storage-management
-
None
-
False
-
False
-
-
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
- Note: add fstab lookup for non-root snapsets
- needs either root=UUID/LABEL support in boom or a lookup to resolve any
- 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)