18:00:03 <nirik>#startmeeting Fedora Infrastructure Ops Daily Standup Meeting18:00:03 <zodbot> Meeting started Mon May 2 18:00:03 2022 UTC.
18:00:03 <zodbot> This meeting is logged and archived in a public location.
18:00:03 <zodbot> The chair is nirik. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
18:00:03 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:00:03 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting'
18:00:03 <nirik>#chair mboddu nirik mobrien nb18:00:03 <zodbot> Current chairs: mboddu mobrien nb nirik
18:00:03 <nirik>#meetingname fedora_infrastructure_ops_daily_standup_meeting18:00:03 <nirik>#info meeting is 30 minutes MAX. At the end of 30, its stops18:00:03 <nirik>#info agenda is at https://board.net/p/fedora-infra-daily18:00:03 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting'
18:00:04 <nirik>#info reminder: speak up if you want to work on a ticket!18:00:06 <nirik>#topic Tickets needing review18:00:08 <nirik>#info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=118:00:19 <leothecat> .hello leo
18:00:20 <zodbot>leothecat: leo 'Leo Puvilland' <firstname.lastname@example.org>
18:00:31 <aheath1992> .hello aheath1992
18:00:32 <zodbot>aheath1992: aheath1992 'Andrew Heath' <email@example.com>
18:00:42 <nirik> hey leothecat and aheath1992.
18:01:13 <nirik> .ticket 10661
18:01:14 <zodbot>nirik: Issue #10661: Badges not showing up in Fedora Badges - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10661
18:01:21 <nirik> I am going to ask them to file upstream here and close this one.
18:03:42 <nirik> .ticket 10666
18:03:43 <zodbot>nirik: Issue #10666: problems with Kerberized web access - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10666
18:03:47 <nirik> scary ticket number. ;)
18:04:17 <nirik> this is a squirrley one... not sure it's us or copr or a browser bug.
18:04:40 <leothecat> oof
18:04:57 * nirikre-reads18:06:18 <nirik> so, I think this may be solved
18:06:41 <nirik> except I can still see it here.
18:06:58 <nirik> so I guess lets do med/med/ops and I will try and figure out if I am just seeing another issue.
18:07:54 <nirik> .ticket 10669
18:07:57 <zodbot>nirik: Issue #10669: Request for new FAS group: biosboot-sig - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10669
18:08:05 <nirik> low/low/ops and I can do this later
18:08:45 <nirik> .ticket 10670
18:08:46 <zodbot>nirik: Issue #10670: MBS tasks taking too long - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10670
18:08:59 <nirik> may be duplicate of another mbs one. Will try ccing briley on it.
18:10:07 <nirik> .ticket 10670
18:10:08 <zodbot>nirik: Issue #10670: MBS tasks taking too long - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10670
18:10:12 <nirik> oops..
18:10:15 <nirik> .ticket 10671
18:10:16 <zodbot>nirik: Issue #10671: Alert admins of the openshift apps when the pod crashes - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10671
18:10:34 <nirik> I think this is possible with alertmanager... but I am not sure exactly how to do it. needs some research.
18:10:45 <mboddu> Sorry nirik for leaving you again :(
18:11:01 <mboddu> I cant make it today :(
18:11:17 <nirik>mboddu: no worries at all... go...
18:11:44 <nirik> thats it for new infra tickets
18:12:15 <nirik> just some f37 change tickets for releng.
18:12:20 <nirik>#topic Planning / Upcoming work18:12:32 <nirik> Probibly will be a rc request today/tomorrow...
18:13:11 <nirik> I have my tipical pile of backlog to keep me warm.
18:13:16 <nirik>#topic Discussion / AOB18:13:22 <nirik> anything anyone would like to discuss today?
18:13:50 <aheath1992> yep, would like some more info on https://pagure.io/fedora-infrastructure/issue/10509 so I can take care of it
18:15:25 <nirik> sure.
18:15:34 <nirik> basically we had a script before
18:16:06 <nirik> it took a group name and queried our account system for users in that group, then their ssh keys and output all those
18:16:20 <nirik> now we have a new account system, so we need to adjust it.
18:17:05 <nirik> let me find the old one
18:17:25 <nirik> oh yeah: /scripts/auth-keys-from-fas
18:18:24 <nirik> I think it should be able to just use 'getent' and 'groups' and 'id' and leverage ipa on the host...
18:19:18 <aheath1992> this on batcave?
18:19:22 <nirik> yes
18:19:44 <nirik> but I suppose it could instead query fasjson (our new account system api)... but for that it would need an account/auth/keytab
18:21:07 <nirik> the users keys can easily be gotten with
18:21:15 <nirik> sss_ssh_authorizedkeys
18:21:22 <nirik> once you know what users are in the group
18:22:58 <nirik> does that make sense/provide the info?
18:23:43 <aheath1992> for the most part I can ping if i have more questions
18:23:53 <nirik> sure, happy to expand on that.
18:23:57 <nirik> basically it should be:
18:23:59 <nirik> groupname
18:24:18 <nirik> expand via 'getent group groupname' to get users
18:24:41 <nirik> for each user 'sss_ssh_authorizedkeys user'
18:25:06 <nirik> ok, if nothing else will close out in a min her.e
18:26:53 <nirik> Thanks for coming!