Description of problem:


Version-Release number of selected component (if applicable):  002-13.4 and 003-4(at least)


How reproducible: 100%


Steps to Reproduce:

1. Create /etc/mdadm.conf and /etc/mdadm/mdadm.conf differently.
2. Run dracut to create an initramfs.
3. Try to boot - the /etc/mdadm/mdadm.conf file will be used, even though mdadm uses /etc/mdadm.conf and you would think that dracut would also.
  
Actual results:

The /etc/mdadm/mdadm.conf file will be used, although this is unexpected, because mdadm itself as released in FC11 and FC12 uses /etc/mdadm.conf.

Expected results:

Should use /etc/mdadm.conf, or at least warn the user that it may be doing something unexpected.

Additional info:

This is especially an issue with the FC11 to FC12 transition because FC12 enumerates SCSI and SATA drives in the opposite order (FC11=SCSI before SATA; FC12=SATA before SCSI, at least in my system). The point being that the mdadm.conf has to be exactly correct or mdadm will fail. In my case, /etc/mdadm/mdadm.conf referred to /dev/sda, /dev/sdb whereas /etc/mdadm.conf had similar information but using UUIDs instead of device names. No difference until FC12 enumerated backwards. Then, the system drive was no longer a raid on /dev/sda and /dev/sdb but on /dev/sdi and /dev/sdj. It was not clear until I did some debugging that dracut was using the wrong mdadm.conf file. 

NOTE: The mdadm command uses /etc/mdadm.conf. I can put bad data in /etc/mdadm/mdadm.conf all day long and mdadm is unaffected. Not so dracut.