[09:41] <gilbahat> Hi dear mirror managers, I am getting a random error of 'unable to locate package jq' on freshly spun AWS instances using archive.ubuntu.com, it's a main package for jammy so this is really unexpected. it also happens for some runs (this happens with packer in our CI) and for some does not.
[09:48] <sajoupa> gilbahat: Hi, in which region is this happening ?
[09:49] <gilbahat> us-east-2
[09:51] <sajoupa> isn't the instance using us-east-2.ec2.archive.ubuntu.com (which should be the default) ?
[09:51] <gilbahat> the apt-get update log shows archive.ubuntu.com. that might be anomalous, let me double-check my packer manifest
[09:54] <gilbahat>   source_ami_filter {
[09:54] <gilbahat>     filters = {
[09:54] <gilbahat>       name                = "ubuntu/images/*ubuntu-jammy-22.04-amd64-server-*"
[09:54] <gilbahat>       root-device-type    = "ebs"
[09:54] <gilbahat>       virtualization-type = "hvm"
[09:54] <gilbahat>     }
[09:54] <gilbahat>     most_recent = true
[09:54] <gilbahat>     owners      = ["099720109477"]
[09:54] <gilbahat>   }
[09:54] <gilbahat> nothing fancy here.
[09:54] <gilbahat> I just ran it again and this time it used the right mirror and indeed there was no error. perhaps the erroneous runs are the ones when an incorrect DNS answer is received.
[11:11] <gilbahat> perhaps the AWS IP database isn't up to date and some regions aren't being picked up as 'in AWS'?
[11:11] <gilbahat> IP ranges
[11:14] <gilbahat> I have an idea - if there's a list of all http mirrors, I could write a simple script to test all of them for missing jq in the Packages.xz file