Bug 547424

Summary: RFE: multipathd configuration should be checked, not enforced
Product: [Community] oVirt Reporter: Ayal Baron <abaron>
Component: vdsmAssignee: Ayal Baron <abaron>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: abaron, acathrow, amureini, bazulay, iheim, lpeer, Rhev-m-bugs, sgrinber, ykaul
Target Milestone: ---Keywords: FutureFeature, Improvement
Target Release: 3.3.4   
Hardware: All   
OS: Linux   
Whiteboard: storage
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
: 811599 (view as bug list) Environment:
Last Closed: 2013-01-30 17:51:24 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Bug Depends On:    
Bug Blocks: 811599    

Description Ayal Baron 2009-12-14 11:29:49 EST
Description of problem:
Currently we enforce multipath configuration to a specific set of params we determined are necessary, this behavior might cause problems if an existing (compliant) configuration is used.
Current solution is to mark the configuration as private but no further checking is done to make sure that the private configuration complies with rhev's requirements.

What we should do is:
a. upon startup, check configuration (e.g. make sure that use_friendly_names=no) and if the configuration is not ok, either enforce it (add relevant params instead of overriding entire conf) or fail on startup (if private flag is marked)

In case of hybrid servers (run both as hypervisor and additional services) this has to be dealt with.
Comment 2 Itamar Heim 2011-11-29 16:02:52 EST
still relevant?
Comment 3 Ayal Baron 2011-12-10 17:29:51 EST
yes
Comment 4 Itamar Heim 2013-01-30 17:51:24 EST
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.