dustymabe reported a new issue against the project: `releng` that you are following: `` * Describe the issue
Today we had an issue where the distrepo yum repos for our coreos tags went away. @mohanboddu regenerated them for us. We're not sure why they went away (this should probably also be investigated), but we'd like the ability to regen them on our own in case this happens again in the future (i.e. we'd like to be able to unblock ourselves in case it happens in a scenario where we need a build and time is critical)
the commands were:
- `koji dist-repo f29-coreos-continuous 429476B4 --allow-missing-signatures` - `koji dist-repo f30-coreos-continuous CFC659B9 --allow-missing-signatures` - `koji dist-repo coreos-pool 429476B4 CFC659B9`
* When do you need this? (YYYY/MM/DD)
would be nice to have it in the nxt week
* When is this no longer needed or useful? (YYYY/MM/DD)
never
* If we cannot complete your request, what is the impact?
we wait until releng can complete our request ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8421
dustymabe added a new comment to an issue you are following: `` cc @jlebon ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8421
dustymabe added a new comment to an issue you are following: ``
Today we had an issue where the distrepo yum repos for our coreos tags went away
One thing that i just remembered is that tag2distrepo was just converted to a koji plugin by @puiterwijk . Maybe a bug there? ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8421
mohanboddu added a new comment to an issue you are following: `` From RelEng meeting on Jun 19th 2019
``` [12:18:32] <mboddu> #info mizdebsk is working on fixing the dist repo generation (probably adding it to kojira) [12:19:15] <mboddu> #info For the mean time, we will renable cron job that generates the dist repos ``` ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8421
The status of the issue: `allow coreos team to regen coreos distrepos` of project: `releng` has been updated to: Closed as Fixed by mohanboddu.
mohanboddu added a new comment to an issue you are following: `` Ignore my previous [comment](https://pagure.io/releng/issue/8421#comment-577039)
To answer the original issue, the repos disappeared. Its because the timeout to cleanup the dist-repos is set for 7 days.
Now, we increased the timeout to 6 months for now, which will be set to indefinite for latest rpm generated dist-repos and for non-latest rpm generated dist-repos we will set a lower retention time. This need a koji fix.
But, you dont need the permissions to generate the repo as its event based and once a build is tagged, it will generate the repo for you. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8421
dustymabe added a new comment to an issue you are following: ``
Ignore my previous comment
done :)
To answer the original issue, the repos disappeared. Its because the timeout to cleanup the dist-repos is set for 7 days. Now, we increased the timeout to 6 months for now, which will be set to indefinite for latest rpm generated dist-repos and for non-latest rpm generated dist-repos we will set a lower retention time. This need a koji fix.
How do we see what it is currently set to for each type of repo? ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8421
The status of the issue: `allow coreos team to regen coreos distrepos` of project: `releng` has been updated to: Open by dustymabe.
dustymabe added a new comment to an issue you are following: `` i'm going to re-open this issue and re-request permissions for this to be given to users who have `coreos-continuous` permissions.
The main reason for the need for this is that there is a [race condition](https://pagure.io/koji/issue/1630) we sometimes need to resolve.
There is a race condition in the tag2distrepo functionality where if we tag many packages at once (let's say 10) then many distrepo tasks (10) get kicked off at the same time. If the 2nd distrepo task that got created is the last one to finish then the resulting distrepo in ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8421
dustymabe added a new comment to an issue you are following: `` in the releng meeting today they decided to grant access for members of `coreos-continuous` to do a `dist-repo`. In a hack session right after the meeting we couldn't figure out how to get the policy set up exactly the way we want it so we settled on a two pronged solutions:
- give dist-repo access to @dustymabe and @jlebon for now - work with koji team to set up `dist-repo` capability on the `coreos-pool` and `fxx-coreos-continuous` tags in the future ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8421
The issue: `allow coreos team to regen coreos distrepos` of project: `releng` has been assigned to `kevin` by dustymabe.
kevin added a new comment to an issue you are following: `` Additionally, we found that there's no 'dist-repo' permission in production right now. I wonder if this could be a missed item in upgrade schemas... ? will investigate. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8421
dustymabe added a new comment to an issue you are following: `` @kevin can we work with the koji team this week to figure this one out? ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8421
dustymabe added a new comment to an issue you are following: `` Can someone run this for me today since I still can't?
``` koji dist-repo --non-latest coreos-pool 429476b4 cfc659b9 3c3359c4 12c944d0 ``` ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8421
dustymabe added a new comment to an issue you are following: ``
Can someone run this for me today since I still can't?
@smooge ran this for me (thanks @smooge). Maybe we can get the rest of this ticket sorted out before it happens the next time. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8421
kevin added a new comment to an issue you are following: `` I did file a koji ticket on the missing perm:
https://pagure.io/koji/issue/1637
``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8421
rel-eng@lists.fedoraproject.org