18:00:32 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:00:32 Meeting started Thu Mar 19 18:00:32 2020 UTC. 18:00:32 This meeting is logged and archived in a public location. 18:00:32 The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:32 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:32 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:32 #chair cverna mboddu nirik smooge 18:00:32 #info meeting is 30 minutes MAX. At the end of 30, its stops 18:00:32 Current chairs: cverna mboddu nirik smooge 18:00:32 #info agenda is at https://board.net/p/fedora-infra-daily 18:00:32 #topic Tickets needing review 18:00:34 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:00:43 .ticket 8759 18:00:44 nirik: Issue #8759: External VM for AAA - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8759 18:01:02 I guess aws is the best place for this one... move to waiting for assignee 18:01:05 my laptop clock seems a bit off 18:01:07 * mboddu is here 18:01:15 * cverna is around but in another meeting 18:01:18 or mine is 18:01:25 nirik: yeah AWS sounds like a good candidate 18:01:34 .ticket 8761 18:01:35 nirik: Issue #8761: Communishift error in a fresh project - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8761 18:01:43 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8759 https://pagure.io/fedora-infrastructure/issue/8759 18:01:57 this looks like kubevirt is causing some problem. I guess I should just remove it since I never got it working right... 18:02:03 but anyhow, move to waiting on asignee... 18:02:16 oh, do we want to rate these on trouble/gain? 18:02:25 pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#8761: communishift https://pagure.io/fedora-infrastructure/issue/8761 18:02:26 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8761 https://pagure.io/fedora-infrastructure/issue/8761 18:02:31 pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#8759: aws https://pagure.io/fedora-infrastructure/issue/8759 18:02:44 yeah we probably do 18:02:57 sure :) 18:03:06 I think 8759 is low trouble high gain 18:03:29 yeah, same here. 18:03:41 8761 is low gain, low trouble? 18:03:50 8761 I don't know the trouble 18:04:10 true, hard to say without knowing more... 18:04:10 pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#8759: high-gain and low-trouble https://pagure.io/fedora-infrastructure/issue/8759 18:04:33 pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#8761: low-gain and medium-trouble https://pagure.io/fedora-infrastructure/issue/8761 18:04:39 ok done 18:04:58 if we don't really know we can just tag it as medium ? 18:05:12 +1 18:05:27 ok, any other tickets we want to discuss? or do we want to go over what we are working on? 18:05:51 how about any others on the top of the queue we want to retag? 18:06:04 8758 18:06:34 .ticket 8758 18:06:35 nirik: Issue #8758: ppcle group file, to be removed? - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8758 18:06:41 pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#8758: low-gain and low-trouble https://pagure.io/fedora-infrastructure/issue/8758 18:06:57 sorry stupid finger hit return in wrong window 18:06:58 that can be just done. that group was old rhel based epel builders. 18:07:49 done 18:08:01 pagure.issue.edit -- smooge edited the close_status and status fields of ticket fedora-infrastructure#8758 https://pagure.io/fedora-infrastructure/issue/8758 18:08:03 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#8758: "ppcle group file, to be removed?" https://pagure.io/fedora-infrastructure/issue/8758#comment-634563 18:08:54 do we want to close 8744? 18:09:05 or keep it open to track ordering new drives? 18:09:32 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#8749: "Setup EPEL8 in stg to use CentOS Devel repo" https://pagure.io/fedora-infrastructure/issue/8749#comment-634565 18:09:59 .ticket 8679 18:10:01 nirik: Issue #8679: Fedora mirrors problems (31/32)? - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8679 18:10:11 I am going to re-enable cloudfront and close this one? 18:10:43 I think we can close it 18:11:09 pagure.issue.edit -- kevin edited the close_status and status fields of ticket fedora-infrastructure#8679 https://pagure.io/fedora-infrastructure/issue/8679 18:11:10 pagure.issue.comment.added -- kevin commented on ticket fedora-infrastructure#8679: "Fedora mirrors problems (31/32)?" https://pagure.io/fedora-infrastructure/issue/8679#comment-634566 18:11:24 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#8744: "New openQA aarch64 worker hosts (openqa-aarch64-0*) bottlenecked by storage" https://pagure.io/fedora-infrastructure/issue/8744#comment-634568 18:12:14 pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#8744: backlog, hardware, and 2 others https://pagure.io/fedora-infrastructure/issue/8744 18:13:10 is 8547 done? or that was still pending 18:13:15 .ticket 8547 18:13:16 nirik: Issue #8547: Rack and install servers for QA - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8547 18:13:29 nirik, it is still pending 18:13:38 I am trying to get these boxes installed 18:13:40 cverna: is 8621 done? 18:13:45 .ticket 8621 18:13:46 nirik: Issue #8621: XML parser error when building two flatpak containers - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8621 18:13:46 but it is 3 steps forward and 4 back 18:14:14 I think it was waiting for a patch upstream, I think we can close it 18:14:43 nirik: I ll close it and add some words there 18:15:38 cverna: ok. patch to koji? 18:15:52 .ticket 8537 18:15:53 nirik: Issue #8537: RFR: deploy coreos-cincinnati to prod cluster - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8537 18:16:07 yeah otaylor opened a PR, If I remember correctly 18:16:13 ^ this one could move forward now that we are out of freeze, should be pretty easy... just removing staging when's from proxies for it. 18:16:22 I don't know if it is merged or not yet 18:16:49 https://pagure.io/koji/pull-request/2040 18:17:24 I guess no. 18:17:35 we could pull it into a infra build if needed... 18:17:54 yeah :( 18:18:00 not even a review 18:18:17 we could ping on it... and note the infra issue? 18:19:07 yeah, I ll update the ticket and see what otaylor and kalev thinks about it 18:19:22 works for me 18:19:24 +1 18:20:25 pagure.issue.comment.added -- kevin commented on ticket fedora-infrastructure#8659: "openshift: allow for users to be able to start a rollout of a deployment" https://pagure.io/fedora-infrastructure/issue/8659#comment-634572 18:20:48 ok, anything else today? 18:21:58 ok, thanks for coming! 18:22:01 #endmeeting