Bug 1651741

Summary:	[RFE] Set GPT Partition Name via kickstart
Product:	Red Hat Enterprise Linux 8	Reporter:	Pat Riehecky <riehecky>
Component:	python-blivet	Assignee:	Blivet Maintenance Team <blivet-maint-list>
Status:	CLOSED WONTFIX	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	8.0	CC:	csieh, dcantrell, jstodola, misterbonnie, release-test-team-automation
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	8.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1324126	Environment:
Last Closed:	2021-02-01 07:30:37 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Pat Riehecky 2018-11-20 16:39:40 UTC

+++ This bug was initially created as a clone of Bug #1324126 +++

Description of problem:
It would be helpful if in addition to setting the filesystem label from kickstart I could also set the GPT Partition Name.

I'd expect the behavior to be somewhat similar to --asprimary (ignored on non-GPT disks)

Version-Release number of selected component (if applicable): 	pykickstart-1.99.66.6-1.el7


How reproducible:100%


Steps to Reproduce:
1.seek kickstart option to set GPT Partition Name for specific volume
2.
3.

Actual results:
No current option exists

Expected results:
An option to pass at 'part' to set GPT Partition Name.

Additional info:

Comment 1 David Cantrell 2019-02-27 19:57:39 UTC

I'm not sure libparted supports this.  It's not exposed in pyparted.  And I am not sure if blivet exposes a mechanism to do this.  Any of those tools would need to first support this before pykickstart could expose functionality.  Reassigning to blivet for input.

Comment 5 RHEL Program Management 2021-02-01 07:30:37 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.