#6978 Mirrormanager f28 propagation statistics seem wrong
Closed: Fixed 2 years ago Opened 2 years ago by tibbs.

The F28 propagation statistics page at https://admin.fedoraproject.org/mirrormanager/propgation/f28_updates seems to be nonfunctional. There is a page there, but there should be far more hosts and at least some of them should be shown as up to date.

For comparison, the F27 page looks correct: https://admin.fedoraproject.org/mirrormanager/propgation/f27_updates

I suspect that the revised structure of the updates tree in F28 is to blame. there's an extra directory 'Everything' to be traversed before you arrive at the updates which are directly in the 27 updates directory.

I doubt this is urgent, but I assume those statistics pages are kept for a reason so they might as well be functional.

Metadata Update from @kevin:
- Issue assigned to adrian
- Issue priority set to: Waiting on Assignee (was: Needs Review)

2 years ago

Metadata Update from @smooge:
- Issue assigned to smooge (was: adrian)

2 years ago

Problem was in infrastructure script

I added a test for releases after f27

# check propagation for the active branches                                                                                                                                  
for version in `jq -r ".results[$i].version" < ${ACTIVE} | grep -v Rawhide`; do
    if [[ ${version -lt 28 ]]; then
        ${CRAWLER} --propagation --proppath updates/${version}/x86_64/repodata --threads 50 2>&1 | grep SHA256 > ${LOGBASE}/f${version}_updates-propagation.log.$( date +%s \
        ${CRAWLER} --propagation --proppath updates/${version}/Everything/x86_64/repodata --threads 50 2>&1 | grep SHA256 > ${LOGBASE}/f${version}_updates-propagation.log.$\
( date +%s )

Confirmed that this is working now. It looks a bit odd as it doesn't show any hosts in the state "synced -1" or "synced -2" but I am assuming that will work itself out after a few update cycles as the script actually knows what the older repodata looks like.

Yep. Looks working again...


Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.