Using RHEV3 Hypervisors: "RHEV3 Migration failed due to Error: Migration destination has an invalid hostname"

Latest response

I am attempting to carry out a vm Migration from one host to another.

 

I am having a similar problem as described here: https://access.redhat.com/knowledge/ja/node/68634, however I am using RHEV3 hypervisors, which uses a read-only filesystem (and rightly so I might add).

 

The hosts have been configured using Admin configurator on setup from a usb device, and both hosts appear in the browser admin page with fqdn and IPs displayed correctly. As far as I understand it this error does not make sense. 

 

Does someone know something I don't? Any advise appreciated.

Responses

It's a dns resolution problem or conflicting entries in /etc/hosts. Though the rhev-h is readonly, it has a small partition to persist configuration files  and is read-write.

 

Run  the below commands from both hypervisors (source and destination). They should return output that does not conflit.

 

# hostname

# host <fqdn of source>

# host <fqdn of destination>

# host <ip of source>

# host <ip of destination>

 

Then check /etc/hosts of both hypervisor and verify they don't have conflicting entries.

Not sure why RHEV-H got this wrong after the no-probs settup. :-/

 

[root@rhevbox3 ~]# hostname
rhevbox3.domain.com
[root@rhevbox3 ~]# host rhevbox3.domain.com

Host rhevbox3.domain.com not found: 3(NXDOMAIN)
[root@rhevbox3 ~]# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6
[root@rhevbox3 ~]#

 

I tried entering the IP it's supposed to be (192.168.42.42) instead of 127.0.0.1 and restarted networking but no fix. When I try to ping from another machine (the manager) to rhevbox3.domain.com, I get 

 

[root@rhevman ~]# ping rhevbox3.domain.com
ping: unknown host rhevbox3.domain.com

 

I am also unable to ping the IP address for rhevbx3.domain.com

 

[root@rhevman ~]# host 192.168.42.42
Host 42.42.168.192.in-addr.arpa. not found: 3(NXDOMAIN)

 

What do I need to edit to fix this, /etc/hosts? I did that but it didn't work. Should I be looking on the RHEV-Manager?

RHEV relies on your local DNS setup, so you need all the hosts and RHEV-M to be resolvable by both FQDN and IP (have a PTR record). If this is not the case, then this is where you should start looking first.

From the output of the above commands, I can see name resolution is not working properly in your environment.

 

You need to have a DNS server to resolve all the hypervisors and RHEV-M forward and reverse (you can set up RHEV-M itself as a DNS server) or use /etc/hosts of all these servers properly to make name resolution working properly.

Just to update- yes this was down to no PTR for those IP's on the IIS side of things. This was quikly resolved by the Windows guy. Thanks for assist ppl.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.