18:01:45 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:01:45 Meeting started Thu May 28 18:01:45 2020 UTC. 18:01:45 This meeting is logged and archived in a public location. 18:01:45 The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:01:45 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:01:45 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:01:45 #chair cverna mboddu nirik smooge 18:01:45 Current chairs: cverna mboddu nirik smooge 18:01:45 #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:01:45 #info meeting is 30 minutes MAX. At the end of 30, its stops 18:01:45 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:01:46 #info agenda is at https://board.net/p/fedora-infra-daily 18:01:47 #topic Tickets needing review 18:01:48 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:01:56 pagure.issue.comment.added -- dustymabe commented on ticket fedora-infrastructure#8962: "new robosignatory release/deploy with coreos patches" https://pagure.io/fedora-infrastructure/issue/8962#comment-655161 18:02:20 who all is around? 18:02:45 i am 18:03:08 * dustymabe lurks 18:03:56 ok 18:04:02 .ticket 8955 18:04:03 nirik: Issue #8955: 'fedpkg update' does not work - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8955 18:04:16 I think this is closable now. let me confirm the bodhi pods are still ok 18:04:45 yeah, running 6 hours and I think new submissions are working fine. 18:04:54 we cloud also wait for cverna to confirm 18:04:55 pagure.issue.assigned.added -- smooge assigned ticket fedora-infrastructure#8959 to smooge https://pagure.io/fedora-infrastructure/issue/8959 18:05:58 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#8959: "The s390x Koji builders are extraordinary slow" https://pagure.io/fedora-infrastructure/issue/8959#comment-655163 18:05:58 I guess close it and ask them to reopen if it's still happening? 18:06:07 smooge: you want to modify tickets today? 18:06:12 yep 18:06:24 thanks 18:06:34 .ticket 8958 18:06:35 nirik: Issue #8958: Please issue Access keys (access key ID and secret access key) to AWS - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8958 18:06:54 pagure.issue.edit -- smooge edited the close_status and status fields of ticket fedora-infrastructure#8955 https://pagure.io/fedora-infrastructure/issue/8955 18:06:55 so... I thought I already sent them to someone, let me look. 18:06:55 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#8955: "'fedpkg update' does not work" https://pagure.io/fedora-infrastructure/issue/8955#comment-655164 18:07:47 there was also an email to admin 18:08:00 I need a cheet sheet for all the ci groups. ;) 18:08:41 sorry infrastructure 18:09:12 ok. I issued one to fedora-ci-testing-farm... 18:10:48 pagure.issue.tag.added -- kevin tagged ticket fedora-infrastructure#8958: aws https://pagure.io/fedora-infrastructure/issue/8958 18:10:49 pagure.issue.edit -- kevin edited the priority fields of ticket fedora-infrastructure#8958 https://pagure.io/fedora-infrastructure/issue/8958 18:10:50 pagure.issue.comment.added -- kevin commented on ticket fedora-infrastructure#8958: "Please issue Access keys (access key ID and secret access key) to AWS" https://pagure.io/fedora-infrastructure/issue/8958#comment-655166 18:10:56 added some questions. 18:10:57 * pingou 18:11:03 * mboddu is here 18:11:08 .ticket 8960 18:11:09 nirik: Issue #8960: Adjust playbooks/manual/staging-sync/templates/koji-reset-staging.sql script for phx2->iad2 koji migration - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8960 18:11:29 this just needs doing. medium-effort, high-gain, groomed, waiting on asignee 18:11:46 pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#8958: groomed https://pagure.io/fedora-infrastructure/issue/8958 18:11:47 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8958 https://pagure.io/fedora-infrastructure/issue/8958 18:12:06 .ticket 8961 18:12:07 nirik: Issue #8961: Double mail from myfasname@fedoraproject.org - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8961 18:12:13 pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#8960: groomed, medium-gain, and medium-trouble https://pagure.io/fedora-infrastructure/issue/8960 18:12:14 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8960 https://pagure.io/fedora-infrastructure/issue/8960 18:12:44 this may be some mailman thing if they are double subscribed? propose: low-gain, medium-effort, groomed, waiting on asignee 18:13:57 acks? 18:14:03 wfm 18:14:17 though this one I don't know how to process it (or if I have the rights to) 18:15:08 pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#8961: groomed, low-gain, and medium-trouble https://pagure.io/fedora-infrastructure/issue/8961 18:15:09 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8961 https://pagure.io/fedora-infrastructure/issue/8961 18:15:10 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#8961: "Double mail from myfasname@fedoraproject.org" https://pagure.io/fedora-infrastructure/issue/8961#comment-655174 18:15:11 pingou: process it how? 18:15:25 .ticket 8962 18:15:29 nirik: Issue #8962: new robosignatory release/deploy with coreos patches - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8962 18:15:33 I looked and they only have 1 alias set up.. I have asked for them to give copies of the emails 18:15:33 how to check if it's a mailman thing, I guess it needs access to the mailman admin ui? 18:15:52 pingou: ah, no, probibly just looking at logs and mail headers... 18:15:56 ok 18:16:03 let's wait for the emails then 18:16:21 I would look to see in log01 and see if there are 'dupes' going to his two emails 18:16:26 might be also a good one for mobrien[m] / jednorozec / siddharthvipul if they want something to investigate and learn more about the mail system. 18:16:50 I don't know what their old email was 18:16:57 pagure.issue.comment.added -- stefanberger commented on ticket fedora-infrastructure#8955: "'fedpkg update' does not work" https://pagure.io/fedora-infrastructure/issue/8955#comment-655185 18:17:00 nirik: +1 18:17:53 ok, this next one... If mboddu has time he could test the info I gave him on how to update autosign. ;) we also need abompard to review the patches... 18:18:14 dustymabe: would monday be ok for this? tomorrow is day of learning for many... 18:18:21 so for #43 I've tested in stg back then, so I'm ok with it 18:18:44 #46 looks fine code wise 18:18:48 cool. yeah, 18:19:38 I think this shows the limit of having a single expert on an app 18:19:56 so, move to medium gain, low trouble, waiting on asignee, groomed, and mention to abompard to review and mboddu to see if he can update monday? 18:19:58 nirik: Sure, we could give it a try 18:20:09 pingou: yeah. agreed. 18:20:18 pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#8962: groomed, low-trouble, and medium-gain https://pagure.io/fedora-infrastructure/issue/8962 18:20:19 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8962 https://pagure.io/fedora-infrastructure/issue/8962 18:20:19 Yeah, I can try it on Monday 18:20:33 mboddu: thanks. Hopefully thats soon enough 18:20:40 dusty said he was out this week mostly 18:20:58 so I expect Modnay works better 18:21:04 ok, any releng tickets to discuss? 18:21:15 Yeah, side tag request 18:21:18 the ideal target is next week Tue, but if it lands later it's ok (as long as it's before Jun 16th) 18:21:23 .releng 9485 18:21:24 mboddu: Issue #9485: f33-kde side tag - releng - Pagure.io - https://pagure.io/releng/issue/9485 18:21:47 Its a low trouble, medium gain 18:21:57 I don't think we want to have side tags depending on side tags. 18:22:13 can't we just wait a bit since python is really close to merging? 18:22:31 nirik: But we could add both right? Giving preference to f33-python tag? 18:22:50 Yes, that is my plan if we dont want to use f33-python tag 18:23:21 nirik: read the ticket and log, I will try to investigate on the mail system.. If there is a resource/doc focused on our Infra around mail system, do share :) 18:23:27 Thank you :) 18:23:30 I will ask in the ticket if they wait until python stack is merged back, if not then we can think about it 18:23:44 can wait* 18:23:51 you mean make f33-kde inherit from f33-python which inhertis from f33-build? yes, in theory we could... but what do we do once we merge the python one? 18:24:22 we would have to keep everything, but then it's old next to build, and then chaos and cats and dogs. :) 18:24:41 siddharthvipul: I will work on that with you if that's OK. Get some familiarity with it 18:24:44 I guess you can move the inherit. 18:24:47 nirik: sorry I had stepped away - i'm back now 18:24:48 pagure.issue.comment.added -- sagitter commented on ticket fedora-infrastructure#8961: "Double mail from myfasname@fedoraproject.org" https://pagure.io/fedora-infrastructure/issue/8961#comment-655194 18:24:55 nirik: Yeah, I can see your point 18:25:01 anyhow, I think it would be much easier to just wait... 18:25:12 mobrien[m]: more than okay, I am super happy tbh. Just a warning, I don't know anything around it 18:25:15 nirik: monday would be great! 18:25:27 pagure.issue.comment.added -- astepano commented on ticket fedora-infrastructure#8958: "Please issue Access keys (access key ID and secret access key) to AWS" https://pagure.io/fedora-infrastructure/issue/8958#comment-655196 18:25:31 siddharthvipul / mobrien[m] cool. Might be something in infra docs, but log01.phx2.fedoraproject.org /var/log/merged/mail.log has all our mail logs... 18:25:39 dustymabe: cool. thanks. 18:25:52 dustymabe: Awesome, thanks 18:26:11 mboddu: any other releng ones? 18:26:24 nirik: I worked on the others already :D 18:26:49 cool. 18:26:53 nirik: noted, will explore :) 18:26:55 But, thats it 18:27:05 nirik: who should I talk to on monday? 18:27:21 dustymabe: mboddu will be doing it... he can let you know when it's done. :) 18:27:38 I gave a dc move update in the infra meeting, not sure I need to repeat here. ;) 18:27:51 any other tickets to discuss, blockers, etc? 18:28:01 dustymabe: the person working on the ticket should assign it to themselves 18:28:02 dustymabe: That would be me, I will let you know when I start working on it on Monday 18:28:16 +1 18:28:28 But abompard will be reviewing the changes and I will deploy the changes 18:29:47 pingou: so, thats something I have bene pondering 18:30:04 we have NOT been wanting to assign tickets to people until they are actually working on them 18:30:12 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#8961: "Double mail from myfasname@fedoraproject.org" https://pagure.io/fedora-infrastructure/issue/8961#comment-655197 18:30:37 because it means you have someone who assigns tickets when they hope to someday do them and they aren't really being worked on at all. ;( 18:30:57 but I was pondering a better way to fix that this morning. 18:31:54 running man ticket queue 18:32:11 1) let people assign tickets when they just plan to do it sometime/whatever, 2) add a 'in progress' state to our pagure trackers at least 3) adjust our dashboard to not look at asignee until the state is 'in progress' 18:32:34 but not sure how that will work for bugzilla or github or whatever. 18:32:50 anyhow we are over time. lets close and continue discussing? 18:33:17 * pingou pondering about nirik's idea, +1 to close 18:33:32 #endmeeting