Ask OpenStack: Q&A Site for OpenStack Users and Developers - Latest question feedhttps://ask.openstack.org/en/questions/Questions and answers OpenStack CommunityenCopyright of the authors unless stated otherwiseFri, 28 Oct 2016 15:14:13 -0500Mirantis Fuel KVM migration causes DNS to failhttps://ask.openstack.org/en/question/98433/mirantis-fuel-kvm-migration-causes-dns-to-fail/ 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 8.8.8.8 (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.ram5391Fri, 28 Oct 2016 15:14:13 -0500https://ask.openstack.org/en/question/98433/Mirantis fuel 9.0, change of domain name after fuel master node deployment.https://ask.openstack.org/en/question/97841/mirantis-fuel-90-change-of-domain-name-after-fuel-master-node-deployment/ Hi,
At time of deploying fuel 9.0, domain name is not changed to open.tld using fuel menu(Default is domain.tld).
Fuel master node is deployed, before deployment of openstack components on fuel-slave nodes. Wish to change domain name(i.e domain.tld to something looks like open.tld).
changes are done manually to /etc/fuel/astute.yaml as mentioned below
"DNS_DOMAIN": "domain.tld"
"DNS_SEARCH": "domain.tld"
to
"DNS_DOMAIN": "open.tld"
"DNS_SEARCH": "open.tld"
Those changes are not reflected on the created controllers and computes, but it defaults to node-1.domain.tld and node-2.domain.tld.
Is any way to make change domain name after fuel master node deployed????
Please let use know if any possibilities..
Looking forward for reply.
Regards,
AnilAnil karriWed, 12 Oct 2016 04:41:05 -0500https://ask.openstack.org/en/question/97841/dnsmasq stop allocate host name to new hardwarehttps://ask.openstack.org/en/question/66367/dnsmasq-stop-allocate-host-name-to-new-hardware/Hi,
I deployed an openstack cloud with Mirantis Fuel, it works fine. but when I move some hardware to deploy a new openstack cluster, the cobbler docker container allocate ip address to new hardwares, but doesn't allocate host names.
I can find the new hardware in Mirantis Fuel UI, add nodes page. the status of these hardware are "DISCOVERED".
normally when a new hardware is put into the environment, it will be added to the file /etc/dnsmasq.conf, with a line like below:
dhcp-host=net:x86_64,74:c9:9a:4f:ba:c8,node-60.domain,192.168.250.48
and under folder /var/log/remote, there should be a link from ip address to the hostname
lrwxrwxrwx 1 root root 29 May 5 10:38 192.168.250.48 -> node-60.domain
but now when the hardware "discovered" in Mirantis, I can not see any dhcp-host added to dnsmasq.conf file, and a folder with the allocated ip address will be created under /var/log/remote, instead of node-xx.domain.
drwxr-xr-x 3 root root 22 May 6 15:12 192.168.250.49
Is there any way to clean up these hardware discovery history in Fuel and force it to re-discover hardware and allocate host name again?
Thanks to omar-munoz! it's found that cobbler didn't update the discovered node.
[root@fuel ~]# fuel node
id | status | name | cluster | ip | mac | roles | pending_roles | online | group_id
---|----------|--------------------------|---------|----------------|-------------------|---------------------------|---------------|--------|---------
66 | ready | GEP5 Slot 1-5 (node-66) | 16 | 192.168.250.51 | be:57:c6:cc:31:4b | compute | | True | 16
57 | ready | GEP5 Slot 1-11 (node-57) | 16 | 192.168.250.44 | be:bc:bc:06:06:45 | compute | | True | 16
64 | ready | GEP5 Slot 1-19 (node-64) | 16 | 192.168.250.52 | f6:7e:d3:39:6a:43 | compute | | True | 16
77 | discover | Untitled (ce:fe) | None | 192.168.250.50 | 00:13:5e:e9:ce:fe | | | True | None
73 | discover | Untitled (ce:8e) | None | 192.168.250.49 | 00:13:5e:e9:ce:8e | | | True | None
56 | ready | GEP5 Slot 1-13 (node-56) | 16 | 192.168.250.42 | 2a:12:9f:f7:85:45 | compute | | True | 16
78 | discover | Untitled (18:7e) | None | 192.168.250.53 | 00:13:5e:ea:18:7e | | | True | None
[root@fuel ~]# cobbler system list
default
node-55
node-56
node-57
node-58
node-60
node-64
node-66
node-67
PainInNetworkWed, 06 May 2015 10:28:31 -0500https://ask.openstack.org/en/question/66367/