Description of problem: When a customer uses multipathing to the physical storage and therefore populates /etc/multipath.conf, this configuration is overwritten by vdsmd startup. Version-Release number of selected component (if applicable): RHS 2.0U4 How reproducible: Boot RHS. Configure /etc/multipath.conf and then restart vdsmd. Steps to Reproduce: 1. Boot RHS2.0U4 2. Configure /etc/multipath.conf 3. Restart vdsmd by "service vdsmd restart" Actual results: /etc/multipath.conf is overwritten Expected results: /etc/multipath.conf expected to consistent Additional info: This is discovered during installation at a customers site. As a workaround they have disabled vdsm, but this is needed later on for the RHS-C Gui component. Could engineering make VDSM bypass touching multipathd please ?
The behaviour of vdsm is to configure multipath and other services on startup if they are not matching it needs. Adding below lines as first two lines of multipath.conf prevents vdsm to modify the file. # Do not delete this and below line # RHEV PRIVATE RHS 2.0 comes with a fix bz#928311 which prevents overwrites. Does modified /etc/multipath.conf file have above two lines?
Tried this solution. Works well. The modified /etc/multipath.conf file did not have the required lines. After adding these 2 lines at the top the issue was resolved. This resolves the issue.
I would consider this bug is tracker to add this information into the admin guide of RHS.
Added to doc tracker bug 973888