rhevm-manage-domains gives strange result

Latest response

Hi, after I had managed to install rhevm, I moved on to setting up ipa server for my rhevm. The command kinit admin works all fine. However, when I try this command: rhevm-manage-domains -action=add -domain=demo.redhat.com -user=admin -interactive -provider=IPA, it returns in following:

The domain demo.redhat.com has been added to the engine as an authentication source but no users from that domain have been granted permissions within oVirt Manager.

Users from this domain can be granted permissions from the Web administration interface or by editing the domain using -action=edit and specifying -addPermissions

Failed setting configuration value for option AdUserPassword. Details: Failed setting configuration value for option AdUserPassword.


One more thing, I can access to the portal of rhevm, but I cannot login with as admin with the password I provided when I setup. The password I provided is simple: 123456 so I dont think I type wrong.

Here is my DNS record:

@       IN      SOA     demo.redhat.com. rname.invalid. (
                       2               ; serial 
                       1D              ; refresh
                       1H              ; retry
                       1W              ; expiry
                       3H )            ; minimum
_kerberos._tcp          IN SRV 0 100 88         rhevm.demo.redhat.com.
_kerberos._udp          IN SRV 0 100 88         rhevm.demo.redhat.com.
_ldap._tcp              IN SRV 0 100 389        rhevm.demo.redhat.com.
rhevm                   IN A


I won't be of much value getting IPA to work, but you should be able to login to your RHEVM admin portal as admin.  Until you get IPA working, when logging in to the admin portal, make sure the domain field in your login screen says"internal" and not your IPA domain.  You should see a dropdown list in that box where you can select the domain you want. 

- Greg Scott

I'm sorry because I was too hasty on this matter, I reinstall rhevm with rhevm-cleanup and it works again. I have problem starting IPA because there's an instance which is using port 443. I'm working this out.