Description of problem: Updating ovirt node (ovirt-node-ng-image-update-4.3.0-0.1.master.20180708000257) and restart, it deletes the /etc/multipath/conf.d folder and any custom config files within it, causing big problems with partitions that are needed with VDO etc Version-Release number of selected component (if applicable): ovirt-node-ng-image-update-4.3.0-0.1.master.20180708000257 How reproducible: I've tried this on 3 separate servers Steps to Reproduce: 1. Create a custom multipath rule in /etc/multipath/conf.d/sdb.conf, as per the comments in /etc/multipath.conf file 2. Update the server using yum update 3. Restart the server Actual results: The /etc/multipath/conf.d/sdb.conf file and /etc/multipath/conf.d folder no longer exists and multipath has automatically initialized the drives that were blacklisted in the custom configuration file. In my case this caused VDO to crash and have lost the partition data. Expected results: The /etc/multipath/conf.d/sdb.conf file and /etc/multipath/conf.d folder remains in place Additional info:
Also found that this update clears root drive multipath exclusion so all the system partitions now have mutlipath aliases which conflicts with the fstab entries
Recreating /etc/multipath/conf.d/sdb.conf is ignored after update
The update seems to moved the config files into a sub folder, /etc/multipath/conf.d/conf.d/sdb.conf, and then ignores all configuration files. Also deletes any other folder that was created such as /exports which breaks nfs. Seems to have created another root directory structure and conflicting between them both. I used the default/auto-generated LVM structure