This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2190228 - Support defining mount units on the kernel command line
Summary: Support defining mount units on the kernel command line
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: systemd
Version: 8.4
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: David Tardon
QA Contact: Frantisek Sumsal
URL:
Whiteboard:
Depends On:
Blocks: 1794460
TreeView+ depends on / blocked
 
Reported: 2023-04-27 15:34 UTC by Bryn M. Reeves
Modified: 2023-09-21 12:33 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2190226
Environment:
Last Closed: 2023-09-21 12:33:50 UTC
Type: Story
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github redhat-plumbers systemd-rhel8 pull 398 0 None open Support defining mount units on the kernel command line 2023-06-20 15:00:35 UTC
Github systemd systemd pull 27563 0 None Merged fstab-generator: support defining mount units through kernel command line 2023-05-31 06:37:15 UTC
Github systemd systemd pull 27800 0 None Merged fstab-generator: use correct swap name var 2023-05-31 06:37:15 UTC
Github systemd systemd pull 28518 0 None Merged fstab-generator: fixes for systemd.mount-extra= 2023-07-31 15:19:00 UTC
Github systemd systemd pull 28544 0 None Merged fstab-generator: enable fsck for block device mounts specified in sys… 2023-07-31 15:21:11 UTC
Red Hat Issue Tracker   RHEL-5989 0 None Migrated None 2023-09-21 12:32:35 UTC
Red Hat Issue Tracker RHELPLAN-155960 0 None None None 2023-04-27 15:36:49 UTC

Description Bryn M. Reeves 2023-04-27 15:34:43 UTC 
+++ This bug was initially created as a clone of Bug #2190226 +++

Description of problem:
We'd like the ability to define mount units on the kernel command line. This allows the system to be booted into a snapshot of the system state (for e.g. using LVM2 CoW or thin provisioned snapshots) and enables rollback for system updates by allowing the administrator to preserve a copy of the prior system state and to optionally roll the system back to that state at a later time using the snapshot merge facility.

This would add new kernel command line syntax something like the following:

  systemd.mount=what:where:fstype:options

The feature has been proposed to upstream systemd and has received some initial positive comments:

  https://github.com/systemd/systemd/issues/27260

The new functionality would be added to the existing systemd-fstab-generator to write out mount units during early boot.

Version-Release number of selected component (if applicable):
systemd-239-68.el8

How reproducible:
100%

Steps to Reproduce:
1. man systemd-fstab-generator

Actual results:
No syntax exists for specifying kernel command line mount units.

Expected results:
The ability to specify mount units on the kernel command line

Additional info:
This will be used by Leapp and boom to provide rollback capable upgrades.
Comment 1 Bryn M. Reeves 2023-07-31 15:24:10 UTC 
There are two additional pull requests for this feature that were merged for v254:

  fstab-generator: fixes for systemd.mount-extra=
  https://github.com/systemd/systemd/pull/28518

  fstab-generator: enable fsck for block device mounts specified in sys…
  https://github.com/systemd/systemd/pull/28544
Comment 7 RHEL Program Management 2023-09-21 12:28:44 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 8 RHEL Program Management 2023-09-21 12:33:50 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.