Bug 768858

Summary: [ovirt] [vdsm] content of multipath.conf not being preserved and private config being deleted
Product: [Retired] oVirt Reporter: Haim <hateya>
Component: vdsmAssignee: Dan Kenigsberg <danken>
Status: CLOSED WONTFIX QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: abaron, acathrow, amureini, bazulay, iheim, mgoldboi, yeylon, ykaul
Target Milestone: ---   
Target Release: 3.3.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-12 09:36:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Haim 2011-12-19 08:02:34 UTC
Description of problem:

we should implement mechanism to preserve private multipath config; currently, the only flow vdsm handles, is check revision in the head of multipath.conf, if its lower then the one configured in constants.py, then config being override.

case: 

- user configured multipath.conf with use_friendly_names = yes and added a bunch of aliases 

- vdsm being installed with newer version, and in case multipath revision was changes, config being override. 
- multipath table being rescanned, and devices are no longer used with friendly names

of course, this is just an example to show a real life scenario.

Comment 1 Dan Kenigsberg 2011-12-19 11:42:03 UTC
Put
 # RHEV PRIVATE
in the second line of /etc/multipathd.conf so that Vdsm does not try to out-smart your configuration.

However, it is quite unfortunate that we still trash the default multipath.conf; I hope we could avoid that, somehow.

Comment 2 Itamar Heim 2013-03-12 09:36:56 UTC
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.