Task #2155
closed
Investigate (and maybe fix) copr on-demand repodata generation
Description
copr supports two mechanisms for regenerating repodata in the repos it publishes. The default is to regenerate repodata after every build, and the other is to regenerate repodata on-demand (by hitting a button in the copr UI). During my work with building packages in copr, the automatic repodata generation after a build was working perfectly, but the on-demand regeneration never worked.
The on-demand regeneration feature is necessary, in my opinion, for atomic releases of pulp using copr, with the regeneration of the repodata being the final step to make a release available once all of its component package builds have succeeded. Regenerating the repodata per-build in our GA release repos can result in an inconsistent repo state while builds are in progress, potentially leading to a very broken installation.
- Related to Task #1993: Clean up our distribution packaging by moving it to a dedicated repository and building with copr added
- Status changed from NEW to ASSIGNED
- Assignee set to semyers
For starters, I'm going to double check that this feature really does not work, and make sure it wasn't a case of me just doing stuff wrong. Assuming it really is broken, I've already opened up some lines of communication with fedora folks that work on copr, so I'm going get some guidance from them on how they'd prefer us to proceed. Right now, it's most likely going to be us opening a bugzilla reporting the issue, along with a patch against copr for how to fix it if we can see what's gone wrong.
- Sprint Candidate changed from No to Yes
I'm currently trying to reproduce this in a test copr environment, so that this issue can be filed upstream.
The current plan is to use Pulp itself to distribute Pulp packages with the release of Pulp 3, which will give us the ability to atomically push repo updates, as well as the ability to archive pulp releases.
- Status changed from ASSIGNED to CLOSED - NOTABUG
I did an isolated test on copr and saw that manual repodata generation is working, so my earlier experiences that brought about this ticket appear to be invalid, and there's nothing more to be done (woot).
Also available in: Atom
PDF
.