There are two network cards available in the host machine and only one used so far. Should I use the remaining interface mapped to the controller (VM) interface? As DNS not resolved I tried to add entries in to /etc/hosts file, but it still has same issue. I highly appreciate if someone help me to fix this. controller-0:~$ cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 192.168.204.1 controller registry.local 192.168.206.2 controller-0-infra 169.254.202.1 pxecontroller 10.10.10.2 oamcontroller 192.168.204.4 controller-platform-nfs 192.168.204.3 controller-1 192.168.204.2 controller-0 192.168.206.3 controller-1-infra 192.168.204.5 controller-nfs 108.177.15.82 k8s.gcr.io 108.177.15.82 gcr.io 3.233.133.41 quay.io 52.55.43.248 docker.io 34.68.230.202 docker.elastic.co controller-0:~$ ping docker.elastic.co PING docker.elastic.co (34.68.230.202) 56(84) bytes of data. 64 bytes from docker.elastic.co (34.68.230.202): icmp_seq=1 ttl=100 time=116 ms 64 bytes from docker.elastic.co (34.68.230.202): icmp_seq=2 ttl=100 time=113 ms 64 bytes from docker.elastic.co (34.68.230.202): icmp_seq=3 ttl=100 time=114 ms --- docker.elastic.co ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 113.932/114.719/116.135/1.076 ms controller-0:~$ traceroute docker.elastic.co traceroute to docker.elastic.co (34.68.230.202), 30 hops max, 60 byte packets 1 10.10.10.1 (10.10.10.1) 1.049 ms 0.934 ms 0.887 ms 2 10.10.10.1 (10.10.10.1) 10012.319 ms !X 10012.286 ms !X 10012.234 ms !X controller-0:~$ On Thu, Jan 28, 2021 at 11:13 AM open infra <openinfradn@gmail.com> wrote:
iptables rules http://paste.openstack.org/show/802058/
I even added few entries in /etc/hosts files and to get the ansible-playbook running, but no luck. http://paste.openstack.org/show/802059/
outpit of netstat http://paste.openstack.org/show/802060/
On Wed, Jan 27, 2021 at 10:07 PM open infra <openinfradn@gmail.com> wrote:
Hi,
I have installed controller-0 and bootstrap was failed at 'Download images and push to local registry'.
I noticed that, dns resolution is failing in the controller but not in the host. controller-0:~$ dig docker.io
; <<>> DiG 9.9.4-RedHat-9.9.4-72.el7 <<>> docker.io ;; global options: +cmd ;; connection timed out; no servers could be reached controller-0:~$ ping quay.io PING quay.io (3.233.133.41) 56(84) bytes of data.
--- quay.io ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2054ms
I can ping from the controller. I have added following entries to iptables but no luck.
sudo iptables -A OUTPUT -p udp -d 8.8.4.4,8.8.8.8 --dport 53 -m state --state NEW,ESTABLISHED -j ACCEPT sudo iptables -A INPUT -p udp -s 8.8.4.4,8.8.8.8 --sport 53 -m state --state ESTABLISHED -j ACCEPT sudo iptables -A OUTPUT -p tcp -d 8.8.4.4,8.8.8.8 --dport 53 -m state --state NEW,ESTABLISHED -j ACCEPT sudo iptables -A INPUT -p tcp -s 8.8.4.4,8.8.8.8 --sport 53 -m state --state ESTABLISHED -j ACCEPT
I am not sure if my network configuration is correct.
controller-0:~$ ip route list default via 10.10.10.1 dev ens3 10.10.10.0/24 dev ens3 proto kernel scope link src 10.10.10.3 169.254.0.0/16 dev eth1000 scope link metric 1002 169.254.0.0/16 dev eth1001 scope link metric 1003 169.254.0.0/16 dev ens3 scope link metric 1004 169.254.0.0/16 dev ens4 scope link metric 1005 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
Following is my local routing configuration and host IP is 192.168.10.100. $ ip route list default via 192.168.172.3 dev eno1 proto static metric 100 10.10.10.0/24 dev stxbr1 proto kernel scope link src 10.10.10.1 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 192.168.10.0/24 dev eno1 proto kernel scope link src 192.168.10.100 metric 100
IP -a results available at http://paste.openstack.org/show/802048/