Bug 1337415

Summary:	disk devices need to be identified by their UUID
Product:	[Red Hat Storage] Red Hat Storage Console	Reporter:	Jeff Applewhite <japplewh>
Component:	core	Assignee:	Shubhendu Tripathi <shtripat>
core sub component:	provisioning	QA Contact:	sds-qe-bugs
Status:	CLOSED WONTFIX	Docs Contact:
Severity:	high
Priority:	unspecified	CC:	nthomas
Version:	2
Target Milestone:	---
Target Release:	3
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-23 04:06:12 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 Jeff Applewhite 2016-05-19 07:22:54 UTC

Description of problem:
There is a risk of a node having multiple disks and losing a disk then another disk will take it's device name. 

Ex. 

/dev/sda
/dev/sdb
/dev/sdc
/dev/sdd

Now /dev/sdc fails. The host reboots. What will happen is that /dev/sdd will now have the identifier /dev/sdc which will cause problems in our handling of the disks.

Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1. Fail a disk. 
2. Roboot the host 
3. watch that the disks will be re-ordered


Actual results:


Expected results:
We should refer to disks by their unique id that can be found at /dev/disk/by-uuid/<uuid> because this does not change on reboot.

Additional info:

Comment 2 Nishanth Thomas 2016-05-24 06:53:19 UTC

*** Bug 1337417 has been marked as a duplicate of this bug. ***

Comment 4 Shubhendu Tripathi 2016-07-15 11:27:15 UTC

Jeff, I tried doing a patch and impact seems to be more and all the flows would be required to be verified as well.

Also, it would be certainly risky at this moment to change something at framework level.

So Nishanth suggested for 3.0..