UnknownURLScheme raised running distributionmirror-prober script

This also means that some data input validator is probably missing in the distribution mirror registration workflow.

I was thinking the same. we have a validator on the release finder and I suspect we have two implementations, one being broken

The underlying issue here is that the remote site is issuing a redirect to an unsupported URL. I think this case need to log the issue and continue to the next item. This should not be an oops condition since there will always be condintions like outside the control of the the Lp code and the mirror admins. The offending mirror must be disabled or updated.

Does this make it a dup of https://bugs.launchpad.net/launchpad-registry/+bug/680750 ?

I cannot tell. I do not know much about the mirror-prober. I am not an admin so I cannot see logs. I assume that since the mirror-prober has redirect code, there is not bug because there is a redirect, but the redirect destination could be invalid, so problems should be logged, instead of raising an oops.

Bug 680750 looks like the issue a really a 404. I think this condition should be logged as unreachable and the mirror will ultimately be marked as stale.

This bug looks like the issue with an unsupported protocol. I cannot identify the problem mirror its name is not in the oops; we only see the bad redirect.

Setting this back down in case someone else wants to run with it.

The class in question is RedirectAwareProberProtocol; we basically need to modify it to log the issue and move on--there are examples of that in the class.

Fixed in stable r12051 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/12051>.