Bug 2172573

Summary:	[RFE] ImageBuilder : Support custom swap partitioning in images
Product:	Red Hat Enterprise Linux 8	Reporter:	Vaibhav Bhope <vbhope>
Component:	osbuild-composer	Assignee:	Image Builder team <osbuilders>
Status:	CLOSED MIGRATED	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	high	Docs Contact:
Priority:	medium
Version:	8.7	CC:	amdas, cbesson, myllynen, sbarcomb
Target Milestone:	rc	Keywords:	FutureFeature, MigratedToJIRA
Target Release:	---	Flags:	amdas: needinfo? pm-rhel: mirror+
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-18 13:36:28 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:

Description Vaibhav Bhope 2023-02-22 15:07:40 UTC

What is the nature and description of the request?
Request the ability to customize swap partitions for images built by Composer/OSBuild.

Why does we need this? (List the business requirements here)
The ability to customize swap partitions would help customers create images that better suit their needs.

List any affected packages or components.
osbuild

Comment 4 RHEL Program Management 2023-09-18 13:34:27 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 5 RHEL Program Management 2023-09-18 13:36:28 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.