This is a problem because the values are often written into service configuration files. When they change, services get notified and restart.
We should restore the previous fqdn_rand behavior of calculating its seed value using MD5 when running on a non-FIPS enabled master. FIPS enabled masters should continue using SHA256.
fqdn_rand uses SHA256 to compute seed/rand when running on FIPS enabled hosts which is a change from using MD5 on non-fips enabled hosts. So a given host will yield different fqdn_rand values when in fips mode and when not in fips mode.