Mirantis Fuel KVM migration causes DNS to fail

asked 2016-10-28 15:17:22 -0600

ram5391 gravatar image

Has anyone had experience migrating a KVM based Fuel9.0 installation?

I copied the working .qcow2 disk image to the new host, did a virsh dumpxml, and defined the domain on the new host. That part works flawlessly.

Fuel comes up and everything works fine except DNS resolution to nodes, it looks like whatever fuel is using as a DNS server is not working.

nslookup will not resolve node names, it hits (which suggests it has failed to use itself as a lookup)

The new instance does have access to the internet, and can ping the machines on their internal IPs, but I cannot ssh into the nodes with their internal IPs.

What is the service that fuel uses for its DNS to its nodes? That looks like it has been corrupted somehow.

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted

answered 2016-11-02 15:13:34 -0600

ram5391 gravatar image

This ended up being a simple fix, after clearing the Fuel VM's ARP table and restarting the dnsmasq service, the DNS names resolve correctly now.

edit flag offensive delete link more

answered 2016-11-01 06:45:46 -0600

volenbovsky gravatar image

Hi, you need to check /etc/resolv.conf it sounds that you are hitting https://bugs.launchpad.net/fuel/+bug/1503616 (https://bugs.launchpad.net/fuel/+bug/...)

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2016-10-28 15:14:13 -0600

Seen: 116 times

Last updated: Nov 02 '16