Incorrect status from mirror prober for

Bug #1986027 reported by Lance Albertson

This bug report will be marked for expiration in 20 days if no further activity occurs. (find out why)

This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself

Bug Description

We received an automation message stating the following (snipped):

This is an automated failure notice that has been generated by the mirror
content checker.

A possible failure has been detected on the following mirror: of Ubuntu


The mirror content checker failed to locate the minimal set of files a
Ubuntu mirror should contain, and so the mirror has been
temporarily removed from the mirror listings. The log file[1] of the
content check should give you more detailed information of what failed.


Following is a snippet of the log file above:
Thu Aug 11 18:53:12 2022: Failed
Thu Aug 11 18:53:12 2022: Failed

However I have verified that all three servers in our rotation do have these files and I see that our mirror hasn't been added back. Can you please let us know if this is a problem with your probing software or provide additional information on why we got flagged?

Revision history for this message
Guruprasad (lgp171188) wrote :

I checked the list of mirrors and can see that OSUOSL mirror has already been added back to the list, if it was removed. The Ubuntu 22.04.1 release happened on the day in question and the mirror prober could have caught the OSUOSL mirror just before it fully sync'ed the new ISOs. Please let us know if you notice similar issues in this future.

Changed in launchpad:
status: New → Incomplete
Revision history for this message
Lance Albertson (lance-osuosl) wrote :

That's what I wondered. I'll let you know if it happens again. Thanks!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers