RHEV-M setup often thinks IPA setup worked when it hasn't
IPA is extremely picky about DNS, hostnames etc - if for example forward and reverse DNS are set correctly but the hostname isn't a FDQN, it will appear to start but not function correctly. In this case, the RHEV installer will think that IPA is working when it isn't.
There are a bunch of other cases where IPA can appear to be working to the RHEV installer when it isn't, but that's the one I can remember right now.
Responses
Look like verification that authentication against the directory is in order here.
P.S. For this specific issue, one of the prerequisites is that the hostname resolvable FQDN (reverse and forward). I'll verify again that the documentation does state this fact.
Can you please provide more info on the entries in /etc/sysconfig/network and /etc/hosts?
I actuallyset up my own DNS and environment last week (You can find it on another thread in this group) and with that, I did not need to modify anything. Just set the hostname during installation of the RHEV Manager host, and configure the name server in /etc/reslov.conf to point to my DNS (Which is standard procedure)