fedora-infrastructure

#5992 mass-rebuild script constantly updating files in fedora-alt
Closed: Fixed Opened by tibbs.

Closed: Fixed
Reopen Issue

I figured I'd go ahead and file a ticket since dealing with this may be sort of complex. I hope this is more appropriate here rather than rel-eng.

Pretty much once an hour, the following five files update on the mirrors in the fedora-alt module:

    alt/.lock.create-filelist
    alt/fullfilelist
    alt/fullfiletimelist-alt
    alt/mass-rebuild/f26-failures.html
    alt/mass-rebuild/f26-need-rebuild.html

Fortunately this only entails a checkin of the alt module alone now instead of the entire repository (which was making mirrormanager unhappy). But it does bring up a few questions:

1) Does that mass-rebuild script still need to be running?
2) If it does need to be running, is it necessary to put its content into the mirror network? Most mirrors will basically never have the proper content for something that changes once an hour.
3) If not, where should should that content go instead?
4) Does the lock file need to be within the module itself? If so, it should be excluded from the file list.
5) Should I just make those lockfiles mode 600? The updated file list generator would then just ignore it automatically. (Once I actually finish making it do that…)

@ausil and @mohanboddu can you answer items 1, 2, 3 here?

4) I will need to do some digging as I am not sure where that lock file is coming from... the job there has '-l /tmp/update-fullfiletimelist.lock' so it should be in /tmp.

5) mode 600 sounds fine to me.

So thinking about this some, alt is sort of our 'we need to put this somewhere' go to... but as you say, not all of it needs mirroring. Perhaps we need to split alt into 2 trees... one mirrored and one not. Or move all the items that should be mirrored under one of the other trees.

1) yes, people are still or should be still fixing failures.
2 and 3) its not necessary to put on the mirrors, it was a convenient place to put the output as I used to run the process from secondary01 and it was essentially the only place to write the content that was exposed via http, and was a step up from the old generate it on my desktop and scp to fedorapeople.org. given we have other places to run it today, we could find a place to run it and write to somewhere exposed via kojipkgs.fp.o in theory it should actually be updated about every 10 minutes

Yeah, so how about we modify the mass rebuild update script to update something like /mnt/fedora_koji/mass_rebuild/NN/whatever and then it would be behind kojipkgs and should not cause mirroring churn.

If that sounds ok, I can file a releng ticket to update the mass rebuild script for next time and close this one?

that was not an option when we started down this path, it is fine, we need to update the way we run the script not the script itself. it will need some sop updates and some templates to be updated for emails.

This has been moved to https://kojipkgs.fedoraproject.org/mass-rebuild/ now.

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.