fedora-copr / copr

RPM build system - upstream for https://copr.fedorainfracloud.org/
113 stars 62 forks source link

IPv6-only builders are IMHO misconfigured #2426

Closed FrostyX closed 1 year ago

FrostyX commented 1 year ago

Sorry for abusing the upstream issue tracker for ansible issues of the Fedora Copr instance.

IMHO our IPV6-only builders don't have the network configured properly.

I can see IPv6 addresses on eth0 and eth1

[root@copr-hv-x86-64-01-dev-XXX ~]# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether 52:54:00:XX:XX:XX  txqueuelen 1000  (Ethernet)
        ...

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::2adc:XXX:XXXX:XXXX  prefixlen 64  scopeid 0x20<link>
        inet6 2620:52:3:1:XXXX:XXXX:XXXX:XXXX  prefixlen 128  scopeid 0x0<global>
        ether 52:54:XX:XX:XX:XX  txqueuelen 1000  (Ethernet)
        ...

But there is no default gateway

[root@copr-hv-x86-64-01-dev-00000848-20221201-194425 ~]# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface

There isn't any chance for them to curl anything? Or is it?

FrostyX commented 1 year ago

My bad, I should have used route -6 But I still have issues to curl anything, so keeping open.

FrostyX commented 1 year ago

The issue was caused by a missing DNS configuration. The /etc/resolv.conf was empty. I manually added

# https://developers.google.com/speed/public-dns/docs/using
nameserver 2001:4860:4860::8888
nameserver 2001:4860:4860::8844

and ping and curl works fine. I think we need to add this into our builder playbooks.

xsuchy commented 1 year ago

Isn't this fault of AWS or NetworkManager? This should be set automatically from DHCP6.

kenyon commented 1 year ago

ifconfig and route are deprecated on Linux, and sometimes give confusing or incorrect output. The iproute2 commands are the replacements: https://baturin.org/docs/iproute2/

FrostyX commented 1 year ago

I think this was a duplicate of #2433