Bug 2167241

Summary:	VROC created device will be appended a "_0" suffix to device name.
Product:	Red Hat Enterprise Linux 9	Reporter:	Fine Fan <ffan>
Component:	mdadm	Assignee:	XiaoNi <xni>
Status:	CLOSED MIGRATED	QA Contact:	Fine Fan <ffan>
Severity:	medium	Docs Contact:
Priority:	low
Version:	9.2	CC:	ncroxon, xni
Target Milestone:	rc	Keywords:	MigratedToJIRA, Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-23 18:50:43 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 Fine Fan 2023-02-06 02:00:33 UTC

Description of problem:


Version-Release number of selected component (if applicable):
On VROC machine smicro-s110p-01.lab.eng.pek2.redhat.com
mdadm-4.2-8.el9.x86_64
kernel-5.14.0-244.el9.x86_64

How reproducible:


Steps to Reproduce:
1.Boot up the machine , get into the VROC configure page,
2.Create a RAID device ,and change the Name like "F_Raid0_VROC"
3.After the OS installed , login and check the device name under /dev by using below command:
ls /dev/md*


Actual results:
All VROC created device added a "_0" suffix.
/dev/md/F_Raid0_VROC_0

Expected results:
All VROC created device name don't have the "_0" suffix.
like /dev/md/F_Raid0_VROC

Additional info:

Comment 2 Nigel Croxon 2023-02-06 15:06:28 UTC

If a name is untrusted, or if the name is already in use by another
array, then a numeric suffix like "_0", "_1" is appended to create
a unique name for the array.

Comment 6 RHEL Program Management 2023-09-23 18:49:00 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 7 RHEL Program Management 2023-09-23 18:50:43 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.