Bug 2177839

Summary:	[RFE] boom: support for multi-volumes snapshots
Product:	Red Hat Enterprise Linux 9	Reporter:	Milan P. Gandhi <mgandhi>
Component:	boom-boot	Assignee:	Bryn M. Reeves <bmr>
Status:	CLOSED MIGRATED	QA Contact:	cluster-qe <cluster-qe>
Severity:	low	Docs Contact:
Priority:	medium
Version:	9.2	CC:	agk, amkulkar, bmader, bmr, dkeefe, eddie.rowe, jbrassow, jentrena, jesper.schmidt, jhouston, jwesterl, mcsontos, myllynen, ovasik, pdwyer, rhandlin, rtweed, sandkuma, sujagtap, swachira, vchepkov, yferszt
Target Milestone:	rc	Keywords:	FutureFeature, MigratedToJIRA, Triaged
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:	1794460	Environment:
Last Closed:	2023-09-23 18:50:24 UTC	Type:	Story
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1794460, 2190226
Bug Blocks:

Comment 1 Bryn M. Reeves 2023-04-27 14:38:41 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 3 RHEL Program Management 2023-09-23 15:53:32 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 4 RHEL Program Management 2023-09-23 18:50:24 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.