16:03:14 #startmeeting Infrastructure (2021-08-19) 16:03:14 Meeting started Thu Aug 19 16:03:14 2021 UTC. 16:03:14 This meeting is logged and archived in a public location. 16:03:14 The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:03:14 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:03:14 The meeting name has been set to 'infrastructure_(2021-08-19)' 16:03:14 #meetingname infrastructure 16:03:14 The meeting name has been set to 'infrastructure' 16:03:14 #chair nirik siddharthvipul mobrien zlopez pingou bodanel dtometzki jnsamyak computerkid 16:03:15 #info Agenda is at: https://board.net/p/fedora-infra 16:03:15 Current chairs: bodanel computerkid dtometzki jnsamyak mobrien nirik pingou siddharthvipul zlopez 16:03:15 #info About our team: https://docs.fedoraproject.org/en-US/cpe/ 16:03:16 #topic greetings! 16:03:28 .hi 16:03:29 darknao: darknao 'Francois Andrieu' 16:03:34 .hi 16:03:35 lenkaseg: lenkaseg 'Lenka Segura' 16:03:42 .hi 16:03:43 ekidney: Sorry, but you don't exist 16:03:44 hi 16:03:47 .hello jnsamyak 16:03:50 jnsamyak: jnsamyak 'Samyak Jain' 16:03:52 .hello petebuffon 16:03:53 .hi 16:03:53 petebuffon[m]: petebuffon 'Peter Buffon' 16:03:56 pqp[m]: Sorry, but you don't exist 16:04:14 ekidney pqp try `.hello ` 16:04:20 .hello pqp 16:04:21 pqp[m]: pqp 'Patrick Pace' 16:04:22 .hello odra 16:04:24 odra: Sorry, but you don't exist 16:04:28 oh, there we go 16:04:53 #topic New folks introductions 16:04:54 #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves 16:04:54 #info Getting Started Guide: https://fedoraproject.org/wiki/Infrastructure/GettingStarted 16:05:15 any new folks like to introduce themselves? 16:05:39 me 16:06:29 I just started at red hat and I'll be working in fedora projects 16:06:52 hey pmoura. Welcome! 16:07:01 tks 16:07:19 welcome pmoura :) 16:07:24 .hello ekidney 16:07:25 ekidney: Sorry, but you don't exist 16:07:29 hello pmoura! 16:07:31 oh well 16:07:31 welcome pmoura ! 16:08:12 welcome! 16:08:37 welcome pmoura ! 16:09:08 thank you all 16:09:17 Any other new folks today? 16:10:39 #info chair 2021-08-26 - mkonecny 16:10:40 #info chair 2021-09-02 - ? 16:10:54 anyone want to take the 09-02 chair? 16:11:02 #topic Next chair 16:11:03 #info magic eight ball says: 16:14:18 I can chair 9-02 16:14:29 petebuffon[m]: thanks! 16:15:03 :wq 16:15:05 #topic announcements and information 16:15:05 #info CPE Infra&Releng EU-hours team has a Monday through Thursday 30 minute meeting going through tickets at 1030 Europe/paris in #centos-meeting 16:15:05 #info CPE Infra&Releng NA-hours team has a Monday through Thursday 30 minute meeting going through tickets at 1800 UTC in #fedora-meeting-3 16:15:05 #info If your team wants support from the Fedora Program Management Team, file an isssue: https://pagure.io/fedora-pgm/pgm_team/issues?template=support_request 16:15:06 #info Nest with Fedora is over, videos to be posted in sept 16:15:09 sorry 16:15:22 no worries. 16:15:50 any other announcements or info? 16:17:13 #topic Oncall 16:17:13 #info https://fedoraproject.org/wiki/Infrastructure/Oncall 16:17:13 #info darknao is on call for 2021-08-05 to 2021-08-12 16:17:13 #info petebuffon is on call for 2021-08-12 to 2021-08-19 16:17:14 #info ?? is on call for 2021-08-19 to 2021-08-26 16:18:13 anyone want the next oncall? I can take it... 16:18:38 #info Summary of last week: (from current oncall ) 16:19:20 There was a ping over the weekend that was resolved and there was a ping this morning, but the person never got back to me. 16:20:04 cool. 16:20:35 #topic Monitoring discussion [nirik] 16:20:35 #info https://nagios.fedoraproject.org/nagios 16:20:35 #info Go over existing out items and fix 16:21:22 there's not really much different from last week. 16:22:37 So, not sure if we have any learning topic today, or want to look at backlog... 16:22:47 or just call it a quick meeting. 16:24:33 anyone have preferences? 16:24:56 backlog then ? 16:25:06 * nirik has a phone call, just a sec. 16:26:26 ok, back. Sure, we can talk backlog 16:26:40 #topic Fedora Infra backlog refinement 16:26:40 #info Refine oldest tickets on https://pagure.io/fedora-infrastructure/issues 16:26:48 Hi everyone 16:26:58 hey mkonecny 16:27:25 Let's check the oldest tickets by modified date 16:27:44 .ticket 9648 16:27:45 mkonecny: Issue #9648: IAD2: PDU bring up/configuration - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9648 16:28:06 hum, theres older? are you on the first page? 16:28:16 I was going to say... 16:28:19 .ticket 7880 16:28:20 nirik: Issue #7880: email2fas not working in production (fedmsg/datanommer, fedmsg/irc) - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/7880 16:28:31 I have them sorted by modified day 16:29:08 Ok, but we can go with this one 16:29:13 ah, so that one is the one longest since modified? 16:29:19 we can do them both? ;) 16:30:14 9647 is without any reply 16:30:26 *9648 16:30:44 so, this is basically waiting on datacenter/networking people. 16:30:54 we can't do anything about it until they get things setup. 16:31:01 6 months? 16:31:14 I think we can close this actually. 16:31:22 no, I think things were already moved, it's done. 16:31:37 I can ask to make sure tho 16:31:52 It will be nice to have this one closed :-) 16:32:43 The same situation is probably with 9650 16:32:46 .ticket 9650 16:32:47 mkonecny: Issue #9650: IAD2: Power9 hardware repair - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9650 16:33:31 And 9647 16:33:37 .ticket 9647 16:33:38 I have spent so long on that box. 16:33:38 mkonecny: Issue #9647: IAD2: Mustang cleanup work - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9647 16:33:55 I am waiting to hear from adamw that it's now working normally finally. 16:34:59 it's been up 7 days now, so I hope it's working. 16:35:02 16:34:47 up 7 days, 21:13, 1 user, load average: 0.09, 0.07, 0.50 16:35:08 on the mustangs... 16:35:37 I don't know if that was done or not either. I can inquire. 16:36:06 I'll close 9650 and update the other 2 16:36:28 Last response on the mustangs ticket is that this was postponed, because of Red Hat Infra freeze 16:36:37 But this is 6 months old 16:37:32 Thanks nirik 16:37:39 right. But it might also require someone being onsite. 16:37:47 we don't have dedicated employees on site there... 16:38:02 I see 16:38:30 I've asked internally on those... will update when I hear anything. 16:38:37 In this case, we can return to 7880 16:38:45 .ticket 7880 16:38:47 mkonecny: Issue #7880: email2fas not working in production (fedmsg/datanommer, fedmsg/irc) - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/7880 16:39:57 Is this still the case? 16:40:15 I think this was migrated to toddlers 16:41:02 bugzilla2fedmsg was... 16:41:15 not the function tho 16:41:38 but indeed. I think this is fixed. 16:41:54 Aug 01 00:00:39 bugzilla.bug.update -- kevin commented on RHBZ#1985587 'spamd starts before resolv.conf setup, c...' https://bugzilla.redhat.com/show_bug.cgi?id=1985587 16:41:58 Ok, I remember doing some work on pairing mails from bugzilla to FAS 16:42:12 so, it has my account name there correctly, not email that it got from bugzilla 16:42:34 but... this ticket was wider than just bugzilla2fedmsg wasn't it? 16:42:57 Let me quickly go through it 16:43:50 looks like mailman and anitya... 16:43:54 and mailman is working: 16:43:56 Aug 02 23:50:11 mailman.receive -- On the devel list, kevin replied to 'Re: Fedora 35 Change: Autoconf-2.71 (Self-Contained Change proposal)' https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/FG2MWL2EDUENT6BZ4TXICFDKNQFCXFND/ 16:44:55 BTW, for anyone wondering where I am getting these messages, we have two irc channels: #fedora-fedmsg and #fedora-fedmsg-stg that has a bot that just spews all the messages on our message bus to those channels. ;) It's kinda a nice way to search easily (via irc logs) for things 16:45:09 Anitya should too 16:46:10 I think this is still using fedmsg_meta_infrastructure to recognize the user 16:46:38 all of them? 16:47:03 Probably not, because this needs fedmsg to be emitted 16:47:03 we need to move them to new account system, since fas will go away. 16:48:00 In Anitya I moved all the fedmsg_meta methods to fedora_messaging scheme, so everybody should be able to use the methods when consuming messages 16:48:17 This probably needs to be done for plenty of others 16:48:33 well, the problem here isn't fedmsg vs fedora-messaging, but this function using fas right? 16:48:42 But it looks like in the bugzilla case it's working 16:49:27 I'm not sure how exactly the email2fas is working, how it queries the usernames 16:49:40 ah... it was ported to use fasjson 16:49:49 https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/blob/develop/CHANGELOG.rst 16:50:49 so, I think we are ok? 16:51:31 In this case I think we are 16:52:15 so, close? or ask adamw to confirm and close? 16:53:08 Ask adamw first, so we are sure 16:53:30 can do 16:53:56 I'm looking at Anitya and I don't have it in the schema 16:54:30 So it's on consumer to map it to fedora username 16:55:09 datanommer might be doing it? 16:55:29 or... is anitya emitting fedora-messages? 16:55:38 Yes, it is 16:56:03 then the fedbot/datanommer ones are fedmsgs that come thru the messaging-bridges, so possibly it converts them? 16:56:48 Yes, there was a bridge set up to provide the converted messages, but not sure what happens once we decide to kill it 16:57:37 IMHO we shouldn't. 16:57:56 just leave it for any external fedmsg consumers. 16:58:03 Ok 16:58:20 but of course we should convert all our stuff to fedora-messaging... 16:59:48 Yes, but it depends what info services like datagrepper and fedora badges will need to have in the message 17:00:23 If there will be something that every message schema needs to implement or not 17:00:30 sure. 17:00:53 This could a pain to maintain in longer term :-/ 17:01:33 Or we can create some basic scheme that could be inherited by every new message scheme 17:01:53 well, I guess we don't need to keep it forever... 17:02:02 but perhaps a bigger discussion. 17:02:18 we are over time now... 17:02:19 Yes, we should end the meeting now 17:02:23 #topic Open Floor 17:02:32 anything anyone has quickly for open floor? 17:04:01 #endmeeting