mirror probe failed without any explanation in logs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
High
|
Unassigned |
Bug Description
This morning I received an email alert from launchpad indicating my releases mirror at mirror.
https:/
The log file referenced at the time was:
http://
This log file indicates no errors (this is the whole thing):
-
Mon Feb 10 09:23:43 2020: Found all ISO images for series The Bionic Beaver and flavour ubuntu.
Mon Feb 10 09:23:43 2020: Found all ISO images for series The Eoan Ermine and flavour ubuntu.
Mon Feb 10 09:23:43 2020: Found all ISO images for series The Precise Pangolin and flavour ubuntu.
Mon Feb 10 09:23:43 2020: Found all ISO images for series The Trusty Tahr and flavour ubuntu.
Mon Feb 10 09:23:43 2020: Found all ISO images for series The Xenial Xerus and flavour ubuntu.
-
Upon deeper inspection, I was able to determine that my mirror was missing all of the Disco release. Based on discussion with fo0bar and hloeung in #ubuntu-mirrors it appears that Disco was intended to be removed today, though one of the rsync pool servers continued to have it.
Assuming that Disco missing was the fault, there is no indication that's the case. If it was not the fault, there is still no clue as to why the mirror was failed. It's possible the root cause was effectively a race condition due to the timing of the Disco removals.
The bug I'm reporting is that launchpad should certainly provide some indication why the mirror was failed in the log files if it's going to be failed out.
description: | updated |
Changed in launchpad: | |
importance: | Undecided → High |
status: | New → Triaged |
tags: | added: mirror |
tags: | added: lp-registry |