-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
rhel-8.10
-
rhel-upgrades
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
In the new storage mounting solution, we generate mount systemd units by invoking systemd-fstab-generator manually and then prefix the units filenames with "sysroot-". There are some potential corner cases that might require further handling.
Based on my understanding of the fstab-generator source code, these can only be hit when explicitly specified, that is an option from the following options is found in the mount options in fstab (NOTE that this list might not be complete, this is what was found in a quick analysis):
- x-systemd.automount - An .automount unit file will be generated instead? of .mount unit file. These are unhandled in the current solution (the files are not prefixed with "sysroot".
- x-systemd.
{wanted-by,required-by,wants,requires,before,after}
- When any of these is defined, the generated unit files contain the specified unit's name. If the unit is a mount unit, we need to prefix the name.
- x-systemd.wants-mounts-for, x-systemd.requires-mounts-for - these options allow specifying a list of paths from which mount units are generated, we might need to do adjustments on the paths
These cases are potential corner cases, because we have yet to find a setup where they are used.
- is related to
-
RHEL-35446 [RFE] leapp upgrade: update the storage initialisation when booting to the upgrade enviroment
-
- In Progress
-