19:01:18 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 19:01:18 Meeting started Mon Nov 16 19:01:18 2020 UTC. 19:01:18 This meeting is logged and archived in a public location. 19:01:18 The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:01:18 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:01:18 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 19:01:18 #chair mboddu nirik smooge pingou mobrien 19:01:18 #meetingname fedora_infrastructure_ops_daily_standup_meeting 19:01:18 #info meeting is 30 minutes MAX. At the end of 30, its stops 19:01:18 Current chairs: mboddu mobrien nirik pingou smooge 19:01:18 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 19:01:19 #info agenda is at https://board.net/p/fedora-infra-daily 19:01:20 #topic Tickets needing review 19:01:21 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 19:01:34 I am here 19:01:34 here 19:01:44 * mboddu lets smooge mod the tickets :) 19:01:47 ok 19:01:55 I was going to say the same.. but you beat me! 19:02:10 .ticket 9467 19:02:11 nirik: Issue #9467: Staging data grepper shows production messages? - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9467 19:02:33 low/low/ops - this isn't intended, needs investigating. Something is crossing the streams 19:02:46 smooge: hehe :) 19:03:00 rabbitmq or soemthing else? 19:03:08 pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#9467: low-gain, low-trouble, and ops https://pagure.io/fedora-infrastructure/issue/9467 19:03:09 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#9467 https://pagure.io/fedora-infrastructure/issue/9467 19:03:30 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#9467: "Staging data grepper shows production messages?" https://pagure.io/fedora-infrastructure/issue/9467#comment-701736 19:03:32 not sure. Could be the messaging bridge is sending prod/stg ? or ? 19:03:42 .ticket 9468 19:03:48 nirik: Issue #9468: AWS: please allow terminate instances for me and for token, that I have created - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9468 19:04:14 med/med/ops? I suspect this might be related to the instances being created for eks? but not sure, need to dig. 19:04:40 pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#9468: aws, medium-gain, and 2 others https://pagure.io/fedora-infrastructure/issue/9468 19:04:41 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#9468 https://pagure.io/fedora-infrastructure/issue/9468 19:04:42 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#9468: "AWS: please allow terminate instances for me and for token, that I have created" https://pagure.io/fedora-infrastructure/issue/9468#comment-701737 19:05:01 thats all new needs-reviews on infra... how about on releng side? 19:05:22 mboddu, ? 19:05:27 Yes 19:05:42 .releng 9854 19:05:43 mboddu: Issue #9854: retire_packagers.py fails to orphan packages: EINVALIDREQ - releng - Pagure.io - https://pagure.io/releng/issue/9854 19:05:52 This is already fixed 19:06:05 nice 19:06:06 Clsoing the ticket 19:06:36 .releng 9855 19:06:37 mboddu: Issue #9855: [RFE] Pass rawhide modular builds through Bodhi - releng - Pagure.io - https://pagure.io/releng/issue/9855 19:06:55 This needs gating enabled for module builds 19:07:00 I guess this is possible... 19:07:20 Possible, but without gating or with gating? 19:07:56 With gating requires work, without gating mean, moving the build around tags (which seems unnecessary) 19:07:58 well, the hard part is changing the workflow/tagging... 19:08:14 yeah, if we do it we should enable gating, otherwise whats the point? 19:08:21 Yup 19:08:58 I dont know how much of value we get to enable gating on modules for the work we need to do 19:09:15 So, high trouble, med gain, dev+ops? 19:09:20 yeah, I'd put there one... yep. +1 19:09:39 Awesome 19:09:53 .releng 9856 19:09:54 mboddu: Issue #9856: update epel-release-latest - releng - Pagure.io - https://pagure.io/releng/issue/9856 19:10:07 smooge: didn't we have a script that did this? 19:10:07 I am not sure who maintains this package, smooge ? 19:10:14 * nirik says for about the 4th time I think... 19:10:27 it's not a package. it's a link 19:10:51 nirik, dennis had a script that did it for a while 19:11:05 I have had to do this my hand since then 19:11:18 I remember us having this conversation a few times... we always think it was automated, but it's not anymore. ;( 19:11:20 it was pre pungi 19:11:44 basically when we moved to a newer compose the script didn't work 19:11:45 I can automate it, but I dont know what it does 19:11:48 anyhow. fix it manually, and try and find time to make a script? 19:12:03 mboddu: https://dl.fedoraproject.org/pub/epel/ 19:12:17 look there at the 'epel-release-latest-8.noarch.rpm' 19:12:23 Yeah, I see epel-release-latest-.noarch.rpm 19:12:31 it's a link to the package 19:12:47 Right, but where is it getting built and what does it contain? 19:13:02 so, people can put in their scripts or kickstarts: curl https:// ... /epel-release-latest-8.noarch.rpm 19:13:11 basically whenever the package epel-release- gets updated to a new subrelease, 19:13:33 without that, you have to parse the repodata or scrape the web to see that it's epel-release-8-9.noarch.org or 8-7 or whatever 19:13:51 currently I have it as a hardlink to 8/x86_64/Packages/e/epel-release-8-8 19:14:06 Ahhh, okay, now I get it 19:14:09 the reason was that this should still work 19:14:17 you just need to do a yum update afterwords 19:14:46 because a lot of the rpm changes were macros and such versus major ones 19:14:57 this might could be a toddler? 19:15:10 it would need perms tho, so nevermind... 19:15:31 do not give a 2 year old root access to FTP_Fedora 19:15:40 hell don't give me access 19:15:51 what could possibly go wrong? less files == less problems. ;) 19:15:57 but I guess it could add files. ;) 19:16:22 anyhow, lets fix manually for now, and open a low pri ticket to script it? 19:16:37 anyway.. the last fix was that pungi needed to send some sort of trigger on these files 19:16:47 nirik: Maybe the bodhi automated pushes can verify and update the symlinks? 19:16:58 well, we have messages... 19:17:26 mboddu: or updates-sync could update them? 19:17:40 Yeah, that too, but messages seems like an over kill 19:18:06 Anyhow, med,med,dev? 19:18:10 To automate it 19:18:15 I like doing it in updates-sync... just check at the end... is it still pointing to the latest? no, update, yes, finish 19:18:18 Manually fixing it is easy 19:18:23 sure 19:18:30 Okay 19:18:32 Thats all I got 19:19:55 cool. 19:20:06 Any blockers, prs, info, or tickets to discuss? 19:20:13 I am once again... off on friday. 19:20:59 and next week is thanksgiving week in the US... and I am out all week. :) Thursday and Friday are US holidays. 19:21:32 Nice nirik 19:21:57 nirik, mboddu sym links have been updated for 7 and 8 epel 19:22:25 smooge: I am about to ask you whether you are doing it or should I? this time you beat me to it :) 19:22:26 I need to work out when I am taking 12 days of PTO 19:22:34 #info nirik out friday and all next week 19:22:44 smooge: you should! 19:23:28 I will just sleep/play/watch during my PTO 19:24:59 all good things. :) 19:25:06 anyhow, if nothing else will close in a min. 19:27:43 #endmeeting