Comment 10 for bug 1983718

Hello,

While checking why we added 127.0.0.1 in resolv.conf - we came across the below Upstream bug and patch which suggests using local unbound service.

~~~
Bug: https://bugs.launchpad.net/tripleo/+bug/1711262 (comment#3)
Patch: https://opendev.org/openstack/tripleo-ci/commit/5d612318c95b9b3ff78e66e91d5c225274cb8b09
~~~

One observation I want to add is that unbound service is not installed/running on the node in RDO Centos9 and it's present in the Upstream C9 node/rdo Centos8 node.

Upstream Node:-

https://b31788cff7a995401de2-45518917cf8baf33fe991d0324b9a061.ssl.cf1.rackcdn.com/846947/2/gate/tripleo-ci-centos-9-scenario001-standalone/4cac8c0/logs/undercloud/var/log/extra/package-list-installed.txt

~~~
unbound.x86_64 1.16.0-3.el9 @appstream
unbound-libs.x86_64 1.16.0-3.el9 @appstream
~~~

https://b31788cff7a995401de2-45518917cf8baf33fe991d0324b9a061.ssl.cf1.rackcdn.com/846947/2/gate/tripleo-ci-centos-9-scenario001-standalone/4cac8c0/logs/undercloud/var/log/extra/services.txt
~~~
unbound.service loaded active running Unbound recursive Domain Name Server
~~~

RDO node:-

https://logserver.rdoproject.org/openstack-periodic-integration-stable1/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-centos-9-scenario001-standalone-wallaby/1c1c2d4/logs/undercloud/var/log/extra/package-list-installed.txt.gz
~~~
unbound-libs.x86_64 1.16.0-3.el9 @appstream
~~~

In rdo node, unbound.service is not present.

https://logserver.rdoproject.org/openstack-periodic-integration-stable1/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-centos-9-scenario001-standalone-wallaby/1c1c2d4/logs/undercloud/var/log/extra/services.txt.gz

In Centos8 wallaby, we have unbound installed, and we did not see the same issue in Centos8 node.
https://logserver.rdoproject.org/openstack-periodic-integration-stable1-cs8/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-centos-8-standalone-wallaby/8cb7e4a/logs/undercloud/etc/unbound/

On the affected node installing unbound and starting unbound service solved the issue.

[root@standalone conf.d]# time host www.google.com
www.google.com has address 142.251.41.68
www.google.com has IPv6 address 2607:f8b0:400b:807::2004

real 0m3.046s
user 0m0.013s
sys 0m0.015s

[root@standalone conf.d]# dnf install unbound
.
.
Installed:
  unbound-1.16.2-2.el9.x86_64

[root@standalone conf.d]# systemctl start unbound.service
[root@standalone conf.d]# time host www.google.com
www.google.com has address 142.251.41.68
www.google.com has IPv6 address 2607:f8b0:400b:804::2004

real 0m0.133s
user 0m0.007s
sys 0m0.014s

Next step: Investigate why rdo Centos9 nodepool image doesn't have unbound installed and add unbound service to be consistent with upstream.