search

rh-osp-demo / dp-demo

Repo for Dev Preview 2 of RHOSO
4 stars 8 forks source link

Incorrect DNS settings on preprovisioned compute node #18

Open flozanorht opened 2 months ago

flozanorht commented 2 months ago

After having issues with deploying a dataplane, described in https://github.com/rh-osp-demo/dp-demo/issues/15#issuecomment-2096474234

I found that the node was not able to resolve hosts from the Internet, which prevented access to Red Hat YUM repos.

By comparing the DNS configuration of the compute node before and after changes at step

And with the DNS configuration in other hosts in the environment, I got the following working configuration

[root@edpm-compute-0 ~]# cat /etc/resolv.conf
# Generated by NetworkManager
search ctlplane.aio.example.com external.aio.example.com internalapi.aio.example.com storage.aio.example.com tenant.aio.example.com aio.example.com
nameserver 192.168.123.100
nameserver 10.11.5.160

The first server is required for internet, and the second I don't know what it does (no other host in the environment uses it) but I suppose it's required for intra-osp name resolution. I found no other host in the demo environment using the 172.22.0.89 DNS server that I removed. I remember there were issues with more than two nameservers in resolv.conf, else I would just leave the three servers there.

With it, dataplane deployment works, and I didn't need interactive podman logins. :-)

flozanorht commented 2 months ago

Caveat: I didn't finish the demo yet... not sure my data plane actually works. But I got past the deployment step with the DNS change.