If there is empty /etc/multipath.conf file is present on the node then multipathd gets activated and running identifying secondary devices as mpath devices which is not expected. 

OCP 4.x

Always

1. Create empty /etc/multipath.conf file and try to reboot the node. 
2.
3.

Multipathd gets activated and running with empty /etc/multipath.conf file.

Multipathd should not get activated and running with empty /etc/multipath.conf file.

This behavior was observed with one of the customer where they had Dell vendor daemonset pod having hostpath configuration with type FileOrCreate. So, this FileOrCreate type will create the empty file if the file is not present. In cu scenario this file was /etc/multipath.conf. So, it got created and due to which on next reboot multipathd got activated and running identifying secondary devices as mpath devices which created huge production issue as secondary devices mounts got failed and corresponding pods did not start.