Bug 672796

Summary:	Testing of lvm2 needs option for using real /dev
Product:	[Fedora] Fedora	Reporter:	Zdenek Kabelac <zkabelac>
Component:	lvm2	Assignee:	Petr Rockai <prockai>
Status:	CLOSED NEXTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	agk, bmarzins, bmr, dwysocha, heinzm, jonathan, lvm-team, mbroz, msnitzer, prajnoha, prockai
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-02-09 17:59:19 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Zdenek Kabelac 2011-01-26 12:33:27 UTC

Description of problem:

It would be nice to have some way to specify running internal test suite
of lvm2 over the real /dev directory.
Some udev related problem could not be revealed with our current virtual
/dev dir.

maybe something like  

make REAL_DEV=1 check
and symlinking dev to /dev
could be a way - but cleanup routine might need some extra care then.



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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Alasdair Kergon 2011-01-26 23:51:47 UTC

Totally disagree:)

If the problem is udev interaction, use some udev configuration that updates the private /dev area as required.  (Even chroot if necessary)

Comment 2 Zdenek Kabelac 2011-01-27 09:34:33 UTC

As a long term goal, we may probably get some help from udev for this kind of operation - at this moment the only purpose of this would be, to test locally as a developer on a life system the interaction with real /dev and udev - with all related problems like unstable uncontrollable environment.

Comment 3 Peter Rajnoha 2011-01-27 09:59:38 UTC

I don't think people from udev will ever be willing to support something like this (using a customized additional dev dir). So I'm voting for Zdenek's proposal. Its real main purpose is for us to test the changes properly before we do a release. I wouldn't complicate this if that's not really needed... :)

Comment 4 Petr Rockai 2011-02-09 17:59:19 UTC

I think it is reasonable to allow an override here, it is the responsibility of whoever overrides this to something dangerous (like real /dev) to bear the consequences. I have checked in an envvar-based override (like we have with other optional behaviours of the test suite), using LVM_TEST_DEVDIR.