The only thing that changed is that we are also on ipv6. May that be related?
[ssmoogen@localhost ansible (main)]$ host copr-keygen-dev.aws.fedoraproject.org copr-keygen-dev.aws.fedoraproject.org has address 54.225.23.248 copr-keygen-dev.aws.fedoraproject.org has IPv6 address 2600:1f18:8ee:ae00:e904:b814:a97a:a69f [ssmoogen@localhost ansible (main)]$ ping 54.225.23.248 PING 54.225.23.248 (54.225.23.248) 56(84) bytes of data. ^C --- 54.225.23.248 ping statistics --- 5 packets transmitted, 0 received, 100% packet loss, time 4092ms [smooge@batcave01 fedora]$ host copr-keygen.aws.fedoraproject.org copr-keygen.aws.fedoraproject.org has address 54.83.48.73 copr-keygen.aws.fedoraproject.org has IPv6 address 2600:1f18:8ee:ae00:5082:27a6:4de1:62a2 [smooge@batcave01 fedora]$ ping 54.83.48.73 PING 54.83.48.73 (54.83.48.73) 56(84) bytes of data. ^C --- 54.83.48.73 ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 94ms
None of the ipv4 are pingable by outside world
Metadata Update from @smooge: - Issue tagged with: cloud, copr, medium-gain, medium-trouble, monitoring, ops
Metadata Update from @smooge: - Issue priority set to: None (was: Needs Review)
But that was never the case?
I was wrong in my initial analysis. The actual problem is that noc02 can not make ipv6 ssh connections to the hosts
copr-dist-git-dev.aws.fedoraproject.org copr-dist-git-dev.fedorainfracloud.org copr-keygen-dev.aws.fedoraproject.org copr-keygen.aws.fedoraproject.org
It can do so via ipv4.
praiskup found the problem in the aws firewall and fixed.
Metadata Update from @smooge: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Issue status updated to: Open (was: Closed)
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.