18:00:08 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:00:08 Meeting started Wed Oct 7 18:00:08 2020 UTC. 18:00:08 This meeting is logged and archived in a public location. 18:00:08 The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:08 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:08 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:08 #chair mboddu nirik smooge pingou mobrien 18:00:08 #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:00:08 #info meeting is 30 minutes MAX. At the end of 30, its stops 18:00:08 Current chairs: mboddu mobrien nirik pingou smooge 18:00:08 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:09 #info agenda is at https://board.net/p/fedora-infra-daily 18:00:10 #topic Tickets needing review 18:00:11 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:00:19 anyone around for standup today? 18:00:39 here 18:00:45 i can do the tickets 18:01:08 .ticket 9379 18:01:09 nirik: Issue #9379: Access to the AAA board on Github - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9379 18:01:16 this is actually likely already done by pingou 18:01:24 * mboddu is here 18:01:27 pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#9379: dev, low-gain, and low-trouble https://pagure.io/fedora-infrastructure/issue/9379 18:01:28 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#9379 https://pagure.io/fedora-infrastructure/issue/9379 18:01:28 we could just close it, or... med/med/ops? 18:01:46 ooops I put it in dev 18:01:56 i also said low 18:02:05 should have read closer 18:02:10 well, it seems more opsy, but pingou already did it... so I don't know that I care. ;) 18:02:15 thats it on the infra side. 18:02:21 anything in releng mboddu ? 18:02:49 Nope, already processed in the early morning stand up, nothing new since then (well, one, but I already completed it) 18:03:09 ok, great. 18:03:24 any other tickets folks want to discuss or pr's or anything? 18:03:56 the ssh-fp ticket that was opened/closed reminds me... 18:04:02 so for our old 'groomed' tickets, should I go and put them in ops/dev and remove groomed (while I am waiting for IBM to troubleticket a system) 18:04:07 smooge: did we update sshfp for new batcave/bastions? 18:04:24 for bastion I just copied over the ssh keys from the old one 18:04:25 sure, if you like 18:04:38 so it has the same hostkey? 18:04:57 yep.. too many things were breaking at the time 18:05:20 ok. 18:05:36 I need to fix (after f33) hostkeys anyhow. 18:05:43 it may be time for us to rotate them to something else but I wanted to do it outside of the fire 18:05:54 yes. 18:06:00 batcave I don't remember doing anything 18:06:01 new openssh warns about the ones we have 18:06:05 check_host_cert: certificate signature algorithm ssh-rsa: signature algorithm not supported 18:06:24 but yes, there's a way to add a new one and rotate it in. 18:06:28 we can do that after f33. 18:07:13 ok, if nothing else will close in a min 18:07:18 oh, reminder: 18:07:27 #info nirik is on PTO this friday. 18:07:56 None from me 18:08:07 ok, thanks everyone 18:08:11 #endmeeting