On Tue, Mar 17, 2020 at 10:40:43AM +0100, Clement Verna wrote:
Hi all,
Let's look at 5 tickets and rate them using the following categories :
* low-trouble, medium-trouble, high-trouble
* low-gain, medium-gain, high-gain
#6441 Monitoring the worker's queue of pagure -
https://pagure.io/fedora-infrastructure/issue/6441
Trouble : ?
Gain : ?
Trouble: Medium
Gain: low
#6801 run hardlink on fedora-secondary -
https://pagure.io/fedora-infrastructure/issue/6801
Trouble : ?
Gain : ?
I think this one needs closing and reopening as a sort of new one.
The problem is that yes, we could hardlink fedora-secondary and
everything would be happy. Until the next updates sync/compose.
Instead of one off running it, we need to look at our updates sync
script and compose sync scripts and make sure they have all the right
arguments to hard link as much as they can...
If we do that:
Trouble: medium
Gain: high
I actually don't see /usr/bin/sar.py in the release-monitoring pods?
Is it distributed? which pod?
Trouble: Low
Gain: Hig (legal +1s)
#7377 SSH keys length can prevent user from login in Fedora infrastructure
-
https://pagure.io/fedora-infrastructure/issue/7377
Trouble : ?
Gain : ?
Trouble: high
Gain: low
I'd say close and make sure we have a issue to make noggin not behave
this way.
#7603 Problem with package-owner-aliases cron script on bastion servers -
https://pagure.io/fedora-infrastructure/issue/7603
Trouble : ?
Gain : ?
Trouble: medium
Gain: high
This sends emails... all the time. Would be great to make it stop
kevin