Bug 2052596

Summary: Names in raid --device and volgroup have to be unique
Product: Red Hat Enterprise Linux 8 Reporter: Daniel Milewski <daniel.milewski>
Component: python-blivetAssignee: Blivet Maintenance Team <blivet-maint-list>
Status: CLOSED WONTFIX QA Contact: Release Test Team <release-test-team>
Severity: low Docs Contact:
Priority: unspecified    
Version: 8.5CC: jstodola, vtrefny
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-09 07:28:25 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:
Attachments:
Description Flags
kickstart none

Description Daniel Milewski 2022-02-09 16:05:03 UTC 
Description of problem:
In RHEL 8 it isn't allowed to use the same name in raid --device and volgroup. It was allowed in RHEL 7 though. I believe there is no such restriction as far as the system is concerned, since it's possible to rename the md device using the same name as LVM VG after installation completes.

How reproducible:
Always.

Steps to Reproduce:
clearpart --all --initlabel --drives=sdb,sda

partition --ondisk=sdb --size=1024 raid.1p1
partition --ondisk=sda --size=1024 raid.2p1
partition --ondisk=sdb --size=1024 raid.1p2
partition --ondisk=sda --size=1024 raid.2p2
partition --ondisk=sdb --grow raid.1p3
partition --ondisk=sda --grow raid.2p3

raid --device=boot-efi --level=1 --fstype=efi /boot/efi raid.1p1 raid.2p1
raid --device=boot --level=1 /boot raid.1p2 raid.2p2
raid --device=system --level=1 pv.system raid.1p3 raid.2p3

volgroup system pv.system

logvol --vgname=system --name=root --size=8192 /
logvol --vgname=system --name=home --size=2048 /home
logvol --vgname=system --name=var --size=2048 /var

Actual results:
name 'system' is already in use

Expected results:
Installation continues.
Comment 1 Jan Stodola 2022-02-11 19:13:20 UTC 
Created attachment 1860661 [details]
kickstart

Reproduced on RHEL-8.6.0-20220210.3 with python3-blivet-3.4.0-8.el8, anaconda-33.16.6.5-1.el8 and the attached kickstart.


from storage.log:
...
DEBUG:blivet:resolved 'system' to 'system' (mdarray)
ERROR:anaconda.modules.storage.partitioning.base_partitioning:Storage configuration has failed: The following problem occurred on line 7 of the kickstart file:

name 'system' is already in use

INFO:anaconda.threading:Thread Failed: AnaTaskThread-CustomPartitioningTask-1 (139673661966080)
ERROR:anaconda.modules.common.task.task:Thread AnaTaskThread-CustomPartitioningTask-1 has failed: Traceback (most recent call last):
  File "/usr/lib64/python3.6/site-packages/pyanaconda/modules/storage/partitioning/custom/custom_partitioning.py", line 828, in _execute_volgroup_data
    pe_size=pesize
  File "/usr/lib/python3.6/site-packages/blivet/threads.py", line 53, in run_with_lock
    return m(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/blivet/blivet.py", line 558, in new_vg
    raise ValueError("name '%s' is already in use" % name)
ValueError: name 'system' is already in use


Reassigning to blivet for review.

I cannot confirm that this worked on RHEL-7, because RHEL-7.9 failed with the attached kickstart as well.
In case of RHEL-7.9, there is a traceback visible to the user, RHEL-8 and RHEL-9 fail with just an error message.
Comment 7 RHEL Program Management 2023-08-09 07:28:25 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.