18:00:46 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:00:46 #chair cverna mboddu nirik smooge 18:00:46 Meeting started Wed Jun 3 18:00:46 2020 UTC. 18:00:46 This meeting is logged and archived in a public location. 18:00:46 The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:46 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:46 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:46 Current chairs: cverna mboddu nirik smooge 18:00:46 #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:00:46 #info meeting is 30 minutes MAX. At the end of 30, its stops 18:00:46 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:47 #info agenda is at https://board.net/p/fedora-infra-daily 18:00:48 #topic Tickets needing review 18:00:48 Nice 18:00:49 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:00:58 who all is around for a standup... 18:01:14 thank you nirik !! 18:01:27 mrcxavier: good luck... 18:02:09 * cverna is around 18:02:29 .ticket 8971 18:02:29 nirik: Issue #8971: Grant bstinson access to create EC2 instances with CentOS Labels - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8971 18:02:40 someone want to modify tickets today? 18:02:52 Hello 18:02:56 I can modify the tickets 18:03:00 for this one, I guess we close now? I agree we need to go over our aws setup in more detail after the dc move. 18:03:27 I'd like to also see about granting mobrien[m] perms so he can help/do some of these tickets 18:04:00 these as in fedora-infra tickets or AWS tickets? 18:04:01 +1 18:04:24 pagure.issue.edit -- mohanboddu edited the close_status and status fields of ticket fedora-infrastructure#8971 https://pagure.io/fedora-infrastructure/issue/8971 18:04:25 pagure.issue.comment.added -- mohanboddu commented on ticket fedora-infrastructure#8971: "Grant bstinson access to create EC2 instances with CentOS Labels" https://pagure.io/fedora-infrastructure/issue/8971#comment-656230 18:05:27 fedora infra tickets asking for aws stuff. ;) 18:05:54 I'd like to setup a git repo and use ansible to configure things too if we can. Then we can do PR's, etc. 18:06:13 .ticket 8972 18:06:14 nirik: Issue #8972: Gitolite authorized_keys is still in place on pagure01 - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8972 18:06:30 I guess close this now? pingou_ moved the one we had and hopefully there will not be one in iad2? 18:06:38 ok out of meeting 18:06:50 Yes we can close this 18:07:14 +1 18:07:27 .ticket 8973 18:07:28 nirik: Issue #8973: unable to add packager to a new project - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8973 18:07:38 pagure.issue.edit -- mohanboddu edited the close_status and status fields of ticket fedora-infrastructure#8972 https://pagure.io/fedora-infrastructure/issue/8972 18:07:39 pagure.issue.comment.added -- mohanboddu commented on ticket fedora-infrastructure#8972: "Gitolite authorized_keys is still in place on pagure01" https://pagure.io/fedora-infrastructure/issue/8972#comment-656232 18:07:40 no idea whats happening there... hopefully pingou_ can debug 18:07:55 * mboddu looking 18:07:56 so, move to waiting on asignee, medium gain, medium trouble groomed? 18:08:03 ack 18:08:20 pagure.issue.tag.added -- mohanboddu tagged ticket fedora-infrastructure#8973: groomed, medium-gain, and medium-trouble https://pagure.io/fedora-infrastructure/issue/8973 18:08:21 pagure.issue.edit -- mohanboddu edited the priority fields of ticket fedora-infrastructure#8973 https://pagure.io/fedora-infrastructure/issue/8973 18:08:31 .ticket 8974 18:08:32 nirik: Issue #8974: New Service - DNS addition request: packager.fedorainfracloud.org - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8974 18:08:48 just needs doing I guess... medium gain, low trouble, waiting on asignee, groomed? 18:08:59 pagure.issue.comment.edited -- astepano edited a comment 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-656217 18:09:11 +1 18:09:14 ack 18:09:33 pagure.issue.tag.added -- mohanboddu tagged ticket fedora-infrastructure#8974: groomed, low-trouble, and medium-gain https://pagure.io/fedora-infrastructure/issue/8974 18:09:34 pagure.issue.edit -- mohanboddu edited the priority fields of ticket fedora-infrastructure#8974 https://pagure.io/fedora-infrastructure/issue/8974 18:10:12 thats it for needs-review I guess? 18:10:22 * mboddu has one 18:10:33 .releng 9492 18:10:34 mboddu: Issue #9492: bodhi some updates are pending for 3 days - releng - Pagure.io - https://pagure.io/releng/issue/9492 18:11:02 cverna: ^ 18:11:16 Dont know whats going on, but I needed to tag them to epel8-testing-candidate to work 18:11:17 might be from the day of doom? 18:11:26 Might be, but why just epel8? 18:11:48 Not sure we need to look at it 18:12:11 Signing for work works ? 18:12:26 I didn't get that ^ 18:12:38 Oh you mean, signing the build works? 18:12:44 I think robosig applies the testing-candidate tag 18:13:08 Nope 18:13:15 So if the update is stuck in pending maybe that's because it is not signed 18:14:17 They are not stuck in pending tag, for some reason bodhi untagged them from testing-candidate tag before it reached testing 18:14:35 They are definitely signed tho 18:14:58 But looking at the dates, they are from the day of doom, so something might have went wrong 18:15:17 might have been trying to do a push then? dunno. 18:15:43 Yeah maybe 18:17:02 We need to look at all the updates that are in pending since a week and we need to fix them 18:17:31 But if they made another update after that, that means we might be over writing the new build with old build, sigh... :( 18:17:43 I guess, just fix whatever comes our way? 18:17:52 I'd fix the ones mentioned... 18:18:07 Okay 18:18:11 but yeah, after that we may have a lot more to deal with next week anyhow. 18:18:20 haha, true 18:18:30 So, low trouble, medium gain, groomed and I will fix them 18:18:32 ? 18:18:40 +1 18:19:01 Done 18:19:03 Thats all 18:19:09 I fixed the others :D 18:19:25 s/others/other new tickets/ 18:19:45 I have a question tho 18:20:13 nirik: odcs releng backend is on f30, can I upgrade it to f31 or should I wait until the move and it will upgraded to 31 or 32? 18:20:31 please wait 18:20:42 Okay 18:20:55 Thats all 18:21:03 nirik: Any dc move update? 18:21:05 that wasn't one that was going to move was it? but we can see if we have some space somewhere. 18:21:22 yes, we moved dl.fedoraproject.org... so people hitting master mirrors now are hitting iad2. 18:21:43 we are working on getting power boxes up (smooge) and I am working on installing builders. 18:21:52 Nice :) 18:22:23 it's not crazy yet, but it will be. ;) 18:22:26 nirik: odcs releng backend is not going to be one of the important boxes that is scheduled to setup on day 1, but it should be brought up eventually. 18:22:53 nirik: Haha, I thought we like crazy :D 18:23:26 anyhow, we are on schedule so far I think... 18:23:44 we move batcave tomorrow... 18:23:54 so everyone be aware you have to login to the new one after tomorrow. 18:23:58 nirik++ smooge++ 18:24:36 thats about all for now that I have 18:24:42 I need to update my ssh config :) 18:24:52 Yeah, same here 18:25:01 Thanks nirik 18:25:30 ^ for the update 18:25:53 oh, I did get a scratch build mostly completed on iad koji... 18:26:03 nirik I can help with any aws tickets you need. Ansible is also a great idea for that. Keep track 18:26:35 mobrien[m]: yeah, I'd really appreciate it, you know this stuff and I have no time. ;( 18:27:11 although I don't htink things were designed for multiple independt people running multiple independent eks clusters from the same account. :( oh well. 18:28:34 I expect that we are pushing the limits on what is expected to be run per account 18:29:26 #endmeeting