Hey, Sorry for the delay with a reply. Frankly speaking I'm slightly confused now. So I assume you have added `unbound_hosts` to your openstack_user_config.yml? Did you happen to delete /etc/openstack_deploy/openstack_inventory.json file without deleting all containers in advance? As such action will result in Inventory being re-generated from scratch, meaning new container names and IP mappings, so they can overlap as a result. And yes, gluster would totally not like such overlap. But otherwise I'm a bit confused about how/why would records in /etc/hosts overlap. Though frankly speaking I haven't run an unbound scenario here for years now, and potentially it might need some love. And there could be quite valid bug related to unbound as well. Also, I'm not sure that bootstrap-aio.sh is really doing valid things for multi-node deployment. It gets some "reference" for 1-node environments that can be scaled-up, but it also has a couple of opinionated decisions, like making local loopback devices for lvm/storage, and then a bunch of dummy interfaces for networking. So I would suggest leaving aio environment somewhere nearby and then just spawn a multi-node one nearby with providing configuration manually to avoid these opinionated decisions which may strike back at later stages. вт, 26 мар. 2024 г. в 06:59, Tatsuro Makita <tatsuro.makita.bp@nttdata.com>:
additional question:
As shown below, when I run "gluster peer probe" command on repo-container, the corresponding FAILED occurs. I can referenced the hostname" aio1-repo-container-8ee985f4" from /var/log/glusterfs/cmd_history.log. When referencing this aio1-repo-container-8ee985f4 using the nslookup command "172.29.238.62", and when exiting from the container and referencing the IP address from the host (/etc/hosts), the DNS host names(aio1-unbound-container) do not appear to match. This province seems to have a problem with resolvconf? Anyone know what it is?
regards.
---- root@aio1-repo-container-8ee985f4:/# gluster peer probe aio1-repo-container-8ee985f4 peer probe: failed: Probe returned with Transport endpoint is not connected root@aio1-repo-container-8ee985f4:/# root@aio1-repo-container-8ee985f4:/# nslookup aio1_repo_container-8ee985f4 Server: 172.29.238.62 Address: 172.29.238.62#53
** server can't find aio1_repo_container-8ee985f4: NXDOMAIN
root@aio1-repo-container-8ee985f4:/# exit exit # cat /etc/hosts | grep 172.29.238.62 172.29.238.62 aio1-unbound-container-ff4b869c.openstack.local aio1-unbound-container-ff4b869c aio1_unbound_container-ff4b869c