Mirror check-in failing since Fedora 32 upgrade

Hello,

	Here is the qfm log:

		Mirrormanager checkin for fedora-epel did not appear to
succeed.
> > Log: Err: Doesn't look like we got a good return from
mirrormanager.
> > Log: Err: faultCode 1 faultString <type
'exceptions.KeyError'>:'{'
> > Log: Err: Checkin attempt 3 failed.  Will retry.
> > Log: Making xmlrpc call for fedora-epel
> > /usr/bin/curl --verbose -H "Expect:" -H "Content-Type:
text/xml" --data @mirrormanager-xmlrpc-fedora-epel
https://admin.fedoraproject.org/mirrormanager/xmlrpc

Regards,

[Adrian Reber]

On Sat, May 09, 2020 at 01:13:15PM -0400, fedora(a)dst.ca wrote:
>  Hello,
>  
>  	Here is the qfm log:
>  
>  		Mirrormanager checkin for fedora-epel did not appear to
>  succeed.
>  		>> Log: Err: Doesn't look like we got a good return from
>  mirrormanager.
>  		>> Log: Err: faultCode 1 faultString <type
>  'exceptions.KeyError'>:'{'
>  		>> Log: Err: Checkin attempt 3 failed.  Will retry.
>  		>> Log: Making xmlrpc call for fedora-epel
>  		>> /usr/bin/curl --verbose -H "Expect:" -H "Content-Type:
>  text/xml" --data @mirrormanager-xmlrpc-fedora-epel
>  https://admin.fedoraproject.org/mirrormanager/xmlrpc 
We disabled report_mirror for public mirrors a few weeks ago, because it
produced too many failures for the clients. We often had mirrors which
were correctly disabled by our crawler but then re-enabled by
report_mirror. This was actually the most common error report from users
that mirrors were not up to date and the reason was always
report_mirror. report_mirror only reports which directories are
available on a mirror and assumes that they up to date.

report_mirror is still required for private mirrors as they cannot be
crawled.

In short: you need to disable quick-fedora-mirror's report_mirror
functionality.

		Adrian