Bug 768858 - [ovirt] [vdsm] content of multipath.conf not being preserved and private config being deleted
Summary: [ovirt] [vdsm] content of multipath.conf not being preserved and private conf...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: oVirt
Classification: Retired
Component: vdsm
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.3.4
Assignee: Dan Kenigsberg
QA Contact:
URL:
Whiteboard: storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-19 08:02 UTC by Haim
Modified: 2016-02-10 16:34 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-12 09:36:56 UTC
oVirt Team: Storage

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.