18:00:03 <nirik> #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:00:03 <zodbot> Meeting started Tue May 9 18:00:03 2023 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:07 <nirik> #chair nirik nb smooge phsmoura 18:00:07 <zodbot> Current chairs: nb nirik phsmoura smooge 18:01:14 <nirik> #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:01:14 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:01:14 <nirik> #info meeting is 30 minutes MAX. At the end of 30, its stops 18:01:15 <nirik> #info agenda is at https://board.net/p/fedora-infra-daily 18:01:15 <nirik> #info reminder: speak up if you want to work on a ticket! 18:01:15 <nirik> #topic Tickets needing review 18:01:15 <nirik> #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:01:15 <nirik> ticket 11297 18:01:15 <nirik> * .ticket 11297 18:01:26 <nirik> .ticket 11297 18:01:26 <zodbot> nirik: Issue #11297: Reconfigure pagure.io to only allow new projects from 'contributors' or via request - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/11297 18:01:32 <nirik> stupid bridge. ;) 18:01:41 <nirik> I filed this based on a thread on infra list. med med ops. 18:02:12 <nirik> .ticket 11299 18:02:13 <zodbot> nirik: Issue #11299: problem with bodhi login (especially gssapi) - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/11299 18:02:45 <nirik> needs investigating. 18:02:54 <nirik> med med ops I guess 18:03:27 <nirik> I don't think it's affecting everyone or there would have been a lot more complaints... 18:03:45 <nirik> .ticket 11300 18:03:46 <zodbot> nirik: Issue #11300: https://apps.fedoraproject.org/github2fedmsg/ returns 503 - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/11300 18:04:11 <nirik> this may be due to githubs outage this morning. let me look real quick 18:06:28 <nirik> no, it wasn't. it was the pesky openvpn cert. ;( Somehow it didn't restart the service when a new cert was deployed. 18:07:32 <nirik> on to releng. 18:07:37 <nirik> nothing new. 18:07:49 <nirik> #topic work plans / upcoming tasks 18:07:53 <dherrera> hi! 18:08:00 <nirik> hey Diego H (he/him) 18:08:47 <dherrera> regarding MBS, today (in 2~3 hours) the latest version should land on EPEL8 18:09:02 <nirik> so, for me: I am going to try and upgrade wiki instances... then I am going to look at batcave02 (rhel9) again 18:09:20 <nirik> oh nice. Is it just a update of the rpm? or is there anything more to do? 18:09:53 <dherrera> I asked the maintainer and he told me that it should just need an update 18:10:12 <dherrera> .ticket 11042 18:10:14 <zodbot> dherrera: Issue #11042: MBS 3.8.0 Release - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/11042 18:10:26 <dherrera> he responded in the ticket 18:10:27 <nirik> ok, cool. I do want to do a mass update/reboot outage next week... but we could just do this sooner if we want. 18:10:44 <nirik> ah, ok. 18:11:51 <nirik> did you want to just go ahead and update it? or would you prefer I do it? I guess tomorrow after it's stable? or after tomorrow... 18:12:22 <nirik> oh, and... 18:12:40 <nirik> #info friday is a Red Hat recharge day. Many people will be away... recharging. 18:12:57 <dherrera> I would prefer for you to do it, I don't think we need to rush this 18:13:24 <nirik> ok. we could also just do it next week... 18:14:21 <dherrera> if you could show me how it's done I would appreciate it too :D 18:15:20 <nirik> it's just a yum update or the like... we don't have ansible do updates because we don't want things changing under us... 18:16:09 <dherrera> oh, I see, isn't the current MBS server running on EPEL7 though? 18:16:28 <nirik> could be... I will have to swap all the context back in here. ;) 18:16:56 <nirik> yeah, it is. ok, so we need to redeploy with 8... right. 18:17:27 <smooge> hello 18:18:21 <smooge> nirik: i don't remember if the mbs box were 'fixed by hand' by the MBS team in the past. 18:18:54 <nirik> for that the undefining the current one is somewhat manual, but then you should just be able to adjust ansible vars and run the playbook and it should install and setup everything. Unless there's rhel7isms in there that need fixing. I can look at this later in the week I suppose. 18:18:55 <nirik> hey smooge 18:19:03 <nirik> shouldn't have been... but we can keep the old vm disk/xml around and go back to it if need be. 18:19:17 <smooge> would it be 'deploy new boxes in stg' see if stage build system works, then side-deploy in prod and roll back if not 18:20:23 <smooge> or did we ever have mbs working in staging (sorry its been a while) 18:20:54 <nirik> yes, we have a staging setup... 18:21:44 <smooge> sorry i didn't remember if it was functional or not 18:22:37 <nirik> I have no idea. 18:22:48 <nirik> anyhow, anything else today? 18:23:12 <smooge> not from me. 18:23:26 <nirik> Cool. Thanks everyone! 18:23:28 <nirik> #endmeeting