19:00:04 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 19:00:04 Meeting started Wed Mar 4 19:00:04 2020 UTC. 19:00:04 This meeting is logged and archived in a public location. 19:00:04 The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:04 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:00:04 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 19:00:04 #chair cverna mboddu nirik relrod smooge 19:00:04 #info meeting is 30 minutes MAX. At the end of 30, its stops 19:00:04 #info agenda is at https://board.net/p/fedora-infra-daily 19:00:04 Current chairs: cverna mboddu nirik relrod smooge 19:00:04 #topic Tickets needing review 19:00:05 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 19:00:35 adamw: too many. 19:00:39 * nirik is here. 19:00:59 .ticket 8710 19:01:00 nirik: Issue #8710: Error 503 from cdn.registry.fedoraproject.org - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8710 19:01:12 I plan to work on this when I next get to work and not be meeting. ;) 19:01:26 it's caused by proxy30 we now know 19:01:33 * cverna waives 19:01:48 pagure.issue.assigned.added -- kevin assigned ticket fedora-infrastructure#8710 to kevin https://pagure.io/fedora-infrastructure/issue/8710 19:01:49 pagure.issue.edit -- kevin edited the priority fields of ticket fedora-infrastructure#8710 https://pagure.io/fedora-infrastructure/issue/8710 19:01:57 .ticket 8720 19:01:58 nirik: Issue #8720: fedorahosted mailing list request for systemroles - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8720 19:02:00 heylo 19:02:01 I ll be around for a bit after that meeting nirik, let me know if I can help 19:02:22 pagure.issue.new -- mattia opened a new ticket fedora-infrastructure#8723: "Need an update of python-review_stats against epel7-infra tag" https://pagure.io/fedora-infrastructure/issue/8723 19:02:30 which meeting? this one? 19:02:44 this just needs to be done... 8720... move to waiting on asignee? 19:02:53 pagure.issue.comment.added -- mattia commented on ticket Fedora-Infra/review_stats#2: "Deploy script" https://pagure.io/Fedora-Infra/review_stats/issue/2#comment-630808 19:02:57 nirik: yes this one 19:02:59 it's actually just one command on mailman01 19:03:08 pagure.issue.comment.edited -- mattia edited a comment on ticket Fedora-Infra/review_stats#2: "Deploy script" https://pagure.io/Fedora-Infra/review_stats/issue/2#comment-630808 19:03:18 cverna: I am participating in an interview after this... will be another hour before I can look 19:03:21 * mboddu has an update on 8690 19:03:41 mboddu: hang on, lets get thru the needs review first 19:03:44 nirik: ok then I guess I will be sleeping :P 19:03:57 nirik: Sure, just wanted to bring it up 19:03:59 .ticket 8721 19:04:00 nirik: Issue #8721: Requesting a new compose box - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8721 19:04:09 Oh thats me 19:04:35 we may be able to do this short term, but we have no planned capacity for this during the datacenter move. 19:04:37 smooge said that it has to wait until colo move 19:04:58 ok to close this can't fix for the moment? 19:05:09 or move it to backlog 19:05:14 so yeah, wait until after or we might be able to stand up something now, but it would go away in april or so 19:05:15 pagure.issue.comment.added -- cverna commented on ticket Fedora-Infra/review_stats#2: "Deploy script" https://pagure.io/Fedora-Infra/review_stats/issue/2#comment-630809 19:05:55 I think close can't fix for now 19:05:56 nirik: After f32 release, branched composer doesn't do much, can we take the resources from that a create a new VM? 19:06:12 well it isn't going to be at the new location either? 19:06:20 And after the move, add memory to branched composer? 19:06:27 mboddu: but there isn't going to be a branched composer then? 19:06:38 we are counting on that being off after f32 is out. 19:06:42 during the move we will only have what is needed 19:06:57 Ohhh 19:06:58 for bare minimal viability 19:07:04 Right 19:07:17 there will be a lot less builders a lot less everything... everything will be slower... until we bring things back up 19:07:32 doesn't odcs use koji? 19:07:33 Oh well, then, we will just wait, I guess 19:07:44 "until we bring things back up" eventually 19:07:48 :) 19:07:54 nirik: Nope, it uses odcs-backend01.phx2.fp.o, but it has 4G of memory 19:08:23 pagure.issue.edit -- smooge edited the close_status and status fields of ticket fedora-infrastructure#8721 https://pagure.io/fedora-infrastructure/issue/8721 19:08:24 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#8721: "Requesting a new compose box" https://pagure.io/fedora-infrastructure/issue/8721#comment-630810 19:08:37 ha that;s good we did not try to use odcs for bodhi backend then 19:09:09 well, we may be able to bump it... short term... but yeah 19:09:14 Yeah, I didn't know that it has very less memory or else I would have requested it earlier 19:09:33 .ticket 8722 19:09:34 nirik: Issue #8722: add wikiedit permissions - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8722 19:09:37 nirik: Short term? How long is it? mid apr? 19:09:52 just needs doing I guess. odd that the naming voting is on the wiki? 19:10:19 mboddu: yeah, until we have to ship the first round of things out... 19:10:25 april 11 19:10:32 I can look if there's any memory available there. 19:10:48 nirik: yeah that's not great, if we have to add permissions to everyone wanted to vote 19:11:01 pagure.issue.assigned.added -- smooge assigned ticket fedora-infrastructure#8722 to smooge https://pagure.io/fedora-infrastructure/issue/8722 19:11:02 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8722 https://pagure.io/fedora-infrastructure/issue/8722 19:11:11 nirik: maybe we should flag that with the IOT folks 19:11:21 nirik: So, can we get it until apr? So, that we can test our stuff and then we can hold on til the move completes? 19:11:29 * mboddu is sorry for jumping between tickets 19:11:30 .ticket 8723 19:11:31 nirik: Issue #8723: Need an update of python-review_stats against epel7-infra tag - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8723 19:11:57 Only if there is available memory 19:12:00 mboddu: I can look after my meetings... there may be some available memory on that vm we could use until april yes. 19:12:02 I think this needs to wait for another build ^^ 19:12:16 Thanks nirik 19:12:20 pagure.issue.edit -- kevin edited the priority fields of ticket fedora-infrastructure#8720 https://pagure.io/fedora-infrastructure/issue/8720 19:12:44 pagure.issue.comment.added -- cverna commented on ticket fedora-infrastructure#8723: "Need an update of python-review_stats against epel7-infra tag" https://pagure.io/fedora-infrastructure/issue/8723#comment-630815 19:12:46 pagure.issue.edit -- smooge edited the close_status and status fields of ticket fedora-infrastructure#8722 https://pagure.io/fedora-infrastructure/issue/8722 19:12:47 yeah, waiting on asignee 19:12:47 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#8722: "add wikiedit permissions" https://pagure.io/fedora-infrastructure/issue/8722#comment-630816 19:13:03 ok, thats all needs review. mboddu: you had something? 19:13:10 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8723 https://pagure.io/fedora-infrastructure/issue/8723 19:13:46 Right 19:14:08 .ticket 8657 19:14:09 mboddu: Issue #8657: `fedpkg module-build` fails with "The modulemd libreoffice.yaml is invalid. Please verify the syntax is correct." upon buildopts: arches: [x86_64] - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8657 19:14:29 I forgot in which meeting we discussed this yesterday 19:14:50 But I didnt know what 'ALLOWED_PRIVILEGED_MODULE_NAMES' does, so I had a chat with mprahl 19:14:51 this one 19:15:01 He updated the ticket 19:15:41 ah ha. 19:15:45 great work mboddu... 19:15:46 To make it work, we have to update libmodulemd on mbs servers and apply the patch that mentioned in the ticket 19:16:18 there's also 8445 19:16:22 .ticket 8445 19:16:23 nirik: Issue #8445: Provide newer versions of python-kerberos and python-requests-kerberos in epel7-infra-stg - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8445 19:16:27 that would be good to do at the same time 19:17:05 do you want to take these/this on mboddu ? or cverna ? 19:17:42 nirik: Sure, I can take it 19:17:53 thanks 19:18:02 mboddu++ 19:18:14 ok where are we ? 19:18:20 backlog or releng tickets? 19:18:24 any other tickets to discuss? 19:18:26 pagure.issue.assigned.added -- mohanboddu assigned ticket fedora-infrastructure#8445 to mohanboddu https://pagure.io/fedora-infrastructure/issue/8445 19:18:30 Done 19:18:34 mboddu: thanks! let me know if you get blocked anywhere 19:18:43 Well, assigned to myself, not the work is done :) 19:18:50 Thanks nirik 19:18:53 ha. that was quick! :) 19:19:06 mboddu: did you want to do 8445 also? or smooge, you want to keep that one? 19:19:34 I have taken that as well, but smooge can update it as well 19:20:02 * nirik is just thinking smooge has enough on his plate. ;) 19:20:30 +1 19:20:43 anything else? 19:21:10 nothing here 19:21:14 It just needs to be tagged to epel7-infra-candidate tag, that should do it 19:21:39 * mboddu checks releng 19:21:40 mboddu: I didn't think there were any epel7 builds of those? but there might be now I guess 19:21:41 Give me a min 19:22:06 I thought I gave up 8445 19:22:11 sorry yes please take it 19:22:13 nirik: For krb, there are - https://pagure.io/fedora-infrastructure/issue/8445#comment-615054 19:22:20 For libmodulemd, I dont know 19:22:33 ok, will close out then... see everyone tomorrow, same 🦇 time, same 🦇 station 19:22:44 ah, ok. 19:22:47 .releng 9293 19:22:48 mboddu: Issue #9293: Fix koji/bodhi in staging - releng - Pagure.io - https://pagure.io/releng/issue/9293 19:23:04 ah yeah. 19:23:04 We need a prod to stg sync for this 19:23:15 a sync of koji but also src... 19:23:42 last time for koji we didn't sync the db, just re-branched for stg 19:23:43 I can do the koji sync sometime... lets discuss in ticket how to do the rest? 19:23:50 we also need pdc 19:24:02 yeah, this smells like a playbook perhaps? 19:24:16 How long does koji sync takes? 19:24:16 if we do pdc, we don't really need src, we can take care of the branch creation client side 19:24:18 * nirik will brb 19:24:20 days 19:24:26 Maybe I can create the tags and targets 19:24:35 6 hours ish? I thought 19:24:53 I thought last time it was more than that, happy to be wrong 19:25:21 If 6 hours, better start the sync in the night and it will be done by morning 19:25:30 last time the koji sync playbook was broken that's why it took a long time 19:25:54 migration to new version of koji broken the sql edit the playbook does 19:26:01 broke* 19:26:48 but I would be +1 to take the time to create playbook for that, so that we can sync everything that needs to be done with a playbook 19:26:59 * nirik has to run 19:27:00 so next time it will be easy to do 19:27:14 thanks nirik 19:27:35 Thanks nirik 19:27:54 cverna: Yeah, I am happy to help on the playbook part 19:28:04 having a playbook to do branching, could also solve that question 19:28:14 we would run it stg and prod et voila :) 19:28:20 Maybe we can write the playbook to sync everything, koji, bodhi, pdc, src.fp.o.... 19:28:35 ok I think we are out of high level standup items 19:28:51 I am going to end this and we can continue talking about it afterwords 19:28:56 #endmeeting