18:01:19 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:01:19 Meeting started Wed Jun 24 18:01:19 2020 UTC. 18:01:19 This meeting is logged and archived in a public location. 18:01:19 The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:01:19 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:01:19 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:01:20 #chair cverna mboddu nirik smooge 18:01:20 #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:01:20 Current chairs: cverna mboddu nirik smooge 18:01:20 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:01:28 #info meeting is 30 minutes MAX. At the end of 30, its stops 18:01:28 #info agenda is at https://board.net/p/fedora-infra-daily 18:01:28 #topic Tickets needing review 18:01:34 .hello mohanboddu 18:01:35 mboddu: mohanboddu 'Mohan Boddu' 18:01:37 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:02:36 mboddu: you want to modify tickets today again? 18:02:43 nirik: Sure 18:02:45 or shall we wait and see if others she up? 18:03:13 I can update 18:03:19 But we could wait as well 18:05:04 .ticket 9067 18:05:05 nirik: Issue #9067: ppc64le builders are having OOM issues - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9067 18:05:17 med/med/groomed/waiting on asignee? 18:05:32 Sure and punt it to post dc move? 18:05:35 I think we need to balance the number of cpus vs memory or something there. 18:05:47 pagure.issue.tag.added -- mohanboddu tagged ticket fedora-infrastructure#9067: groomed, medium-gain, and medium-trouble https://pagure.io/fedora-infrastructure/issue/9067 18:05:48 pagure.issue.edit -- mohanboddu edited the priority fields of ticket fedora-infrastructure#9067 https://pagure.io/fedora-infrastructure/issue/9067 18:05:49 no, it's pretty important, it causes all them to drop out and builds to pile up 18:06:18 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#9075: "lists.fedorahosted.org times out" https://pagure.io/fedora-infrastructure/issue/9075#comment-660834 18:06:25 .ticket 9069 18:06:27 I thought adding more ppc boxes might fix it 18:06:29 nirik: Issue #9069: Change owner of cluster-commits@lists.fedorahosted.org - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9069 18:06:51 we can add more, but then we need to reduce/change the exisring ones... or they will keep doing it. 18:07:25 Okay 18:07:36 ok, 9069 just needs doing. let me do it now and we can be done with it. 18:07:37 Anyway, #9069 18:07:45 +1 18:09:21 pagure.issue.edit -- kevin edited the close_status and status fields of ticket fedora-infrastructure#9069 https://pagure.io/fedora-infrastructure/issue/9069 18:09:22 pagure.issue.comment.added -- kevin commented on ticket fedora-infrastructure#9069: "Change owner of cluster-commits@lists.fedorahosted.org" https://pagure.io/fedora-infrastructure/issue/9069#comment-660843 18:09:34 .ticket 9071 18:09:35 nirik: Issue #9071: Cannot log in to test machines - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9071 18:09:54 this may be something pingou already fixed in fasClient... 18:10:22 but needs investigating 18:10:32 Ask the reporter to try again? 18:10:43 If we think its fixed 18:10:51 no, if it is that thing we need to build it for f33-infra and update it on the machine. 18:11:00 we only built that fix for f32-infra 18:11:06 Ah okay 18:11:13 med/med/groomed/waiting on asignee? 18:11:18 or low/med 18:11:18 +1 18:11:38 pagure.issue.edit -- kevin edited the close_status and status fields of ticket fedora-infrastructure#9072 https://pagure.io/fedora-infrastructure/issue/9072 18:11:39 pagure.issue.comment.added -- kevin commented on ticket fedora-infrastructure#9072: "Enable no_root_squash for fedora_odcs NFS." https://pagure.io/fedora-infrastructure/issue/9072#comment-660848 18:11:39 Going with med/med since we dont know if it will fix it or not 18:11:50 pagure.issue.tag.added -- mohanboddu tagged ticket fedora-infrastructure#9071: groomed, medium-gain, and medium-trouble https://pagure.io/fedora-infrastructure/issue/9071 18:11:51 ok. +1 18:11:52 pagure.issue.edit -- mohanboddu edited the priority fields of ticket fedora-infrastructure#9071 https://pagure.io/fedora-infrastructure/issue/9071 18:12:03 .ticket 9073 18:12:05 nirik: Issue #9073: loopabull is not updating results for PRs - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9073 18:12:19 I think pingou was looking at moving this all to toddlers from loopabull. 18:12:52 not sure if it's that or loopabull, but something started tagging things an hour or so ago 18:12:57 so, I think it's fixed? 18:13:07 +1 18:13:19 Asking him to reopen if he finds the issue again 18:13:23 close -> fixed 18:13:26 +1 18:13:38 .ticket 9074 18:13:39 nirik: Issue #9074: Hardware disk issue in one server (colo-move/IAD2) - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9074 18:14:00 pagure.issue.edit -- mohanboddu edited the close_status and status fields of ticket fedora-infrastructure#9073 https://pagure.io/fedora-infrastructure/issue/9073 18:14:01 pagure.issue.comment.added -- mohanboddu commented on ticket fedora-infrastructure#9073: "loopabull is not updating results for PRs" https://pagure.io/fedora-infrastructure/issue/9073#comment-660851 18:14:09 so I am not sure the status here... I guess we just mark it low/low/groomed/waiting ? 18:14:16 +1 18:14:33 pagure.issue.tag.added -- mohanboddu tagged ticket fedora-infrastructure#9074: groomed, low-gain, and low-trouble https://pagure.io/fedora-infrastructure/issue/9074 18:14:34 pagure.issue.edit -- mohanboddu edited the priority fields of ticket fedora-infrastructure#9074 https://pagure.io/fedora-infrastructure/issue/9074 18:14:39 .ticket 9075 18:14:40 nirik: Issue #9075: lists.fedorahosted.org times out - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9075 18:14:57 smooge seems to have misunderstood this... I think our dns is wrong and needs fixing. :) 18:14:58 Seems fixed? 18:15:09 oh, it is fixed 18:15:21 smooge must have fixed it 18:15:42 I checked eariler and it was wrong. hum 18:15:49 Okay, close -> fixed? 18:16:30 no, it's still not right... looking 18:16:47 Okay 18:18:25 not sure whats going on. 18:18:29 whois info is wrong. 18:18:49 internal is wrong 18:19:54 we dropped the domain? 18:20:01 What? 18:20:58 so yeah, lets not fix it now, but mark the ticket. 18:21:42 we have an old signed zone for it... 18:21:48 but our dns repo dropped it's template. 18:21:59 med,med, groomed? 18:22:03 so, med/med/groomed/waiting? 18:22:12 I can add my findings to the ticket. 18:22:22 pagure.issue.tag.added -- mohanboddu tagged ticket fedora-infrastructure#9075: groomed, medium-gain, and medium-trouble https://pagure.io/fedora-infrastructure/issue/9075 18:22:23 pagure.issue.edit -- mohanboddu edited the priority fields of ticket fedora-infrastructure#9075 https://pagure.io/fedora-infrastructure/issue/9075 18:23:48 pagure.issue.tag.removed -- kevin removed the groomed, medium-gain, and medium-trouble tags from ticket fedora-infrastructure#9075 https://pagure.io/fedora-infrastructure/issue/9075 18:23:50 pagure.issue.edit -- kevin edited the priority fields of ticket fedora-infrastructure#9075 https://pagure.io/fedora-infrastructure/issue/9075 18:23:50 pagure.issue.comment.added -- kevin commented on ticket fedora-infrastructure#9075: "lists.fedorahosted.org times out" https://pagure.io/fedora-infrastructure/issue/9075#comment-660855 18:24:13 argh. 18:24:27 I guess I had loaded it before you changed things and when I added a comment it changed them all back? 18:24:51 can you re-do it? 18:25:21 Sure 18:25:52 pagure.issue.tag.added -- mohanboddu tagged ticket fedora-infrastructure#9075: groomed, medium-gain, and medium-trouble https://pagure.io/fedora-infrastructure/issue/9075 18:25:55 ok, thats it for needs-review (excepting private tickets). 18:26:06 Cool 18:26:09 I have couple 18:26:10 anything on the releng side today? or blockers or other things to discuss? 18:26:24 .releng 9547 18:26:25 mboddu: Issue #9547: Unable to make changes to bugzilla tickets - releng - Pagure.io - https://pagure.io/releng/issue/9547 18:26:51 src.fp.o has the right info, but it seems he is still not able to assign the tickets to himself 18:26:59 Where is the script running? 18:27:05 med,med, groomed? 18:27:09 it's in openshift now I think... 18:27:51 I can look at their account real quick. sure, +1 on that 18:27:52 nirik: Does sysadmin-main gets full access to openshift apps as well? 18:28:45 mboddu: sure. 18:28:52 yeah, they don't have any of the groups set 18:29:10 we can ask pingou to look, since he was working on it last time? 18:29:16 But fasinfo returning he is part of packager group 18:29:27 .fasinfo yanqiyu 18:29:28 mboddu: User: yanqiyu, Name: None, email: yanqiyu01@gmail.com, Creation: 2018-01-23, IRC Nick: None, Timezone: None, Locale: None, GPG key ID: None, Status: active 18:29:31 mboddu: Approved Groups: packager-zh fedorabugs packager cla_fpca cla_done 18:29:51 Okay, will ping pingou 18:30:17 .releng 9546 18:30:21 mboddu: Issue #9546: s390x arch - cpio: read failed - Inappropriate ioctl for device - releng - Pagure.io - https://pagure.io/releng/issue/9546 18:30:27 I guess its fixed now 18:30:43 close->fixed and reopen if the issue still persists? 18:31:02 sure. I am not sure if it was network on mainframe, but things seem back to normal to me. 18:32:10 Thats it, unless if you wanna discuss https://pagure.io/releng/issue/9545? :P 18:32:15 nirik: ^ 18:32:38 RelEng has nothing to do with the change, so its easy for us :) 18:32:59 may need changes to kickstarts or lorax templates or whatever... 18:33:09 but yeah, shouldn't affect too much from releng side 18:33:17 Yeah, which are expected 18:33:19 Anyway 18:33:23 I have a blocker 18:33:27 actually I am not sure at all where the bugzilla permissions thing is now... 18:33:56 On aarch64 and s390x vm's, when I run sudo, it seems either they are timing out or something is happening 18:34:11 Its giivng incorrect password attempt 18:34:25 After being stuck for 5 min 18:34:44 could be we need to adjust firewall rules there. 18:35:12 can you do a infra ticket on it? 18:35:12 Okay 18:35:16 Sure 18:35:24 I was about to ask 18:35:29 Anyway, thats it 18:35:32 from me 18:36:19 cool. I don't have anything more off hand.. 18:36:25 and we are over. ;) 18:36:27 #endmeeting