[releng] Issue #6786: Kojira cannot handle number of targets it used to
handle month ago.
by Jan Kaluža
jkaluza reported a new issue against the project: `releng` that you are following:
``
Hi,
let me first say something about the current situation and steps we have taken to mitigate it:
1) MBS used to create 2 targets per module build (one classic build target and one -repo target to have the repository with the final tag available in order to allow Copr or taskotron or local builds to get the built RPMs without the need to download all of them from koji directly). This has been done since the very first date of MBS deployment and over the time, the number of targets have grown to 670. In the same time, kojira started having problems generating the repositories and after discussion on #fedora-releng, we have been advised to stop generating so many tags.
2) On Thursday May 4th, we have removed 504 old targets (https://pagure.io/releng/issue/6774) in a hope things will get to normal and we will have a time to fix the MBS to not require any target when building module. I want to note here that we left just 170 targets in Koji - this is number of targets it used to normally handle in the previous months. We did not get to 670 targets over the night and there were whole month in which kojira worked just fine with more than 170 targets. Even with 170 targets left, kojira had the same issues regenerating the repositories.
3) On Thursday May 11, we have decided to remove all modular targets (not only the old ones) (https://pagure.io/releng/issue/6784). That day, we started with no modular target and it used to work well for some time, but after we hit around 40 modular targets, kojira started to be slow again and tasks time-outed on waitrepo. Note that this decision has broken modular builds in Copr and signing of modules in robosignatory which is another complication in Fedora 26 Modular release.
4) On Friday May 12, we have deployed new MBS which creates only single target per module build and which deletes the targets right after the module build finishes, we are now on 22 modular targets and this number will go down to more or less 10 targets in any time (because there are still old builds in progress which created 2 targets instead of 1). After an hour after the removal of targets to get to 22 modular targets, we still see 7 tasks waiting on waitrepo.
Now the question. Why Kojira cannot handle the load it used to handle one month ago? Why it cannot handle even the much lower load currently?
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6786
6 years, 11 months
[releng] Issue #6822: using include statements in pungi-fedora
by Dusty Mabe
dustymabe reported a new issue against the project: `releng` that you are following:
``
My [message](https://lists.fedoraproject.org/archives/list/rel-eng@lists.fedo... to the mailing list didn't get a response so moving to a pagure issue and tagging with meeting keyword.
I've been told recently that we can use include statements within pungi to
include variables/definitions in other files into our current configuration
file we are working on.
Can we start to use this model for our pungi-fedora repo? One example is that
the fedora-atomic.conf file has a bunch of configuration at the top of it that
is very cryptic to know what's relevant to atomic host image/iso creation and what
is not. It would be much better if, for a particular branch, we can have a file
that has most common definitions in it for all pungi configs for that branch. Then
we can make the individual pungi configs much more lightweight and less confusing.
If this is acceptable we can start with the Rawhide branch and when we branch for
future releases this will propagate.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6822
6 years, 11 months