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 1794460 - [RFE] boom: support for multi-volumes snapshots
Summary: [RFE] boom: support for multi-volumes snapshots
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: boom-boot
Version: 8.1
Hardware: All
OS: Linux
medium
low
Target Milestone: rc
: ---
Assignee: Bryn M. Reeves
QA Contact: cluster-qe
URL:
Whiteboard:
Depends On: 2190228
Blocks: 2177839
TreeView+ depends on / blocked
 
Reported: 2020-01-23 16:12 UTC by jhouston
Modified: 2023-09-23 15:59 UTC (History)
22 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2177839 (view as bug list)
Environment:
Last Closed: 2023-09-23 15:59:03 UTC
Type: Story
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github systemd systemd issues 27260 0 None open Support defining mount and swap units on the kernel command line 2023-04-24 16:03:07 UTC
Red Hat Issue Tracker   RHEL-8281 0 None Migrated None 2023-09-23 15:55:30 UTC
Red Hat Knowledge Base (Solution) 5884301 0 None None None 2021-06-03 09:32:40 UTC

Description jhouston 2020-01-23 16:12:51 UTC 
Description of problem:

Like most other enterprise customers, separate out system filesystems for /, /var, /tmp, /var/log, /var/crash, /var/log/audit, /home, etc. When we take a snapshot before patching or another risky activity, we take snapshots of all of these LVs. It would be great to be able to use boom to add a boot entry for snapshots is a situation like above. It is very easy to add a logical volume tag to a number of snapshot LVs (eg "--add tag rhel7.7_snapshot") like the entire list above. What I had in mind is extending the functionality of boom to be able to specify a logical volume tag as the "--rootlv" option instead of just being able to put a specific root snapshot lv. For example:
1. create all the required snapshot lvs for all system logical volumes using option "--addtag rhel7snap" for each.
2. create boom entry using the tag: boom create --title "RHEL7.7 snapshot - 20200121" --rootlv @rhel7snap

Then when the server is rebooted and you specify the "RHEL 7.7 snapshot - 20200121" entry to boot from, it not only boots from the root lv snapshot, but all the lv snapshots associated with all the system logical volumes.
Comment 3 Bryn M. Reeves 2020-01-23 19:47:55 UTC 
Thanks for the interest in boom, and taking the time to file a bug. I've edited the title a little to make it more clear that this is asking about support for snapshots of more than just the root file system. Although there is an update to the boom package in the Red Hat Enterprise Linux 8.2 beta released this week that includes a number of new features and improvements booting is still limited to the root file system volume in this release: we do plan to support multi-volume snapshots in a future RHEL update but there is a system wide change needed before we can enable this functionality. This includes a mechanism to override the system fstab at boot time without modifying the snapshot contents. We have some prototypes that we are evaluating and we plan to start working on the snapshot manager features after the next boom release.

Boom is the first step in a plan to deliver improved bootable snapshot management and rollback capabilities: a white paper was published a couple of years ago that describes the full project - it's still fairly up to date with current work, and it might provide useful information in terms of the direction we are taking for these features. You can find it on GitHub here:

  https://github.com/snapshotmanager/snapshot-boot-docs

The boom project is hosted at:

  https://github.com/snapshotmanager/boom/

Feedback and suggestions on boom and the broader snapshot manager work are welcome, either via bugzilla or the upstream project pages. The snapshot manager and fstab substitution work will be delivered in different components, but I'll keep this open against boom for the time being so that we can keep track of it.
Comment 17 Bryn M. Reeves 2023-04-24 16:01:53 UTC 
I have a prototype for multi-volume snapshots now that is working well in testing. It consists of a new systemd generator that runs in early boot and allows the content of /etc/fstab to be overridden on the kernel command line. This allows booting into a snapshot of the system state including auxiliary mounts such as /var, /home etc.

We are still reviewing the options for including this in the distribution and whether the functionality would be acceptable for systemd upstream but we hope to have more updates soon and will update the bugzilla as this work develops.
Comment 23 RHEL Program Management 2023-09-23 15:53:58 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 24 RHEL Program Management 2023-09-23 15:59:03 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.