OddBloke

I actually hit this problem, and I fixed it by modifying the routing table associated with my VPC to route ::/0 to an Egress Only Internet Gateway. (Just _adding_ the EIGW to a VPC is not sufficient, because routes aren't configured automatically.)

So I'm guessing that was the issue here.

Out of the box, an instance will come up with IPv4. If you then perform DHCP for IPv6, you should still be able to route to the per-region archive mirrors (which only serve over IPv4 because when they were deployed IPv6 wasn't available).

If you disable IPv4 entirely, then it's true that you won't be able to access the archive mirrors. However, this isn't exactly "out of the box". :)

If you do want to disable IPv4, then at the same time you'll also need to modify your /etc/apt/sources.list to point at archive.ubuntu.com (which does serve over IPv6).

We're looking at how we can best make the "no IPv4" case work with the in-cloud mirrors, and hope to have that resolved soon.

  reasons = [
      "leaves on the track",
      "vandalism",
      "drunk chavs",
      "driver being absolutely shitfaced",
      "solar flares",
      "transport police randomly deciding to stop and search everyone on board",
      "you having an interview",
      "a possible UFO sighting in Belgium",
      "British Rail",
      "lack of coffee at the previous station, so the driver has just nipped off to get some",
      "leaves on the track",
      "flooding within 300km of a railway sleeper"
  ]
  delay_all_trains_by_minutes = 5
  if date.today().day % 2 == 1:
      delay_all_trains_by_minutes = random.randint(0, 30)
  print('All trains will be delayed by {} minute(s) due to {}'.format(
      delay_all_trains_by_minutes, random.choice(reasons))